How Many Employees Should I Schedule Each Shift at My Indoor Skydiving Center?

The job this staffing model is hired to do

Most indoor skydiving centers schedule by habit. Somebody decided years ago that Tuesdays run two people and Saturdays run five, and that pattern calcified into the operating rhythm long after the flight manifest changed underneath it. The job this model is hired to do is replace that habit with arithmetic that anyone on the floor can check, and to do it without pretending a wind tunnel is a coffee shop.

Start with the number that makes the whole thing work: the revenue an average flight instructor should support during an ordinary hour of ordinary work. Call it $200 for the sake of a worked example — your real number depends on your first-flight package price, your block-time pricing, your instructor-to-flyer rotation speed, and what your local market bears. The point of the figure is not precision to the dollar. It is that leadership, the owner, and every instructor on the floor share one yardstick. When you tell a new hire "if you show up, handle a normal crowd, and deliver standard service, you should support about $200 an hour," you have said something falsifiable. The instructor who wants to be exceptional does not stop there — they hit the baseline and then chase upsells, rebookings, block-time conversions, and the birthday party that turns into a coach-class package.

The second job is protecting margin during the parts of the week nobody watches. Every operator knows Saturday afternoon is busy. What kills a tunnel's P&L is the Wednesday 11am–2pm stretch where three people are clocked in against $300 of flight revenue, week after week, because that is how the template was built in 2019. Revenue-divided-by-target catches those blocks automatically. Pull the trailing four to eight weeks of revenue by hour and by day, divide, and the schedule writes itself: a $400 Tuesday afternoon block needs two instructors, a $1,200 Saturday evening block needs six.

The third job — and this is where a wind tunnel diverges hard from retail or restaurant staffing — is that the math produces a *minimum from the revenue side only*. It never produces a legal or safe minimum. A certified flight instructor must be in the chamber with every first-time flyer. A separate, qualified tunnel operator must be at the control console, and that operator is not simultaneously spotting in the chamber. Add a front-desk person handling waivers, gear sizing, and payment, and your actual floor minimum during any open hour is typically three people regardless of what revenue says. If revenue math returns 1.4 instructors for a dead Monday hour, the honest answer is that you should probably be closed that hour, not that you should run understaffed.

That reframing is useful. A revenue-per-instructor model does not just tell you how many Employees to schedule — it tells you which hours do not deserve to be open at all. Cutting a three-hour Monday morning block that reliably produces $180 an hour against a $60/hour fully-loaded labor cost per body is often a bigger margin win than any scheduling optimization inside the hours you keep.

How it fits the RevOps stack

Scheduling looks like an HR problem and behaves like a RevOps one. The inputs are demand signals, the outputs are capacity decisions, and the feedback loop runs on revenue per labor hour — which is the same shape as quota capacity planning in a sales org, just with a wind tunnel instead of a pipeline.

Here is the practical data chain at a tunnel. Bookings land in your reservation system — Peek, Checkfront, an in-house manifest, or whatever your franchise mandates. Payments and walk-in retail flow through the POS. Those two together give you revenue by hour, which is the only input the model genuinely requires. That feeds the headcount calculation. The calculation feeds a scheduling app, which publishes to instructors' phones. Clock-in data comes back from the time clock, and the comparison between scheduled-versus-actual labor cost against actual revenue closes the loop for next cycle.

The thing that makes this a RevOps problem rather than a scheduling problem is step J. Most centers publish a schedule and never look back. The loop only compounds if you review actual revenue per labor hour weekly and adjust the target. If instructors consistently clear $260 an hour on a $200 target, your target is stale and you are overstaffing every block by roughly 30%. If they consistently miss it, either the target is fantasy or something upstream — booking conversion, package mix, rotation speed in the chamber — is broken, and no amount of schedule tinkering fixes an upstream problem.

Watch for the integration trap. A POS-connected scheduling tool will happily forecast staffing from sales history, but it forecasts *total* labor, not role-specific coverage. It does not know that your tunnel operator cannot double as the instructor in the chamber. Every demand-forecasting tool needs a manual role-minimum layer bolted on top, and you own that layer.

The same loop applies to adjacent venues — trampoline parks, climbing gyms, karting tracks, escape rooms — anywhere throughput is capped by a physical asset and safety-certified staff. Ropes-course operators run nearly the identical structure: a hard certified-staff-per-participant ratio, a fixed asset that caps throughput, and revenue that clusters into weekend spikes. If you also run a café or a retail counter, model those as separate revenue streams with their own per-employee target, because a $200 flight-instructor target has nothing to do with what a $14 retail transaction supports.

Pricing, engagement models, and typical ranges

The methodology is free; the tooling is not, and the pricing model matters more than the feature list for a business with a deep part-time bench.

Per-location pricing is the friendly shape for a tunnel. Homebase offers a free tier covering scheduling and time clock for a single location with unlimited employees, with paid tiers running roughly $25 to $100 per location per month depending on features. 7shifts is built for hospitality and high-turnover hourly floors, with a free tier for one location and paid plans in the $35 to $80 per location per month range. Because a typical indoor skydiving center carries fifteen to thirty names on the roster — instructors, operators, front desk, party hosts, most of them part-time — per-location pricing is dramatically cheaper than per-seat.

