Pulse - Value Added
FRACTIONAL CRO · MARYLAND-BASED, NATIONWIDE · $0→$200M

Kory White

RevOps & Revenue Leadership

Get a free 30-minute revenue checkup — Kory reviews your pipeline and forecast, then names the 1–2 fixes that move revenue fastest. 25 yrs scaling teams $0→$200M.

Free 30-min revenue checkup →
Hire a Fractional CROHow We Help?LinkedInRésuméCRO Syndicate
← Library
Knowledge Library · pulse-tools
13/13 Gate✓ IQ Certified10/10?

How Many Employees Should I Schedule Each Shift at My Driving Range?

Pulse ToolsHow Many Employees Should I Schedule Each Shift at My Driving Range?
📖 3,679 words🗓️ Published Aug 6, 2026
Direct Answer

Divide each day's average gross profit by a per-attendant daily gross-profit target. If your driving range averages $800 gross profit on Mondays and you set a $200-per-attendant floor, you schedule four attendants. Run that division for every day, then place those shifts against the hours when revenue actually rings up.

Signals you actually need this

Most driving range owners do not schedule from math. They schedule from memory — "we've always run three on the tee line" — and then discover at the end of the month that labor ate the margin. There are specific, observable signals that tell you the guessing has become expensive enough to fix.

The first signal is a labor percentage that swings more than a few points week to week without an obvious cause. If your labor cost as a share of revenue lands at 24% one week and 33% the next, and neither week had a tournament, a storm closure, or a callout wave, the schedule is not tracking demand. It is tracking whoever asked for hours. A stable operation should see labor percentage move within a narrow band because the schedule flexes with the revenue curve, not against it.

The second signal is the mismatch between your busiest hour and your fullest shift. Pull a week of hourly transaction data from your POS and overlay it on your published schedule. On a lot of ranges you will find peak headcount sitting at 11 a.m. on a Tuesday — a habit inherited from an old manager — while the 6 p.m. to 9 p.m. weekday window, which is where a lighted range makes real money, runs with two people and a line at the ball dispenser. The count can be right in aggregate and still be wrong in placement.

How Many Employees Should I Schedule Each Shift at My Driving Range — figure 1

The third signal is manager discretion drift. When headcount decisions live entirely in a manager's head, they bend toward relationships. The person who texts most often gets hours. The reliable closer who never complains gets slotted for the dead Wednesday open. Nobody intends this; it happens because there is no external number to argue against. A published per-attendant gross-profit target removes the argument entirely — the day generates $1,600, the target is $200, that is eight bodies, and no one has to negotiate.

The fourth signal is a growing gap between weekday and weekend performance that the schedule does not reflect. Driving ranges are unusually seasonal and unusually weather-dependent compared with most retail. A range in a four-season market can do 40% of its annual revenue in a fifteen-week window. If your March schedule looks structurally like your July schedule with a couple of shifts trimmed, you are absorbing labor cost during shoulder season that the revenue cannot carry.

The fifth signal is the one owners feel before they can name it: you cannot answer "why does Saturday have six people?" with a number. If the answer is a story rather than a calculation, you need this method. That is the whole diagnostic. Ask the question about any shift on your current schedule and see whether a number comes out.

How Many Employees Should I Schedule Each Shift at My Driving Range — figure 2

Adjacent operations hit the same wall in the same way. A mini-golf course, an indoor golf simulator lounge, a batting cage complex, a small-bay pickleball facility — all of them have the same shape: a fixed footprint, variable hourly traffic, mostly part-time hourly labor, and a revenue curve driven by weather and daylight. The math travels. The only thing that changes is the storefront and the per-worker target you settle on.

What good looks like versus what bad looks like

Bad scheduling at a driving range has a signature. The schedule is copied forward week over week with minor edits. Headcount is flat across days that do not perform the same. Shifts are built around when employees want to work rather than when guests show up. Nobody knows the gross profit of a Tuesday. And when labor runs hot, the correction is a blunt across-the-board cut that pulls a body off the Saturday morning rush — the exact shift that was paying for itself.

Good scheduling has a different signature, and it starts before any app is opened. You and whoever helps you run the business agree on one number: the daily gross profit an average attendant should produce running an average shift for an average number of guests. Say $200. Say it plainly to the team, too: if you show up, take care of a normal number of guests, and give normal service, you should produce no less than $200 a day in gross profit. That is a floor, not a ceiling. The attendants who want to make real money do not coast to $200 and clock out — they hit it doing average work and then dig for the next $200 by upselling large buckets, moving range cards, pushing lesson bookings, or working the snack window between ball-picker runs.

