How Many Employees Should I Schedule Each Shift at My Cooking School in 2026?

What the seats-per-instructor ratio is and why it decides your labor line

Every staffing question at a cooking school collapses into one number you and your head chef have to agree on out loud: how many students can a single chef-instructor teach at the cooking stations without anyone standing idle, waiting for help, or handling a hot pan or a sharp knife unsupervised. That number is your ratio. It is a safety and quality floor, not a stretch target, and once it exists, the schedule stops being a negotiation and becomes arithmetic.

For a standard hands-on class — students at their own stations, knives out, burners lit — 10 students per chef-instructor is a defensible working floor. It gives the instructor enough room to demo a technique at the front, then walk the line and correct grip, heat, and seasoning at every station before the dish is ruined. Push to 14 or 16 in a hands-on format and the instructor stops teaching and starts triaging: the fast students get bored, the slow ones get skipped, and the food-safety oversight that justifies your insurance premium becomes theoretical.

The ratio moves with the format, and that movement is the part most owners miss. A demonstration class, where students watch the chef cook and then eat, carries almost no per-student supervision load — nobody is holding a knife — so one instructor can comfortably run 16 or more, limited by sightlines and audio rather than safety. An advanced pastry or knife-skills class runs the other direction: laminated dough, tempering, or a full French knife-cuts progression demands hands-on correction per student, and the honest ratio drops to 8, sometimes 6 for a serious butchery or sugar-work session. Kids' classes drop further still, and in many jurisdictions carry their own supervision requirements that override anything you decide internally.

Write the ratio down per class type, not per school. A single number applied across a catalog of demos, hands-on dinners, and technique intensives will over-staff the easy formats and under-staff the hard ones, which is the worst of both errors at once. Your catalog probably has three to five format buckets; assign each a ratio and you have the entire input side of the model.

The reason this matters beyond safety is that instructor labor is usually the single largest controllable cost in a teaching kitchen, and it is the one cost that scales with a decision you make weeks in advance. Ingredients scale with attendance automatically — twenty students buy twenty portions. Rent does not move. But if you schedule two instructors for a class that books eight seats, you have permanently spent that money regardless of how the class fills. Every shift you staff by habit rather than by arithmetic is a bet placed before the bookings come in. The ratio is what turns that bet into a calculation.

The same discipline that RevOps teams apply to capacity planning on a sales floor applies here without translation: define the unit of work, define how much of it one person can absorb, then let demand set headcount instead of tradition. A cooking school has an unusually clean version of this problem because bookings are known in advance, capacity is physically bounded by station count, and the work is time-boxed into discrete blocks. Very few small businesses get inputs that clean.

The step-by-step process for building a shift count

The method is three moves, run in order, for every block on the calendar.

Step one — set the ratio per class format. Sit down with your head chef and name the number for each bucket: hands-on at 10, demo at 16, advanced technique at 8, kids at whatever your local supervision rules and your own comfort dictate. Say it to the whole instructor team so there is a shared yardstick and nobody quietly decides they can handle 15. This conversation takes twenty minutes once and then governs the schedule for a season.

Step two — pull expected seats per block and divide. Take each recurring class block and average its booked seats over a trailing four to eight weeks. Saturday 11 a.m. hands-on Italian averages 20 booked seats: 20 ÷ 10 = two chef-instructors. Wednesday evening knife skills averages 8 seats at an advanced ratio of 8: 8 ÷ 8 = one chef-instructor. Round up, always — you cannot schedule 1.4 people, and rounding down is how you end up with an instructor supervising fourteen open flames alone.

Step three — add support staff by trigger, not by feel. The clean rule: any block running two or more chef-instructors gets one prep-and-dish assistant. That person portions mise-en-place before the class, runs the dishwasher during it, and resets stations between courses so the instructors never leave the floor. Blocks with a single instructor and a short runtime usually do not need one, though a two-and-a-half-hour single-instructor class with a heavy dish load often does. A second trigger worth adopting: any block where the menu has four or more components, regardless of instructor count.

