How Many Employees Should I Schedule Each Shift at My Laser Tag Arena?

Signals you actually need this

Most arena owners do not go looking for a staffing formula. They arrive at one after a specific kind of pain, and the pain has a recognizable shape. If two or more of the following describe your last four weeks, you are past due for the arithmetic.

Your labor percentage swings more than eight points week to week with no explanation. A stable operation lands in a band. If you closed one week at 24% labor and the next at 33% on similar revenue, the variance is coming from the schedule, not from the market. Somebody added a body "just in case," or a supervisor stacked a Friday with friends, and nobody caught it because there was no target to catch it against.

You have a shift where two people stand at the front desk watching the parking lot. Every arena has one — the Tuesday 3pm block, the Thursday open, the Sunday final hour. If you cannot name the gross profit that shift produces, you cannot know whether one person is one too many. Owners routinely defend these shifts on "coverage" grounds without ever pricing what the coverage costs. Two employees at $14 an hour across a four-hour dead block is $112 in direct wage plus payroll burden, repeated fifty-two times a year, for a shift that may clear $180 in gross profit.

Saturday night runs feral. Party hosts double as game marshals. The snack counter has a line while a vest wall sits unloaded. Somebody is briefing while somebody else is chasing a nosebleed. This is the mirror image of the dead-shift problem and it is more expensive, because understaffing a peak block does not just burn out the crew — it kills the upsell. Nobody sells a third round or a glow band when they are running triage.

Your schedule is a copy of last week's schedule. This is the single loudest signal. Cloning is not planning; it is inheritance. Whatever mistake was baked into the roster eight months ago is still on the grid, drawing wages, invisible because it is familiar.

You cannot answer "how many people should be on Saturday at 7pm?" without hedging. A number should exist. If your answer is "four or five, depends," the depends is doing work that a formula should be doing. Note that this is the same operational blind spot RevOps teams diagnose on the sales side — capacity assigned by habit rather than by throughput math — and the remedy is identical: pick a denominator, publish it, and let it govern.

Turnover among your best part-timers is climbing. Strong employees leave overstaffed shifts because there is nothing to do and nothing to earn, and they leave understaffed shifts because the job becomes unbearable. Both failures come from the same missing number.

A second location is on the table. The moment you go from one arena to two, informal staffing knowledge stops transferring. You cannot walk the floor of both buildings on a Saturday. The formula is what travels; your intuition does not.

What good looks like versus what bad looks like

Bad staffing is not usually dramatic. It is a quiet, persistent drift where headcount answers to habit, seniority preference, and the manager's fear of being short. Good staffing is boring in a specific way: every shift on the grid can be traced back to a number, and anyone can audit it in thirty seconds.

Bad: the roster leads, the revenue follows. The manager opens the scheduler on Wednesday, duplicates the prior week, patches the time-off requests, and publishes. Headcount is uniform across dayparts — four people at 11am, four people at 8pm — because uniformity is easy to defend and impossible to justify. Labor cost is discovered at month-end, in the P&L, after it has already been spent.

Good: the revenue leads, the roster follows. You pull a trailing three-to-six-month gross profit average by day and daypart. You divide by your committed per-employee target. The quotient is the headcount, and the headcount is not negotiable without a stated reason written next to it. A Tuesday 3–7pm block averaging $480 in gross profit gets 3 employees. A Saturday 6–11pm block averaging $1,600 gets 10. A Sunday close averaging $210 gets 1, and you staff exactly one, because the math said one.

Bad: the target is a secret. Leadership knows the labor budget; the floor does not. Employees have no idea what a shift is supposed to produce, so they have no way to beat it. Nobody sells the extra round because nobody knows that selling the extra round is the job.

Good: the target is published. You say it out loud: "On an ordinary shift, with an ordinary crowd, you owe the arena at least $160 in gross profit." That is a floor, not a ceiling. The employees who want a real paycheck clear $160 without noticing and then go hunting — glow bands, extra games, rebooked birthdays, snack-bar attachment. Now the number is a scoreboard rather than a rebuke.

Bad: the day is one number. Averaging a dead Wednesday morning with a booked Wednesday evening yields a blur that overstaffs the morning and understaffs the evening simultaneously. This is the most common single error, and it costs money twice.

Good: the daypart is the unit. Every block gets its own division. Wednesday 11am–3pm is a separate calculation from Wednesday 5pm–9pm, and the answers routinely differ by a factor of three.

Bad: coverage rules are unstated. Nobody knows whether a shift needs a certified safety monitor or how many marshals a full arena requires. So the manager overstaffs defensively.

Good: floor constraints are explicit and layered on top. The formula gives a count; your operating minimums override upward when required. If a live session legally or practically requires one trained marshal in the arena and one at the desk, then a math answer of 1 becomes an operating answer of 2, and you write that down as a standing minimum instead of rediscovering it weekly.

