How Many Staff Should I Schedule Each Shift Across My Food Truck Fleet?

The end-to-end process from booking calendar to published shift

The mistake most fleet owners make is treating the schedule as a roster problem. It is a revenue problem. Your trucks are not one restaurant with five service lines — they are five independent micro-restaurants that happen to share a commissary, a payroll file, and a logo. Truck 3 parked at a brewery lot on a Thursday has almost nothing in common with Truck 1 at a downtown office curb on a Tuesday except the wrap on the side. So the process has to start at the level where the money actually differs: the individual truck at an individual location in an individual daypart.

Step one is agreeing on the per-employee gross-profit number, and this is a leadership conversation, not a spreadsheet exercise. Sit down with whoever runs operations and settle on the gross profit an average crew member should produce during an average service. For food, the honest floor is around $150 per person per service. Food is a lean-margin business — food cost typically runs 28-35% of the ticket, propane and generator fuel eat another slice, commissary rent is fixed regardless of whether you sell, and permit fees per event stack on top. That is why a food truck floor sits near $150 when a furniture showroom might set $400 per body per day. Say the number out loud to the crew so nobody can claim they did not know the yardstick: "If you show up, run an average window, and give average service, you should produce no less than $150 in gross profit on that shift."

Step two is pulling the actual gross profit per truck, per location, per daypart, over a trailing three to six months. Not revenue — gross profit, meaning sales minus food cost minus the direct consumables that go out the window with the order. Most modern POS systems (Square, Toast, Clover) will export ticket-level sales by location if you tag each parking spot as its own "location" or use a location code in the order. If your POS will not slice it, tag it manually for a month; even a hand-kept log of "Truck 2, brewery lot, Thursday dinner: $1,240 sales, $410 food cost" for six weeks gives you a defensible average.

Step three is the division. Downtown weekday lunch curb averages $450 gross profit? $450 ÷ $150 = three crew: one on the window taking orders and cash, one on the line, one on prep and expo. A Saturday festival that historically clears $1,800 in gross profit? $1,800 ÷ $150 = twelve crew — and twelve people cannot physically work inside a 16-foot box, which is exactly the signal that the booking justifies a second truck, a tent-and-table satellite, or a hard cap on the menu so the line moves faster. The number does not just staff the shift; it tells you when the shift has outgrown the asset.

Step four is placing the bodies against the hourly demand curve rather than spreading them flat across the service window. The count answers "how many." The receipt timing answers "when." A downtown truck dies at 2:00 p.m. sharp when offices empty. A brewery lot does nothing until 5:00 and then runs hot until close. A festival is a four-hour wall with no lull at all. Staff to that shape: two prep bodies at 9:30, all three on the window from 11:15 to 1:30, one closer breaking down at 2:00.

Step five closes the loop. After every service, compare actual gross profit per body against the $150 target. That single ratio is the most honest scoreboard a fleet owner has. If Truck 4 at the office park consistently returns $95 per body, you are either overstaffed there, parked in the wrong spot, or running a menu too slow for a 45-minute lunch window. If Truck 2 hits $240 per body at the brewery every Thursday, you are understaffed and leaving money in the line that walked away. The loop is the whole system — the initial division is just the opening bid.

Where this creates revenue and where the fleet quietly leaks it

Fleet labor leaks in two directions, and most owners only ever see one of them. The visible leak is overstaffing: four people on a truck that generated $380 in gross profit, meaning each body returned $95 against a $150 target, and the missing $220 came straight out of the operating margin. That one shows up on the P&L as labor percentage creep and it gets attention because it is a number on a statement.

The invisible leak is worse and larger. It is the sale that never rang. A festival window with six crew when the math said twelve does not produce a bad labor line — it produces a *great* labor line, because gross profit per body looks enormous. What it actually produced was a forty-minute queue, three hundred people who looked at the line and walked to the taco truck two spaces down, and a booking you will describe as "we crushed it" while having captured maybe 55% of the available demand. There is no line item on any P&L called "customers who left." The only way to see it is to track throughput — tickets per hour per crew member — and to compare it against what the same truck does when it is properly staffed at a comparable event.

