Chapter 39 — Instructor Material
Teaching Notes
Where this chapter sits. Part VIII, second-to-last. Students arrive having built a complete business plan and having spent Part VII learning to read the numbers. This is the chapter where the numbers are turned around and pointed at the reader. Plan for a heavier emotional register than any other session in the course, and plan for it deliberately rather than being surprised by it.
The one-sentence thesis. Telling the difference between a problem you can fix and a business that is over is a technical skill with a procedure, and the cost of not having the procedure is not a wasted quarter — it is the option set you had at the start of the quarter.
Common misconceptions, in the order they surface
1. "Bankruptcy wipes out what you owe." The most common and the most consequential. Students consistently believe that a business filing protects the owner. It does not. The automatic stay protects the debtor, and a personal guaranty is a separate obligation of a separate person. Drill this until it is automatic; a class that leaves with only this is a class that got its money's worth.
2. "The turnaround is always worth trying." It is cheap in capital and expensive in the two things a distressed restaurant has least of: management attention and runway. Students want to run the turnaround because it is the action that feels like competence. Case Study 2 exists specifically to break this.
3. "Waiting gives you more information." It does not. By month five you know what month eight will tell you. Waiting converts information you already have into options you no longer have. Figure 39.4 is the visual for this and it is worth putting on the board and leaving there.
4. "We'll sell the equipment." Students routinely budget an exit against equipment proceeds. Equipment is bought new and sold at forced-sale prices, and the proceeds usually belong to a secured lender. This is the fastest way to demonstrate why the closure floor must exist as cash.
5. "Cutting labor is the responsive move." Exercise 39.26 is built around this. Cutting dish and prep shifts moves work to more expensive positions, raises ticket times, degrades prep discipline (which raises food cost), and creates a sanitation exposure. A labor cut can raise prime cost.
6. "You tell the staff last so they don't quit." Somebody in every class will advocate this, usually with real conviction and often from experience. Do not shut it down; make them argue it, then have the room work out the operational consequences. The argument wins itself.
7. Confusing the two Chapters. Students will say "Chapter 11" and mean either the Bankruptcy Code or this book's food-costing chapter. Establish the "Chapter 11 bankruptcy" / "Chapter 7 bankruptcy" convention in the first two minutes and hold everyone to it, including yourself.
The hardest point to teach
That a concept problem and a math problem are indistinguishable from inside the business, and that one number separates them.
Students grasp execution problems immediately — prime cost is over, go fix prime cost. They struggle badly with Step 5, because it requires holding two counterfactuals at once: what if the room were full? and what would full even mean, sustainably, in February?
The failure mode in class is that students treat "not enough guests" as a single diagnosis. It is two, and they have opposite treatments: a concept problem routes to a pivot (which can work), a math problem routes to restructuring or closure (where a pivot burns your last cash).
What works: do it as arithmetic on the board before any discussion. Put up a room — seats, turns, check — and a fixed base, and make the class compute break-even covers as a percentage of physical capacity. Then move the rent up in \$10,000 increments and watch the percentage climb. Somewhere around 80% of capacity the room goes quiet, and that is the moment the concept lands. Case Study 2's 12.7% occupancy is the same lesson with a story attached; teach the arithmetic first and the story second, never the reverse.
Demonstration idea — "The Week You Looked"
A forty-minute in-class exercise that reliably produces the chapter's central insight.
Setup. Hand every student the same thirteen-week cash forecast (Figure 39.5, or a variant). Divide the room into four groups and give each a different week at which they are permitted to start acting: week 1, week 4, week 8, and week 11. Each group has the same restaurant, the same trough of \$15,540, and the same menu of instruments (§39.3 turnaround, §39.4 pivot, §39.5 restructuring).
The constraint. Each group must produce (a) a specific plan, (b) the cash it generates by the trough, and (c) a one-sentence version of the conversation they will have with the landlord.
What happens. Week 1 covers the trough with room to spare and negotiates from a current position. Week 4 covers it barely. Week 8 cannot cover it and discovers that their landlord conversation is now a default conversation. Week 11 discovers there is nothing left to plan and spends its time arguing about whose fault it is — which is exactly what happens in real restaurants, and worth naming out loud when you debrief.
The debrief question: Nothing about the restaurant differed between the four groups. What differed? Then put Figure 39.4 back on the board.
Timing: 5 min setup, 20 min group work, 15 min report-out and debrief.
Timing and sequencing
A 3-hour session, or two 90-minute sessions:
| Block | Minutes | Content |
|---|---|---|
| Framing and the three diagnoses | 20 | §39.1 table; establish the bankruptcy naming convention |
| Figure 39.1 on the board | 20 | the downside P&L; run it backward to 0.56 covers of cushion |
| Step 5 arithmetic drill | 25 | break-even covers vs. physical capacity, rent moved in increments |
| The Week You Looked | 40 | the demonstration above |
| Break | 10 | |
| Turnaround: annualized vs. realized | 20 | Figure 39.6; why the right column is the one that matters |
| Restructuring and the counterparty's alternatives | 25 | Figure in §39.5; the \$18,000 / \$219,200 comparison |
| Bankruptcy structurally | 20 | the comparison table; the automatic stay; Case Study 1's scale arithmetic |
| Closing well | 25 | Figure 39.9; final pay; the T−10 argument |
| Personal guaranty and the good-guy clause | 15 | Figure 39.10; read Chapter 6 backward |
If you have only 90 minutes: the three diagnoses, Step 5 arithmetic, The Week You Looked, and the personal-guaranty section. Cut the bankruptcy detail to the single fact that the stay does not reach a guaranty. Assign §39.3–39.6 as reading.
Assessment notes
- Exercise 39.25 (read this P&L and find the leak) is the best single summative item in the chapter. It rewards students who defend a diagnosis against rivals rather than asserting one.
- Exercise 39.40 (the full Risk & Contingency section) is the natural take-home. Grade the closure floor hardest: students almost universally under-build it, and the omission is always the vendor line or the professionals.
- Exercises 39.32, 39.35, 39.37, and 39.39 are the judgment cluster. Grade them on whether the student put staff first and could articulate the operational reason, not only the moral one. A student who can only give the moral reason has not internalized the chapter.
- Watch for students who quote the "90% fail in year one" myth in an essay. It is a useful diagnostic of who read Chapter 1 and who read a blog.
A note on register
Some fraction of any restaurant-management class has already lived this, or is watching a parent or an employer live it. Teach it without melodrama and without cheerfulness. The two failure modes are treating closure as a horror story (which produces fatalism, and fatalism is what the failure-rate myth already causes) and treating it as a brisk technical matter (which is false and reads as callous).
The register that works is the one the chapter uses: this is a serious event that happens to competent people for ordinary reasons, it has a right way to be done, and doing it right is a professional skill you can learn before you need it. If a student discloses that they are living it, have the name of a small-business support organization ready and do not make them the class example.