Per-user pricing works when your crew is lean and stable. When I Work starts around $2.50 per user per month and climbs to roughly $8 with attendance and labor tools. Deputy runs about $4.50 per user for scheduling and around $6 for the premium tier with time and attendance. Sling has a genuinely usable free tier with paid plans in the low single digits per user. Do the arithmetic honestly: at 25 staff, a $4.50 per-user tool costs $112 a month while a $35 per-location tool costs $35. At 6 staff, the ordering flips.

Operator-grade and enterprise. Workforce.com sits around $4 per user per month and targets multi-location hourly operators with demand-driven scheduling, wage forecasting, and multi-jurisdiction compliance. HotSchedules (now part of Fourth) and Shiftboard sell through custom quotes and are built for chains with dedicated operations staff. Shiftboard's credential-based scheduling — matching certifications to shifts automatically — is genuinely relevant to a tunnel where instructor ratings gate who can work which slot, but it is heavy for a single site.

Treat all published pricing as a starting point and verify current rates directly; vendors change tiers frequently.

The cost that actually moves your P&L is labor, not software. Run the numbers on your own floor. If a fully-loaded instructor hour costs you $28 including payroll taxes and workers' comp — and workers' comp on a wind tunnel is not a rounding error — then one unnecessary body across a six-hour weekday shift burns $168, or roughly $8,700 a year on a single recurring overstaffed block. That dwarfs any scheduling subscription. It also means the discipline of running the division every month is worth more than which app you pick.

Certification and training carry real cost too. Instructor ratings require documented tunnel hours and periodic recurrency, and the person earning those hours is not generating revenue while doing it. Budget training time as a separate line rather than hiding it inside a revenue-producing shift, or your revenue-per-instructor numbers will look artificially bad in the weeks you develop people. The same applies to safety drills and equipment checks — schedule them into low-revenue blocks where they cost you the least.

How to evaluate and shortlist

Pick the method before the tool. A scheduling app fed a made-up target produces a confident, well-designed, wrong schedule.

Establish and pressure-test the target. Sit with your floor leadership and pick the revenue-per-instructor figure. Then sanity-check it against reality: take last month's total flight revenue and divide by total instructor hours worked. If your stated target is $200 and the actual came in at $145, either you are chronically overstaffed or your target is aspirational rather than baseline. Fix the discrepancy before you build a schedule on it.

Pull demand at the right granularity. Hourly, by day of week, over four to eight weeks. Four weeks is enough to see the shape; eight smooths out a rained-out weekend or a school-break spike. Longer than that and you start averaging across seasonal shifts that you actually want to see. Tunnels are strongly seasonal — school holidays, summer, the run-up to the winter holidays — so keep last year's same-period data available as a cross-check rather than relying on the trailing window alone during a season change.

Run the division and stress the edges. Revenue ÷ target = raw instructor count per block. Then walk each block against the safety floor and role minimums. Any block where the math returns fewer bodies than the safety floor gets flagged for a different decision: shorten hours, consolidate into block-time sessions, or accept the loss as a customer-availability investment and say so out loud.

Place shifts where the revenue lands, not where the clock is convenient. The count tells you how many; the demand curve tells you when. A tunnel with an evening-and-weekend concentration wants a light opening shift, a thin mid or swing through the afternoon lull, and heavy weekend coverage — not everybody parked from noon to eight. Build overlap deliberately at the shoulders: fifteen to thirty minutes of overlap at shift change so gear handoff, manifest briefing, and chamber turnover do not stall a paying flyer. Overlap is a real cost; budget it explicitly instead of discovering it in the timecards.

Then shortlist the tool against four questions. Does it price the way your roster is shaped? Does it connect to your POS or booking system, or will you re-key revenue by hand every month? Can it encode role minimums and certifications, or does it treat all bodies as interchangeable? And does it handle the compliance you actually face — minor-employee hour restrictions, break rules, overtime alerts, and predictive-scheduling ordinances if you operate in a jurisdiction that has them?

Prove it free for a month. Every serious tool in this category has a free tier or a trial. Run one full cycle: build the schedule from the division, publish it, then compare actual revenue per labor hour against plan. If the method holds on your floor, then decide whether execution features are worth paying for. If it does not hold, the tool was never the problem.

Buyer decision framework

The decision tree is short because most of the branches collapse quickly once you know your roster shape and whether you run one site or several.

A few branches deserve commentary. The "under 10 staff" fork is genuinely about arithmetic, not sophistication — small tunnels often need *more* scheduling nuance than large ones because a single call-out is a 25% capacity loss. Do not read low headcount as low complexity.

The POS-integration fork is where operators most often overbuy. Automated demand forecasting is worth real money if your revenue pattern is volatile and hard to eyeball. If your tunnel does the same thing every week — quiet weekday mornings, moderate afternoons, packed Friday evening through Sunday — you can run the division in a spreadsheet in twenty minutes a month and spend nothing. Buy forecasting when the pattern is genuinely hard to see, not because the feature exists.

