Part I close-outFrom Agreement Test to Architecture to Timing

What Part I Has Established

By the end of Chapter 3, a reader has three controls that the rest of the book assumes are already in place: a test for whether a material assumption is decision-ready, a map of how the budget's components connect to each other, and a calendar that says when each build pass happens and who owns it. None of these controls produce a single dollar of revenue or a single line of cost — that work starts in Part II — but every dollar built from here forward will be judged against them.

Integrated Case — Azure City Resort Opens Its Budget Season

Azure City Resort's GM calls the budget kickoff meeting eleven weeks before the new fiscal year. Before any department submits a number, the finance lead walks the room through three things. First, the Budget Agreement Test: every material line this year must carry a source, a named assumption owner, an action owner, and a review trigger — last year's practice of submitting “last year plus a percentage” will be returned, not approved. Second, the architecture map: rooms and F&B assumptions will feed departmental workload and labour before departmental expense is built, departmental profit will roll into undistributed expenses and GOP, and capital, cash, and the balance sheet will connect to that operating result rather than being built separately at the end. Third, the calendar: five controlled passes, each with a deadline and an owner, ending with an approved baseline that immediately becomes the first rolling forecast update under Chapter 27's governance. Nothing in this scene is a financial calculation — it is entirely a management control — and it is the reason Azure's later chapters can trust the numbers that arrive from Part II onward.

Self-Understanding Checklist

• I can state the five-question test from memory and apply it to a real budget line, not just recite it.
• I can name the owner of at least three material assumptions in my own property's current budget.
• I can draw or describe the eight architecture components and show how two of them connect.
• I know which of the eight components my own role is accountable for.
• I can name the five controlled build passes and the deadline for each.
• I know who in my organization owns the decision to approve, condition, or return a budget line.
• I understand how the approved baseline hands off into the rolling forecast, and I know it is not the same document.
• I can explain, in one sentence, why a budget that balances can still fail the Budget Agreement Test.

Portfolio Task — Produce a Part I Readiness Pack

Using DC-01, DC-02, and DC-03, build a one-page readiness pack for your own property or for Azure City Resort: a list of the current year's five most material budget assumptions with source, owner, and review trigger; a one-page architecture map showing how those assumptions connect through to GOP, capital, and cash; and a build calendar with five dated passes and named owners. This pack is the input every later part of the book assumes you already have.

Bridge to Part II

Part II turns the architecture and calendar from Part I into the hotel's first real numbers: rooms, food and beverage, banquets and events, and other operated revenue. Every revenue assumption built from here forward must still pass the Budget Agreement Test, and every revenue chapter's forecast-handoff section will assume the calendar established in Chapter 3 is already running.