Chapter 24 — Instructor Material

Revenue Management: Covers, Seat Turns, RevPASH, and Pricing the Room Part V — Service: Running the Room

Teaching Notes

Where this chapter sits

Chapter 24 is the revenue-side counterpart to Chapter 19's labor material and the analytical counterpart to Chapter 22's operational one. Chapter 22 taught students how a dining room is run; Chapter 24 teaches them what it is worth per hour. It is also the chapter where the running business plan's oldest open item — the \$139,240 revenue gap left standing since Chapter 1 — finally closes, which makes it a natural mid-course assessment point.

Students arrive having been trained by Chapters 1 through 23 to think in costs. This is the first chapter in the book that asks them to raise the top line, and many of them will find it disorienting in a specific way: they have been taught, correctly, that a restaurant dies of cost drift, and they now have to hold simultaneously that the fastest route to profit at Bellwether is ten more covers on a Tuesday.

Prerequisites that actually matter: Chapter 1 (the \$1,410,760 estimate, cover, average check, the fixed labor floor), Chapter 14 (the hearth at 28 items an hour, wave-splitting creates zero capacity), and Chapter 19 (labor modeled as a percentage). A student who has not internalized Chapter 14 will propose duration solutions all the way through §24.5 and cannot be talked out of it, because the constraint is invisible from the dining room.

The single hardest point to teach

That RevPASH is not a number to maximize.

Every student who understands the metric will, within about ten minutes, try to optimize it — and the metric will immediately tell them to do something stupid. In the Business Plan checkpoint, adding Bellwether's patio lowers on-premise RevPASH from \$12.09 to \$11.60 while adding \$64,800 of revenue. Students find this genuinely upsetting. Some conclude the patio is bad. Others conclude the formula is broken.

The resolution is worth twenty minutes of class time because it is a transferable statistical point, not a restaurant point: RevPASH is a ratio with capacity in the denominator, so any change that adds capacity dilutes it. It is a comparison instrument within a fixed capacity — this Tuesday against last Tuesday, this hour against that hour, this room against that room. It is not an objective function, and capacity decisions are contribution decisions.

The same trap has a second door: putting takeout revenue in the numerator. The chapter shows that dividing the plan's \$1,550,000 headline by its 127,248 on-premise seat-hours gives \$12.18, a number that is simply false because \$74,440 of it never touched a seat. Students who have worked in restaurants during the delivery boom find this one immediately convincing, which makes it a good way in to the first point.

Second hardest: getting students to accept that the cost of a mis-seated deuce or a no-show depends entirely on whether anyone wanted the seat. They want a number. The honest answer is "\$92 on Saturday, zero on Tuesday," and that conditional structure is the thing being taught.

Common misconceptions

1. "More covers is always better." Chapter 24 is where this dies. Saturday brunch does 77% more covers than Tuesday dinner and \$212 less revenue. Put those two lines on the board before you introduce any formula and let students sit with it. It is the single most efficient two minutes in the chapter.

2. "Seat turns is basically RevPASH." Exercise 11 exists to kill this: an 84-seat restaurant at 1.9 turns across eleven hours returns \$3.63; a 40-seat room at 1.2 turns across four hours returns \$20.40. Same industry, same word, factor of 5.6.

3. "Shorter dine time = more money." Students reach for this instantly and it is wrong at Bellwether on every single night. Walk the constraint table in §24.5 with them: three nights are demand-constrained (a faster table produces an emptier room), two are hearth-constrained (a faster table hands the kitchen a party it cannot cook for). Duration savings pay only where the seat is the binding constraint, and at Bellwether it never is.

4. "A discount fills slow nights." The unfenced-discount callout in §24.6 quantifies the leakage: \$1,610 a week to Friday and Saturday guests who were already coming. The insight students need is sociological rather than financial — your social-media followers are your regulars, and your regulars come on the busy nights. Once they see that, fencing stops being jargon.

5. "Surge pricing is just efficient, people need to get over it." Economics students in particular arrive with this and it is not stupid — the efficiency argument is genuinely strong. Do not flatten it. Let them make it well, then introduce the observation that peak restaurant demand is generated by people whose schedules are set by their employers, so a peak surcharge charges the most to those with the least flexibility. The point is not to produce agreement. It is to produce a student who can state both cases and who understands that the operator's practical constraint — guests punish pricing they find insulting far out of proportion to the dollars — makes the conservative choice correct even for a pure profit-maximizer.

