Why the biggest spend on the trip has no number
Everything an event sells through its own checkout is measured because the checkout measures it. Tickets, parking passes, merchandise and add-ons arrive as rows in an order table, and the dashboard that reads the table is the organizer's picture of the event. Lodging is bought somewhere else, from somebody else, on a page the organizer never sees, and so it never becomes a row. The absence of a number is not a sign that the spend is small; it is a sign that the spend happens off the organizer's property.
The one lodging document that does reach the organizer is the hotel's pickup report, and it is the source of most of the confusion. Pickup is a precise count of a narrow thing: rooms booked inside the contracted block, at the block rate, before the cutoff. It is read as if it were a measure of the audience's lodging, which it is not. An event with modest pickup can have a large travelling audience that booked everywhere except the block, and the report cannot tell the difference between those two events.
The result is that lodging decisions get made on the one number that exists rather than the number that matters. Blocks are sized from last year's pickup, partnerships are judged by the hotel's enthusiasm, and the question of what the travelling audience actually spent on beds is answered with a shrug. The fix is not a better pickup report. It is a short set of figures the organizer can produce from data it already holds, laid out in the order each one depends on the last.
Start with the travelling share: the estimate everything else hangs from
The first figure is how much of the audience travels far enough to need a bed, and it is the only one on the scoreboard that comes directly from the organizer's own order data. Every ticket order carries a billing address or a postal code. Sort orders by distance from the venue, decide on the radius beyond which a same-day return is unrealistic for the event's start and end times, and count the orders past it. That count, as a share of all orders, is the travelling share, and it is the base every later figure is divided by.
Do not refine it into a forecast. Attendees on the far side of the radius sometimes stay with friends and attendees inside it sometimes book a room to avoid the drive, and neither case is worth modelling. The figure's job is to put a floor under the lodging demand so that it can never again be described as negligible. An event that discovers a travelling share in the thousands has learned the most important thing about its lodging line before any partner, hotel or platform has entered the conversation.
Multiply the travelling orders by the nights the event spans, plus one if arrivals commonly come the evening before, and the result is a room-night floor: the minimum number of nights the audience booked somewhere. This is the figure to hold against the pickup report, because the gap between the two is the audience the block never saw. It is also the figure a lodging partner should be asked to report against, since capture only means something as a fraction of a known whole.
Pickup counts the block, not the audience
Pickup belongs on the scoreboard, but in its own column and with its definition written beside it. It counts rooms reserved under the block code, at the block rate, before the cutoff date, as reported by the hotel. Everything outside that definition is invisible to it: the attendee who booked the same hotel at a cheaper public rate, the attendee who booked the hotel across the street, the group that took a house, and everyone who decided after the cutoff. In a real event market we measured, at a sold-out date only about 31% of the lodging money went to properties inside the block. The rest went where the block was never looking.
That figure is the reason pickup and demand drift apart in both directions. A block that fills early and sells out stops counting at the moment demand is accelerating, so a strong event reports a flat pickup line that ends weeks before the dates. A block that sits half empty reports low pickup while the same attendees book outside it, so the event concludes its audience does not travel when the audience has in fact travelled around the contract. Both readings are wrong, and both are the natural reading of a pickup report with no travelling share next to it.
The practical use of pickup is contractual, not strategic. It is the number attrition is calculated from, the number the cutoff date freezes, and the number to raise before that date by pointing attendees at the block code. Track it for those reasons, and defend it against the hotel's definition where outside bookings at the hotel can be argued into it. Just never let it stand in for the size of the travelling audience, which it was never built to measure.
The timing curve: when the audience actually decides
The third figure is a shape rather than a count. Lodging demand does not arrive evenly across the sales cycle; it bunches late. In the same event market, roughly 70% of the lodging money was committed inside the final 30 days before the dates. Most of the audience buys the ticket early and the bed late, and the gap between those two decisions is where the organizer's visibility ends, because the ticket shows up in the dashboard and the bed does not.
The timing curve matters because it decides where a lodging offer has to be placed and when a lodging report has to be read. An offer announced at on-sale and then left alone has done its work before most of the bookings exist. A report read the week after on-sale will show almost nothing and will tempt an organizer to conclude that the line does not work. The curve says to put the offer on surfaces that fire late, meaning the reminder emails, the FAQ page and the confirmation page for late ticket buyers, and to judge the line only once the final month has passed.
An organizer can see its own curve by asking for booking dates, not just booking totals, in whatever lodging report it receives. A block pickup report usually shows the count at a point in time; ask for the date of each reservation and the curve appears. A lodging partner's report should carry a booking date on every row for the same reason. Once the curve is visible, the cutoff date on the hotel contract can be judged against it, and the usual finding is that the cutoff lands before the demand it was meant to catch.
The inbox and the box office as a demand signal
Before any offer is placed or any partner is reporting, there is a lodging signal the organizer already generates and almost never counts: the questions. Where should we stay, is there a hotel near the venue, do you have a discount code, can we check in early, is there parking. They arrive in the support inbox, the social replies, the box office line and the volunteer tent, and each one is an attendee announcing a purchase they are about to make somewhere.
Counting them is cheap. Tag lodging questions in the help desk for one cycle, or keep a tally sheet at the box office for one week of the sales period, and note how many were answered with a link the attendee could book from versus a sentence they had to go and act on themselves. The count will be smaller than the travelling share, because most attendees never ask, but its ratio to the travelling share says how much of the audience is reaching the organizer with the question at all.
The second thing the count does is establish a baseline for the offer. If the lodging offer is placed where the questions arise, on the confirmation page, in the FAQ answer and in the reminder email, the question volume should fall in the next cycle while the booked volume rises, because the answer arrived before the question was typed. A lodging line that produces bookings while the inbox stays as busy as ever is reaching a different audience from the one asking, which is a placement problem worth finding.
The offer's own numbers: capture, room-nights and revenue per travelling buyer
Once a lodging offer is live, the scoreboard gains the figures a channel is actually run on. The first is bookings, as a count. The second is room-nights, which is bookings multiplied by nights and is the figure that compares cleanly against the room-night floor from the travelling share. The third is gross booking value, meaning the rate the attendee paid, which is what the commission is calculated on. The fourth is the commission, which properties pay to whichever channel delivers the guest and which generally sits in the 15-20% range. The fifth is the organizer's share of that commission, which is the revenue line.
From those five columns come the two ratios worth watching. Capture is room-nights booked through the offer divided by the room-night floor, and it says how much of the known travelling audience the organizer's placement reached. Revenue per travelling buyer is the organizer's share divided by the number of travelling orders, and it turns the lodging line into a figure that can sit beside ticket yield in the same spreadsheet. Neither ratio needs the organizer to know anything about the partner's business; both need the partner to report per booking rather than as a summary.
That reporting requirement is the test of a partner. A report that shows only a revenue total asks the organizer to accept a share without the base it was calculated from. A report with a row per booking, carrying the booking date, nights, gross value, commission and share, lets the organizer check the arithmetic, draw the timing curve and compute capture without asking for anything else. One organizer's program delivered 550 room-nights from a single confirmation-page placement, and the reason that figure is usable is that it was counted a booking at a time rather than announced.
Reading the scoreboard across cycles
The scoreboard is only useful once it has two cycles on it, because almost every lodging figure is more meaningful as a change than as a level. Capture in the first cycle is a baseline rather than a verdict; the first cycle usually places the offer late and in one spot, and the figure reflects the placement more than the audience. The comparison that matters is capture in the second cycle against the first, with the placements that changed between them written next to it.
Keep the columns separate when the numbers are reported upward. Pickup answers to the hotel contract. The travelling share answers to who bought tickets. Capture and revenue per travelling buyer answer to placement and timing. Blending them into a single lodging figure hides which lever moved, and the lever that moved is the only thing the next cycle can act on. A board that sees three short columns can ask a useful question; a board that sees one total can only ask whether it went up.
Finally, use the scoreboard at the moments it has leverage. A hotel negotiation with a travelling share and a timing curve on the table is a different conversation from one with last year's pickup alone, because the organizer can now show demand the block never counted and a cutoff that lands before it. A lodging partner's renewal with a year of per-booking data behind it is likewise a different conversation from the first signing. Spot-check a few bookings a quarter against the report, renegotiate on the anniversary of the data, and leave the figures that cannot be counted, such as how much an attendee enjoyed the hotel, out of the scoreboard entirely.