Real cost and ROI ranges

The reason this arithmetic matters is that labor is almost certainly your largest controllable line, and in an entertainment venue it is controllable in a way that rent and insurance are not.

Sizing the exposure. Take a modest arena running roughly 70 shift-slots a week across all dayparts. If your blended loaded labor cost — wage plus payroll taxes, plus whatever you carry in workers' comp and benefits — sits around $17 an hour on a $14 base, then a single unnecessary four-hour body costs about $68 per occurrence. Two of those a week is roughly $7,000 a year. Four is $14,000. That is not a rounding error at arena-scale margins; it is frequently the difference between a profitable and a break-even quarter.

The upside is symmetric and often larger. Understaffing a peak block does not show up as a cost — it shows up as revenue that never happened. If a Saturday prime block clears $1,600 in gross profit with 7 people when the math called for 10, the missing three are not saving you $200 in wages; they are costing you the attachment sales, the faster turns, and the party upsells that a properly covered floor generates. Arena revenue is throughput-bound: sessions per hour times fill rate times spend per head. Every one of those three multipliers degrades when the floor is thin.

What a per-employee target should actually be built from. Do not take $160 as gospel. Build your own from three inputs. First, your loaded hourly cost times average shift length — say $17 × 5 hours = $85. Second, the share of gross profit you intend labor to consume; if you want direct floor labor at roughly 50% of shift gross profit, your target is $170. Third, a sanity check against reality: pull your best-performing quarter and compute what gross profit per employee-shift actually was when the operation felt right. If those three converge in a band, take the middle. If your loaded cost is $13 and you want labor at 40% of shift GP, your target lands nearer $160–$180. If you are in a high-wage metro at $22 loaded, the target may need to be $220 or higher, and that will pull headcount down across the board — which is the formula correctly telling you that expensive labor must be more productive labor.

Tooling cost, honestly. Scheduling software is not where the money is, but the pricing models differ enough to matter at arena headcounts. Per-user pricing is common and generally lands in the low single digits per employee per month for scheduling-only tiers, climbing when you add time-and-attendance and labor forecasting. Per-location pricing is the alternative, typically a flat monthly fee per venue regardless of headcount. The rule of thumb: if you carry a deep bench of part-timers and summer seasonals — and most arenas do, often 25 to 40 names for 70 weekly slots — per-location billing usually wins outright, because you are paying for doors rather than for a roster that churns. If your crew is a small, stable, veteran group of eight, per-user pricing can be cheaper. Several vendors offer a genuinely usable free tier for a single location; test the method there before you spend anything.

Payback math. Suppose you adopt the formula and it removes two unnecessary four-hour bodies a week while adding coverage to two peak blocks. The cost side saves roughly $7,000 annually. The revenue side is harder to pin but rarely zero — even a 3% lift in per-head spend on your two busiest blocks compounds meaningfully across a year. Against a scheduling tool costing somewhere between nothing and roughly $1,200 a year for a single location, the payback period is measured in weeks, not quarters. The honest caveat: none of that return comes from the software. It comes from having a denominator and enforcing it. The software just makes the enforcement fast.

Where the math does not pay. If you run a single small arena with three total employees and one daypart, this is overhead. Write the target on a whiteboard and move on. The formula earns its keep once you have enough dayparts and enough bench that intuition can no longer hold the whole grid.

How it plugs into your weekly operating workflow

A formula that lives in a document is decoration. The version that survives contact with a real arena is wired into a weekly rhythm with named owners and a feedback loop.

Monday — pull and refresh. Export gross profit by day and daypart from your POS for the trailing period. Refresh the rolling average. This takes fifteen minutes and it is the only genuinely analytical step in the week. Seasonality is handled here, not by argument: when summer arrives and a Tuesday afternoon block's average gross profit climbs from $480 to $720, the division returns 4.5 instead of 3, and the roster grows without anyone having to lobby for it.

Tuesday — divide and draft. Run the division for all seven days and every daypart inside them. You now have a raw headcount grid. Layer your operating minimums on top — safety-certified staff per live session, one person on the desk whenever the doors are open, whatever your insurance and your local rules require. The result is a target grid, not yet a schedule.

Wednesday — fill against availability, then publish. Now, and only now, do names enter the picture. Match availability to slots. Preserve role mix: a shift of 10 is not 10 interchangeable bodies, it is roughly a desk pair, three or four marshals, two party hosts, a snack-counter body, and a floor lead. The count comes from the math; the composition comes from your role model. Publish early enough that swaps happen before the week starts rather than during it.

