How Many Employees Should I Schedule Each Shift at My Burrito Restaurant in 2027?

The Tuesday afternoon that costs you a Friday night

Walk into a burrito restaurant at 2:15 PM on a Tuesday and count the people behind the line. In most independent shops the answer is five or six. Two are wiping down a prep table that was already clean. One is restocking a salsa well that will not empty again until 5 PM. One is on a phone. The register has rung eleven transactions in the last ninety minutes.

Now walk into the same restaurant at 12:10 PM on a Friday. The line runs to the door. Two builders are working the assembly rail, one of them also running the register because the third person called out. Tickets are stacking. A customer at the back of the line looks at the queue, looks at their watch, and leaves. Three more do the same over the next forty minutes.

That is one restaurant, one week, and two opposite failures that cancel each other out on the profit-and-loss statement — and that is exactly why they never get fixed. Total labor for the week looks fine. Labor as a percentage of sales lands somewhere in the high twenties. The owner sees a number that does not scream, so nothing changes. Meanwhile the Tuesday shift burned roughly twenty paid hours producing almost nothing, and the Friday lunch left an unknown but real amount of revenue standing on the sidewalk.

The reason this happens is not laziness. It is that most schedules are built from the wrong inputs. The three most common inputs are: who asked for hours, who is available, and what we ran last week. None of those inputs contain any information about how much money the shift is expected to make. A schedule built from availability is a schedule optimized for the staff's calendar, not for the restaurant's demand curve.

There is a second reason, more specific to burrito restaurants. The assembly line format creates an illusion of flexibility. Because any employee can theoretically stand at any position on the rail, owners tend to think of headcount as a single undifferentiated pool — "I have five people today" — rather than as a set of stations with different throughput ceilings. Five people is not a useful number. Five people with nobody on the grill during a rush is a broken line. Three people with the grill covered, one builder, and a cashier is a functioning one. Headcount without station assignment is not a schedule; it is a guest list.

The fix is to build the schedule from two numbers you already have and one number you have to decide: the gross profit each shift historically produces, the hour-by-hour shape of when those receipts ring, and the gross profit you expect one average employee to generate on an average shift. Everything else in this article is mechanics.

How the gross-profit-per-employee method actually works

Start with the target. Sit down with whoever runs the restaurant with you and agree on one number: the gross profit an average employee should produce working an average shift, serving an average number of guests, at average speed. For a fast-casual burrito operation, $150 per shift is a reasonable starting floor. It is not a stretch goal and it is not a ceiling — it is the amount of margin a competent person on a normal day should cover.

Why gross profit and not revenue? Because revenue does not account for what you actually pay out to produce it. A burrito shop with a heavy protein mix, expensive avocado, and generous portioning has a very different margin per dollar of sales than one running a rice-and-bean-forward menu. If you schedule off revenue, two restaurants with identical top lines will get identical schedules despite one of them having roughly thirty percent less margin to pay labor out of. Gross profit — sales minus cost of goods sold — is the pool the labor actually comes from, so it is the pool the labor should be sized against.

Getting the gross profit per shift is the part most owners skip because it sounds like accounting. It is not. Pull three to six months of daily sales from your point-of-sale system, broken into your shift blocks — say open-to-3 PM and 3 PM-to-close. Apply your food cost percentage to each block. If your food cost runs 30 percent, a lunch block averaging $2,000 in sales carries roughly $1,400 in gross profit. If you track food cost more precisely by daypart — and lunch and dinner often differ, because dinner tends to skew toward higher-margin add-ons like drinks and chips — use the daypart figure instead.

Then divide. Gross profit for the shift, divided by your per-employee target, equals the number of employees to schedule for that shift.

Two guardrails keep this from producing nonsense at the edges.

