Recipe 43 - The Pace Deficit and Pickup Timing Calculator: The Two Numbers That Decide Whether a Forecast Is Credible

The Two Numbers That Decide Whether a Forecast Is Credible

From The Spiral Sales Office Recipe Vault | By Paul Woodley

A forecast is a claim about the future. The pace deficit is the test of whether that claim has anything behind it. And the coverage test is the question nobody in most funnel reviews asks out loud, even though it is the only question that actually matters: is the pipeline large enough to close the remaining gap at the hotel's real conversion rate?

If the answer is no, there are exactly two honest responses. The forecast comes down, or the activity goes up. There is no third option. Recipe 43 produces both numbers before the meeting starts, so the conversation begins from truth rather than from optimism.

What This Recipe Makes

Two critical numbers computed every forecast cycle: the pace deficit in dollars and room nights, and the coverage test result that tells you whether the pipeline can close it. Plus two supporting outputs: a stalled-pipeline total and a timing check that tells you which months are still inside a workable booking window.

• Head Chef: DOSM
• When to Cook It: Every forecast cycle, and before every funnel review
• Ingredients: The team's remaining goal for the period; the funnel by status with value, decision date, and days in current status; historical booking-window data by segment if available

The Four Outputs This Prompt Returns

1. The Pace Deficit - What the team needs for the period minus the value of status one and two opportunities. Stated in dollars and in room nights where both are available. This is the number that tells you how much revenue is genuinely at risk of not closing, as distinct from the total pipeline volume which includes business at every probability level
2. The Coverage Test - Whether the status three pipeline is large enough to close the remaining deficit at the hotel's historical conversion rate. If the prompt does not have the conversion rate, it asks for it. If the answer to the coverage test is no, the prompt says so directly. There is no softened version of this output
3. The Stalled Pipeline Total - Every opportunity sitting unusually long for its current stage, with the total dollar value of stalled pipeline currently supporting the forecast number. Opportunities do not usually die from rejection. They die from silence, and silence is invisible in a volume report while the dollars sit there quietly holding up a number they no longer deserve
4. The Timing Check - For each remaining gap month, a comparison of time left against the typical booking window for the segments that would fill it. Which months are still inside a workable window and which are past the point where prospecting activity can realistically produce results in time

Why This Is Arithmetic Nobody Does Before the Meeting

The pace deficit is a calculation available to every DOSM from data that is already in the system. It takes five minutes to compute. And it is almost never computed before a funnel review, because the number it produces is sometimes uncomfortable and because the question it answers is easier to leave implicit than explicit.

Recipe 43 makes it explicit before the meeting rather than during it. The DOSM who walks into a funnel review already knowing the pace deficit, the coverage result, and the stalled pipeline total is leading a different conversation from the one who discovers those numbers by working through the agenda.

The Timing Check Protects Against Wasted Effort

Assigning prospecting activity against a month that is already inside its booking window is not diligence. It is theatre. A corporate group that typically books six weeks out cannot be prospected into a month that closes in four weeks, regardless of how many calls are made.

Knowing which months are still workable and which have closed their realistic window tells the team where to focus energy in a way that can actually change the outcome. Recipe 43 produces that read as part of every cycle.

Where the Output Goes

The forecast build in Recipe 39, where the pace deficit informs the pickup assumptions. The biweekly funnel review, where the coverage test and stalled pipeline total drive the action list. The weekly revenue strategy meeting, where the timing check tells the RM and DOSM which need periods are still actionable. The honest answer in the monthly critique when the question is whether the team can make the number.

The Mirror

What is your current pace deficit? If you cannot answer that question right now without pulling a report, you are managing the pipeline by volume rather than by probability. Recipe 43 is how you shift to managing by the number that actually matters.

A Note on Data Handling

Confirm what your employer, owner, brand, and management company permit before pasting pipeline and goal data into any AI platform. Remaining revenue goals and funnel data with opportunity values may be commercially sensitive. When in doubt, use percentage-of-goal rather than absolute dollar values. Every output is a starting position. The forecast decision and the activity assignment still belong to you.

Your Next Step

Before your next funnel review, export the pipeline with status and days in current status. Pull the remaining team goal for the period. Run Recipe 43. Walk into the review knowing the pace deficit, the coverage result, and which months are still inside a workable window. Then lead the conversation that matches the reality of those numbers.

A funnel review that does not calculate the pace deficit is a review of volume. A funnel review that does is a review of probability. Recipe 43 is the difference between the two.

Paul Woodley | The Spiral Sales Office