A practical way to surface the invisible leak: log the longest observed queue length at three fixed times during each service (peak minus 30, peak, peak plus 30). If your peak queue routinely exceeds about 12-15 people at a truck window, you are almost certainly turning away walkaways. Most people will not stand in a food truck line longer than 10-12 minutes. If your average ticket takes 90 seconds to fulfill and you have one window, a 15-person line is already a 22-minute wait and half of it is going to evaporate.

The upstream effect is the part people miss entirely: staffing decisions change which bookings you should accept. Once you can say "this event historically clears $1,800 gross profit and requires twelve bodies, so it costs me roughly $1,150 in labor before I count fuel and permit," you can compare it honestly against a $450 curb that costs $290 in labor. Suddenly the glamorous festival is a 36% contribution margin and the boring office curb is 35% — nearly identical, except the festival ties up two trucks and eight extra people you have to recruit, train, and manage. That comparison is what turns a scheduling method into a booking strategy. The same math that fills a shift also tells you which shifts are worth filling.

The downstream effect lands on retention, and this is where fleets bleed money invisibly for years. Crew who work chronically understaffed shifts burn out and quit, and in mobile food the replacement cost is brutal — you are not just hiring, you are re-teaching the menu, the POS, the food-safety log, the generator quirks, and the fact that Truck 3's fryer runs hot. Every crew member who quits at month four instead of month fourteen costs you a training cycle you have to run during service. Meanwhile the crew who work chronically *over*staffed shifts learn that slow is normal, and that habit follows them to the busy trucks. Staffing to the receipts protects both the margin and the culture.

There is a third leak worth naming because it is specific to fleets: the commissary. Prep labor at a shared commissary is often scheduled by habit — "two people come in at 7" — regardless of what the trucks are actually running that day. If Tuesday is three trucks and Saturday is six trucks plus two festival bookings, the same two prep bodies cannot possibly be right for both. Apply the same division to prep: estimate the gross profit the day's combined bookings will generate, and let that set the prep crew, not the calendar habit. A fleet running $4,800 in projected daily gross profit across six trucks needs materially more prep than a $1,400 Tuesday.

Concrete numbers, benchmarks, and worked examples

Start with the labor-percentage guardrail, because the gross-profit division and the labor ratio should agree with each other. Food service generally targets labor at roughly 25-35% of sales, with quick-service and mobile operations usually living in the lower half of that band because there is no table service, no host, no busser, and no dining room to clean. A truck running 40% labor on sales is either badly overstaffed, badly underpriced, or parked somewhere that does not deserve the visit.

Now cross-check the two methods on a real-shaped example. Truck 1, downtown office curb, Tuesday lunch. Historical average: $1,300 in sales, roughly 33% food cost, so about $870 in gross profit. Divide by $150 and you get roughly six crew — which immediately fails a smell test, because six people cannot work a 16-foot truck window and $870 of gross profit will not cover six people's wages plus your margin. This is the moment to notice that the $150 floor is a *floor for a full service*, and a 90-minute lunch window is not a full service. For short windows, prorate: a 2-hour service at a $150-per-full-service target is closer to $60-75 per body of expected gross profit contribution, which puts that curb at three to four crew. Run the labor check: four crew at 5 hours each (prep, drive, service, breakdown) at $17/hour is $340 against $1,300 in sales — about 26% labor. That passes. Three crew would be 20%, tight but workable if the line does not wrap.

Second worked example. Truck 3, brewery lot, Thursday dinner, 5:00-9:00 p.m. Historical: $1,900 sales, 30% food cost, about $1,330 gross profit. Four hours of hard service, so it is close to a full service. $1,330 ÷ $150 ≈ nine, which again exceeds the box. Here is where the number is telling you something real: this location has outgrown one window. Options are a second service window cut into the truck, a pre-order pickup channel to pull 20-30% of tickets out of the physical queue, a tightened five-item menu so ticket times drop under 60 seconds, or a second truck. Do not just staff five and call it solved — the division told you the constraint is the asset, not the roster.

