Research brief 03.04Forward reading
Booking Pace: Reading Next Year's Revenue in This Year's Ledger
Your next twelve months of revenue are already partially written: in contracts signed, deposits held, and dates gone. Pace is the discipline of reading that writing early enough to change the ending.
A venue's revenue doesn't arrive by surprise; it arrives by appointment, booked months ahead. That lead time is a gift most operators leave unopened: because future revenue is visible early, weakness in it is visible early too, if you keep the one table that makes the comparison honest. That table is booking pace: what's on the books for each future period, compared against what was on the books for the same period at the same distance last year.
1. The instrument: OTB and STLY
The magic is entirely in the second line. Raw OTB is almost useless alone: of course next June looks empty in September; it always does. The question is whether it looks emptier than last June looked from last September. That comparison cancels out the lead-time curve and leaves the signal: demand for your future, measured against your own history.
The cost of the instrument is one habit: a monthly snapshot. On the first of each month, record OTB (count of bookings and contract value) for each of the next twelve months, by event type. The first year of snapshots buys you nothing but the baseline; every year after, the pace table reads your future each month for ten minutes of clerical work. Venues with booking software can often export this; a spreadsheet does it fine.
2. A worked pace table
| Future period | OTB now | STLY | Pace | Final last year |
|---|---|---|---|---|
| May | $61,000 | $54,000 | 113% | $118,000 |
| June | $48,000 | $71,000 | 68% | $139,000 |
| July | $52,000 | $50,000 | 104% | $121,000 |
May and July are pacing at or ahead of last year; June is running at two-thirds of its normal book for this distance out. That's the entire report, and it arrived eight months before June does. The final-last-year column adds the sobering context: most of June's revenue, on last year's pattern, would normally already be materializing by now. A venue reading this in September can act; a venue that discovers June in June can only absorb it.
3. Reading pace without fooling yourself
- Value and count can disagree. OTB dollars ahead on fewer, larger bookings is a different situation from more, smaller ones. Track both. A pace built on one giant corporate contract is a concentration, not a trend.
- Type mix matters. Weddings book far out; corporate books close in. Blended pace early in the cycle is mostly a wedding report with corporate noise. Segment by type or the short-lead segments will look permanently, meaninglessly weak.
- One year of STLY is a small sample. Last year might have been the weird one. Where you have the history, compare against an average of prior years at the same distance; where you don't, hold the conclusions loosely and let the baseline accumulate.
- Policy changes bend the curve. If you raised prices, changed deposit terms, or restructured packages since last year, pace confounds demand with policy. Note the change on the table and read accordingly: a soft pace after a price increase may be the increase working exactly as priced.
4. Acting on a soft period: early beats hard
The whole value of pace is that it converts a revenue problem into a time problem, and time is the input every fix needs. A soft period identified early gets the gentle tools: aimed marketing (the acquisition spend pointed specifically at the weak months), outreach to the planner and corporate lists, packaging that differentiates the slow period instead of discounting the flagship, and (because supply is also a dial) opening that period's dates to event types that don't normally get them. The same softness discovered late gets only the harsh tools: deep discounts with their punishing recovery math, or resignation. Pace doesn't make demand; it buys the months in which demand can still be built.
The symmetric case matters too: a period pacing far ahead is information about pricing. Dates selling faster than history at current rates are dates the market is telling you were priced low: the textbook signal to test rate on what remains, per the utilization article's reading of a nearly-sold segment.
5. The monthly pace review: a ritual worth twenty minutes
The snapshot is clerical; the review is where pace earns its keep. Once a month, same day the snapshot is taken, answer four questions in writing. Which periods moved most since last month, and was the movement bookings arriving or bookings you already expected finally signing? Which periods sit below an action threshold you chose in advance (a pace floor, say, any period below a chosen fraction of STLY with under six months to run, so that "should we worry?" was decided calmly, once, rather than re-litigated monthly)? What action did last month's review trigger, and did it move anything: the aimed campaign, the planner outreach, the package launch each get graded against the periods they targeted? And what does the type-level view say that the blended view hides? Twenty minutes, written down, filed with the snapshot. The written record matters more than it seems: pace decisions are exactly the kind that hindsight repaints, and the file of what you knew when is how the venue actually learns which interventions work at which distances.
New venues, lacking any STLY, should run the same ritual on the pieces they do have: the pipeline (inquiries, tours, quotes outstanding, by target month) and the accumulating snapshot archive itself, which starts paying out comparisons in year two. The worst response to having no baseline is keeping no records. That just schedules the same blindness for next year.
6. Pace as the spine of the projection
Every revenue projection this site discusses (the lender's plan, the DSCR numerator, the annual budget) is, at bottom, a claim about future bookings. Pace is what disciplines the claim. A projection built as "each month's final revenue = OTB + (historical fill from this distance)" is auditable arithmetic; a projection built as "up 15% because we'll work harder" is a mood. The fill-in factor, what fraction of a month's final book typically arrives inside each window, falls straight out of your snapshot archive after a couple of years, and it quietly answers the operating questions too: when to worry, when to stop holding prime dates for full-price late demand, and when a slow month is actually still on schedule.