How Many Employees Should I Schedule Each Shift at My Driving Range — figure 3

Then you pull each location's gross profit by day of week across a trailing three to six months. Not revenue — gross profit, after cost of goods on balls, buckets, concessions, and retail. Divide by the target. A Monday averaging $800 needs four attendants. A Tuesday averaging $1,600 needs eight. The staffing plan writes itself, and it writes itself the same way for every manager, at every location, in every season.

The trailing window matters more than people expect. Three months is responsive enough to catch a real trend and long enough to absorb one rained-out weekend. Six months smooths harder and is better for a range with a stable, year-round climate. If you are in a market with a hard winter, do not average across the seasonal boundary — build a separate in-season and off-season baseline, or you will overstaff February and understaff June by the same arithmetic error.

Three guardrails keep the raw division honest. First, a coverage floor: no shift runs below two people regardless of what the math says, because one person cannot run a register, pick the field, and handle an incident at the same time. A slow Tuesday open that calculates to 1.4 attendants still gets two. Second, a task floor: certain jobs are non-negotiable regardless of traffic — ball washing and dispensing, mat and mat-line maintenance, the picker run, opening and closing counts. Those hours exist whether or not a single guest shows up, and they belong in the schedule as fixed labor before you distribute the variable headcount. Third, a fairness check: rotate the desirable shifts. The gross-profit math tells you how many bodies, not which body, and if the same person always gets the lucrative Saturday and the same person always gets the dead Monday open, you will lose one of them.

How Many Employees Should I Schedule Each Shift at My Driving Range — figure 4

Good also means the schedule is published far enough out that people can plan their lives. Ten to fourteen days is a reasonable standard, and in some cities with predictive-scheduling ordinances it is closer to a legal requirement than a courtesy. Late schedules generate callouts, and callouts destroy the very coverage the math was built to protect.

Real cost and ROI ranges

The method costs nothing to run. The tools that execute it cost something, and the pricing models differ enough that picking wrong can double your spend on identical functionality.

Per-user pricing scales with headcount. Entry-tier shift-scheduling apps for hourly teams commonly start in the low single digits per user per month and climb toward the high single digits once you add time and attendance, labor forecasting, and compliance features. For a lean, stable crew — say eight to twelve people across a single range — per-user pricing is cheap and predictable.

How Many Employees Should I Schedule Each Shift at My Driving Range — figure 5

Per-location pricing scales with sites. It typically runs in the mid-double-digits per location per month for a mid-tier plan, and there are genuinely capable free tiers for a single location with unlimited employees. This is usually the better model for a driving range, because ranges carry a lot of part-timers and seasonals. If you run a roster of thirty people to cover twelve simultaneous slots — high schoolers in summer, retirees on weekday mornings, a couple of full-timers — per-user billing punishes you for a roster shape you cannot avoid. Per-location billing does not care.

Enterprise workforce platforms sold by custom quote sit at the top. They bring deep forecasting, labor-budget enforcement, credential-based scheduling, and multi-jurisdiction compliance. They also bring implementation weight that a single-site range cannot absorb. Verify current pricing directly with each vendor before you commit — published tiers change often, and annual versus monthly billing usually moves the number.

Now the return, which is where the argument gets easy. Labor is typically the largest controllable line item at a range after cost of goods. If you are running a facility doing meaningful annual revenue and your labor sits a few points above where the demand curve says it should, that gap is real money leaving every month. Tightening scheduling accuracy by even two or three percentage points of labor cost usually dwarfs any subscription fee by an order of magnitude. That is the honest ROI case: the software is a rounding error against the mis-scheduling it prevents.

There is a second, less obvious return. Understaffing costs more than it saves. A Saturday morning with two attendants instead of four means slow ball dispensing, a line at the register, unpicked field sections, and a guest who leaves without buying the second bucket or the lesson package. You do not see that loss on a labor report — it shows up as flat revenue, which the next scheduling cycle then reads as "this day does not need more people," and the range spirals down into a self-fulfilling understaffing loop. Gross-profit-driven scheduling breaks the loop because it responds to what the day produces, and if you starve the day, you will see the produced number fall and can diagnose it directly.

How Many Employees Should I Schedule Each Shift at My Driving Range — figure 6

