How Many Employees Should I Schedule Each Shift at My Skate Park?

Why the gross-profit divide beats the alternatives

Most skate park operators schedule one of four ways, and only one of them survives a bad quarter.

The habit method. "We've always run three on a weekday, six on a weekend." It's the most common approach in owner-operated facilities and it's the most expensive one, because habit never contracts. When a Monday session that used to draw 40 skaters drops to 18, the three employees stay on the schedule — the manager has no trigger to cut. Habit also never expands: when a new middle school opens two miles away and Wednesday afternoons double, the deck stays at three and your wait times, register lines, and rental counter all degrade at exactly the moment you finally have demand.

The ratio method. Some parks staff purely to a supervision ratio — one employee per 25 skaters on the floor, one per 40, whatever the insurance carrier or state youth-facility rule specifies. This is a floor you absolutely must honor, but it's a terrible primary scheduling logic because it's blind to revenue. A ratio tells you the minimum bodies required to run the session legally and safely. It says nothing about whether the session earns enough to pay for those bodies. Ratio-first parks routinely staff a dead Tuesday morning to the same standard as a packed Saturday birthday block and wonder why labor eats 38% of revenue.

The percent-of-sales method. Restaurants live here: hold labor at, say, 26% of sales, and let that percentage dictate hours. It's a real improvement over habit because it moves with volume. Its weakness at a skate park is that revenue mix varies wildly by session — a $12 admission session and a $400 birthday party book very different margins after you back out pizza cost, party-host wages, and consumable rentals. Percent-of-sales treats a dollar of party revenue and a dollar of admission revenue as identical when they are not.

The gross-profit divide. This is the method the answer is built on, and it fixes the blind spot in the other three. You take revenue *after* variable cost of goods — so admission dollars, session dollars, rental dollars, and concession margin all land in a single comparable pool — and you divide by an agreed per-employee daily contribution target. The result is a headcount that is automatically volume-aware, mix-aware, and defensible to a manager who wants to schedule their friends.

The number matters less than the agreement. Say your leadership team sets $150 in daily gross profit as the floor an average employee produces on an average shift with average traffic. That is not a stretch goal. It is the honest baseline that says: if you clocked in, worked the counter or the deck competently, and served a normal number of guests, you covered your wage, your share of the burden, and left profit behind. Employees who want real money don't stop at $150 — they hit it doing ordinary work and then dig for the next $150 in party upsells, pro-shop attachment, and rebookings.

Where the divide gets overridden: the ratio floor always wins. If the math says two employees and your carrier's supervision rule says three for the expected head count, you run three. The divide is a ceiling-setter and a cut-trigger, not a license to understaff a floor full of nine-year-olds.

How to choose between them for your specific park

Pick the method that matches your data maturity and your risk profile, not the one that sounds most sophisticated.

If you have twelve or more months of clean POS data by day-part, run the gross-profit divide as your primary and the ratio as your override. You have enough history to trust a trailing three-to-six-month average, and you can segment by session type — open skate, lesson block, league night, private party — instead of just by day.

If you have three to six months of data, still run the divide, but rebuild the averages monthly rather than quarterly and widen your buffer. Short histories over-weight one anomalous week. A single rained-out Saturday or one viral TikTok that packed a Thursday will drag a three-month average enough to mis-staff you for a full scheduling cycle.

If you have no day-part data at all, do not improvise a formula. Start recording it this week — most modern POS systems export transaction-level data by hour with two clicks — and in the interim staff to the ratio floor plus one flex employee you can send home at the 90-minute mark if the session doesn't materialize. That flex-cut policy has to be written and communicated in advance, or you burn goodwill with part-timers who drove twenty minutes for a two-hour shift.

If you're multi-site, the divide is the only one of the four that scales, because it produces a comparable number across locations with different price points and different square footage. A downtown park charging $18 and a suburban park charging $11 can't be compared on percent-of-sales, but both can be held to $150 of gross profit per employee-day.

One more selection criterion people skip: who is going to run this every week? If your general manager builds the schedule in eleven minutes on a Sunday night, a method requiring a POS export, a pivot table, and a judgment call will quietly revert to habit inside a month. The divide survives because it collapses to one division problem per shift, which a manager can do on a phone.

Costs, timelines, and expected impact

What it costs to implement. The method itself is free — it's arithmetic against data you already generate. The real costs are software and time.

Scheduling platforms in this category price two ways, and the choice matters more for a skate park than most operators realize. Per-user pricing (When I Work, Deputy, Sling) charges by headcount, typically low single-digit dollars per user per month, scaling up with time-and-attendance modules. Per-location pricing (Homebase, 7shifts) charges a flat monthly fee per site regardless of how many employees you carry. Skate parks skew heavily toward large rosters of part-time and seasonal staff — a 40-person roster covering 14 concurrent slots — which makes per-location pricing structurally cheaper. Homebase notably runs a free tier for a single location with unlimited employees, which is often enough to run this method for a full season before you spend anything. Verify current pricing directly with each vendor; these plans change.

