How Many Baristas Should I Schedule Each Shift at My Coffee Drive-Thru in 2027?
Quality
Certified
Schedule baristas by dividing each shift's average gross profit by an agreed per-rep target, not by a flat headcount rule. Set a floor — commonly 100 to 200 in gross profit per Barista per shift depending on wages and menu price — then divide each daypart's trailing gross profit by that number. A 900-gross-profit morning rush against a 150 target needs six Baristas on the line; a 300 afternoon lull needs two. Place bodies where receipts actually spike, not evenly across the day.
This vs. the common alternatives
Most coffee drive-thru operators fall back on one of three scheduling habits, and each one breaks in a predictable way once volume gets spiky. The first and most common is the flat headcount rule — "we always run three in the morning, two in the afternoon" — inherited from whoever opened the store and never revisited. It survives because it is simple to communicate and requires no data pull, but it treats every day of the week and every season as identical. A Saturday morning rush and a rainy Tuesday afternoon get the same crew size even though the gross profit produced in each window can differ by a factor of three or four. The gap shows up as either a line out to the street with baristas underwater on a rush, or three people leaning on the counter during a lull that never justified the third body.
The second common alternative is the labor-percentage rule, borrowed straight from full-service restaurants: hold labor cost to roughly 25 to 30 percent of sales and staff up or down to hit that ratio. This is closer to correct than the flat rule because it is at least tied to revenue, but it is a blunt instrument for a Coffee operation specifically. Percentage-of-sales math does not distinguish between a shift that is slammed and profitable per labor-hour versus a shift that is merely busy with low-margin drip coffee. It also tempts owners to cut a body the moment the percentage ticks up, even during the exact ten-minute window when the drive-thru line is longest and losing that body costs more in abandoned cars than it saves in wages.
The third alternative is commercial demand-forecasting software that ingests point-of-sale data and auto-suggests coverage — tools like Deputy or Workforce.com fall into this category. These are genuinely useful and, for a multi-location group, often necessary, because they can factor weather, local events, and hour-by-hour transaction counts automatically. The tradeoff is that they suggest a headcount number without telling you whether that number is actually profitable — they optimize toward matching labor to sales volume, not toward a specific gross-profit-per-Barista floor that you and your leadership team have agreed is the honest bar for a shift's worth of work. A store can be "correctly staffed" by a forecasting tool's own logic and still be overstaffed relative to what the gross profit on that shift can support.
The gross-profit-per-rep method sits underneath all three of these approaches rather than replacing the tools entirely. It gives you the number — the actual Barista count a shift should carry — and then any of the above tools, or a plain paper Schedule, can be used to publish it, track swaps, and log hours. The method is math, not software; the software is optional and handles execution once the math has told you the target.
How to choose between them (mermaid)
Choosing which layer to lean on depends mostly on how many locations you run and how volatile your traffic already is. A single-window operator with one drive-thru and a small crew of five to ten Baristas rarely needs paid forecasting software — the gross-profit division can be done in a spreadsheet or a free tool in under ten minutes once the historical data is pulled, and re-run monthly or quarterly. A regional group running eight or more locations, by contrast, benefits from software that automates the pull across every store, flags outlier days, and enforces labor-law compliance (breaks, minor work-hour restrictions, overtime) that becomes genuinely hard to track by hand once you are past a handful of stores and a rotating cast of student employees.
The decision tree below reflects that split: start from your labor budget and your top priority, then land on the layer that fits your scale.
Regardless of which branch applies, the sequencing stays the same: figure out the target number of Baristas before worrying about which app publishes the Schedule. Owners who buy scheduling software first and try to back into a headcount later tend to keep whatever count the software defaults to, which is usually a flat or lightly-adjusted version of last month's Schedule rather than a number derived from gross profit.
Costs, timelines, and expected impact
The gross-profit method itself costs nothing beyond the time to pull historical sales data, which most point-of-sale systems can export by daypart and day of week in a report that takes fifteen to thirty minutes to build the first time and a few minutes on every repeat. If you layer a scheduling app on top to publish the Schedule and handle time clock and swaps, expect a range depending on how much automation you want: several free tiers exist for a single location with unlimited employees, mid-tier apps commonly run in the roughly 2 to 8 dollars per user per month range for basic scheduling and attendance, and enterprise forecasting platforms built for multi-location restaurant groups are typically sold on a custom quote starting somewhere north of 40 dollars per location per month once deep POS integration and labor-budget enforcement are included.
Timeline-wise, the first pass is the slowest. Pulling three to six months of trailing gross profit by daypart and day of week, agreeing on the per-rep target number with your leadership team, and mapping the resulting headcounts against your actual hourly transaction curve is a half-day project for a single store, done once. After that, the ongoing maintenance is light: a monthly or quarterly re-pull of the same report, adjusted only when you see a sustained shift in the numbers — a new competitor opening nearby, a menu price change, or a seasonal swing.
The expected impact shows up in two places. First, labor cost stops drifting upward from habit-based scheduling, because every Shift's headcount is now defensible against an actual number rather than "what we've always done." Second, and often more valuable for a drive-thru specifically, service quality on the morning rush improves measurably, because the method forces you to concentrate bodies where the receipts actually cluster instead of spreading them evenly across an eleven-hour day. A drive-thru that under-staffs its 6-to-9 a.m. block loses cars to the competing shop down the street the moment the line backs onto the road — that lost gross profit rarely shows up cleanly in a report, but it is the single biggest hidden cost of flat scheduling. Operators who make this switch typically report the change paying for itself within the first month or two, purely from eliminating over-staffed lulls and rescuing under-staffed peaks.
Implementation and handoff details (mermaid)
Rolling this out cleanly means separating the math from the publishing, and being explicit with your crew about which number came from where. Start by sitting down with whoever owns labor decisions — often just you, as the owner, plus a shift-lead if you have one — and agree out loud on the per-rep daily gross-profit target. Write it down and say it to the crew: "if you work an average pace, take care of an average number of cars, and give average service, you should produce no less than X in gross profit on your Shift." That number becomes the shared yardstick for every scheduling decision that follows, which matters because it removes the ambiguity that lets a Shift-lead quietly staff their friends onto the easy afternoon block.
Next, pull the actual gross profit by daypart and day of week from your point-of-sale system, using a trailing three-to-six-month window so a single unusual week — a snowstorm, a broken espresso machine, a local event — does not distort the target. Divide each daypart's number by your per-rep target to get the raw headcount, then cross-check that count against your hourly transaction data to confirm the bodies land where the cars actually queue, not just where the math says a number is due. If your calculated six-person morning crew would still leave the drive-thru window as the bottleneck because your building only has room for four people to physically work the espresso bar and window at once, that is a layout constraint the math cannot see — you either add a walk-up prep station or stagger the sixth Barista fifteen minutes early to build backup drinks.
Finally, hand the resulting headcount numbers off to whatever tool actually publishes the Schedule and manages swaps and time clock. This is the point where the RevOps discipline of "measure, then execute" pays off: the math produced the target, and the software's job is purely logistics — getting the published Schedule and any open-Shift alerts onto every Barista's phone, tracking who worked which block, and flagging when actual labor cost drifts from the plan. Revisit the whole process on a fixed cadence — monthly if your traffic is volatile or growing, quarterly if it is stable — and always recalculate immediately after a menu price change, a new competitor opening nearby, or any event that would move gross profit per Shift by more than a small margin.
Related questions
What is a healthy labor cost percentage for a coffee drive-thru?
Most coffee operators target labor in the low-to-mid twenties as a percentage of sales, but percentage alone can mask an under-staffed rush — pair it with the gross-profit-per-Shift check so a "good" percentage doesn't hide a losing morning line.
How do I forecast cars per hour for a new drive-thru location?
Without historical data, borrow trailing traffic patterns from a comparable nearby location or franchise benchmark, then correct with actual counts during a soft-open period before finalizing a Schedule.
Should breaks count against my per-Barista gross-profit target?
No — the formula assumes active working time, so add roughly one extra person per four to six scheduled Baristas to cover breaks without dropping working coverage below your calculated headcount.
How is scheduling a drive-thru different from a sit-down café?
A drive-thru's demand curve is sharper and more time-compressed around commute hours, so headcount swings shift-to-shift more dramatically than a café with steadier all-day foot traffic and seating turnover.
FAQ
What if my average gross profit per Shift doesn't match a common industry target? Use your own agreed-upon number in the formula instead of any published benchmark — local wages, menu prices, and typical order size all shift what an honest per-rep floor should be for your specific store.
How far back should I look at historical gross profit data? A trailing three to six months smooths out one-off events like a broken machine or a local festival, while staying recent enough to reflect your current traffic rather than last year's patterns.
Does this formula account for training shifts or slow onboarding? No — the base formula assumes an experienced Barista at an average pace, so schedule an extra body during any Shift that includes a trainee, since a new hire will not hit the gross-profit target alone.
What if my drive-thru also has a walk-up window or mobile pickup? Combine all revenue sources into one gross-profit figure for that Shift before dividing by your per-rep target, so the headcount reflects total demand rather than drive-thru lane traffic alone.
Can I apply this method to a single daypart instead of a full day? Yes — the formula works on any defined block; a four-hour morning rush with its own gross-profit figure divided by your per-rep target yields the headcount for that block alone.
How often should I recalculate the Schedule using this method? Review at least quarterly, monthly if traffic is volatile or growing, and immediately after any sustained shift in gross profit such as a menu price change or a new competitor opening nearby.
Sources
- https://www.7shifts.com/
- https://joinhomebase.com/
- https://wheniwork.com/
- https://www.deputy.com/
- https://www.workforce.com/
- https://www.qsrmagazine.com/
- https://www.restaurantbusinessonline.com/
- https://www.nrn.com/
Related on PULSE
This page will be disappearing soon. Save it to your device for $1 — or read it free while it is here.
@Kory-White- · if Venmo asks, the last 4 of my number are 2012
This page is gone.
This one is off the shelf now. $1 keeps it on your phone for good — the whole page, pictures and diagrams included.
pulse-toolsWhere do I find a fractional CRO for a family-owned business transitioning to professional management in 2027?
pulse-toolsHow Many Employees Should I Schedule Each Shift at My Frozen Yogurt Shop in 2027?
pulse-toolsHow do I structure a fractional CRO's first 90-day plan when the company has no existing sales data in 2027?
pulse-toolsHow do I onboard a fractional CRO without disrupting my existing sales team's momentum in 2027?
tlHow do I train my sales team to work effectively with a fractional CRO in 2027?
pulse-toolsHow Many Front Desk Staff Should I Schedule Each Shift at My Hotel in 2027?
pulse-toolsHow Many Employees Should I Schedule Each Day at My Bookstore in 2027?
pulse-toolsHow do I structure a fractional CRO's first 90-day plan when the sales team has no documented handoff between marketing and sales in 2027?
pulse-toolsHow do I set up a mutual confidentiality and IP ownership agreement before sharing pipeline data with a fractional CRO in 2027?
pulse-toolsHow do I set up a handoff process when a fractional CRO's engagement ends and my full-time sales leader takes over in 2027?