Recipe 33 - The Volume Contract Actualization Check: Make Sure Negotiated Production Is Recorded Before It Disappears Into the Wrong Bucket

Make Sure Negotiated Production Is Recorded Before It Disappears Into the Wrong Bucket

From The Spiral Sales Office Recipe Vault | By Paul Woodley

There is a specific kind of month-end surprise that belongs exclusively to the negotiated transient segment: a conversation that begins with the segment looks soft this month, follows with a review of the data, and ends with the discovery that the business did not go anywhere. It simply was not recorded against the volume contracts in the sales system, so it never appeared in the pace report, and the narrative was written about a performance problem that was actually a recording gap.

Recipe 33 prevents that conversation by closing the month before the reporting package is assembled, not after it is presented in a critique.

What This Recipe Makes

A reconciliation of negotiated and volume-contract transient production between the revenue or PMS side and the sales system, identifying invisible production, recording discrepancies, and the pattern behind any gap, with a task list and a narrative flag ready for whoever asks whether the segment is genuinely soft.

• Head Chef: Business Travel Sales Manager with Revenue Manager
• When to Cook It: Monthly at close, before the reporting package is assembled
• Ingredients: Actual negotiated production from the revenue or PMS side for the closed period; the corresponding volume-contract or negotiated-account records in the sales system for the same period

The Five Outputs This Prompt Returns

1. The Reconciliation - For every account, actual production from the PMS versus what has been recorded in the sales system. Three categories are flagged:
   Accounts with actual production and no corresponding record in the sales system: invisible production that is not showing up in the pace report or segment narrative
   Accounts where the recorded figure differs materially from actual: a data-entry or timing problem that is distorting the segment picture
   Accounts with a contract record but zero production: either a dead account still occupying a rate code, or production landing under a different rate code and being attributed to another segment
2. The Materiality Ranking - Every discrepancy ranked by room nights and revenue, so the largest gaps are addressed first. A small actualization gap in a low-volume account matters less than a large gap in a major producer that is pulling the segment narrative in the wrong direction
3. The Pattern - Whether the gap is concentrated in particular accounts, a particular rate-code family, or a particular step in the actualization process. Each pattern points to a different fix: account-level outreach, rate-code mapping, or a coordinator process correction
4. The Task List - Specific actions: what needs to be entered, corrected, or investigated, in priority order, with the person responsible for each
5. The Narrative Flag - If the reconciliation reveals a gap, one sentence the DOSM can use in the critique narrative to explain that the segment's reported performance reflects a recording gap rather than a genuine revenue shortfall. This is the sentence that prevents ownership from drawing the wrong conclusion from an accurate-looking but incomplete number

Why This Runs Before the Reporting Package Is Assembled

The reporting package becomes the critique narrative, and the critique narrative becomes the ownership's understanding of the property's negotiated transient performance. If the package is assembled from unreconciled data, the narrative may be built on a number that does not reflect what actually happened in the month.

Running Recipe 33 at close, before the package is built, means the narrative is based on the reconciled number. Any gap that existed is either closed through actualization or explained in the text. Either way, the critique conversation starts from an accurate position rather than from a misunderstanding that requires correction once the meeting is already underway.

The Rate Code Landing Problem

One of the three flag categories in the reconciliation is production landing under a different rate code than the one associated with the negotiated account record. This is a common actualization failure that is easy to miss: the revenue shows up in the PMS but in the wrong segment bucket, making the negotiated segment look weak while another segment looks stronger than it should. The overall room count is correct; the attribution is wrong. Recipe 33 catches this before it becomes a story about segment performance that requires unwinding in the next month's critique.

Where the Output Goes

The month-end close checklist, where actualization becomes a standard pre-submission step rather than an occasional investigation triggered by an unexplained soft month. The negotiated transient narrative field in the workbook, where the reconciled number becomes the basis for the commentary. The process conversation with the Revenue Manager and sales coordinator, where the pattern finding from step three becomes a specific workflow correction for the following month.

The Mirror

In the last time your negotiated transient segment showed soft in a month-end report, did you verify that the production had been fully actualized in the sales system before concluding the segment had underperformed? If not, the soft month may have had a recording answer that was never found. Recipe 33 builds the habit of looking before drawing the conclusion.

A Note on Data Handling

Confirm what your employer, owner, brand, and management company permit before pasting negotiated account production and system records into any AI platform. Named account room-night figures and rate-code mapping data may be commercially sensitive. When in doubt, use account codes rather than company names. Every output is a starting position. The data corrections and the narrative decisions still belong to you.

Your Next Step

Add Recipe 33 to your month-end close checklist as a standing step before the reporting package is assembled. Pull actual production from the PMS and the corresponding sales system records. Run the reconciliation. Close the gaps or explain them in the narrative. Then submit a package where the negotiated transient section reflects what actually happened in the month.

A soft segment that is only soft on paper is a recording problem. Recipe 33 finds it before anyone presents it as a performance problem.

Paul Woodley | The Spiral Sales Office