The compliance fork is the one people underestimate. Employing minors as party hosts or front-desk staff brings hour restrictions and break rules that vary by state. Multi-site operations can trip fair-workweek ordinances requiring advance schedule notice and penalty pay for late changes. If either applies to you, built-in compliance guardrails are not a nice-to-have — they are the cheapest liability insurance in the stack.

One more thing the tree does not show: staffing is not purely a cost decision. Understaffing a peak block does not just risk safety, it shortens flight rotations, lengthens the wait between turns, and produces the review that says "felt rushed, felt like a conveyor belt." That review costs you future bookings, which shrinks next month's revenue, which the model then reads as a signal to schedule fewer people. The doom loop is real. When a block sits genuinely on the line between two headcounts, round up — the marginal instructor hour is cheap relative to the experience quality that drives repeat business and referrals in a discretionary-spend category.

Related questions

How do I handle no-shows and call-outs without overstaffing every shift?

Build an on-call tier rather than padding every block. Designate one or two instructors per weekend as on-call with a defined callback window and a small stipend if activated. That costs far less than adding a standing body to every peak shift, and it keeps your baseline honest.

Should front-desk and party hosts use the same revenue target as instructors?

No. Model each role against the revenue it actually supports. A flight instructor's number reflects tunnel time; a retail or café employee's number reflects a completely different transaction size. Blending them produces a target that describes nobody's job accurately.

How often should I recalculate the schedule?

Refresh the underlying demand data monthly and rebuild the block-level headcounts at least quarterly, plus ahead of any known seasonal shift — summer, school breaks, the winter holidays. Weekly, just review actual revenue per labor hour against plan and patch obvious misses.

Does this method work for a multi-tunnel or franchise group?

Yes, with one adjustment: set the revenue-per-instructor target per site, not corporately. Market pricing, package mix, and tunnel throughput vary enough between locations that a single group-wide number will overstaff some sites and starve others.

What if my revenue data is messy or incomplete?

Start with what you have — even four weeks of imperfect hourly totals beats scheduling by habit. Clean the obvious outliers, note the gaps, and use the resulting numbers as a directional draft. Data quality improves fastest once someone is actually using it.

FAQ

What is the single most important input to this calculation?

Projected revenue for each hour of operation. Everything else derives from it. Dividing that hourly revenue by a pre-agreed revenue-per-instructor target gives you a defensible headcount that reflects actual customer demand rather than tradition, manager preference, or whoever complains loudest about hours.

How do I set the revenue-per-instructor target for my center?

Agree on a figure with your floor leadership that reflects what an average instructor supports during an average shift, then validate it against history — last month's flight revenue divided by total instructor hours. It is a baseline, not a ceiling. Revisit it whenever pricing, package mix, or rotation speed changes materially.

Can I ever schedule fewer people than the math suggests?

No. The revenue calculation produces a floor from the revenue side only. You still need a certified flight instructor in the chamber for every flyer and a separate qualified operator at the control console, plus front-desk coverage during open hours. If the math returns fewer bodies than the safety and role minimums, close that block rather than run it thin.

What if my revenue swings hard between hours and days?

That volatility is precisely the argument for using trailing four-to-eight-week data broken out by hour and day. It captures the real shape — a quiet Tuesday afternoon versus a packed Saturday evening — so each block gets its own headcount rather than inheriting a weekly average that fits no actual hour.

How do I decide where to place the shifts once I know the counts?

Overlay the counts on your hourly demand curve. Schedule a light open, a thinner mid or swing shift through the afternoon lull, and heavy coverage across weekend and holiday peaks. Add fifteen to thirty minutes of deliberate overlap at each handoff so gear checks and manifest briefings do not stall a paying flyer.

Does the same approach transfer to other venues?

Yes, anywhere a physical asset caps throughput and certified staff gate safety — trampoline parks, climbing gyms, karting tracks, ropes courses. The revenue-per-employee division is identical; only the role minimums and certification rules change, and those you encode as a hard layer on top of the math.

Sources

• U.S. Department of Labor, Wage and Hour Division — youth employment and hours standards: https://www.dol.gov/agencies/whd/youthrules
• OSHA — recordkeeping and general duty clause guidance for employers: https://www.osha.gov/recordkeeping
• U.S. Bureau of Labor Statistics — Employer Costs for Employee Compensation: https://www.bls.gov/ncs/ect/
• U.S. Small Business Administration — managing employees and staffing: https://www.sba.gov/business-guide/manage-your-business/hire-manage-employees
• Homebase — scheduling and time-clock plan details: https://joinhomebase.com/pricing/
• 7shifts — hospitality scheduling plans and POS integrations: https://www.7shifts.com/pricing
• When I Work — shift scheduling pricing and documentation: https://wheniwork.com/pricing
• Deputy — scheduling and demand-forecasting plans: https://www.deputy.com/pricing
• Workforce.com — labor forecasting and compliance platform: https://workforce.com/
• International Bodyflight Association — instructor rating and tunnel safety program: https://www.tunnelflight.com/

Related on PULSE

• [How Many Attendants Should I Schedule Each Day at My Car Wash?](/knowledge/tl0067)
• [How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?](/knowledge/tl0002)
• [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)