How Many Employees Should I Schedule Each Shift at My Roller Rink in 2026?

What the revenue-per-employee method is and why it matters

The revenue-per-employee method is a staffing discipline that replaces habit with arithmetic. You and your floor leadership agree on one number: the revenue a single average floor guard should support while doing an average job for an average crowd. Then you divide each block's expected revenue by that number to get the headcount for that block. That is the entire engine. Everything else — shift blocks, safety minimums, role-specific targets — hangs off that one division.

Why it matters for a Roller rink specifically comes down to the shape of your demand curve. A rink is not a retail store with a flat-ish weekday and a mild weekend bump. It is a venue with brutal peaks and dead valleys. A Tuesday afternoon might run $190 an hour while a Saturday night party block runs $665 an hour — a 3.5x swing inside the same building, same square footage, same skate rental counter. If you staff to the average, you are overstaffed in the valleys and dangerously thin at the peak. If you staff to the peak, you burn payroll all week for two good nights.

Most rink owners default to one of two failure modes. The first is the "we've always run four people" schedule — a fixed grid copied forward week after week, never revisited against sales. The second is the gut call: whoever is managing that night decides how many bodies feel right. Both produce the same result, which is payroll that does not track revenue. You end up with a labor percentage that swings wildly, a floor that feels chaotic during the rush, and a crew standing around during the lull wondering why they were called in.

The revenue-per-employee number fixes this because it gives everyone the same yardstick. Leadership, the manager writing the Schedule, and every floor guard on the floor can look at the same block and see the same answer. It also converts staffing from a political act into a defensible one. When a guard asks why they got two hours instead of six, the answer is not favoritism — it is that the block generated what it generated, and the math assigned the bodies. That transparency matters enormously in a business staffed heavily by part-timers and teenagers, where perceived unfairness in scheduling is one of the top drivers of turnover.

There is a second reason the method matters, and it is cultural. Once you state the target out loud — "in our business, if you show up, take care of an average crowd, and give average service, you should support no less than $95 an hour in revenue" — you have defined the floor, not the ceiling. The guards who want to grow do not coast to $95 and clock out. They hit $95 doing average work, then hunt the upsell, the rebooking, the birthday party deposit, the second skate rental. The number becomes a performance conversation instead of a payroll line item. That is the difference between staffing as cost control and staffing as a revenue lever, which is exactly the lens a RevOps-minded operator brings to any labor decision.

Finally, the method scales. A single-location rink and a regional group of venues use the identical division — you just swap the floor plan and the daily averages. Once the target is agreed and the hourly revenue is pulled, the headcount falls out mechanically. That portability is why the method survives contact with reality in a way that a fixed headcount grid never does.

The step-by-step process for building the Schedule

Here is the method end to end, in the order you actually do it. Work through these steps once and you have a repeatable process you can rerun every quarter as your revenue mix shifts.

Step one: agree on the per-employee hourly revenue target. Sit down with your floor leadership and set the revenue one average floor guard should support on an average Shift. Be explicit that this is a floor, not a ceiling. A reasonable starting range for a Roller rink is $85 to $110 an hour per floor guard, adjusted for your market, your pricing, and your average wage. If your guards are experienced and paid above market, push the target up — $110 to $120 — because each body costs more. If you run a lean, lower-wage crew, $85 to $95 may be honest. Write the number down and say it out loud to the team.

Step two: pull revenue by day and by hour. Take your point-of-sale data and average revenue by hour over a trailing four to eight weeks. Four weeks is the minimum; eight is better because it smooths one-off spikes and slow weeks. You want a grid: every day of the week down the side, every operating hour across the top, average revenue in each cell. If you do not have hourly data yet, start capturing it now and estimate in the meantime using total daily revenue and typical traffic patterns — for example, assume 25 to 35 percent of a Saturday's revenue lands in the peak two-hour window. Rough estimates still produce a usable plan; accuracy improves as the data accumulates.