Step four — place the shifts against the real load curve. The count tells you how many; the kitchen rhythm tells you when. Prep stacks up 45 to 60 minutes before a hands-on class — someone portions ingredients, labels stations, preheats ovens, stages towels and cutting boards. Service is the class itself. Cleanup lands hard at the end, when every station, pan, plate, and surface has to be broken down and reset. If your Saturday runs an 11 a.m. and a 3 p.m. block back to back, you staff the prep-and-dish assistant continuously across the whole day rather than in two split shifts, because the changeover between blocks is the single busiest hour in the building.

Run that loop for every block and the schedule writes itself. There are no favorites, no "we always run two people on Saturdays," no instructor quietly stacking shifts with friends. Seats divided by ratio, plus a support trigger, placed on a load curve.

One refinement worth building in from the start: separate *booked* seats from *expected attended* seats. Cooking schools with prepaid, non-refundable classes see attendance close to bookings. Schools with flexible cancellation or corporate group bookings see meaningful no-show rates. If your trailing data shows a consistent gap, staff to attendance, not to bookings — but never let that adjustment push you below the safety floor for the students who do show up.

Costs, timelines, and typical ranges to plan against

The staffing count only matters in dollars, so translate it. Chef-instructor pay varies enormously by market and credential, so rather than pretend a national number exists, build the model with your own rates: instructor hourly rate × scheduled hours per block, plus assistant hourly rate × their hours, plus payroll burden. Payroll taxes and workers' comp in a commercial kitchen environment add meaningfully on top of base wage — check your actual rates with your payroll provider rather than guessing, because kitchen classifications typically carry higher comp rates than office work.

The scheduled-hours side is where owners routinely undercount. A "two-hour class" is rarely a two-hour shift. A hands-on block that runs 11 a.m. to 1 p.m. realistically means the lead instructor is on the clock from 10:15 and off at 1:45, and the prep-and-dish assistant may run 10:00 to 2:00. That two-hour class is 3.5 instructor hours and 4 assistant hours. Multiply that gap across a full calendar and the difference between the naive model and the honest one is often 40 to 60 percent more paid hours than the class runtimes suggest.

Set your prep and cleanup windows explicitly rather than letting them float: 30 to 60 minutes before a class for setup depending on menu complexity, and 30 to 45 minutes after for breakdown. Publishing these as actual shift boundaries does two things — it stops surprise overtime, and it makes the kitchen genuinely ready for the next block instead of relying on someone's goodwill.

On the software side, scheduling tools cluster into two pricing shapes and the choice between them is structural, not a matter of taste. Per-user tools charge by headcount — When I Work and Deputy sit in the low single digits per user per month for scheduling, rising when you add time-and-attendance and labor tools. Per-location tools charge a flat monthly fee regardless of roster size — Homebase and 7shifts both work this way, and both offer a free tier for a single location. Connecteam has a free tier for small teams and paid plans aimed at deskless operations. Sling offers a free tier with inexpensive paid steps. Workforce.com and HotSchedules (part of Fourth) sit at the operator-grade end, built for multi-location businesses with real compliance exposure, generally quoted rather than list-priced. Shiftboard is enterprise workforce scheduling by quote, with credential-based scheduling that matters if only certified staff may supervise a kitchen. Verify current pricing on each vendor's own page before you commit — this category re-prices often.

The structural rule: per-location pricing wins when you run one school with a large part-time instructor roster; per-user pricing wins when you run a small, stable crew. A cooking school with 14 part-time chef-instructors and 4 assistants on a per-user plan pays for 18 seats even though only 5 people work on a given Tuesday. That same school on a flat per-location plan pays once. Flip it — a school with 4 total employees — and per-user is cheaper and lighter.

On timeline: give yourself two to four weeks to install the method properly. Week one, set the ratios and pull trailing attendance per block. Week two, build the shift counts and publish them alongside your existing schedule without acting on them, so you can compare. Weeks three and four, run the calculated schedule for real and log every block where you felt understaffed or watched someone stand idle. Adjust the ratio or the support triggers from those logs, not from a single bad Saturday.

If you are opening a new school with no attendance history, start conservative: assume roughly half to two-thirds of your seats fill in the first month, staff to that number, and re-baseline after four weeks of real bookings. Slight over-staffing during the opening period is the cheaper error — an under-supervised hot kitchen full of beginners is a risk that dwarfs the wage difference.

Where teams get this wrong

