Most parking annual reports are written for the department that produced them. They list every number the system can generate, in the order the system exports them, and the council or board member who opens the PDF stops at page three. The report that gets read is organized around the questions elected and appointed officials actually ask: Is the program paying for itself? Are people able to find a space? Is the money being spent well? Is anything about to cost us a lot?

Lead With the Questions, Then the Numbers

Open with a single page that answers those four questions in plain language, each backed by one or two figures. Everything after that page is reference material for readers who want to check your work. A good one-page summary includes:

  • Financial position: total revenue, operating cost, net operating income, and the change from the prior year.
  • Access and demand: occupancy against target and, where measured, turnover.
  • Service quality: equipment uptime and customer complaints or appeals outcomes.
  • Looking ahead: the largest capital need and what the department is asking for.

Place the ask last on that page, so it arrives after the evidence rather than before it.

The Metrics That Earn Their Space

Occupancy against a target range

Occupancy is the most-cited demand metric, and the strongest reports compare it to a stated target instead of reporting a raw average. Baltimore’s parking performance scorecard, for example, sets a goal for the share of demand-based meter blocks falling within a 75 to 85 percent occupancy range. Seattle’s transportation department defines occupancy as the percentage of on-street parking in which a vehicle is parked at a given time and ties its targets to the city goal of one to two open spaces per blockface; it also notes occupancy can exceed 100 percent because more vehicles can fit on a blockface than the estimated space count. Define your own method in a footnote, because the definition changes the number.

Turnover and duration

Turnover shows whether short-term spaces are serving short-term visitors. Newport Beach’s parking study measured it through duration data collected from partial license plate records, which identifies repeat vehicles without capturing personal information. If you cannot measure turnover, say so and report what you can: transactions per day, a measure Tacoma’s downtown parking report puts at the front of its key-metrics dashboard.

Revenue and cost, together

Report gross revenue by stream and operating cost on the same page, with net operating income calculated for the reader. Revenue per space is popular but has no single standard definition, as the sources we reviewed noted, so if you use it, state the denominator: total spaces, paid spaces, or occupied spaces. Without that, a board member comparing it with another city is comparing two different things.

Equipment uptime and service

Baltimore’s scorecard sets a meter uptime target of 98 percent. Whatever your own target is, report actual uptime against it. Boards that fund equipment replacement want to see whether the failures they are paying for are showing up in the data.

Enforcement and appeals

Report citations issued, collected, and contested, plus the dismissal rate on appeal. A high dismissal rate is a signal about signage, training, or policy that a board would prefer to learn from you rather than from a news story.

A single year tells a reader nothing about direction. Use at least three years of data on the headline measures and mark any events that explain breaks: a garage closure, a rate change, a pandemic-era baseline, a system migration. Annotated trends are more credible than a clean line, because they show you know what happened.

Be equally direct about measurement gaps. A Shasta County, California grand jury report on Redding’s paid parking program noted that effective programs monitor and publicly report occupancy and turnover, and that Redding had not measured occupancy since 2018, and it recommended regular reporting on whether revenue covers program cost. Whatever you think of that finding, it is a reminder that a missing metric becomes a public question.

Format Choices That Get the Report Read

  • Keep the summary to one page and the full body under what a board packet can reasonably carry.
  • Use charts for trends and tables for reference. A line chart with three years and annotations beats a table of 36 cells.
  • Define every metric once, in a glossary or footnotes, so the figures are comparable year to year.
  • Plain language over jargon. PARCS, LPR, and NOI may be everyday terms for you; spell them out once.
  • Link metrics to decisions. Every figure should connect to something the board can do: approve a rate, fund a replacement, adopt a policy.

Presenting It, Not Just Publishing It

Prepare for the meeting as you would for a budget hearing. Anticipate the three hardest questions, such as why a rate is rising, why a facility is underused, and why a project costs what it does, and have a backup slide for each. Bring one comparison with a peer community, labeled with the source and year, so the board has context. And hand the reader something they can quote: one sentence that states the program’s net position and direction.

The practical takeaway is simple. Cut the report until every remaining metric answers a question someone on the board has actually asked, define it clearly, and show its three-year trend. A short report that gets read will do more for your next budget than a long one that does not.