How Many Employees Should I Schedule Each Shift at My Axe Throwing Venue?

The end-to-end process from revenue data to a posted schedule

The whole method rests on one agreement you make before you touch a spreadsheet: what revenue should an average lane coach support during an average hour, doing an average job, for an average crowd? Most axe throwing venues land somewhere around $120 an hour. That number is not a stretch goal and it is not a ceiling — it is the honest floor. A coach who supports $120 in an hour is meeting the bar. The coaches who want to grow hit $120 doing ordinary work and then go looking for the upsell: extra throw time, the party package upgrade, the merch rack, the rebooking for next month's corporate event.

Once that number is locked, the process runs in a straight line. Pull trailing four-to-eight-week revenue, broken out by hour and by day of week. Four weeks is the minimum for a stable average; eight weeks smooths out the outlier week when a wedding party rented the whole floor. Any shorter and you are scheduling off noise. Divide each hour block's average revenue by $120. That quotient is your revenue-driven headcount for that block.

Then apply the safety override. One trained, certified coach for every two active throwing lanes, no exceptions, no matter what the division says. If you run twelve lanes and Saturday night has all twelve live, you need six coaches on the floor for safety alone — and the revenue math happens to agree at $720/hour. But on a Tuesday afternoon where four lanes are booked and revenue only justifies two coaches, the safety floor also says two. The two numbers usually converge because both scale with occupied lanes. When they diverge, safety wins, always. A coach watching live blades is not a line item you optimize.

The last step is placement. Headcount tells you how many; revenue timing tells you when. Pull the hourly sales curve and look at when bookings and walk-ins actually post — not when you think they do. Most venues discover the curve is far spikier than the schedule assumes. A light open, a swing shift through the afternoon lull, and heavy overlap for the Friday and Saturday night rush beats parking everyone at noon because that is what last quarter's template said.

That final loop matters more than any single calculation. The schedule is not a document you write once — it is a model you recalibrate as the revenue data moves under you. Venues that re-run the division monthly catch the seasonal drift before it costs them; venues that copy last week forward discover it in the P&L three months late.

Where the schedule creates or leaks revenue

Overstaffing and understaffing do not cost the same thing, and treating them as symmetrical is the most expensive mistake in shift planning. Overstaffing costs you exactly one thing: wages. It is a known, bounded, visible number that shows up on the labor line. Understaffing costs you the walk-out, the bad review, the party that never rebooks, and — in a venue with live blades — a safety exposure that dwarfs any labor savings. The asymmetry means your error bias should lean toward one extra coach on genuinely uncertain blocks, not one fewer.

The clearest revenue leak in an axe throwing venue is the upsell that never happens because nobody had time. Coach-to-guest ratio directly gates the extras: the additional half hour, the axe upgrade, the food and drink add-on, the group photo package, the deposit on the next corporate booking. A coach running four lanes solo is doing pure crowd control — resetting boards, retrieving stuck axes, keeping people behind the line. A coach running two lanes has the ten seconds of slack to walk over and ask whether the group wants to extend. That ten seconds is where margin lives. When you cut a coach from a peak block to save roughly $18 in wages, you are frequently trading it against several times that in unsold extras.

The other side is real too. Dead labor on a Tuesday afternoon compounds. Three coaches on a block that generates $240 means your revenue-per-labor-hour is $80 against a $120 target — you are running the block at two-thirds efficiency, and doing it fifty-two weeks a year turns a rounding error into a meaningful annual number. This is where the trailing-data discipline pays: the slow blocks are usually slow every week, predictably, and they are the easiest place to reclaim hours without touching guest experience at all.

There is an upstream effect most owners miss. The schedule is a demand signal that flows backward into marketing and booking. If your Wednesday evenings consistently need only two employees, that is not just a staffing fact — it is a merchandising fact. It tells you where to aim the league night, the corporate weekday package, the happy-hour rate. Venues that treat the revenue-by-hour table purely as a labor input are using half the information in it. The same table that tells you to staff two coaches on Wednesday at 6pm is telling you that Wednesday at 6pm has capacity to sell.