6. "The bridge should be built from the better dollars." This is the sophisticated version of the mistake, and strong students make it. Bridge B's dollars are better: an incremental dinner cover carries almost no additional cost. The chapter still rejects it, on the grounds that it is the contingency. Students who can articulate why a plan may not bank its own recovery instrument have understood the most transferable idea in the chapter, and it is not really about restaurants.

7. "No-shows are the big problem." They are not, at Bellwether: \$14,352 a year against \$28,704 lost to table mix. No-shows generate more emotion than any other topic in restaurant operations and are rarely the largest hole in the room. Use the comparison to teach proportionality in policy design.

A demonstration that works

The seat-hour count, done live, before anything else.

Do not open with the formula. Open by asking the room: "How much inventory does this restaurant have?" You will get food answers — the walk-in, the wine list, the freezer. Write them up. Then draw 68 chairs and five hours on the board and count the seat-hours: 340, 1,700, 116,688. Ask what happens to an unsold one at 10:01 p.m.

Then — and this is the part that lands — ask what it cost. Rent, insurance, the loan on the hearth, the salaried manager, the dishwasher who has to be there at 9:40 whether you did 40 covers or 140. All of it committed before anyone walked in.

Students who have worked in restaurants often visibly re-file several years of experience at this point. It takes about eight minutes and it earns the rest of the chapter.

Follow-on demonstration, if you have a second session: the arrival-curve exercise (Exercise 24). Give teams the plan's Saturday grid — seatings of 14 / 26 / 34 / 31 / 18, hearth firing 11 / 24 / 32 / 32 / 24 against a rated 28 — and one instruction: raise the cover count without exceeding 28 in any hour. Most teams find something in the 130s. Then ask the killer follow-up: what has to be true at the host stand for your grid to happen? The answer — that somebody has to cap the 7:00–9:00 inventory and decline a 7:30 walk-in — is where the exercise becomes a management lesson rather than an arithmetic one.

Timing

For a fifteen-week semester course meeting twice weekly, this chapter comfortably fills three sessions, and can be compressed to two.

If you have only two sessions, merge §24.7 into session two and give the whole of session three to pricing and the bridge — those are the two places where discussion earns the most.

For a one-day professional workshop: the seat-hour demonstration, the RevPASH decomposition, the constraint table from §24.5, and the bridge decision. Skip the table-mix arithmetic and hand out Exercise 21 as homework.

Assessment notes

• Exercises 10, 12, 15, and 17 are the computational core. A student who can do all four can do the chapter. Exercise 17 is the sneakiest — the "identical by construction" observation is the point, and weaker students will report the two \$14.86 figures as a finding rather than as a flaw.
• Exercise 38 (rebuild the plan on Bridge B and then argue against it) is the best single summative item in the chapter. It requires the arithmetic, the hearth constraint, the distribution question, and the contingency argument all at once, and it cannot be answered from the summary.
• Exercise 35 is the ethics item. Grade it on whether the student identifies the case the test handles badly. A student who declares the fairness problem solved has not done the exercise, however elegantly they wrote it up.
• Watch for arithmetic that does not resolve. This chapter's whole posture is that numbers foot. Require the decomposition check on every RevPASH answer: utilization × (check ÷ dine time) must equal revenue ÷ available seat-hours. If it does not, something upstream is wrong.
• Exercises 31 and 33 (the pre-shift briefing and the host's manual page) assess voice and judgment rather than computation and are excellent for students on the Managing track.

Note on the two case studies

Case Study 24.1 (ticketed dining) and Case Study 24.2 (the 2024 dynamic-pricing episode) are a matched pair: one shows revenue management working, the other shows it being rejected by the public before it was even tried. Teach them together if you can. The synthesis question — why did prepaid ticketing at \$300 a head provoke no backlash while a possible fifty-cent lunch differential provoked a national one? — is the best discussion prompt in the chapter and appears below.

Both case studies are built on public record. Be careful with students who want to quote no-show statistics from Case Study 24.1: those figures are the founders' public claims, not audited findings, and the case study says so. That distinction is itself worth teaching.