Track two numbers monthly and you will know whether the method is working. The first is gross profit per labor hour: total gross profit divided by total hours worked, computed by day of week. If Tuesdays produce meaningfully less gross profit per labor hour than Saturdays, Tuesday is overstaffed relative to your target and the division needs rerunning. The second is overtime as a share of total hours. Overtime creeping up while headcount is flat means your shift placement is wrong even though your daily count is right — you are covering the demand peak with fewer, longer shifts rather than more, shorter ones.

Reset the baseline quarterly, or immediately after any structural change: adding lights, adding heated bays, opening a simulator room, a competitor opening or closing within your drive radius, or a materially different season. A stale baseline is the most common way this method quietly stops working while everyone still believes in it.

How it plugs into your workflow

The method is not a spreadsheet you build once. It is a loop that sits between your POS and your scheduling app, and it runs on a fixed cadence. This is standard RevOps discipline applied to hourly labor: define the metric, wire the data, automate the decision, review the variance, adjust the input.

How Many Employees Should I Schedule Each Shift at My Driving Range — figure 7

Step one, weekly: export hourly and daily gross profit from your POS by location. Most POS systems used at ranges can produce this natively; if yours cannot separate cost of goods, approximate gross profit with a category-level margin assumption and be consistent about it. Consistency matters more than precision here — you are sizing a crew, not filing taxes.

Step two, weekly: run the division. Day gross profit ÷ per-attendant target = raw headcount. Apply the coverage floor and the fixed task hours. That gives you the day count.

Step three, weekly: overlay the hourly curve to place the shifts. Look at where transactions actually post. Most lighted ranges see weekday evening and weekend morning peaks, with a real lull midday on weekdays. Staff the peaks heavy, run a lean swing through the lull, and right-size open and close instead of parking everyone at noon out of habit. Where a shift straddles the peak, stagger the start times in thirty- or sixty-minute increments so bodies arrive as the curve rises rather than all at once.

How Many Employees Should I Schedule Each Shift at My Driving Range — figure 8

Step four, weekly: publish through whatever scheduling app you use, so the schedule lands on every phone with reminders and a clean swap process. This is the part software is genuinely good at, and it is worth paying for even if you do the math yourself.

Step five, monthly: review gross profit per labor hour by day against the target and adjust. This is the feedback that keeps the whole thing from drifting.

The integration decision worth thinking hard about is whether you want the scheduling tool connected to your POS. Tools with a POS feed can auto-suggest coverage against projected sales, which is the closest off-the-shelf cousin to the gross-profit method and saves you the weekly export. Lighter tools make you supply the headcount but cost far less. Either works. The method is the asset; the app is delivery.

How Many Employees Should I Schedule Each Shift at My Driving Range — figure 9

Compliance is the last plug-in point and the one most likely to bite an unprepared operator. Ranges employ minors, especially in summer, and minor labor rules restrict hours per day, hours per week, and how late a shift can run — and they vary by state. If you run multiple sites across state lines, or operate in a city with a predictive-scheduling ordinance, the guardrails built into the better scheduling platforms are worth more than the scheduling features. Verify the current rules for your jurisdiction with your state labor department rather than trusting a vendor's summary.

Adjacent scenarios where the same division applies

The formula is portable because the underlying shape is portable: variable daily traffic, hourly labor as a direct cost, and gross profit that can be attributed to a day. Wherever those three hold, the division works.

A car wash is the closest analogue — same weather dependence, same part-time roster, same fixed opening and closing tasks. A mini-golf course or batting cage complex differs only in that a larger share of revenue arrives in birthday-party and league blocks, which means you layer event-driven headcount on top of the baseline division rather than replacing it. A golf simulator lounge inverts the weather relationship entirely: bad weather is a demand driver, so the seasonal baseline runs opposite to an outdoor range and a range with both needs two separate calculations.

How Many Employees Should I Schedule Each Shift at My Driving Range — figure 10

If your driving range runs concessions, a pro shop, or a teaching program alongside the tee line, the honest move is to calculate each revenue stream separately rather than blending them. The tee line, the snack bar, and the pro shop have different margins and different demand curves, and blending them produces a target that fits none of them. Run the division per stream, sum the headcount, then look for cross-coverage where one person can plausibly hold two roles during a lull.