Third example, the festival. Saturday street fair, 11:00 a.m. to 7:00 p.m., historical $5,400 sales at 32% food cost, roughly $3,670 gross profit. Divide by $150 and you get about 24 bodies. That is unambiguously a multi-truck, multi-shift booking: two trucks, each with a crew of six, run in two overlapping shifts of four hours so nobody works an eight-hour festival on their feet without a break. Twelve unique people, twenty-four body-shifts. Labor at $17/hour across 24 four-hour shifts is $1,632 against $5,400 in sales — 30% labor, at the top of the acceptable band, which is normal for events because event throughput is genuinely labor-intensive.

A few operating benchmarks worth writing on the commissary wall. Ticket time on a well-run truck should sit around 60-90 seconds from order to hand-off for a tight menu; if you are over two minutes, adding a body to the line will do more for revenue than adding a body to the window. Menu breadth is a labor multiplier — every additional cook-to-order item adds prep, adds station complexity, and adds ticket time; fleets that cap at six to eight items per truck consistently run leaner crews than fleets running fourteen. Plan roughly 30-45 minutes of setup and 30 minutes of breakdown into every scheduled shift; if you only pay for the service window, you are either getting unpaid work (a liability problem) or your crew is arriving late (a revenue problem).

Also budget a buffer body on any shift where a single absence kills the service. A three-person truck that loses one person to a flat tire or a sick call is now a two-person truck doing a three-person service, and the queue math collapses. On high-value bookings — anything over roughly $1,000 in projected gross profit — carry one named on-call person who gets a small stipend for holding the window. That stipend is cheap insurance against a festival you only get to run once a year.

Pitfalls, edge cases, and how to keep the method honest

The first pitfall is scheduling by tradition. "Truck 2 always rolls with four" is the single most expensive sentence in fleet operations, because it survives long after the location, menu, and demand curve that justified it have all changed. Kill the phrase. Every shift gets the division run fresh against current trailing data, every week.

The second is using revenue instead of gross profit. A truck doing $2,000 in sales on a menu with 45% food cost is generating $1,100 of gross profit; a truck doing $1,500 in sales at 25% food cost generates $1,125. The second truck deserves the same or more crew despite ringing $500 less. If you staff to revenue you will systematically overstaff your low-margin menus and starve your high-margin ones — precisely backwards.

The third is averaging across locations. A fleet-wide average gross profit per truck is a fiction that describes no actual shift. If Truck 1 does $870 downtown and Truck 5 does $310 at a suburban lot, the "average" of $590 will overstaff the suburb and understaff downtown simultaneously. Always slice by truck *and* location *and* daypart. Three dimensions, no shortcuts.

The fourth is treating the $150 target as sacred. It is a starting calibration, not a law of physics. Recheck it quarterly. If your whole fleet consistently produces $220 per body while running 24% labor and no queue complaints, your target was set too low and you have been overstaffing for a year. If nobody anywhere can clear $110, either the target is wrong for your price point, your menu is priced under market, or your food cost has drifted while nobody was watching the invoices. The target is a diagnostic instrument — when it stops fitting, that is information about the business, not a reason to ignore the method.

Fifth: weather and seasonality break trailing averages badly in mobile food, far worse than in a fixed restaurant. A rained-out Saturday is not evidence that the location is weak. Flag weather-affected services and either exclude them from the trailing average or keep two averages — fair-weather and adverse — and schedule to the forecast. In most markets, a 40°F drop or steady rain can cut a lunch curb by half. Likewise, seasonality is severe: a beach-adjacent lot in July and the same lot in November are different businesses with the same GPS coordinates.

