Most parking operators build a budget once a year and revisit it seriously only when something goes badly wrong. The mid-year reforecast is the point where the annual plan meets reality — and where operators who do the work gain a genuine advantage over those who don’t.
A reforecast isn’t a performance review. It’s a forward-looking document. The purpose isn’t to explain why H1 came in where it did (though that analysis is necessary); it’s to produce an accurate H2 projection that management and ownership can act on. Done well, a mid-year reforecast provides a cleaner picture of full-year revenue than the original budget — because it replaces six months of assumptions with six months of actual data.
Reading H1 Variance Before Projecting H2
The analysis has to start with a clean read of what actually happened versus plan. This sounds obvious, but most parking P&Ls don’t produce variance automatically — someone has to calculate it.
The core formula is straightforward: (Actual − Budget) ÷ Budget, expressed as a percentage. A positive variance means you outperformed plan; negative means you underperformed. The percentage matters as much as the dollar figure — a $20,000 shortfall against a $100,000 quarterly budget is a 20% miss, which is a planning problem. The same $20,000 shortfall against a $2M quarterly budget is 1%, which is noise.
For parking operations, the H1 variance analysis should decompose into at least three components:
Rate variance: Did actual collected rates differ from budgeted rates? This is not posted rates versus budget — it’s collected revenue divided by paid transactions compared to the same calculation from the budget model. Rate underperformance often signals higher-than-expected validation leakage, pricing changes that weren’t modeled, or a transient/monthly mix shift.
Volume variance: Did transaction volume (transient entries, monthly permits, event events) come in as projected? Volume shortfalls that explain most of the revenue gap typically trace to occupancy drivers — office return rates, residential demand, event schedule changes — rather than pricing or operational failures.
Mix variance: Did the transient/monthly/event revenue mix shift relative to plan? A facility that budgeted 40% monthly revenue but is running 30% has a different full-year revenue profile than the budget assumes — even if total transactions match plan — because transient revenue typically carries higher rate per transaction than monthly.
Understanding which component explains the H1 variance determines how you build the H2 reforecast. A rate-variance problem requires a different response than a volume-variance problem.
Causal Factors Worth Isolating
H1 variances in parking rarely have a single cause. The most common causal clusters:
Occupancy driver changes. Office leasing changes in the catchment area, retail tenant mix shifts, hotel demand changes for hotel-adjacent facilities — these are structural changes that won’t self-correct in H2. A building that lost a major tenant in Q1 has permanently lower commuter parking demand for the remainder of the year. The reforecast needs to reflect the new demand baseline, not assume recovery to original projections.
Event schedule changes. For facilities with material event revenue, any deviation from the budgeted event schedule — cancellations, rescheduling, venue changes, strike/weather impacts — has a disproportionate effect on total revenue. Event revenue is highly concentrated; missing three events can represent a month of transient revenue in a single line.
Competitive landscape shifts. A new competing facility opening, a major competitor closing (which increases your demand), or a competitor changing pricing strategy mid-year all affect the revenue environment. These typically show up as volume variance but can also drive rate variance if the competitive response altered your pricing.
Capital or operational disruptions. Construction affecting access, payment system outages affecting transaction completion rates, or staffing changes affecting enforcement quality all produce variances that shouldn’t be projected forward if the disruption is resolved. These are one-time items that need to be explicitly called out as non-recurring in the reforecast.
Building the H2 Reforecast
Once you’ve isolated what drove H1 variance and classified it as structural (will persist) or transient (won’t persist), the H2 reforecast is a mechanical process with a few key judgment calls.
Start with run-rate, not budget. Take your H1 actuals, annualize them to get a run-rate, and use that as the H2 starting point. This captures the structural changes already embedded in your operations. Then add back any H1 disruptions you’ve classified as non-recurring (construction ended, staffing stabilized, event cancellations that have been rescheduled).
Model the event calendar explicitly. Every confirmed event in H2 should appear as a line in the reforecast with its own revenue projection. Unknown or speculative events should be excluded or modeled conservatively. This is the area where parking budgets most often incorporate wishful thinking — assuming H2 event revenue bounces back to original budget levels without an explicit event-by-event basis for that projection.
Apply revised rate assumptions. If H1 showed a consistent rate-versus-plan gap, investigate whether it’s structural. If validation leakage is running higher than budgeted, that’s unlikely to self-correct without an operational intervention. If you’ve already made a rate change or policy change in Q2 that addresses the gap, model the effect of that change on H2 rather than assuming the original budget rate automatically applies.
Segment monthly versus transient separately. Monthly permits are largely deterministic in H2 — you know your current permit count and your average rate. Model attrition (based on H1 churn data) and new permits separately. Transient revenue in H2 is more variable and requires an occupancy and rate assumption; use H1 actuals as the base and adjust for known changes in the demand environment.
Presenting the Reforecast
The output that’s actually useful to leadership and ownership is a three-column view: Original Budget / H1 Actuals / H2 Reforecast + Full Year Projection. Each row should be a revenue line (transient, monthly, event, other). The variance columns show H1 actuals versus budget (closed period) and H2 reforecast versus budget (forward period).
Two supplementary items make the reforecast credible:
A brief narrative on the causal factors behind material variances — what happened, whether it’s structural or transient, and what assumption changes flow from it. Leadership shouldn’t have to guess why the monthly line is down 12% or why event revenue is up.
A sensitivity table on the H2 projection’s primary assumptions: occupancy rate, rate per transaction, event count. A simple two-by-two (what does full-year revenue look like if occupancy is 5 points better or worse than the reforecast assumption? if the event calendar gains or loses two major events?) gives ownership a range rather than a false point estimate.
The reforecast that gets acted on is the one that comes with a clear line of sight from the H1 data to the H2 assumptions, with variance explanations that match what operations teams know to be true. A reforecast that looks like an internal negotiation — minimizing the H1 shortfall while restoring H2 to near-original budget — typically generates skepticism rather than useful decision support.
Revenue management is more useful in the second half of the year than the first precisely because you have real data. Use it.