Friday and Saturday — hold the line. The failure mode is the day-of add. A manager sees a full parking lot at 6pm and calls in two more. Sometimes that is correct. Make it a decision with a record: if you exceed the target grid, note why. Three weeks of "Saturday needed two extra" is not chaos — it is data telling you the Saturday average has moved and the grid needs updating.

Monday again — reconcile. Compare actual gross profit per employee-shift against the target. Not to punish, but to calibrate. If Saturdays are routinely delivering $210 per employee-shift against a $160 target, you are still understaffed at peak and leaving throughput on the table. If Tuesdays are delivering $95, that block is carrying a body it cannot afford.

Adjacent workflows this feeds. The same trailing gross-profit-by-daypart dataset is the input for three other decisions worth making. It tells you which hours to actually be open — a block that cannot clear one employee's target may not deserve to have the lights on. It sizes your hiring pipeline, because summing the grid gives you total weekly slots, and dividing by realistic per-person weekly hours gives you the headcount you need on the bench. And it prices your party packages, because you now know the gross profit a booked-party block must produce to justify the hosts it consumes.

Comparable operations. The identical arithmetic runs a trampoline park, a bowling center, an escape-room venue, or an axe-throwing bar — anywhere revenue arrives in booked blocks and walk-in surges rather than evenly. The variable that changes between them is the per-employee target, because loaded labor cost and gross margin differ. The method does not change at all. A multi-site group runs it per location with each venue's own averages; the grid redraws itself building by building.

Common objections and where the formula genuinely breaks

The method is simple enough that people distrust it. Some of that distrust is warranted; most of it is not. Worth separating the two.

"Gross profit is a lagging number — I'm staffing the future off the past." True, and unavoidable. Every forecast is built from history. The mitigations are practical: use a trailing window long enough to smooth noise but short enough to catch trends (three to six months is the usual band), and override manually for known events. A booked corporate buyout, a school holiday week, a local festival — these are known in advance and the grid should be adjusted by hand. The formula sets the default; your calendar overrides it.

"My gross profit data is messy." Frequently true. Party packages get rung up inconsistently, comps and voucher redemptions distort the picture, and snack-counter margin may not be tracked separately at all. Clean this before you trust the output. If you cannot get gross profit cleanly, run the same division on net revenue with a fixed margin assumption and accept a slightly blunter answer. A blunt number beats no number.

"Not every employee generates revenue." Correct, and the formula already accounts for it — the shift's gross profit is paying for the vest maintenance, the arena reset, the deep clean, and the restock, not just the face-to-face selling. If a specific block is unusually loaded with non-revenue work — say a Monday morning that exists purely for maintenance and inventory — treat it as a separate category with its own lower target, or exclude it from the formula entirely and staff it as a fixed operating cost.

"This will make my managers cut into the bone." It can, if you deploy the target as a ceiling instead of a floor and pair it with the wrong incentive. Guard against it by making the operating minimums non-negotiable and by tracking a service metric alongside labor percentage — session start punctuality, party-host coverage, incident counts. If labor percentage improves while service degrades, the target is set wrong, not the crew.

Where it genuinely breaks. Three cases. First, a brand-new arena with no trailing data — you have nothing to average, so you staff by judgment for a quarter and then switch to the formula. Second, a step-change in the business: a new attraction, a major renovation, a competitor opening or closing nearby invalidates your history and you should shorten the trailing window aggressively or reset it. Third, credential-gated coverage. If your insurance or your local rules require a certified operator per active session and your math returns fewer people than that, the math loses. Constraints always outrank optimization.

The cultural piece nobody mentions. Publishing a per-employee number changes how the floor behaves, and not always in the direction you expect. Some employees will hear a quota and get defensive. Frame it as a floor with visible upside — this is what a shift owes; everything past it is where raises and lead roles come from — and it lands as a scoreboard. Frame it as a threat and you will get gaming: staff pushing the highest-margin item regardless of fit, or quietly discouraging refunds. Watch for that in the first month and correct it fast.

Related questions

How do I set the per-employee gross-profit target if I have no history?

Build it from cost. Take your loaded hourly labor cost, multiply by average shift length, then divide by the share of gross profit you want labor to consume. At $17 loaded, a 5-hour shift, and a 50% labor share, the target is $170. Refine once you have a quarter of real data.

Does the formula change for salaried managers?

Yes — exclude them. Salaried leadership is fixed overhead, not variable shift labor. Run the division on your hourly floor crew only, then layer the manager on top as a constant. Mixing fixed and variable headcount into one calculation distorts every daypart at once.

How do I handle booked parties that land in an otherwise dead block?

Treat confirmed bookings as a manual override to the average. If your reservation board shows three parties on a Tuesday afternoon that normally averages $480, staff to the booked revenue, not to the historical mean. The average is your default; the booking sheet outranks it.

Should each role have its own target?

