Instructor Guide — Overview

Restaurant Management: Behind the Pass is a forty-chapter textbook for people who know food and do not yet know the business. This guide is for whoever has to teach it.

1. What this book is trying to do

Most restaurant management texts are organized around functions — marketing, operations, finance, human resources — and read like a management survey that happens to mention food. This one is organized around the sequence in which an operator actually confronts the decisions, from "should this restaurant exist" to "what happens to me after it does."

The book has one central claim, stated in Chapter 1 and re-earned in every part:

The food is the easy part.

Not because cooking is easy — because a person who can cook has already solved the hardest creative problem and is about to discover that the business is a different discipline entirely, one nobody taught them, one that will decide whether the cooking ever reaches anybody. The book's job is to teach that discipline to someone who did not come looking for it.

Four other themes run through every chapter, and each chapter advances at least two:

2. The one thing to know before you teach Chapter 1

The book opens by correcting a statistic that the students have already heard.

"Ninety percent of restaurants fail in the first year" — or the softer, more respectable-sounding "sixty percent fail in year one" — is a myth. It is repeated in trade press, in business school lectures, and in the trailers of documentaries about restaurants. It is not what the research shows. The peer-reviewed work puts first-year failure closer to one in four — roughly 26–27% — with cumulative failure approaching 60% over three years.

Chapter 1 names the myth, corrects it, and keeps the stakes, because the corrected figures are sobering enough. Do not soften this in class, and do not let it pass as trivia. It is the book's opening demonstration of its own method: a number everybody repeats, traced to its source, found wanting, and replaced with the defensible one. Students who absorb that move in week one apply it for the rest of the course. Students who miss it will produce business plans full of numbers they read somewhere.

If a student pushes back — and one usually does, because the myth is everywhere — the productive response is to ask what a first-year failure rate of 90% would imply about how many restaurants would have to open each year to sustain the number that exist. The arithmetic answers itself.

3. Structure

Forty chapters in eight parts. Each part is a coherent unit of two to seven chapters and can be taught as a module.

Every chapter contains seven files: the chapter itself (index.md), an exercise set, a quiz, two case studies, key takeaways, and further reading. The exercises and quizzes are substantial — most chapters carry 25–35 exercises — and are meant to be assigned selectively, not exhaustively.

4. The progressive project — the reason the book works

Every chapter ends with a 🍽️ The Business Plan checkpoint contributing one section of a real business plan. Across forty chapters the student assembles a complete financing package for a restaurant they invented in Chapter 2.

This is not an add-on. It is the assessment the book is designed around. See rubrics/business-plan-rubric.md for the full grading apparatus, including the four graded checkpoints and the eleven arithmetic ties.

The book demonstrates the project with a constructed running example, Bellwether — a 68-seat chef-driven neighborhood American restaurant with a wood-fired hearth, in a gentrifying warehouse district of a mid-size Midwestern city. Bellwether is explicitly labeled as constructed everywhere it appears, and its numbers are internally consistent across all forty chapters: the same P&L, the same lease, the same schedule, the same cost cards. That consistency is deliberate and pedagogically load-bearing — the book is modeling the thing it is asking students to do.

A caution worth passing to students. Bellwether's plan is coherent, not correct. Several chapters deliberately catch it out: Chapter 31 finds six places where the plan contradicts itself, Chapter 32 finds that break-even sits well above the estimate the business plan carried, and Chapter 33 finds that the restaurant runs out of cash in week two despite being profitable on paper. Students should be told early that the running example is going to be shown to be wrong, because otherwise they read the first thirty chapters as a model answer.

5. The three other anchors

Besides Bellwether, three scenarios recur across the book. Each is constructed and labeled. Each returns in five or six chapters, seen from a different discipline each time — which is the book's main structural device for showing that these problems are not departmental.

The Hearth Chicken — the recurring costing lab. A single dish, costed at \$8.35 plus a 2% waste allowance = \$8.52**, priced at **\$29, yielding 29.4% food cost and a \$20.48 contribution margin. It appears in Chapter 11 as a cost card, Chapter 12 as a Star on the menu-engineering matrix, Chapter 13 as a purchasing and yield problem, Chapter 14 as a station and execution problem, and Chapter 24 as a pricing decision. Teaching tip: put the same dish on the board five times across the term and ask what changed. Nothing about the chicken changed. The question being asked of it did.

The Friday night — the second Friday in October. 142 covers on the books including a 40-top at 6:30. The grill cook does not show at 3:40 p.m. The sous is already on a double. The schedule was written to a 30% labor target. It returns in Chapters 14, 17, 19, 21, 22, and 33 — as a kitchen problem, a hiring problem, a labor-model problem, a leadership problem, a service problem, and finally a cash problem. It is the best single vehicle in the book for the claim that the numbers and the floor are the same subject.