Time to first schedule. Pulling six months of gross profit by day-part from a modern POS: two to four hours if your item categories are clean, a full day if you have to re-map miscoded SKUs. Agreeing on the per-employee target with your leadership team: one meeting. Building the first schedule off the divide: about an hour. Total, roughly one working day.

Time to trustworthy numbers. Four to six weeks. Your first two schedules will feel wrong because they'll contradict habit, and you'll get pushback — "we can't run four on a Monday, we've always run five." Hold the line for a month and track the actual complaint volume, wait times, and incident reports. If they don't move, the fifth body was never load-bearing.

Expected impact. The honest answer is that impact is entirely a function of how mis-staffed you were before, and any operator quoting you a universal savings percentage is guessing. What the method reliably produces is *directional* correctness: fewer bodies on genuinely dead sessions, more on the sessions that actually earn. Parks that were staffing flat across the week typically discover they were simultaneously overstaffed on two or three weekday sessions and understaffed on peak weekend blocks — the total hours barely move, but the distribution changes substantially, which shows up as shorter rental-counter lines on Saturday rather than as a smaller payroll number.

Second-order effects worth pricing in. Cutting a habitual shift has downstream costs. Part-timers who lose hours quit, and replacing a trained deck attendant costs you recruiting time, a background check where required, and two to three weeks of supervised ramp. If the divide says cut a shift on a session where you have a strong employee who needs the hours, the smarter play is often to move that shift to a peak block rather than delete it. The schedule optimizes gross profit per employee-day; retention optimizes over a season. Reconcile those explicitly instead of letting the spreadsheet decide.

Compliance costs. If you employ minors — and most skate parks do — youth labor rules constrain hours, end-of-shift times, and break requirements, and they vary by state. Some cities add predictive-scheduling ordinances requiring schedules published a set number of days in advance with premium pay for late changes. Both are enforcement risks that dwarf any labor savings the divide produces. Tools with built-in compliance guardrails (Deputy, Workforce.com) exist specifically for this, and the cost of that tier is cheap relative to a single wage-and-hour claim.

Implementation and handoff details

The method dies in handoff, not in design. Here's the sequence that survives a manager change.

Step one — write the target down and say it out loud. Not in a spreadsheet cell. In a one-page document your leadership team signs off on, stating: an average employee working an average shift with average traffic should produce no less than $150 in daily gross profit. Include how you got there and what would change it. When a new GM starts, that page is the first thing they read.

Step two — define what counts as gross profit. Ambiguity here silently corrupts every downstream number. Decide explicitly: admissions and session fees at full value; retail and pro-shop at revenue minus COGS; concessions at revenue minus food cost; parties at package revenue minus food, consumables, and any dedicated party-host wages. Rental revenue net of replacement reserve if you carry one. Write the definition next to the target.

Step three — build the day-part table. One row per session block per day of week, with the trailing average gross profit and the computed headcount. Ten to twenty rows for a single park. Print it. The point of a printed table is that it's auditable — anyone can check whether Saturday's posted schedule matches the number.

Step four — overlay the revenue curve. Headcount tells you how many; the curve tells you when. Pull hourly transaction counts and find where the money actually rings. At most parks that's after-school on weekdays and midday-to-evening on weekends, with a real trough that habit-scheduling ignores entirely. Stagger starts against that curve — an opener, a mid, a closer — rather than starting everyone at the same time and paying four people to watch an empty deck for ninety minutes.

Step five — assign role coverage inside the count. Four employees is a number, not a plan. Four means: one on the register, one on rentals, two on the deck. If your ratio rule counts only floor-supervising employees, your register person doesn't help you meet it, and your effective headcount is two, not four. Map roles inside the count before you publish.

Step six — define the escape hatches in advance. A written call-in-or-send-home policy: if projected attendance at T-minus-90-minutes is below X, the designated flex employee is released with a minimum-hours guarantee. If it's above Y, the on-call is activated. Both thresholds are written, both are known to staff, neither is a manager's mood.

Step seven — run the weekly variance review. Fifteen minutes. Compare each shift's actual gross profit against what the schedule assumed. Two consecutive weeks of a block coming in 20% above or below its average is a signal to rebuild that row, not to wait for the quarterly refresh. This is the step that makes the whole thing a RevOps loop rather than a one-time exercise: instrument, measure variance, correct, repeat.

