Recipe 40 - The To-Be Register Audit: Turn Every Forecast Assumption Into a Ledger You Can Defend

Turn Every Forecast Assumption Into a Ledger You Can Defend

From The Spiral Sales Office Recipe Vault | By Paul Woodley

The To-Be is the only line in a hotel forecast with no system record behind it. It is the only place where a number can be entered without a confirmed booking, a named event, or a contracted commitment to support it. And because of that, it is the place where wishful thinking hides most easily, and where most forecast disasters begin.

Recipe 40 turns the To-Be from a plug number into a clean ledger of named, evidenced, owned assumptions. And it strips out the ones that are really just a gap someone needed to fill.

What This Recipe Makes

A To-Be register audit that scores every line against eight required fields, applies a four-question test to each entry, flags plug numbers, and identifies zero-check failures, leaving a clean register you can submit with confidence and explain under scrutiny.

• Head Chef: DOSM with Director of Catering and Events
• When to Cook It: Monthly before submission; again mid-month if a large piece of business changes
• Ingredients: Your current To-Be lines with whatever detail exists behind each; the funnel for the same periods; the budget gap by month and stream

The Eight Fields Every To-Be Line Must Carry

The prompt applies a non-negotiable standard to every line in the register. A To-Be that cannot satisfy all eight fields is not a forecast assumption. It is a pipeline entry that has wandered into the wrong column.

1. Account name - or a precisely defined historical pattern
2. Consumption date or period - with meal periods where relevant for catering lines
3. Revenue stream - food, beverage, rental, AV, or other
4. Dollar value - plus any offsetting risk
5. Evidence - a named opportunity, a booking curve, a repeat event, a market driver, or documented customer intent
6. Stage and probability - using the hotel's own status rules
7. Decision or trigger date - when it converts, changes, or comes out of the forecast
8. Owner and one observable next action - the person responsible and the specific thing they are doing about it this week

The Four-Question Test

After the eight-field scorecard, every To-Be line faces four questions that must be answerable from the information provided, without opening another file:

• What is it?
• Why is it likely?
• When will we know?
• Who owns the next action?

Any line that fails this test belongs in pipeline, not in the forecast. The prompt lists these separately with their total dollar value, which is the forecast's real exposure in plain language.

The Plug Detector

The plug detector is the output that most often changes a forecast on the spot. When a To-Be line's dollar value suspiciously equals the remaining budget gap for that month or stream, the prompt flags it explicitly. That is not forecasting. That is arithmetic run backwards from the answer someone wanted.

It is extremely common. It is obvious once you look for it. And almost nobody looks for it in a self-review.

The Zero Check

The zero check identifies any month or stream where definite bookings already exceed budget but a To-Be is still being carried. A To-Be in a month that is already over budget serves no purpose and creates a double-count risk. The prompt flags it and recommends removal.

Where the Output Goes

The forecast submission, after the failing lines have been moved to pipeline or closed. The twice-weekly catering rollup, where the surviving To-Be lines become the working assumption list. The conversation with whoever owns each surviving line, where the next action is assigned and a checkpoint is set.

The Mirror

Look at your current To-Be register. Pick the largest single line. Can you answer all four questions from memory, without opening another file? If not, that line is currently supporting your forecast with information you do not actually have. Recipe 40 is how you find out how many of your lines are in the same position.

A Note on Data Handling

Confirm what your employer, owner, brand, and management company permit before pasting forecast data into any AI platform. To-Be register data with account names, revenue values, and event detail may be commercially sensitive. When in doubt, use account codes rather than names. Every output is a starting position. The forecast commitment still belongs to you.

Your Next Step

Pull your To-Be register exactly as it currently exists, gaps and all, before your next forecast submission. Paste it into Recipe 40 along with the funnel for the same periods and your budget gap by month and stream. Let the audit show you what you are actually carrying versus what you have evidence to support. Then submit the number you can defend, not the one that closes the gap on the spreadsheet.

A forecast that reconciles to evidence is not the same as a forecast that reconciles to budget. Recipe 40 tells you the difference.

Paul Woodley | The Spiral Sales Office