The surprise inspection — Tuesday, 10:40 a.m., mid-prep. Walk-in at 46°F. Raw chicken over ready-to-eat greens. Sanitizer at 50 ppm. No thermometer in the reach-in. One employee without a food-handler card. Result: re-inspection in ten days, not a closure — but one more finding and the doors close at noon. It returns in Chapters 13, 14, 22, 25, and 34, and it is grounded in the FDA Food Code, with the standing caveat that the Food Code is a model code and every jurisdiction adopts and amends it differently.

6. The signature device

🧾 Read the Numbers — a six-field block built around a single artifact: a cost card, a menu-mix report, a schedule, a P&L, an invoice, an inspection report.

There are more than a hundred of these across the book, and they are the highest-value teaching material in it. The pedagogical move to steal: teach the artifact before the concept. Put the document on the screen, ask the room what it shows, let them get it partly wrong, then ask what it does not show. The WHAT IT DOESN'T field is where students learn that every number is an answer to a question somebody chose to ask.

Seven other callouts recur: 👨‍🍳 On the Line (what this looks like during service), 🧮 Run the Numbers (a worked calculation), ⚠️ Where the Money Leaks (the specific failure mode), ⚖️ Code and Compliance (the legal or regulatory constraint), 🤝 Hospitality, 🍽️ The Business Plan (the checkpoint), and 🔍 Check Your Understanding (a short self-check, ideal for cold calls).

7. The four learning paths

Not every reader needs all forty chapters in order. The book supports four routes, and they are also four ways to differentiate a course:

In a mixed-experience section, assigning path-specific reading for two or three weeks and then having each group teach the others is the highest-yield structure this material supports. The Beverage and Small Format groups in particular will surface things the whole-class sequence flattens.

8. What is deliberately not in this book

Say these out loud early; they will otherwise be read as omissions.

• No program code. No Python, no spreadsheet macros, no software. Every model in the book is a table and an arithmetic relationship the reader could rebuild by hand. Appendix F gives the worksheets as specifications rather than files, for the deliberate reason that an operator who understands the worksheet can rebuild it in whatever tool they end up with — and the tool changes every four years.
• No named fictional characters. The book uses roles: your sous chef, the general manager, the landlord. The spine is a business, not a cast. This is a house convention and it is worth explaining, because students sometimes read the absence of characters as coldness. It is the opposite: the book refuses to let a decision be excused by a personality.
• No invented statistics, statutes, or studies. Every claim is one of three tiers: verified canonical sources (FDA Food Code, FLSA, ADA, SBA 7(a), BLS and NRA as institutions); attributed but unpinned claims, marked as such; and constructed illustrations, labeled as constructed. When students ask why a number in the book has a caveat attached, the answer is that the caveat is the lesson.
• No promise that any of this works. The book's recurring closing move is a section on what the technique cannot do. Chapter 39 — "When It's Not Working" — is not an appendix to the optimistic material. It is the chapter the honest version of this book has to have.

9. Prerequisites, and who is actually in the room

Formal prerequisites: none. The arithmetic never exceeds percentages, ratios, and weighted averages, and Appendix A collects every formula in one place.

Actual prerequisites: a calculator, and the willingness to use it. The obstacle in this course is never conceptual difficulty. It is that a substantial fraction of students entered food because they preferred it to a spreadsheet, and will avoid the arithmetic if permitted to. Do not permit it. The single most effective structural decision an instructor can make in this course is to require that every claim about money be accompanied by the calculation, from week one, in every context — discussion, case study, and plan.

Expect a wide experience spread. In a typical section, a third have worked in restaurants, a third have worked in food service adjacent to restaurants, and a third have not. See rubrics/participation-rubric.md §7 for handling the asymmetry, which if left alone will silence the inexperienced third within two weeks.

10. What is in this instructor guide

The chapter notes are the part to read. They are written by whoever wrote the chapter, they name the specific misconceptions that chapter provokes, and several of them contain a single fifteen-minute board demonstration that carries the whole session. Chapter 31's cancelling-errors demonstration and Chapter 33's week-two cash trough are the two best in the book.

11. Three suggestions from the way the book is built

Teach the arithmetic in public. Every worked example in this book foots. Put one on the board, get it wrong on purpose in a way the class can catch, and let them catch it. The habit you are building is not computation; it is the expectation that a number can be checked.

Never let a percentage stand alone. The book's most-repeated technical rule is that dollar figures are canonical and percentages are rounded displays. A student who writes "labor is 32.3%" and then back-computes \$500,650 from it has introduced an error that will propagate through nine subsequent sections of their plan. This happens in every section, every term. Name it in week two.

Assign Chapter 39 before students think they need it. "When It's Not Working" reads, out of sequence, as the depressing chapter. In sequence it is the one that makes the rest honest — and students who read it after they have built a plan they are proud of get considerably more out of it than students who read it as a warning at the start.