Usually not at a single arena — it adds complexity without much payoff. Run one blended target for the whole floor crew and manage composition through your role mix. Split targets only if you have a genuinely separate profit center, such as a full bar or kitchen, with its own margin structure.

How often should I re-run the calculation?

Refresh the trailing average weekly, but only redraw the grid when the average moves enough to change a headcount — roughly a 15% shift in a block's gross profit. Re-cutting the schedule for noise creates churn on the floor and erodes trust in the number.

FAQ

What if my laser tag arena's gross profit per shift swings hard by season?

Seasonal swing is expected, not a defect in the method. Use a trailing three-to-six-month average so one hot summer week or a dead January does not whipsaw your counts. When a block's average gross profit climbs 50% for the summer stretch, you re-run the division for that season — the target stays fixed and the headcount rises on its own. Many operators keep two saved grids, a peak-season and an off-season version, and swap between them on known dates.

Can I use this if my crew mixes part-time and full-time employees?

Yes. The target attaches to the shift, not to employment status, so it applies identically to a weekend teenager and a full-time lead. Divide the block's average gross profit by the target to get total bodies required, then fill those slots with whatever mix your availability board allows. The only adjustment worth making is on shift length: if your part-timers work four hours and your full-timers work eight, build the target off a standard shift length and prorate for outliers.

What if my agreed target is not $160?

Then use your own. $160 is a workable starting point for a typical arena, not a mandate. Your figure should come out of your actual loaded labor rates, your local wage market, and the labor share you intend to keep. Pick a number leadership genuinely stands behind and apply it uniformly across every daypart, because the comparisons between blocks are only honest if the denominator is constant.

How do I schedule a shift whose gross profit is below one employee's target?

The math is telling you it wants roughly one person — often just an opener or a manager keeping the lights on. The formula does not break; it returns a fraction under one. Staff the bare minimum needed to open safely and legally, and no more. If that block returns a fraction under one for several consecutive months, the more useful question is whether those hours should be open at all, or whether the doors could open ninety minutes later.

Does this account for cleaning, vest maintenance, and restocking?

Indirectly, yes — the gross profit a shift produces is already funding that non-revenue labor. The formula assumes everyone clocked in contributes to the operation, not only to guest-facing sales. If a particular block carries an unusually heavy maintenance load, nudge that block's target down to make room, or carve maintenance out as a separately scheduled fixed cost so it stops distorting your revenue-facing dayparts.

How does this connect to the RevOps capacity planning I read about for sales teams?

It is the same discipline in a different building. A RevOps leader sizes a sales team by dividing a revenue target by quota per rep; you size a shift by dividing gross profit by target per employee. Both replace headcount-by-habit with headcount-by-throughput, both require a published denominator, and both fail identically when the denominator is invented rather than derived from real cost and real performance.

Sources

• U.S. Bureau of Labor Statistics, Amusement and Recreation Industries occupational employment and wage data — https://www.bls.gov/oes/current/naics4_713900.htm
• U.S. Bureau of Labor Statistics, Employer Costs for Employee Compensation (loaded labor cost benchmarks) — https://www.bls.gov/news.release/ecec.nr0.htm
• U.S. Small Business Administration, guidance on managing business costs and cash flow — https://www.sba.gov/business-guide/manage-your-business
• U.S. Department of Labor, Wage and Hour Division — Fair Labor Standards Act compliance for hourly and youth employees — https://www.dol.gov/agencies/whd/flsa
• IRS, Employment Taxes for Small Businesses (payroll burden) — https://www.irs.gov/businesses/small-businesses-self-employed/employment-taxes
• International Association of Amusement Parks and Attractions (IAAPA) — industry operations and safety resources — https://www.iaapa.org/
• Harvard Business Review, "Why Good People Leave Bad Schedules" and related research on scheduling stability in hourly work — https://hbr.org/2019/03/research-when-retailers-schedule-workers-more-predictably-sales-and-profits-go-up
• U.S. Census Bureau, Service Annual Survey — arts, entertainment, and recreation revenue data — https://www.census.gov/services/index.html
• OSHA, Small Business Safety and Health Handbook — https://www.osha.gov/smallbusiness

Related on PULSE

• [How Do I Know Where, When, and How Many People to Schedule at Each of My Multi-Unit Retail Locations?](/knowledge/tl0001)
• [How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?](/knowledge/tl0002)
• [How Do I Know How Many Cooks and Servers to Schedule Each Shift at My Pizza Restaurant?](/knowledge/tl0003)
• [How Many Salespeople Should I Schedule Each Day on My Furniture Store Floor?](/knowledge/tl0004)
• [How Do I Decide How Many Reps to Schedule at Each Store in My Mattress Retail Chain?](/knowledge/tl0005)