Step eight — hand it off with the reasoning intact. When a manager inherits the schedule, they inherit the target document, the gross-profit definition, the day-part table, and the variance log. Without those four artifacts, they inherit a grid of names and will revert to habit within a scheduling cycle, because a grid with no logic behind it is indistinguishable from tradition.

Adjacent applications. The same divide runs unchanged at a trampoline park, a climbing gym, a roller rink, a laser tag facility, or a car wash — anywhere a variable-traffic session model meets an hourly workforce. The only inputs that change are the per-employee target (a function of your margins) and the supervision ratio (a function of your risk profile and regulator). Multi-concept operators running a skate park and a trampoline park under one roof should compute separate targets per concept, then schedule cross-trained employees against the combined curve, which is where the method starts genuinely outperforming anything habit could produce.

Related questions

What if the math says 3.4 employees?

Round to whole people using the trend, not the decimal. If that block has been climbing three weeks running, round up; if declining, round down and keep one on call. Never round down below your supervision-ratio floor regardless of what the trend shows.

Does this work for salaried managers?

No. The divide covers variable hourly coverage only. Salaried management is fixed overhead that sits above the calculation — include their wages in your operating cost when setting the per-employee target, but never in the headcount the division produces.

How do birthday parties change the count?

Treat each booked party as its own line with a dedicated host, priced off package gross profit rather than the open-skate average. Parties have fixed labor requirements independent of general session volume, so they add to the computed count rather than being absorbed by it.

Should seasonal swings change the target or the headcount?

The headcount. Your per-employee gross-profit target is a standard and should stay fixed year-round. Seasonality shows up in the trailing averages, which move the divide's output naturally without anyone renegotiating what an average employee should produce.

What if a shift never hits the target no matter the staffing?

That's a pricing or programming problem, not a scheduling one. A session block that can't clear one employee's target at ratio-minimum staffing is telling you to change the offer, shorten the hours, or close that block entirely.

FAQ

How do I set the per-employee daily gross-profit target?

Work backward from your actual costs. Take a typical employee's fully loaded hourly cost — wage plus payroll taxes, workers' comp, and any benefits — multiply by shift length, then add the share of fixed overhead and profit margin each employee-day needs to carry. Round to a clean number your team can remember. $150 is a common starting point for this kind of facility, but the right figure is the one your own margins produce.

What if my gross profit swings hard week to week?

Use a trailing three-to-six-month average per day-part rather than last week's actuals. That window smooths weather, school calendars, and one-off events while still tracking real trend. If a single week distorts the average by more than about 15%, exclude it as an outlier and note why — a scheduled tournament or a two-day closure shouldn't set your baseline staffing.

Can I apply this per shift instead of per day?

Yes, and you should. Per-day is the coarse version; per-shift is where the money is. Divide each individual session block's average gross profit by the same target, scaled for shift length if your blocks differ — a four-hour evening block should be measured against roughly half of an eight-hour target, not the full number.

Does this work for a park with only five employees?

It works better, because the stakes per body are higher. With a small roster the divide mostly functions as an overstaffing brake — it tells you when the second or third person on a slow Monday isn't earning their shift. Your supervision-ratio floor will bind more often at that size, so expect the ratio to override the math more frequently.

How do I handle employees who consistently beat the target?

Recognize it in scheduling and in pay. High performers should be concentrated on your highest-gross-profit blocks, not spread evenly for fairness. If someone reliably produces double the target, they're carrying a shift that the formula assumed needed two people, and your compensation structure should reflect that before a competitor's does.

What data do I need before I can start?

Three things: transaction-level revenue with timestamps, cost of goods by category, and your labor hours by shift. Every modern POS exports the first; the second requires clean item categorization; the third comes from your time clock. If any one is missing, fix that before building the schedule — the method's output is only as honest as its inputs.

Sources

• U.S. Department of Labor, Wage and Hour Division — youth employment rules: https://www.dol.gov/agencies/whd/youthrules
• U.S. Department of Labor — Fair Labor Standards Act overview: https://www.dol.gov/agencies/whd/flsa
• U.S. Bureau of Labor Statistics — Occupational Employment and Wage Statistics: https://www.bls.gov/oes/
• U.S. Bureau of Labor Statistics — Employer Costs for Employee Compensation: https://www.bls.gov/news.release/ecec.nr0.htm
• OSHA — Small Business Safety and Health resources: https://www.osha.gov/smallbusiness
• U.S. Small Business Administration — Manage your business: https://www.sba.gov/business-guide/manage-your-business
• Homebase — scheduling and time-clock plans: https://www.joinhomebase.com/pricing
• When I Work — employee scheduling pricing: https://wheniwork.com/pricing
• Deputy — scheduling and demand forecasting: https://www.deputy.com/pricing
• 7shifts — labor management for hospitality: https://www.7shifts.com/pricing

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)