Downstream, the schedule feeds retention. Chronic understaffing on peak nights is the single most reliable way to burn out the good coaches, and in a venue that runs on certified staff, losing an experienced coach costs you weeks of training runway before the replacement is safe on the floor unsupervised. A schedule that consistently puts six people on a six-person block is a retention tool disguised as a spreadsheet. The RevOps framing applies cleanly here: labor is not a cost center to minimize, it is a capacity input to optimize against revenue, and the discipline of measuring output per unit of input is the same discipline whether the unit is a sales rep or a lane coach.

Concrete numbers and benchmarks to anchor against

Start with the target. The $120-per-coach-hour figure works for a mid-market axe throwing venue with typical walk-in and party mix, but it is not universal — it is derived, not borrowed. Calculate your own: take a representative recent month's revenue, divide by the coach hours you actually worked that month, and you have your current baseline. If it comes out at $95, you either have a staffing problem or a pricing problem, and the division will tell you which. If it comes out at $150, your team is likely stretched thin and you may be leaking upsell revenue that a slightly richer schedule would recover.

Run the arithmetic across a real week. A Tuesday afternoon block averaging $240/hour divides to two coaches. Wednesday evening at $360 gives three. Thursday at $480 gives four. Friday night at $600 gives five. Saturday peak at $720 gives six — not five, not seven, six. Sunday afternoon family blocks at $300 give two-and-a-half, which you round up to three because you never round headcount down against a safety-sensitive floor. Total those blocks across the week and you have your labor hours; multiply by your blended wage and you have your labor cost before you have hired anyone.

Watch the seasonal drift. If summer corporate team-building pushes your Saturday peak from $720 to $960, the formula moves you from six coaches to eight without any argument or negotiation. That is the point — the number changes because the revenue changed, not because a manager lobbied for it. Same in reverse: a January slump that drops Saturday to $480 means four coaches, and the conversation with the team is about the data, not about favoritism.

Some practical benchmarks worth tracking alongside the headcount number. Labor as a percentage of revenue is the standard hospitality frame; entertainment venues commonly run their floor labor in a band that a $120 target implicitly sets — if your blended coach wage is $18 loaded, then $120 of supported revenue puts direct floor labor around 15% of revenue for that block. Track it weekly. When it drifts above your band on a specific recurring block, that block is either overstaffed or underpriced.

Track scheduled-versus-actual as a separate number. Most venues schedule well and then leak on execution: the coach who clocks in twelve minutes early every shift, the peak block that runs thirty minutes past close because nobody was released. Those minutes are invisible individually and material in aggregate. A time clock that enforces the scheduled start is worth more than another round of schedule optimization.

For a brand-new venue with no history, back into the estimate. Take your lane count, your realistic Saturday-night occupancy assumption, your average booking price per person, and your average party size. Twelve lanes at 80% occupancy, six throwers per lane rotation, at $25 a head for a 90-minute session gives you a defensible starting revenue estimate for that block. Divide by $120, apply the safety floor, and staff it. Then replace every assumption with real data as the first four weeks land. A rough model corrected weekly beats a confident guess held for a year.

Pitfalls that quietly wreck an otherwise sound schedule

The most common failure is scheduling to headcount instead of to hours. An owner decides the venue "runs six people on Saturday" and posts six full shifts covering open to close. But the $720 peak lasts three hours, not eight. The other five hours run at $300 and need three. Scheduling six flat across the day burns roughly fifteen unnecessary coach-hours every Saturday. The fix is staggered shifts with deliberate overlap: two coaches open, two more arrive as the curve climbs, two more for the peak, and early releases as it falls. Staggering feels fussy to build the first time and then becomes the template.

Second pitfall: averaging away the spike. If you average an entire Friday evening you get a number that is wrong for every hour in it. Seventy percent of the revenue may land in a three-hour window, and an evening-wide average leaves you overstaffed at 5pm and underwater at 8pm. Always divide at the hour or half-hour block level, never the daypart.

Third: letting the safety floor become a ceiling. One coach per two active lanes is the minimum, and some blocks legitimately need more than the ratio or the revenue math produces — a large corporate group with first-time throwers needs more hands than the same revenue from experienced league players. Build a manual override into the process and use it for known-difficult bookings. The formula is a default, not a straitjacket.

Fourth: ignoring the certification pipeline. Your schedule is only feasible if you have enough certified employees to fill it. Venues that run lean on certified staff discover that a single call-out on a Saturday drops them below the safety floor and forces a lane closure — which costs far more than the wages of the bench coach they never trained. Keep certified headcount comfortably above your peak requirement so a call-out is an inconvenience, not a closure.