Step three: divide. For each block, take the expected revenue and divide by your target. A slow Tuesday afternoon at $190 divided by $95 gives you 2 floor guards. A Saturday night peak at $665 divided by $95 gives you 7. Round to the nearest whole body, and round up rather than down whenever the block involves a party booking or a school group, because those crowds behave differently from walk-in traffic.

Step four: place the shifts where the revenue actually lands. The count tells you how many; the revenue timing tells you when. Pull the hourly sales and look at when bookings and walk-ins actually post. Most rinks see a light open, a mid or swing Shift through the lull, and a heavy weekend night and party-block rush. Staff to that curve rather than parking everyone at noon. If a guard works a four-hour block that spans a slow afternoon into a busy evening, their cost is covered by the higher-revenue hours — that is intentional, not a scheduling error.

Step five: hold the safety floor on top of the math. This step is non-negotiable. Regardless of what the division says, you always keep trained floor guards watching the skate floor at all times, plus a skate-rental counter rotation. On a dead Wednesday morning the math might say one body; the safety floor says you need at least one trained guard on the floor and one person covering rentals. The math never overrides eyes on the floor.

Step six: publish, measure, and rerun. Publish the Schedule, then compare actual revenue per labor hour against your target after each week. If blocks consistently beat the target with fewer people, your target is too low. If blocks consistently miss it, either the target is too high or the block is overstaffed. Adjust the target, not the individual shifts, and rerun the whole division.

The loop at the bottom is the part most operators skip. The target is not a permanent constant — it is a calibration you revisit as your pricing, wage rates, and traffic mix change. A rink that sets $95 in January and never touches it again is running the method halfway.

Costs, timelines, and typical ranges

The method itself costs nothing but a spreadsheet and an hour of leadership time. What costs money is the scheduling software you use to execute it, and the ranges here are wide enough that the pricing model matters more than the sticker price.

Per-location pricing wins when you have a deep bench of part-timers and seasonal staff, which is the normal shape of a Roller rink crew. Tools priced per location rather than per head — Homebase and 7shifts are the common examples — get dramatically cheaper as your roster grows. A rink with forty part-timers on the books but only eight working any given night is exactly the profile that per-location pricing was built for. Expect free tiers for a single location with unlimited employees on some platforms, with paid tiers landing somewhere in the $25 to $100 per location per month range depending on how much forecasting and compliance you want bundled in.

Per-user pricing wins when you run a lean, stable crew. When I Work and Deputy are the usual names here, generally in the $2.50 to $8 per user per month range depending on whether attendance, labor tools, and demand forecasting are included. With a small core crew this is cheap; with a large seasonal roster it gets expensive fast, which is why matching the pricing model to your actual headcount shape is the single biggest cost decision you make.

Enterprise platforms — the Fourth and HotSchedules tier, plus workforce management suites sold by custom quote — generally start around $40-plus per location per month and climb with the number of sites and the depth of forecasting you need. These are built for multi-location groups with dedicated operations staff, not a single-site owner. If you run one rink, the setup weight alone will exceed the value.

Timeline-wise, expect the following. Pulling your hourly revenue history takes an afternoon if your POS reports it cleanly and a week or two if you are reconstructing it manually. Agreeing the target with floor leadership takes one meeting. Building the first Schedule off the division takes an hour. Running the full loop — publish, measure, adjust — takes one full cycle, so roughly four to six weeks before the target is properly calibrated to your building. Software onboarding, if you adopt a tool, runs from same-day for the light platforms to several weeks for the enterprise tier with POS integration and compliance configuration.

The trade-off to weigh is straightforward. A free or cheap tool with no POS connection makes you supply the headcount targets manually — fine if you have already done the division yourself. A more expensive tool with demand forecasting tied to sales will suggest coverage automatically, which saves ongoing management time but costs more per month and requires a clean POS feed. For most single-location rinks, the right answer is to run the division yourself first, prove the target holds on your floor, and only then decide whether paying for auto-suggested coverage is worth the monthly fee.

Where teams get it wrong