Sixth: compliance and skill mix are constraints the pure division ignores. If your crew includes minors, break rules and hour limits are hard boundaries, not preferences. If only two people in the whole fleet can run the fryer safely, your festival crew of twelve still bottlenecks at two, and adding a thirteenth generalist does nothing. Build a simple skill matrix — window, line, fryer, cash, drive/park, food-safety lead — and check that every scheduled shift covers each required skill at least once, ideally twice on high-value bookings. The count tells you how many; the matrix tells you *which*.

Seventh, and specific to fleets: cross-truck cannibalization. If you book two of your own trucks 400 feet apart at the same event, they are splitting one demand pool, and each one's historical solo average is now wrong. Either treat the pair as a single combined booking and staff to the combined projection, or deliberately differentiate the menus so they draw separately.

Finally: never let the schedule become a reward system. Sending your strongest crew to the easiest lot because they earned it, or exiling a struggling cook to the dead suburban shift, corrupts the data and the culture at the same time. The division is neutral. Let it stay neutral — put strength where the receipts are and coach the struggling cook on a shift where there is time to coach.

Choosing the tooling that fits your fleet size

The method works on paper, and for a two-truck operation paper is genuinely fine. The tooling question only matters once you are running enough services per week that recalculating by hand becomes the bottleneck. What you are choosing between is essentially three tiers: a free calculator that runs the division, a restaurant-native scheduler that ties shifts to POS sales, and an operator-grade workforce platform that forecasts labor against sales in real time.

The free tier — including PULSE's browser-based Rep Scheduling Matrix — is right when you want the math without a subscription. You feed it a gross-profit target and a per-shift minimum and it distributes crew counts across trucks and services, protecting the high-value bookings instead of spreading bodies flat. No login, no per-seat fee, no spreadsheet.

The restaurant-native tier is where most fleets between three and ten trucks land. Tools built for restaurants and mobile food connect to Square or Toast, express targets as sales-per-labor-hour, and handle the things general schedulers ignore: tip pooling, shift swaps across units, and a per-unit manager log. Pricing in this tier is typically per location per month, which strongly favors a fleet running a large roster of part-time and rotating cooks — per-user pricing punishes exactly the staffing pattern mobile food depends on. Several vendors offer a free single-location tier, which makes proving the workflow on one truck essentially free.

General shift-scheduling apps sit adjacent: cheap per user, excellent at availability, swaps, and mobile clock-in from a curb your crew has never visited before. They handle the logistics beautifully and answer none of the *why*. They will not tell you the festival needs twelve. If you already run the division yourself, they are a perfectly good publishing layer.

The operator-grade tier — demand-based scheduling with live labor-versus-sales tracking, compliance guardrails for breaks and minors, and wage-cost forecasting — earns its cost once labor control is a daily concern rather than a weekly one. Watching a festival truck's labor against its receipts hour by hour, and pulling a body when the wall breaks, is a real capability. It is overkill for two trucks and close to essential past a dozen.

This is where the RevOps discipline transfers cleanly from software sales into food service. In RevOps you set a quota per rep, measure attainment, and route coverage to the highest-value accounts; here you set a gross-profit target per body, measure attainment per service, and route crew to the highest-value bookings. Same operating logic, different unit of production. Adjacent operations — mobile car detailing, event bartending, pop-up retail, farmers-market vendors — run this identical math because they share the structural trait that makes it necessary: a small, mobile, capacity-constrained asset whose revenue varies enormously by where and when it parks.

Whatever tier you choose, insist on one capability: the ability to see gross profit per body per completed service, per truck. If the tool cannot show you that number after the fact, it is a publishing tool, not a management tool, and you will need to keep the scoreboard somewhere else.

Related questions

How do I staff a brand-new truck with no historical data?

Use a comparable: the closest existing truck by menu, price point, and location type. Schedule to 70% of that comparable's crew count for the first three services, log actual gross profit and queue length, then correct upward or downward. Three services is usually enough to see the shape.

Should the truck manager count toward the crew number?

Yes. Anyone working the service counts, regardless of title. The target is gross profit per body on shift, and a manager taking orders or expediting produces the same throughput as anyone else. Only exclude someone who genuinely does not touch the service.

