Part I introductionContext

Why Part I Opens the Book

Most hotel budgets fail for a reason that has nothing to do with arithmetic. The workbook balances, the totals tie, and the file is approved on schedule — and the budget still stops being useful the week the operating year begins, because no one can say where a number came from, who owns it, or what should happen when performance moves away from it. Part I exists to fix that before a single revenue or cost line is built. It establishes the test a budget line must pass to be decision-ready, the architecture that holds the whole model together, and the calendar discipline that turns a once-a-year file into a rolling management habit.

The Part I Decision Chain

The three chapters build on each other in a fixed order. Chapter 1 supplies the judgment test — source, assumption, owner, action, and review trigger — that every material number in the rest of the book must be able to pass. Chapter 2 supplies the structure that test lives inside: the eight architecture components that connect revenue, cost, capital, cash, and the balance sheet into one traceable model instead of twenty-nine disconnected worksheets. Chapter 3 supplies the calendar: when the budget season starts, who owns which pass, and how the approved budget becomes the rolling forecast that Chapter 27 later governs. A reader who skips Part I can still build a budget. A reader who completes it builds one that survives contact with the actual year.

What Each Chapter Teaches

Chapter 1 — Why Hotel Budgets Fail and How to Make Them Useful

Introduces the Budget Agreement Test and the five-question control — source, assumption, owner, action, review trigger — that separates a budget line that is ready for approval from one that is a placeholder. Uses Azure City Resort to show how the same test applies whether the line is rooms revenue, payroll, a marketing campaign, or a capital request.

Chapter 2 — Hotel Budget Architecture

Lays out the eight architecture components that hold the operational and financial budget together, and explains why finance coordinates the architecture while operators own the assumptions inside it. This is the chapter that keeps later parts of the book — revenue, departmental expense, undistributed expense, capital, and cash — from becoming twenty-nine unrelated spreadsheets.

Chapter 3 — Budget Process Architecture

Turns architecture into a calendar: when to start, who owns each of the five controlled build passes, and how the approved budget hands off into the rolling forecast that Chapter 27 governs later in the book. Establishes the timing discipline every later chapter's forecast-handoff section assumes.

How to Use This Part

Read all three chapters before building any revenue or expense schedule, even if the immediate task is narrower — the five-question test from Chapter 1 and the architecture map from Chapter 2 are referenced throughout the rest of the book without being re-explained. Use the DC-01, DC-02, and DC-03 companions to record your own property's assumption owners, architecture components, and build calendar before moving into Part II.