The first is the station minimum. The math can tell you a Monday 3 PM-to-close block needs 1.8 people. You cannot run a burrito line with 1.8 people, and you should not try to run one with two unless your evening volume is genuinely negligible. The floor is set by the physical layout, not the arithmetic: someone has to cover the grill and hot line, someone has to build, and someone has to take money and hand off. In very low volume you can collapse builder and cashier into one person, giving a hard floor of two. Below the station minimum, the minimum wins and you accept that the shift will not hit the per-employee target.

The second is the ceiling imposed by physical space. A four-station rail cannot productively absorb eight people at once. Past a certain point additional bodies stop adding throughput and start subtracting it, because they collide, wait for access to the same wells, and create hand-off confusion. If the math says twelve and your rail seats five working positions, the twelve does not go on the line — it goes into staggered coverage across a longer window, plus off-line roles: an expediter bagging and calling out, a runner restocking wells and pans, a dedicated drinks-and-chips handoff.

Once you have the headcount, place it against the hourly receipt curve. The count tells you how many; the hourly sales report tells you when. Pull sales by hour for the last several weeks and find where the money actually rings. Most burrito restaurants show a sharp lunch spike between 11:30 AM and 1:15 PM, a deep afternoon trough, and a broader, flatter dinner hump from about 5:30 PM to 7:30 PM. The lunch spike is usually taller and narrower than owners think — a large share of a weekday's total sales can fall inside a ninety-minute window. Staff to the shape of that curve, not to the shape of your shift blocks.

Real numbers, ranges, and station benchmarks

Here are the working figures to build from. Treat them as starting points to calibrate against your own line, not as universal constants — a shop with a build-your-own menu and fourteen toppings runs slower per unit than one with six preset builds.

Throughput per person. A trained builder on a well-stocked rail assembles roughly 1.5 to 2.5 burritos per minute during a sustained rush. The low end applies to complex build-your-own orders with many topping decisions and customer back-and-forth; the high end applies to preset menu items where the builder is executing a known sequence. A cashier processing a straightforward transaction handles roughly 3 to 5 orders per minute when payment is card-tap and there is no menu explanation involved; that drops sharply — often below 2 — when the cashier is also fielding questions from first-time customers.

Sizing peak coverage from throughput. Find your busiest thirty-minute window in the point-of-sale data. Divide total orders in that window by 30 to get orders per minute. Divide that by your per-person build rate to get the raw number of builders needed on the rail. Then add one. The extra body is not slack — it absorbs the complicated order, the allergen question, the register jam, and the bathroom break that would otherwise stall the whole line. Always round up on peak coverage; the cost of one extra hour of labor is smaller than the cost of a walked-away lunch queue.

Worked example: 66 orders in the busiest thirty minutes is 2.2 orders per minute. At 2 burritos per minute per builder, that is 1.1 builders — round to 2 on the rail, plus 1 for the redundancy rule equals 3 on assembly. Add a grill cook and a cashier and you are at 5 for that window, plus an expediter if you are bagging a meaningful number of to-go orders, which puts you at 6.

Headcount by gross profit. A slow weekday afternoon block producing $450 to $600 in gross profit maps to three to four employees at a $150 target. A weekday lunch block producing $1,050 to $1,350 maps to seven to nine. A Friday or Saturday dinner block producing $1,350 to $1,500 maps to nine to ten. Below roughly $450 in shift gross profit, the station minimum takes over and you run your floor of two to three regardless of what the division says.

Orders per hour as a coverage trigger. Under 20 orders per hour, one person can genuinely cover two stations — the same employee preps tortillas and works toppings, or works the register and bags. Between 20 and 40 orders per hour, run one person per station: grill, build, cash. Above 40 orders per hour, add the expediter — the person who bags, stages call-in and delivery-app orders, restocks the rail mid-rush, and never touches the assembly line itself. That role looks like overhead on paper and pays for itself in queue velocity the moment volume is genuinely high.

Weekday versus weekend. Weekday lunch commonly needs four to six employees; weekday dinner often needs less, three to five, because many burrito restaurants skew heavily toward the lunch daypart. Weekend lunch tends to run six to eight and weekend dinner seven to nine, with the weekend curve flatter and longer rather than spiked. Do not schedule weekends off weekday patterns. Pull at least two to three weeks of separate weekend data before you set the weekend template.