How do I handle a truck running lunch and dinner the same day?

Treat each service window as a separate calculation. A truck doing a $450 office lunch and a $1,300 brewery dinner needs three bodies at midday and closer to seven at night — often a shift change rather than one crew working eleven hours.

What if a location's gross profit swings wildly week to week?

Use at least four weeks of trailing data for that exact location and daypart, and schedule to the lower half of the range until the pattern stabilizes. Flag weather-affected and event-affected services separately so they do not distort the baseline.

Does this method work for the commissary prep crew too?

Yes. Project the combined gross profit of the day's bookings across all trucks and divide by the same target, adjusted for the fact that prep is upstream of the sale. A six-truck Saturday needs materially more prep labor than a three-truck Tuesday.

FAQ

What if I schedule fewer staff than the formula says?

You trade a visible cost for an invisible one. Labor percentage looks excellent and gross profit per body looks heroic, but the queue lengthens, walkaways climb, and the shift that "crushed it" actually captured a fraction of available demand. Under-scheduling almost always costs more in missed revenue than the extra wage would have.

Can I apply this to a one-off festival I have never worked before?

Yes, with a conservative projection. Estimate gross profit from the closest comparable event you have run — similar attendance, similar duration, similar food competition — and divide by your target. If the result exceeds what one truck can physically serve, split it across two trucks or cap the menu so ticket times stay under 90 seconds.

Does the per-employee target change if crew members earn different wages?

No. The target measures gross profit produced, not wage cost consumed. Wage differences belong in your labor-percentage check, which runs alongside the division as a second guardrail. Keep one target for simplicity, and revisit it quarterly for the whole fleet rather than per person.

How do tips factor into any of this?

They do not enter the gross-profit calculation, since tips are not fleet revenue. They matter operationally, though: crews will fight for the high-tip bookings, and if you always assign those on merit or seniority you distort both the schedule and the team. Rotate high-tip shifts on a published rotation and let the staffing math stay neutral.

What is the fastest way to start if my POS will not slice sales by location?

Keep a paper or notes-app log for six weeks: truck, location, daypart, sales, food cost, crew count, longest queue. That is enough to compute a defensible trailing gross profit per service and start running the division. You can migrate to POS-tagged locations later without losing the baseline you built.

How often should the whole schedule be rebuilt from the numbers?

Rerun the division weekly against a rolling trailing average, and do a full recalibration of the per-employee target quarterly. Weekly catches location and seasonal drift; quarterly catches food-cost creep, price changes, and menu changes that shift what a body can actually produce.

Sources

• https://www.7shifts.com/ — restaurant and mobile-food scheduling, POS integrations, labor-percentage targeting
• https://www.deputy.com/ — demand-based scheduling and compliance guardrails for hourly teams
• https://joinhomebase.com/ — per-location scheduling, time tracking, and labor-cost forecasting
• https://wheniwork.com/ — shift scheduling, availability, swaps, and mobile clock-in for hourly staff
• https://www.toasttab.com/restaurant-guides — restaurant labor-cost and food-cost benchmarking guides
• https://squareup.com/us/en/townsquare/restaurant-labor-cost — labor cost guidance for food service operators
• https://www.nraef.org/ — National Restaurant Association Educational Foundation, workforce and training resources
• https://www.dol.gov/agencies/whd/flsa — FLSA wage-and-hour rules including youth employment limits
• https://www.sba.gov/business-guide/manage-your-business/hire-manage-employees — SBA guidance on hiring and managing hourly employees

Related on PULSE

• [Who places fractional Chief Revenue Officers?](/knowledge/tl21653)
• [What service finds fractional CROs for you?](/knowledge/tl21652)
• [Can I find a fractional CRO on LinkedIn?](/knowledge/tl21651)
• [Is there a directory of fractional CROs?](/knowledge/tl21650)
• [Who do I contact to find a fractional Chief Revenue Officer?](/knowledge/tl21649)