Staffing to capacity instead of to bookings. A room with 24 stations is not a 24-student class unless 24 people paid. Owners anchor on the physical build-out and schedule to it, then eat the labor on a 9-seat Tuesday. Pull the actual booked number for the actual block; capacity is a ceiling, not a forecast.

One ratio for every format. Running demos and advanced pastry off the same 10-student number over-staffs your cheapest format and under-staffs your riskiest one. Bucket the catalog.

Forgetting the changeover. The most under-staffed hour in most cooking schools is not during a class — it is the 45 minutes between two blocks, when one group's stations must be broken down, washed, and rebuilt before the next group walks in. Scheduling both blocks correctly and leaving the gap uncovered means your instructors do dish work, which is the most expensive dishwashing you will ever buy.

Rounding down. 22 seats at a ratio of 10 is 2.2, which is three instructors or a decision to cap the class at 20. It is never two instructors and 22 students. If your bookings routinely land just over a ratio boundary, either raise the cap on the class or accept the third body — do not quietly stretch the ratio because the number is close.

Letting seniority or friendship set the roster. The count is arithmetic; who fills the slots is a separate decision. When those two get mixed, you get the instructor who always works Saturdays regardless of whether Saturday needs two people, and the new hire who never gets hours. Publish the counts first, then assign names.

No-show and callout blindness. If one instructor calling out sick converts a compliant class into a non-compliant one, you have no buffer. For blocks that would be unsafe at reduced staff, keep a named on-call for the day rather than a general hope. This does not mean scheduling a spare body for every block — that is pure cost — it means knowing in advance which blocks cannot absorb a loss.

Ignoring the labor rules that apply to your footprint. Meal and rest break requirements, overtime thresholds, minor-labor restrictions if teens work or attend, and predictive-scheduling ordinances in some cities all constrain the schedule after the arithmetic produces it. The count tells you headcount; the rules tell you how those hours may legally be arranged. Confirm what applies in your jurisdiction with your own counsel or state labor department — this varies enough that no general article can answer it for you.

Never revisiting the ratio. The number you set in month one was a guess informed by experience. After a season of real classes you have evidence: which blocks felt thin, where students waited, where someone was visibly idle. Re-set the ratio annually or whenever the catalog changes materially.

Choosing your approach: spreadsheet, free tier, or paid platform

Not every school needs software. The decision turns on three things: roster size, whether you need the schedule to reach people's phones reliably, and whether you have compliance exposure that a spreadsheet cannot manage.

A spreadsheet is genuinely sufficient when you have a handful of instructors, a stable weekly calendar, and you are the one who publishes the schedule. The method is the value; the tool just stores it. A tab per class format with ratio, trailing average seats, calculated instructor count, and support trigger will run a small school indefinitely. The failure point is not the math — it is distribution. When a schedule change has to reach eight part-timers on a Friday night, a spreadsheet becomes a phone-call chain.

Move to a free-tier scheduling app when distribution becomes the problem: shift swaps, availability collection, published-schedule notifications, and a mobile clock-in. That is the entire value proposition of the entry tiers, and it is a real one. Note what these tools will *not* do — none of them will tell you that a Saturday hands-on block needs two chef-instructors. You bring the ratio; they handle logistics.

Move to a paid tier when one of three things is true: you want staffing suggested from a booking or POS feed rather than typed in; you have compliance guardrails to enforce (breaks, overtime, minor-labor rules); or you run more than one teaching kitchen and need labor cost tracked against revenue in real time. Demand-linked scheduling is the closest off-the-shelf approximation of the seats-per-instructor method, and it is worth paying for once your calendar is complex enough that running the division by hand every week has become a chore.

Whatever you pick, prove the method before you pay for it. Run four weeks on a spreadsheet or a free tier, log the blocks that felt wrong, adjust the ratios, and only then decide whether execution features are worth a monthly line item. Buying software to fix a staffing problem before you have defined the ratio just gives you a nicely formatted version of the wrong schedule.

Related questions

What ratio should I use for a demonstration-only class?

Demonstration formats carry almost no per-student supervision load — students watch and eat rather than cook. One instructor can typically handle 16 or more, bounded by sightlines and audio rather than safety. Confirm the room actually supports that many viewers before raising the cap.

Do I need a prep assistant for every class?

No. Trigger the assistant on two conditions: any block running two or more instructors, or any block with a heavy dish load — long runtime, four-plus menu components. Single-instructor short demos generally do not need one.