Prep hours are separate. The gross-profit division sizes service coverage. Prep — proteins, rice, beans, salsas, portioning, receiving — is largely volume-driven but happens outside the service window, and if you fold prep hours into the service headcount you will consistently under-staff the rail. Budget prep as its own block, typically one to two people for two to four hours ahead of a normal weekday and longer ahead of a weekend, and schedule that person to start early and roll onto the line as the rush builds rather than leaving before it.

Cross-training and break coverage. In any shift with three or more people, at least one should be cross-trained to cover a second station well enough to hold it for fifteen to twenty minutes. Without this, every legally required break becomes a station outage. With it, breaks are invisible to the customer. This is a scheduling constraint, not just a training one — when you build the schedule, verify that each shift's roster actually contains someone who can cover the grill, not just people who are theoretically willing to.

Trade-offs: rigid blocks, staggered starts, and cross-training

The most consequential trade-off in burrito restaurant scheduling is between rigid shift blocks and staggered start times.

Rigid blocks — everyone on at 11, everyone off at 4 — are simple to write, simple to communicate, and easy for employees to plan around. They also guarantee two structural losses per shift. Before the rush, you pay a full crew to stand in a nearly empty dining room; after it, you pay the same crew to work through a trough. On a lunch block with a 90-minute spike inside a five-hour scheduled window, a substantial share of the paid hours falls outside the period where the money is actually being made.

Staggered starts fix this at the cost of complexity. Instead of one start time, use 15-minute increments to build a coverage ramp. A worked lunch example for a rush that peaks at noon: first employee starts at 10:45 AM to finish prep and open the line; second starts at 11:15 as the early wave begins; third and fourth start at 11:45 to hit the peak with full coverage. On the tail, the first employee leaves at 1:15 PM, the second at 1:45, the third at 2:15, leaving one person to hold the trough. The crew size at noon is what the throughput math demanded; the crew size at 10:50 and at 2:30 is not.

The cost is real. Staggered schedules are harder to write, harder for employees to remember, and more sensitive to a single call-out, because there is less slack anywhere in the ramp. They also require a scheduling tool that people actually check — a paper schedule taped to the walk-in door does not survive four different start times per shift. And in jurisdictions with predictive-scheduling or fair-workweek rules, frequent changes to posted staggered shifts can carry penalty pay, so the schedule needs to be right when it is posted rather than adjusted the day before.

The third option — a small core crew plus people on call — deserves mention mainly so you can reject it. It looks like the cheapest structure on paper and it is the most expensive in practice. Employees who are told to keep an afternoon free without guaranteed pay for it leave, and turnover in a burrito restaurant is genuinely costly: every departure means retraining someone on portioning, on the grill, on the point-of-sale, during which throughput drops and food cost rises from over-portioning. On-call scheduling is also restricted or penalized in a growing number of jurisdictions. Build a schedule you can actually staff with people who stay.

There is also a trade-off between depth and breadth on cross-training. Deep specialists — a grill cook who is genuinely fast — produce more throughput at their own station than a generalist does. Broad generalists give you flexibility to reshuffle mid-shift and to cover call-outs without a scramble. The practical resolution for a burrito restaurant is to keep the grill deep and everything else broad: one or two people who own the grill and are excellent at it, and everyone else able to move between build, cash, and expedite. The grill is the bottleneck station and it does not tolerate a slow substitute; the rail positions do.

Finally, weigh scheduling software against a spreadsheet honestly. Restaurant-focused tools — 7shifts, Homebase, When I Work, Deputy, Sling — handle availability collection, shift swaps, mobile clock-in, and publishing, and several connect to a point-of-sale feed to show labor against sales in real time. What none of them decide for you is the target number. They will happily publish a badly sized schedule with excellent notifications. Do the gross-profit division yourself; use the tool for logistics. A single-location operator who has already done the math can run it from a spreadsheet indefinitely; the tools earn their keep once you have enough employees that availability collection and swap requests become a daily time sink.

