What each number counts
Meetings booked is a scheduling event. Meetings held is a buyer decision. A booked meeting means a prospect accepted an invite. A held meeting means that prospect showed up and stayed long enough to have a conversation. Only the second one creates something a revenue team can work.Most CRMs make booked easy to count and held hard to count, because held requires someone to disposition the calendar event afterward. That reporting asymmetry is why booked becomes the headline number and the gap goes unmanaged for quarters at a time.
The gap is the metric
Held rate is meetings held divided by meetings booked across the same cohort. Track it by the week the meeting was booked rather than the week it happened, or reschedules will smear across periods and bury the trend.
Two teams with identical booking numbers produce very different pipeline. The figures below are illustrative.
| Team | Booked | Held rate | Held meetings |
|---|---|---|---|
| A | 100 | 78% | 78 |
| B | 100 | 52% | 52 |
What drives the gap
Four causes account for most of it.
- Lead time between booking and meeting date. Attendance decays with every additional day of delay. - Weak qualification. A prospect who agreed to end a call rarely blocks time for the follow-up. - Single-threaded invites. One name on the calendar means one conflict kills the meeting. - Booking pressure at period close, when reps accept anyone who says yes.
Put held meetings in the plan
Pipeline creation models should run on held meetings. Booked meetings are an input with a discount rate attached, and that rate moves month to month. When held rate drops six points, the pipeline shortfall lands one sales cycle later, which is exactly why pipeline coverage reads as a lagging view of creation risk and why a coverage multiple on its own answers nothing.
The gap is also buyer signal, not administrative noise. A prospect who books and then disappears is showing the same pattern that predicts deal slippage later in the cycle: the absence of engagement rather than a stated objection. Treat a falling held rate as a demand-quality reading, then check which list sources and personas it came from before adjusting the booking target.
Frequently Asked Questions
Which number should SDRs be paid on?
Held meetings, with a qualification gate applied by the AE who ran the call. Paying on booked meetings pays for calendar entries, and the rep has no reason to protect attendance once the invite is accepted. Paying on held meetings moves the confirmation work to the person who controls it.
What is the difference between held rate and show rate?
Held rate is measured against the booking cohort, so a meeting that was rescheduled twice and then happened still counts as held for the week it was booked. Show rate is measured against the calendar date and treats each scheduled slot separately. Held rate answers a planning question, show rate answers a scheduling question.
Why does the booked-to-held gap widen at the end of a quarter?
Booking pressure rises and qualification drops. Reps accept softer commitments to hit an activity number, and soft commitments do not survive a busy buyer's calendar. The gap surfaces only after the meeting dates arrive, which is why a quarter-end booking spike is a weaker pipeline signal than the same volume booked mid-quarter.
How do you close the gap without lowering booking volume?
Shorten the lead time between the booking and the meeting, and add a second buyer-side attendee to the invite. Long lead times lose attendance every additional day, and a single-name invite means one conflict cancels the meeting outright.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like meetings booked vs meetings held into prescriptive action for your team.
Schedule a Demo