The most common failure is treating the target as a ceiling. Operators set $95 an hour and then use it to justify cutting bodies the moment a block dips below it, which turns the number into a punishment tool. That is backwards. The target is the floor an average guard supports doing average work — it exists so that a guard hitting it has done their job, not so that a slow block gets stripped to skeleton coverage. Cut below the safety floor and you have traded a small payroll saving for a liability exposure.

The second failure is ignoring the safety floor entirely. The math is a guide for how many bodies the revenue supports, not a license to run a busy floor with one guard because the division said so. Trained eyes on the skate floor at all times plus a skate-rental counter rotation is a hard minimum that sits on top of the revenue count, not inside it. Rinks that forget this learn the lesson the expensive way.

The third failure is staffing to the average. Averaging a $190 Tuesday and a $665 Saturday into a single number and scheduling the same headcount every night is the classic error. It produces overstaffing in the valleys and understaffing at the peak, which is the worst of both worlds — high payroll percentage and a chaotic floor during the rush. You must divide block by block, not week by week.

The fourth failure is using stale data. A trailing four-to-eight-week average is the right window. Using last year's numbers ignores pricing changes, new competitors, and shifts in your party booking mix. Using a single week's data lets one anomalous Saturday distort the whole plan. Refresh the window every cycle.

The fifth failure is applying one target to every role. A floor guard watching the skate floor and a concessions worker at the counter do not support the same revenue per hour. Concessions is more transactional and typically supports a higher target — $120 to $150 an hour is a reasonable range — while skate rental, being lower-margin and more mechanical, supports a lower one, maybe $60 to $70. Running one blended number across every role hides the roles that are actually underperforming and overstaffs the ones that are efficient.

The sixth failure is never closing the loop. Publishing a Schedule and never comparing actual revenue per labor hour against the target means you are running the method as a one-time exercise rather than a system. The calibration loop is where the value compounds. Without it, your target drifts out of alignment with reality within a quarter.

Decision framework: when to choose what

Use this to decide how to staff a given block and which tooling to reach for. The framework has two layers: a per-block staffing decision and a per-business tooling decision.

For the per-block staffing decision, work in this order. First, check whether the block contains a party booking, a school group, or a league night. If it does, treat the calculated count as a minimum and add one body, because group crowds concentrate at the rental counter and the floor edge in ways walk-in traffic does not. Second, divide the block's expected revenue by your target and round to the nearest whole number. Third, check the result against your safety floor — one trained guard on the floor plus one on rentals, minimum. If the calculation falls below the floor, staff to the floor. Fourth, confirm the Shift block boundaries match when the revenue actually lands, not when it is convenient to schedule. A block that starts an hour before the rush is an hour of payroll you did not need.

For the per-business tooling decision, the question is how much of the method you want the software to do for you. If you have already run the division and just need to publish, track swaps, and clock people in, a free or low-cost tool with per-location pricing is the right call — you supply the headcount, the tool handles logistics. If you want the tool to suggest coverage from your POS sales automatically, you need a platform with demand forecasting and a clean POS integration, which means a higher monthly cost but less ongoing management time. If you run multiple rink locations and labor compliance across jurisdictions is a daily concern, the enterprise tier earns its price through forecasting depth and built-in guardrails.

The middle path, and the one most single-location operators should take, is to run the method manually for one full calibration cycle before buying anything. Prove the target holds on your floor. Confirm that the calculated counts actually produce the labor percentage you want. Then decide whether paying for automation is worth it — and if it is, you will be feeding the tool a number you already trust rather than a guess.

One more decision point: how often to revisit the target. Revisit it quarterly, or any time you change pricing, wage rates, or your party package structure. A target set against last year's pricing is a target that will quietly overstaff or understaff your floor.

Related questions

How do I set the revenue-per-employee target if I have no hourly data?

Start capturing hourly revenue now through your POS or a manual log, and estimate in the meantime using total daily revenue split by typical traffic patterns. Assume roughly 25 to 35 percent of a peak day's revenue lands in its busiest two hours. A rough target still produces a usable Schedule; accuracy improves within a few weeks of real data.

