When a resident or guest believes a citation, boot, or tow was issued in error, they can file a dispute directly through ParkingPass. As a property manager, you're responsible for reviewing each dispute, deciding the outcome, and responding before the deadline.
This article walks through the full dispute lifecycle: how disputes are filed, where to find them, what each status means, how to respond, and what happens if a dispute escalates to Pending Adjudication. For a quick decision flowchart, see How to Handle Tow or Citation Disputes.
How a Dispute Starts
A dispute begins the moment a resident or guest takes action on an enforcement record:
A citation is issued (warning, ticket, boot, or tow).
The resident or guest opens the violation from their account.
They click Dispute and submit a written explanation along with any supporting evidence (photos, lease docs, registration, etc.).
The dispute is added to your property's Violation Payment Dispute Report and shows up on your dashboard's Citation Disputes panel with an Action Required indicator.
Where to Find Disputes
From the Dashboard
Your dashboard's Citation Disputes panel shows three counts:
Expiring Soon — Disputes approaching the response deadline.
Active Disputes — Disputes currently in your queue awaiting a decision.
Pending Adjudication — Disputes that have been escalated for adjudication review.
Click any count to open the Violation Payment Dispute Report filtered to that status. See Reading Your Dashboard for a walkthrough of the full dashboard.
From the Reports Menu
From the left sidebar, open Reports.
Select Citation Dispute Report (or Violation Payment Dispute Report).
Use the filters at the top to narrow by Dispute Status and Date Range.
You can also reach a specific dispute directly from any resident's profile by opening the violation record they're disputing.
Understanding the Report Columns
The Violation Payment Dispute Report displays the following information for each dispute:
Dispute Date — The date the resident or guest submitted the dispute.
Age — Days since the dispute was filed. A higher number means the response deadline is closer.
Ticket — The violation ticket number.
Tag — The license plate of the disputed vehicle.
Vehicle Info — Make, model, and color.
Property — The property where the violation occurred (relevant for multi-property accounts).
Dispute Status — Current state of the dispute (see Statuses below).
Amount — The amount in dispute.
Details — Click to open the full dispute record and read the resident's submission.
User Actions — Shows the actions the resident/guest has taken (click to view history).
Actions — Your action menu for this dispute (Approve, Deny, Request Investigation, etc.).
Dispute Statuses Explained
Active
The dispute has been submitted and is awaiting your review. This is the default state when a dispute is filed and it's where most of your daily work happens.
Expiring Soon
The dispute has been active long enough that the response deadline is approaching. Treat these as your highest priority — letting one expire without a response can affect the outcome.
Pending Adjudication
The dispute has been escalated. This typically happens when:
You requested an investigation through the Actions menu.
The resident/guest contested your initial decision.
The dispute meets criteria for automatic escalation.
While in Pending Adjudication, the dispute is being reviewed by the appropriate party (ParkingPass Support and/or the tow vendor) and you may be asked for additional information.
Approved
The dispute resolved in the resident's favor — the citation, boot, or tow is reversed and any associated charges are refunded.
Denied
The dispute resolved in the property's favor — the original enforcement action stands.
Canceled
The dispute was closed without a final resolution — typically because the resident withdrew it, the underlying violation was already resolved, or the dispute window expired.
Reviewing a Dispute
Open a dispute by clicking Details on the row in the Violation Payment Dispute Report.
A complete review includes:
Read the resident's submission. What are they claiming? What evidence did they provide?
Open the underlying violation report. Look at the enforcement reason, time stamps, photos, and the rule that was applied.
Check timestamps. At the bottom of the violation report you'll see exact times for the patrol scan, the rule check, and the enforcement action. Cross-reference these against the resident's claim.
Verify vehicle authorization. Was the vehicle properly registered? Did it have an active permit? Was it on the Do-Not-Tow list? Was a Patrol Hold in effect?
Check property settings. Was the parking rule that was applied still in effect at the time of the violation? Did your configured warning structure match what was issued?
💡 Tip: A dispute often hinges on a small detail — vehicle plate typo, lease end date that wasn't updated, a Patrol Hold that wasn't placed in time. The full violation report contains the data you need to make a decision quickly.
Responding to a Dispute
From the Actions dropdown on a dispute row, you can:
Approve the Dispute
Use when the enforcement action shouldn't have happened. Approving:
Reverses the citation, boot, or tow.
Refunds any amount the resident already paid.
Closes the dispute as Approved.
Deny the Dispute
Use when the enforcement action was valid. Denying:
Leaves the citation, boot, or tow in place.
Closes the dispute as Denied.
Notifies the resident of the outcome.
Request Investigation
Use when you suspect the violation may have been caused by a software issue or a confirmed enforcement vendor mistake, and you want ParkingPass Support to review. Requesting investigation:
Moves the dispute to Pending Adjudication.
Triggers a review by ParkingPass Support.
May involve coordination with your patrol vendor.
Use this option sparingly — for clear-cut cases where you've already worked through the violation report and a system error is the likely cause.
Pending Adjudication: What to Expect
If a dispute moves to Pending Adjudication, here's what happens next:
ParkingPass Support reviews the violation report, patrol scan data, and your enforcement configuration.
If the patrol vendor's actions are involved, the vendor may be contacted.
You may receive a request for additional information — respond promptly to keep the dispute moving.
Once a final decision is reached, the dispute's status updates and the appropriate parties (resident, property, vendor) are notified.
Pending Adjudication is not an indefinite state. Most disputes resolve within a few business days, though complex cases may take longer.
Common Dispute Scenarios
Resident's lease was active but the system showed it as expired
Check the resident's profile for the Lease Expiration Date. If it was out of date at the time of the violation, this may justify approving the dispute. Update the lease date going forward — see Updating Resident Lease Dates.
Vehicle was on the Do-Not-Tow list but was towed anyway
Confirm the DNT entry was in place before the violation timestamp. If it was, this is typically a software or vendor issue — request an investigation. If the DNT entry was added after the violation, the tow was valid. See Managing the Do-Not-Tow (DNT) List.
Patrol Hold was in place but enforcement still occurred
Check the Patrol Hold start and end times against the violation timestamp. If the hold should have covered the violation, request an investigation. See Placing and Managing Patrol Holds.
Resident says they paid but the permit shows expired
Check the resident's Payment History on their profile. Look at the actual payment dates against the violation timestamp. If a payment failed silently or processed late, this may justify approving the dispute. See How Residents Make Payments.
Guest pass was created but the guest was towed
Check the guest pass start/end times and the license plate exactly as entered. A typo in the plate or a future-dated pass start time is the most common cause. If the pass was valid for the timeframe and plate matched, request an investigation.
Clear-cut rule violation
Deny the dispute. The resident or guest broke a configured parking rule and the enforcement was valid.
Preventing Future Disputes
Disputes are an unavoidable part of running a parking program, but a few practices reduce volume significantly:
Keep lease dates current. Outdated lease information is the most common cause of "valid resident, wrong outcome" disputes — see Updating Resident Lease Dates.
Use the Do-Not-Tow list proactively. Add employees, vendors, contractors, and known-protected vehicles before they're on site.
Place Patrol Holds for known events. Special events, move-in/move-out days, or community gatherings should have a Patrol Hold scheduled in advance.
Encourage automatic recurring payments. Most "I paid but it expired" disputes come from manual renewals that lapsed — see How Residents Make Payments.
Review Patrol Analytics weekly. Repeat violations from the same vehicles or in the same zones often point to a rule that needs clarifying signage or a configuration adjustment.
Audit your DNT list and Patrol Holds weekly. Stale protections can create both unintended exposure and resident confusion. Build this into your weekly routine — see Property Manager Quick Start: Your Daily Playbook.
Important Notes
Disputes have time-sensitive deadlines. The Age column on the report and the Expiring Soon dashboard count both flag disputes approaching the deadline.
Letting a dispute expire without a response is treated similarly to an approval in many cases — review every Active and Expiring Soon dispute promptly.
ParkingPass does not issue or override enforcement actions directly. Approving a dispute reverses an enforcement record, but the underlying decision is always made by you (the property manager) or by adjudication review.
Each property is responsible for the relationship with its patrol/tow vendor. If a tow vendor caused an error, your property contacts the vendor directly — ParkingPass does not mediate that conversation.
All dispute communication and outcomes are logged. You can export the dispute report at any time using the Export button at the top of the page.