Pitfalls that quietly break the schedule

Combining the grill with anything during service. The hot line is the bottleneck. When the person on the grill also answers the phone, handles a delivery-app tablet, or steps away to restock, everything downstream stalls, because builders cannot build without protein. In low volume — under 20 orders an hour — combining tortilla prep with toppings is fine. Combining grill with anything during a rush is not. If you take one rule from this article, take that one.

Reading total weekly labor percentage instead of shift-level labor. A week where Tuesday is badly overstaffed and Friday is badly understaffed can produce a perfectly ordinary weekly labor percentage. The averaging hides both problems. Look at labor cost as a percentage of sales shift by shift, not week by week, and you will find the outliers immediately. Any shift more than about five points off your target percentage is worth investigating.

Scheduling to availability first. If you start by collecting who is free and then fit the shifts around it, you will systematically overstaff the shifts your employees prefer and understaff the ones they do not — which, in a burrito restaurant, means the Friday and Saturday peaks. Build the demand-driven schedule first, then solve the availability constraint against it. Where the two genuinely conflict, that is a hiring signal, not a scheduling problem.

Forgetting that the delivery tablet is a station. Third-party delivery orders arrive on their own clock and do not queue politely behind the walk-in line. If delivery is a meaningful share of your volume, those orders consume builder time that the in-store order count does not capture. Count delivery orders in your orders-per-hour figure, and once delivery is substantial, give the expediter explicit ownership of staging and handing off those bags so builders are not repeatedly interrupted.

Not accounting for new-employee drag. A first-week employee does not produce a trained employee's throughput; they produce meaningfully less and they consume some of a trainer's attention on top of it. If a shift's roster includes someone in their first two weeks, treat the effective headcount as roughly half a person lower than the raw count and schedule accordingly. Owners who skip this find that every hiring wave coincides with a mysterious drop in service speed.

Setting the target once and never revisiting it. The per-employee gross profit target is not permanent. It moves when your menu prices move, when your food cost moves, and when your throughput improves through better line layout or better training. Revisit it whenever sales shift by more than about ten percent in either direction, and at minimum every quarter. Similarly, re-pull the hourly receipt curve after any change that could move demand: a menu overhaul, a new competitor opening nearby, a nearby office changing its return-to-office pattern, a seasonal swing.

Ignoring the seasonal and event calendar. A restaurant near a school, stadium, or large office campus does not have one demand pattern; it has several, and they switch on a calendar. Building the annual schedule template off a single three-month data pull will systematically misstaff whichever seasons were not in that window. Pull at least a full year where you have it, and keep a short list of local dates that reliably move volume.

Treating the schedule as final once posted. The forecast will be wrong sometimes. Build a short weekly review into the routine: compare each shift's actual gross profit against what you forecast, and note where the headcount was clearly wrong in either direction. Ten minutes a week of this converts the method from a one-time calculation into a system that gets more accurate every month. The employees notice too — a schedule that visibly tracks real demand reads as competent management, and that matters for retention in a labor market where cooks have options.

Related questions

What labor cost percentage should a burrito restaurant target?

Most fast-casual operations aim for labor in the mid-to-high twenties as a percentage of sales, though this varies widely by market wage rates, whether the owner works shifts, and how much prep is done in-house. Track your own trend rather than chasing a benchmark.

Should the owner count as one of the scheduled employees?

Only if the owner reliably works a station for the full shift. An owner who is on the floor but frequently pulled into ordering, banking, or vendor calls should be counted as a partial body at best, or the line will be short exactly when attention is diverted.

How many employees does a burrito restaurant need in total?

A single-unit shop running lunch and dinner seven days typically needs twelve to twenty people on the roster, mostly part-time, to cover the schedule with enough redundancy for call-outs and vacations. Fewer than about ten and every absence becomes a crisis.