The upstream effect worth naming: once you publish a per-attendant gross-profit number, you have accidentally built a performance framework. Hiring changes, because you now know what a productive attendant produces and can say it in an interview. Training changes, because the fastest way to raise the target is to teach upsells rather than add bodies. Compensation changes, because you can build a bonus on top of the floor — you cover $200, everything above it earns a share. That is the same logic that governs a quota-carrying sales team, applied to a tee line, and it is why this belongs in a RevOps conversation rather than a purely operational one.

The downstream effect is cleaner forecasting. Once headcount is a function of gross profit, your labor budget becomes a function of your revenue forecast rather than a separate guess. Forecast $40,000 in monthly gross profit at a $200 target and you know your total attendant-days before you build a single shift. That single dependency makes the annual budget dramatically easier to defend, and it makes seasonal ramp planning a calculation rather than a debate.

Related questions

What if my calculated headcount is a fraction?

Round toward coverage, not toward savings. A day calculating to 4.4 attendants gets four full shifts plus a partial mid-shift covering the peak window, not five full shifts. Fractional results are the argument for staggered start times rather than uniform full shifts.

How do I set the per-attendant target the first time?

Work backward from a labor percentage you can live with. Take a representative recent month, divide total gross profit by total attendant-days worked, and see what your current actual number is. That is your honest starting point. Then set the target slightly above it.

Does this replace my manager's judgment?

No. It replaces the argument about headcount so judgment can go where it matters — who works which shift, who is ready to close alone, when to add a body for a tournament the data has never seen. The math sets the count; the manager sets the roster.

How do I handle a rainout after the schedule is published?

Build a documented weather policy and share it at hire. Define a call-time threshold, who makes the call, and what a sent-home employee is guaranteed. Some jurisdictions require reporting-time pay, so verify local rules before writing the policy.

Should tournaments and events use the same formula?

No. Events are known-volume, known-margin, and known-duration, so staff them from the event contract directly and add that headcount on top of the baseline day count rather than folding event revenue into your day-of-week average.

FAQ

What is the best way to determine how many attendants I need per shift?

Divide your average gross profit for that day of the week by a target daily gross profit per attendant. If a Monday averages $800 in gross profit and your target is $200, you schedule four attendants. This ties staffing directly to what the day actually produces instead of to habit or to whoever asked for hours.

Should I use the same staffing number every day of the week?

No. Ranges see large variation across weekdays and weekends, and the whole point of the method is to reflect that. Calculate a separate number for each day from that day's trailing average gross profit. A Monday might need four attendants while a Saturday needs eight or more.

How do I account for openers versus closers?

The daily count tells you how many; the hourly revenue curve tells you when. Pull hourly transaction data, find where money actually posts, and weight your shifts toward those windows. Most lighted ranges load weekday evenings and weekend mornings, run lean through the weekday midday lull, and keep open and close tight.

What if I run multiple locations?

Apply the formula per location. Each site has its own gross profit by day of week — driven by its own drive radius, lighting, bay count, and competition — so a shared average will overstaff the weaker site and understaff the stronger one. Calculate each separately, then look for cross-site coverage only for salaried or floating roles.

How often should I recalculate?

Refresh the trailing three-to-six-month average quarterly under normal conditions, and immediately after any structural change: new lights, added bays, a competitor opening or closing nearby, or a seasonal transition. A stale baseline fails silently, which is why the monthly gross-profit-per-labor-hour review matters.

Does this method work outside driving ranges?

Yes. Any business where hourly labor is a direct cost tied to daily revenue can use it — car washes, mini-golf, batting cages, simulator lounges, small retail, quick-service food. The formula is unchanged; only the per-worker target and the shape of the demand curve differ by industry.

Sources

flowchart TD S["How Many Employees Should I Schedule E"] S --> N0["Signals you actually need this"] N0 --> N1["What good looks like versus what bad l"] N1 --> N2["Real cost and ROI ranges"] N2 --> N3["How it plugs into your workflow"]
flowchart LR C["How Many Employees Should I Schedule E"] C --> H0["What good looks like versus what bad l"] C --> H1["Real cost and ROI ranges"] C --> H2["How it plugs into your workflow"] C --> H3["Adjacent scenarios where the same divi"]

Related on PULSE

Download:
Was this helpful?  
⌬ Apply this in PULSE
Gross Profit CalculatorModel margin per deal, per rep, per territoryRep Scheduling MatrixProtect high-value selling timeHow-To · SaaS ChurnSilent revenue killer playbook