Should the target be the same for floor guards and concessions staff?

No. Each role supports different revenue per hour. Concessions is more transactional and typically supports $120 to $150 an hour, while skate rental is lower-margin and mechanical, supporting maybe $60 to $70. Floor guards sit in the middle, around $85 to $110. Run a separate division for each role.

What happens if a block's revenue drops below the safety floor?

You staff to the safety floor anyway. One trained guard watching the skate floor plus one covering the rental counter is a hard minimum that sits on top of the revenue math. The division tells you how many bodies the revenue supports; it never authorizes running a floor without trained supervision.

How often should I recalibrate the target?

Quarterly, or any time you change pricing, wage rates, or party package structure. Compare actual revenue per labor hour against the target each week, and adjust the target — not individual shifts — when the pattern is consistent. A target left untouched for a year will drift out of alignment with your building.

Can this method work for a multi-location rink group?

Yes. The division is identical across sites; you just swap the floor plan and the daily averages for each location. Run the target per site rather than blending across the group, because a high-traffic urban rink and a suburban venue will support very different revenue per employee.

FAQ

What if my Roller rink's hourly revenue varies a lot from week to week? Use a trailing four-to-eight-week average for each day and time block. This smooths one-off spikes and slow weeks, giving you a reliable figure to divide by your target. If a Saturday night ranges from $500 to $800, averaging around $665 is reasonable and produces a stable count.

Do I need to Schedule floor guards even when revenue is very low? Yes. Always maintain a hard safety minimum — at least one trained floor guard on the skate floor and one person covering the skate-rental counter, regardless of revenue. The math is a guide for headcount, but safety and supervision are never overridden by a low number.

How do I handle shifts that overlap between slow and busy hours? Schedule guards in blocks that match when revenue actually lands — typically opens, a mid or swing Shift, and the weekend night or party rush. A guard working a four-hour block that spans a slow afternoon into a busy evening is intentional: the higher-revenue hours cover their cost.

What if my floor guards have different skill levels or pay rates? The target assumes an average guard doing an average job. If you run more experienced or higher-paid guards, adjust the target upward — $110 to $120 is a reasonable range. The formula still works; you simply divide by the number that reflects your team's typical cost and performance.

Can I use this method for other roles like skate rental or concessions? Yes, but with a separate revenue target per role. Skate rental might use a lower target, around $60 to $70 an hour, since it is more mechanical. Concessions typically supports a higher target, $120 to $150, based on per-worker sales. Apply the same division to each role's hourly revenue.

What if I don't have historical revenue data by hour? Start tracking now — use your point-of-sale system or manual logs for a few weeks. In the meantime, estimate from total daily revenue and typical traffic patterns, such as assuming 30 percent of daily revenue lands in a peak hour. The formula is still useful with rough estimates; accuracy improves with real data.

Sources

• 7shifts — hospitality scheduling plans and POS integrations: https://www.7shifts.com
• Homebase — pricing and free-tier terms: https://www.joinhomebase.com
• When I Work — official pricing and scheduling documentation: https://wheniwork.com
• Deputy — scheduling and demand-forecasting pricing: https://www.deputy.com
• Sling — free and paid plan details: https://getsling.com
• Connecteam — plan pricing and deskless-employee features: https://connecteam.com
• Workforce.com — labor forecasting and pricing: https://www.workforce.com
• Fourth — enterprise scheduling and workforce management overview: https://www.fourth.com

Related on PULSE

• How do you run a profitable Roller rink — what session schedule maximizes revenue per square foot?
• How Many Employees Should I Schedule Each Shift at My Ice Rink?
• How Many Employees Should I Schedule Each Shift at My Thrift Store?
• How Many Employees Should I Schedule Each Shift at My Vintage Clothing Store?
• How Many Employees Should I Schedule Each Shift at My Record Store?
• How Many Employees Should I Schedule Each Shift at My Comic Book Store?