Does a drive-through change the staffing math?

Yes, substantially. A drive-through adds an order-taking position and a separate hand-off point that cannot be covered by the in-store cashier during a rush, typically adding one to two people to every peak shift regardless of what the gross-profit division alone suggests.

How far in advance should the schedule be posted?

Two weeks is a reasonable standard and is legally required in some jurisdictions with fair-workweek rules. Two weeks also gives you enough time to fill gaps before they become day-of scrambles, which is when overstaffing decisions get made badly.

FAQ

How do I know if I'm overstaffed or understaffed right now?

Watch the line during your peak thirty minutes. If more than one person is idle for ten minutes or longer, you are overstaffed for that window. If orders are stacking and the wait from queue entry to hand-off exceeds five to seven minutes, you are understaffed. During rushes, one person per station — grill, build, register — is the working baseline, plus an expediter once you clear roughly 40 orders per hour.

What's the simplest formula to start with?

Take the shift's average gross profit and divide by $150. That is your target headcount for the shift. A block averaging $900 in gross profit points to six employees. Adjust up by one for a complex build-your-own menu or a large delivery share, and down by one only if you have a fast, experienced crew and you have verified the wait times hold.

How many people do I need for a slow shift versus a rush?

For a genuinely slow window such as 2 PM to 4 PM on a weekday, two to three people can handle prep, cleaning, and intermittent orders. For a normal lunch or dinner rush, five to seven is typical. Once a shift is producing $1,350 or more in gross profit, expect to need nine or ten to keep hand-off times short.

Should weekends be scheduled differently from weekdays?

Yes. Weekday lunch commonly needs four to six employees while weekend lunch often needs six to eight, and the weekend demand curve is usually flatter and longer rather than sharply spiked. Pull at least two to three weeks of weekend-specific sales data before setting a weekend template — do not extrapolate it from weekday patterns.

What do I do about call-outs and no-shows?

Keep two or three cross-trained part-time employees who can come in on short notice, and make sure every shift roster includes at least one person who can cover the grill. If you are short more than once every couple of weeks, the roster is too thin — hire one more person rather than repeatedly running a station down.

How often should I rebuild the schedule template?

Review it every four to six weeks, and immediately whenever sales move more than about ten percent, you change menu prices, or a nearby demand driver changes. A template built on January data will misstate a June week. The weekly forecast-versus-actual check takes ten minutes and keeps the template honest between full rebuilds.

Sources

• https://www.bls.gov/iag/tgs/iag722.htm — U.S. Bureau of Labor Statistics, Food Services and Drinking Places industry data
• https://www.dol.gov/agencies/whd/flsa — U.S. Department of Labor, Fair Labor Standards Act wage and hour guidance
• https://restaurant.org/ — National Restaurant Association, industry research and operations resources
• https://pos.toasttab.com/blog — Toast, restaurant operations and labor management articles
• https://www.7shifts.com/blog — 7shifts, restaurant scheduling and labor-cost resources
• https://www.homebase.com/ — Homebase, scheduling and time-tracking for hourly teams
• https://www.deputy.com/blog — Deputy, demand-based scheduling and compliance resources
• https://www.sba.gov/business-guide/manage-your-business/hire-manage-employees — U.S. Small Business Administration, guidance on hiring and managing employees
• https://hbr.org/topic/subject/operations-management — Harvard Business Review, operations management research

Related on PULSE

• How Many Employees Should I Schedule Each Shift at My Mediterranean Restaurant?
• How Many Employees Should I Schedule Each Shift at My Thai Restaurant?
• How Many Employees Should I Schedule Each Shift at My Vegan Restaurant?
• How Many Employees Should I Schedule Each Shift at My Indian Restaurant?
• How Many Employees Should I Schedule Each Shift at My Korean BBQ Restaurant?
• How Many Employees Should I Schedule Each Shift at My Hot Pot Restaurant?