How far ahead should I publish the schedule?

Two weeks is a practical minimum for a part-time instructor roster, and some cities' predictive-scheduling ordinances legally require advance notice with penalties for late changes. Check what applies where you operate.

What if bookings spike after I've already published?

Set a booking threshold that triggers a staffing review — for instance, any block crossing a ratio boundary after publication. Either add the instructor from your on-call list or cap registration at the boundary. Do not let the class exceed the ratio.

Should I schedule to booked seats or expected attendance?

Staff to expected attendance if your trailing data shows a consistent no-show gap, but never below the safety floor for students who do arrive. Prepaid non-refundable classes rarely justify the adjustment; flexible-cancellation and corporate bookings often do.

FAQ

How do I determine the right instructor-to-student ratio for my cooking school?

You and your head chef agree on it based on class format and say it out loud to the whole team. For most hands-on classes, one instructor per 10 students is a solid floor. Intensive formats like knife skills or laminated pastry drop to 8 or lower; demonstration classes run higher. Prioritize safety and real teaching contact over squeezing in seats.

What if my class sizes vary a lot between weekdays and weekends?

That is normal — apply the same division shift by shift rather than setting one weekly headcount. A Saturday hands-on block averaging 20 students gets two instructors; a weeknight block averaging 8 gets one. Pull the trailing average per block from your booking system so the variation drives the schedule instead of surprising it.

Do I need to schedule staff beyond the instructors?

Yes, for prep, dishwashing, and station resets. The clean trigger is one prep-and-dish assistant on any block running two or more instructors, plus any single-instructor block with a long runtime or four-plus menu components. That keeps the kitchen flowing and your highest-paid people teaching instead of scrubbing.

How do I handle prep and cleanup time in the schedule?

Build them into the shift, not around it. Budget 30 to 60 minutes of setup before class depending on menu complexity and 30 to 45 minutes of breakdown after. A class running 10 a.m. to noon means a prep shift starting around 9 and cleanup coverage until roughly 12:45. Publishing those boundaries prevents surprise overtime.

What if I'm just starting out and have no attendance history?

Estimate conservatively from your station count and local demand — assume roughly half to two-thirds of seats fill in the first month — then re-baseline after four weeks of real bookings. Slight over-staffing during the opening window is the cheaper mistake; an under-supervised kitchen full of beginners is not a risk worth trimming wages against.

Can a scheduling tool automate this for me?

Partly. Tools with demand-linked scheduling can suggest coverage from a booking or POS feed, which approximates the method. Everything else publishes and distributes a schedule you have already calculated. A spreadsheet updated weekly with booking data runs a small school perfectly well — the ratio is the asset, not the software.

Sources

• https://www.osha.gov/restaurant-industry — OSHA guidance on hazards and safety practices in commercial kitchen environments.
• https://www.dol.gov/agencies/whd/flsa — U.S. Department of Labor, Fair Labor Standards Act overview covering overtime and hours.
• https://www.dol.gov/agencies/whd/youthrules — Federal rules on employing minors, relevant to teen classes and young staff.
• https://www.fda.gov/food/retail-food-protection/fda-food-code — FDA Food Code, the baseline for food-safety supervision requirements.
• https://www.servsafe.com/ — ServSafe food-safety certification programs commonly required of kitchen supervisors.
• https://www.sba.gov/business-guide/manage-your-business/hire-manage-employees — SBA guidance on hiring and managing employees in a small business.
• https://wheniwork.com/ — When I Work, shift-scheduling platform for hourly teams.
• https://joinhomebase.com/ — Homebase, scheduling and time tracking with per-location pricing.
• https://www.deputy.com/ — Deputy, scheduling with demand-based staffing suggestions.
• https://www.7shifts.com/ — 7shifts, hospitality-focused scheduling tied to sales and labor targets.

Related on PULSE

• How Many Employees Should I Schedule Each Shift at My Language School?
• How Many Employees Should I Schedule Each Shift at My Music School?
• How Many Employees Should I Schedule Each Shift at My Swim School?
• Should I open or buy a Celebree School franchise in 2027?
• Should I open or buy a The Coder School franchise in 2027?
• Should I open or buy a Parisi Speed School franchise in 2027?