Fifth: skipping the agreement conversation. If the $120 target lives only in your spreadsheet and never gets said out loud to the floor, the schedule reads as arbitrary. Say it plainly: this is what an average shift should support, here is the data, here is why Saturday gets six and Tuesday gets two. Once the team understands the yardstick, scheduling stops being a political negotiation. It becomes arithmetic that everyone can check.

Sixth: minors and labor-law exposure. Entertainment venues run a lot of young part-time staff, and break rules, hour caps, and school-night restrictions can silently make your posted schedule non-compliant. If you run minors or operate across jurisdictions, use a tool with built-in compliance guardrails rather than tracking it in your head.

Seventh: not closing the loop. The single biggest difference between venues that schedule well and venues that schedule badly is whether anyone compares planned headcount to actual revenue after the fact. Every Monday, take last week's actual revenue by block and divide by the coaches you actually had. If the number came in at $95, you were overstaffed. If it came in at $165, you were thin and probably left upsell revenue on the floor. That one review is worth more than any software purchase.

Selection checklist for the tool that runs the math

The method matters more than the app, and any tool gets better when you feed it a real revenue-per-coach number. But the tools are not interchangeable, and the right pick follows from the shape of your operation rather than from a feature list.

The first fork is pricing model. Per-location pricing wins decisively when you carry a deep bench of part-timers and seasonal staff — common in axe throwing, where a venue may keep twenty-five names on the roster to fill twelve slots on a weekend. Per-user pricing wins when you run a lean, stable crew of full-timers. Do the arithmetic against your actual roster size before you commit; the difference over a year is often larger than the headline price gap suggests.

The second fork is whether you want the tool to suggest coverage or just publish it. Tools that connect to your POS and forecast against sales will propose staffing automatically, which maps directly onto the revenue-divided-by-target method. Lighter tools handle availability, swaps, mobile clock-in, and reminders extremely well but expect you to bring the headcount. If you already know your hourly targets, execution-focused tools are cheaper and entirely sufficient.

The third fork is compliance weight. Run minors, long weekend shifts, or multiple sites and built-in labor-law guardrails stop being a nice-to-have. Single-site venues with adult staff can skip that tier and save real money.

Whatever you pick, prove the method before you pay for it. Run the division by hand or on a free tier for a month and confirm the $120 target actually reflects your floor. If the trailing data says your real number is $140, you have been overstaffing and the tool would have automated the wrong assumption at scale. Software amplifies whatever method you feed it, correct or not.

How the method travels to adjacent operations

The revenue-divided-by-target approach is not specific to axe throwing, which is a useful thing to know if you run more than one concept or plan to expand. A car wash divides its hourly revenue by a per-attendant target. A bowling center divides by a per-lane-attendant target. A restaurant divides by revenue-per-labor-hour, which is the same arithmetic with a different denominator. The mechanics port cleanly; what changes is the target number and the safety overlay.

What makes an axe throwing venue distinctive is that the safety floor is genuinely binding rather than advisory. A car wash that is one attendant light on a slow Tuesday has a slower line. A throwing venue that is one certified coach light has unsupervised blades. That single difference is why the ratio override sits on top of the revenue math rather than inside it, and why your certified-staff bench needs more depth than a comparable venue of the same revenue.

The adjacent workflow worth building next is booking-to-schedule linkage. If your booking system knows that a forty-person corporate event lands next Thursday at 6pm, that information should reach the schedule before you build it, not after. Most venues run these two systems in parallel and reconcile manually, which is exactly the kind of gap where an understaffed peak comes from. Even a weekly manual check — pull next week's confirmed bookings, compare against the revenue-derived headcount, adjust upward where a large group lands — closes most of the exposure without any integration work.

Finally, the same table drives hiring, not just scheduling. Sum your weekly revenue-derived coach-hours, divide by the average weekly hours per employee you can realistically offer, and you have your required roster size. Add a buffer for call-outs, certification lag, and turnover. That gives you a hiring number that is derived from revenue rather than from a vague sense that you are short-handed — the same logic a RevOps team applies when it sizes a sales floor off pipeline coverage instead of off gut feel.

Related questions

