Your team booked six meetings this week. By Friday afternoon, one has happened. That does not mean five prospects failed to show up. Some meetings may be next week, one may have moved, and another may be over without a saved outcome.
To understand what became of this week’s bookings, keep that group together and follow it forward. Don’t divide all the meetings held this week by all the meetings booked this week: those counts can describe different buyers and different work.
This guide is for sales managers and revenue operations teams reviewing booked meetings. It explains how to choose the date that puts a booking into a report, show what is known at the report’s cutoff, and compare groups that have had a similar chance to reach a result. The timeline and worksheet below are suggested reporting methods, not Trellus benchmarks or product features.
Two date filters answer two different questions
A booking-date report asks: “What happened to the meetings we arranged during this period?” A scheduled-date report asks: “What happened to the meeting slots expected during this period?” Both are useful. Neither should quietly borrow the other’s denominator.
Suppose a rep books a meeting on Friday for the following Tuesday. It belongs to Friday’s booking group, but Tuesday’s scheduled-meeting report. A meeting held this Friday might have been arranged last month. It belongs to this Friday’s attendance workload, not this week’s new bookings.
Use booking date when examining what becomes of the commitments a team creates. Use scheduled start when reviewing attendance for the meetings due to happen. The existing meeting show-rate guide explains the latter calculation and its outcome rules. Here, the job is following a fixed set of bookings through time.
Define “booked” before exporting. For this worksheet, it means a confirmed meeting arrangement with a specific scheduled time. A rep suggesting Tuesday or sending a scheduling link is not enough. Your team may use a different verified booking rule; state it and keep it consistent. The SDR-to-AE handoff brief helps preserve what the buyer actually agreed to.
Keep a booking together when its time changes
Give each in-scope booking a stable reference. Save when the original arrangement was made, its original scheduled start, the latest scheduled start and the history of changes. Store only the internal references your report needs; don’t copy prospect details into a new shared spreadsheet unnecessarily.
For this booking-level view, moving a meeting does not create another new booking. The replacement slot stays linked to the original arrangement. Otherwise, a single buyer moving a demo twice can look like three meetings generated.
This does not mean deleting old calendar events. Preserve the original slot and replacement relationship. If a buyer misses the first occurrence and later attends a replacement, the original no-show remains in the attendance history. A later held meeting can change the booking-level result without erasing the earlier event.
A genuinely separate meeting can count as a new arrangement under your rule. A follow-up after an initial demo, for example, may be a different meeting type. Keep it out of a first-meeting cohort unless the scope explicitly includes follow-ups. Do not use a calendar event’s creation time as the original booking time without checking how your system represents reschedules and imported events.
Put an “as of” time beside the result
A date interval selects the bookings. A cutoff tells the reader how long you observed them and what information was available when you reported.
Write both: “First meetings booked October 5–9, 2026; status as of October 9 at 5 p.m., America/New_York.” Use an explicit interval boundary in the underlying report, such as Monday at midnight through Saturday at midnight, with the ending boundary excluded.
At that cutoff, distinguish these conditions:
- Held so far: a qualifying meeting in the booking’s history is confirmed as attended.
- Not yet due: the active scheduled start is after the cutoff. This includes a booking moved to a later slot.
- Past start, outcome unresolved: the time has passed but the host or attendance evidence has not established the result.
- Confirmed no-show, not held so far: an occurrence was missed; keep any later scheduled attempt visible alongside that fact.
- Canceled, not held so far: the arrangement was canceled; record whether a replacement exists rather than guessing that the buyer is permanently lost.
These conditions are not always mutually exclusive: a no-show may also have a future replacement. For a total that adds up, assign one stated current-status bucket per booking and retain the occurrence history separately. For example, place a missed meeting with a future replacement in “not yet due,” while preserving the prior no-show in its history. Never add overlapping flags as though they were different bookings.
A fictional six-booking timeline
All dates below are in October 2026, using America/New_York. All six are separate first-meeting arrangements made October 5–9. The first snapshot is taken Friday, October 9, at 5 p.m. These records are fictional.
- A: booked October 5; scheduled October 8; confirmed held October 8. One held booking at the cutoff.
- B: booked October 5; scheduled October 9; host confirms a no-show before the cutoff. No replacement is scheduled in this example.
- C: booked October 6; scheduled October 13. Not yet due on October 9.
- D: booked October 7; originally scheduled October 9; canceled October 8 with no replacement. Canceled, not held.
- E: booked October 8; originally scheduled October 9; moved in advance to October 15. One booking, not two; not yet due at the cutoff.
- F: booked October 9; scheduled for 4 p.m. that day; no reliable attendance outcome is saved by 5 p.m. Past start, outcome unresolved.
The snapshot contains six bookings: one held, one confirmed no-show without a replacement, two not yet due, one canceled and one unresolved. Held so far is 1 of 6, or 16.7%. That is a description of progress by Friday’s cutoff, not a final attendance rate. It is not correct to label the other five no-shows or failed meetings.
Now follow the same six references. C is confirmed held on October 13. E is confirmed held on October 15. On October 12, the host resolves F as a no-show that occurred October 9. No further meetings occur for B, D or F within the observation window described below.
By October 16, three of the six bookings have led to a held meeting. The list has not grown: A, C and E are the three held arrangements; E’s move did not add a seventh booking. F’s later confirmation improves the record, but it was still unknown in the original Friday snapshot. Save the corrected information without pretending it was already known.
Choose how long you will follow each booking
For a comparable downstream measure, define a follow-up window. One possible measure is: the share of original bookings that lead to at least one held first meeting within 14 elapsed days of the original booking timestamp. Fourteen days is an illustrative choice, not an industry standard. Choose a window that fits the scheduling lead times you actually need to understand.
Use the original booking timestamp to start the clock. In this example, 14 elapsed days means 336 hours: count a qualifying held meeting after the original booking and at or before that deadline. A reschedule does not restart the clock. Store full timestamps so a daylight-saving change does not silently turn an elapsed-time rule into a calendar-date rule. A meeting held after the window can still be valuable, but belongs in a separately labeled later-outcome view rather than being retroactively included in the 14-day measure.
The fictional six-booking group can be reviewed after every booking’s 14-day window has ended. At an October 24 cutoff, that is true for even the booking made late on October 9. A, C and E were held within their individual windows; the other three were not. Under this stated rule, 3 of 6, or 50%, reached a held meeting within 14 days. It is not a benchmark, an estimate of future performance or a qualification rate.
A booking without a held meeting inside the window is not necessarily a no-show. It might have been canceled or scheduled too far ahead. Keep those explanations beside the result. A past slot with an unresolved outcome stays unresolved even after the follow-up clock expires; the passage of time does not fill in a missing record.
Keep unresolved bookings whose windows have ended in the original denominator, and show their count beside the confirmed-held count. If those unknowns could change the result, label the confirmed-held share provisional rather than final. Do not remove the unknowns to make the percentage cleaner or turn them into confirmed failures. In the fictional October 24 example, all six outcomes have been resolved, which is why the 50% can be reported as the completed result under this rule.
Compare bookings at the same observation age
Last month’s bookings have had more time to produce meetings than bookings made yesterday. Comparing their latest held-so-far percentages rewards the older group for having a longer observation period.
For the 14-day measure, include only bookings whose individual windows have ended by the report cutoff, and disclose any excluded younger bookings. Better still, wait until the entire weekly booking group is old enough to report that group’s result. Keep the current week’s progress snapshot visible separately so the team can still act on open work.
If you publish an early comparison, use the same age rule for both groups and label it clearly. Do not compare one week at seven days after its final booking with another week at thirty days after its final booking. Also check meeting type, source, audience and ownership rules. Matching observation age fixes a timing mismatch, not differences in the buyers or sales motion.
Show counts beside percentages. A change from one held booking out of two to two out of three is easy to overinterpret when the report shows only 50% and 66.7%. Small groups can support a record review; they do not justify a sweeping verdict on a rep or campaign.
Copy this booking-cohort worksheet
Use one header for the report:
- Question: weekly booking progress, scheduled-meeting attendance, or held-within-window result?
- Booking definition and scope: first meetings or follow-ups; included team, source and audience; duplicate rule.
- Selection: original booking-time interval and reporting time zone.
- Observation: cutoff timestamp, follow-up window and endpoint rule.
- Population: total bookings; younger bookings excluded from a mature comparison; missing original timestamps.
For each booking, keep its stable reference, original booking timestamp, original and latest scheduled starts, linked replacement history, verified attendance result, when that result became known, and next owner. Add the deadline for its follow-up window if you use one.
The distinction between when a meeting happened and when its outcome became known lets you reproduce an earlier snapshot. If your system does not preserve that history, say the report is a current restatement, not a recreation of what the team knew on Friday. Don’t invent historical timestamps to make the comparison work.
Use the report to assign work, not rush a verdict
Not-yet-due meetings need the normal preparation and confirmation process. Missing outcomes need a host check. Reschedules need continuity with the original commitment. Cancellations need their actual reason and any appropriate next step. None should be automatically relabeled as poor qualification.
If the original booking or call result is itself uncertain, the call-outcome completeness worksheet helps identify the missing evidence. Keep that repair separate from simply waiting for an already-confirmed future meeting.
Start with one recent booking group. Freeze its references, attach an honest cutoff, and show future and unresolved records beside the held count. Revisit those same bookings at the agreed observation point. You will have a report that explains what has happened—and a worklist for what still needs attention.
Navigate Your Cold Calls Like a Pro With Real Time A.I. Sales Coaching