How many lanes can one coach safely supervise?

Two active throwing lanes per certified coach is the standard working floor. Some venues tighten to one-to-one for first-time groups or large corporate events where throwers need more instruction and correction. Never loosen the ratio to hit a labor target.

What if my revenue data is only two weeks old?

Two weeks is workable but noisy. Use it, then widen to four and eight weeks as the data accumulates. A single unusual week — a holiday, a private buyout, a weather event — can distort a two-week average by twenty percent or more in either direction.

Should managers count toward the headcount number?

Only if they are actually coaching lanes. A manager running the desk, handling bookings, and covering the bar is not supervising blades and should not be counted against the safety ratio. Count working coaches, count desk and bar separately.

How often should I rebuild the schedule from scratch?

Re-run the division monthly with fresh trailing data, and rebuild fully at each seasonal turn. Weekly, you are only adjusting for known bookings and availability — not recalculating the model. Copying last week forward indefinitely is how drift starts.

FAQ

What is the most important factor when deciding how many employees to schedule?

Expected revenue for that specific hour block. Dividing that hour's projected revenue by your agreed revenue-per-coach target gives a clear, defensible headcount. This removes guesswork and ties staffing directly to business performance instead of habit, favoritism, or whatever last week's template happened to say.

How do I handle safety minimums when revenue is low?

Safety overrides the formula, always. Even if the division suggests one coach, keep at least one trained, certified coach for every two active throwing lanes. Live blades require supervision regardless of how quiet the block is. If revenue cannot support the safety floor, close lanes rather than thin the coverage.

What if traffic on weekdays looks nothing like weekends?

That is precisely why you pull trailing revenue by hour and by day rather than by week. A slow Tuesday afternoon and a Saturday night peak produce entirely different headcounts from the same formula. The math adapts automatically, which also catches seasonal patterns like a summer surge in corporate team-building bookings.

How do I decide where to place opens, swings, and closes?

Headcount tells you how many; the hourly revenue curve tells you when. Schedule opens at the start of your genuinely busy periods, a swing shift through the afternoon lull, and heavy overlap for the Friday and Saturday rush. Stagger arrivals rather than posting identical full shifts across the day.

Can I use this if I have no historical revenue data yet?

Yes. Estimate from lane count, expected occupancy, average ticket price, and typical party size to build a starting revenue figure per block. Divide by your target, apply the safety floor, and staff it. Replace every assumption with real numbers as the first four to eight weeks of data arrive.

How do I know whether my per-coach target is set correctly?

Take a representative month's revenue and divide by the coach hours you actually worked. That is your current real number. If it lands well below your target you are overstaffed or underpriced; well above it and your team is likely stretched thin and leaving upsell revenue unclaimed.

Sources

• U.S. Bureau of Labor Statistics — Occupational Employment and Wage Statistics for amusement and recreation attendants: https://www.bls.gov/oes/current/oes393091.htm
• U.S. Department of Labor — Wage and Hour Division, youth employment and hours standards: https://www.dol.gov/agencies/whd/youthrules
• U.S. Department of Labor — Fair Labor Standards Act overtime pay requirements: https://www.dol.gov/agencies/whd/overtime
• OSHA — Small Business Safety and Health Handbook: https://www.osha.gov/smallbusiness
• U.S. Small Business Administration — Manage your business operations guidance: https://www.sba.gov/business-guide/manage-your-business
• Homebase — employee scheduling and time tracking plans: https://joinhomebase.com/pricing
• 7shifts — hospitality scheduling and labor cost tools: https://www.7shifts.com/pricing
• When I Work — shift scheduling for hourly teams: https://wheniwork.com/pricing
• Deputy — demand-based scheduling and compliance features: https://www.deputy.com/pricing
• Workforce.com — labor forecasting and wage cost control: https://workforce.com/pricing

Related on PULSE

• [How Many Attendants Should I Schedule Each Day at My Car Wash?](/knowledge/tl0067)
• [How Many Sales Reps Do I Need to Hire for My Logistics Company?](/knowledge/tl0058)
• [How Many Salespeople Do I Need to Hire for My Car Dealership?](/knowledge/tl0052)
• [How Many Producers Do I Need to Hire for My Insurance Agency to Grow My Book?](/knowledge/tl0015)
• [How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?](/knowledge/tl0002)