How Many Employees Should I Schedule Each Shift at My Mini Golf Course?

This vs. the common alternatives

Most course owners do not use a formula at all. They use one of four habits, and each one has a predictable failure mode that shows up in the labor line at the end of the season.

The "two on always" habit. One person at the register, one walking the holes, every hour the gates are open. It is simple and it is why so many small attractions run a labor cost that swings from 12% of revenue on a packed August Saturday to 60% on a damp Tuesday in May. The flat crew is over-staffed for two thirds of the calendar and under-staffed for the twenty or thirty days that actually pay the mortgage. If you only fix one thing, fix this: the same two-person crew cannot be correct across a 10x swing in daily revenue.

The "whoever's available" habit. The schedule is built from the availability grid, not from demand. Three sophomores can only work Thursdays, so Thursday gets three people whether Thursday earns it or not. This is scheduling by supply. It feels fair to the crew and it is invisible to the P&L until the labor percentage report arrives.

The headcount-per-hole rule of thumb. Some operators use a ratio — one attendant per nine holes, plus a register, plus a snack window body. Ratios are not useless; they are a good sanity ceiling. But holes do not generate revenue. Rounds do. A ratio prices your staffing against your physical plant instead of against your traffic, so it produces the same crew in a rainstorm and a heat wave.

The labor-percentage target. Chain restaurants and larger attractions run this: hold labor at, say, 25% of sales, and back into hours from a sales forecast. This is genuinely close to the gross-profit method and it is what most POS-connected scheduling tools implement natively. The difference is the denominator. Labor percentage runs against revenue; the gross-profit method runs against margin. On a mini golf course those diverge meaningfully, because a $9 round and a $4 ICEE do not carry the same margin at all. Concession margin on a fountain drink can run north of 80%; a round of putt-putt is nearly pure margin once the course is built, but party packages that include pizza, prizes, or arcade cards are not. Scheduling against revenue over-staffs the days that skew toward low-margin add-ons.

Why the gross-profit division wins for a small course. It gives you one number every stakeholder can repeat: what one ordinary person on one ordinary shift ought to carry. Say it out loud to the crew — "if you clock in, run the register, keep the eighteen holes flowing, and stock the snack window, you should be worth at least $170 a shift in gross profit." That sentence does more for schedule discipline than any app, because it converts an abstract cost-control goal into a personal standard. It also survives seasonality: when November margin collapses, the division automatically produces a smaller crew instead of requiring you to argue with a shift lead about it.

The honest limitation: the formula names *how many*, not *when*. It is a budget, not a placement. Everything after this section is about spending that budget correctly.

How to choose between them

Pick the method that matches your data maturity and your revenue mix, then pick the tool that supports it. In practice the decision falls out of three questions.

Do you have at least eight to twelve weeks of daily margin data? If yes, run the gross-profit division. If no, you are not stuck — use whatever trailing window exists, even three or four weeks, and treat those rosters as sketches. A brand-new course should start from a ratio ceiling (register + one course walker + one concession body at peak) and convert to the division as soon as the POS history thickens. Do not wait for a perfect dataset; a rough division beats a gut feel immediately.

Is your revenue mix concentrated or split? A pure putt-putt course with a vending machine can run a single per-employee target across the whole operation. A course with a real grill, an arcade, batting cages, or go-karts should run two targets — one for the course-side crew and one for the food-and-attractions crew — because the margin structures are different enough that one blended number will systematically mis-staff both. This is the same logic a restaurant uses when it schedules front-of-house against covers and back-of-house against food sales.

How volatile is your day-to-day? Open-air attractions are weather-whipsawed in a way that indoor retail is not. If a forecast can erase 70% of a Saturday, your method needs an on-call tier baked in, not just a headcount. That means scheduling the division's answer as a core crew plus one or two people explicitly on standby, with a stated call-by time.

Choosing the software layer. Once the method is settled, the tool question gets much smaller. Per-location pricing rewards a course carrying a fat seasonal bench of part-time teens and party hosts; per-user pricing only pays off with a lean, stable crew. If you want coverage auto-suggested rather than hand-entered, you need a tool that ingests a POS feed — that is the dividing line between the demand-aware products and the roster-publishing products. Everything else (swaps, mobile punch, messaging) is table stakes now and should not drive the decision.

One more filter that matters disproportionately for this industry: minor-labor compliance. If most of your green-keepers are sixteen, break windows, school-night hour caps, and hazardous-equipment restrictions are not a nice-to-have. A tool that enforces those rules at schedule-build time prevents a class of violation that is expensive and easy to commit accidentally when you are the one working the register on Saturday.

Costs, timelines, and expected impact

What the method itself costs: nothing but a decision. The arithmetic runs in a spreadsheet. The real cost is the meeting where you and whoever helps run the course commit to a single per-employee number and agree not to quietly override it when a favorite employee wants hours.

What the software layer costs. The market splits cleanly. Free-for-one-location tiers exist and are genuinely usable for a single course — scheduling, time clock, and crew messaging with no employee cap is enough to run a season. Per-user products in this category tend to run in the low single digits per user per month for scheduling alone, stepping up several dollars once time-and-attendance and labor tooling switch on. Per-location products typically run a few tens of dollars per location per month at the entry tier and climb toward triple digits for the all-in-one bands. Enterprise workforce platforms are quoted custom and are engineered for multi-site groups with dedicated ops staff — they are overkill for one course and the setup drag alone will eat a season.

Do the arithmetic on your own shape before choosing. A course with 28 seasonal part-timers on a per-user plan at a few dollars a head is paying meaningfully more than the same course on a flat per-location plan, and the per-location plan does not penalize you for hiring the bench you actually need in July.

Timeline to get this running. Realistically:

• *Week 1* — pull the POS export, average gross profit by weekday for the trailing three to six months, and set the per-employee target. Half a day of work.
• *Weeks 2-3* — build next week's schedule from the division rather than from availability. Expect friction; the crew is used to the old grid.
• *Week 4* — compare actual gross profit per employee against the target, by day. This is where you find out whether $170 was the right floor or whether your course supports $210.
• *Weeks 5-8* — layer the hourly placement. Chart hourly rounds and concession rings, then reshape shifts so the crew arrives with the crowd instead of with the clock.
• *End of season* — re-set the target. Mini golf swings hard with the seasons and a spring number will not hold in August.

Expected impact, stated honestly. The gain is not a fixed percentage and anyone quoting you one is guessing. What reliably happens is that the variance collapses: the over-staffed dead weekdays shed a body or two, and the under-staffed peaks gain them. The net labor hours often land close to where they started — the money shows up as better throughput on the days that matter, faster register lines, shorter waits on the first tee, and fewer walk-aways on a sold-out Saturday. Over-staffing a rained-out Tuesday costs you a few hundred dollars a season; under-staffing four peak Saturdays costs you rounds you never rang up at all, which is the more expensive error and the harder one to see.

Hidden costs worth budgeting for. Onboarding a seasonal bench takes real hours; a tool that bundles checklists and training modules recovers some of that. POS integration is rarely as clean as the marketing implies — budget a day for mapping your product categories to the tool's revenue centers, and verify that party packages and prepaid cards are classified sensibly, because miscategorized deferred revenue will distort every forecast downstream.

Implementation and handoff details

Getting from a formula to a published schedule is a repeatable weekly loop. Here is the operating detail.

Step one — lock and publish the per-employee number. Write it down. Put it on the back-office wall. The number is a floor, never a target to coast to. Revisit it seasonally and after any real change: new pricing, a new league, a fresh party package, or a stretch of ugly weather that resets your baseline.

Step two — average gross profit by weekday. A trailing three-to-six-month pull sands down one-off spikes while still surfacing genuine trends. Exclude obvious anomalies — the day the power went out, the day the local school rented the whole course — or they will permanently distort that weekday's average. Suppose Monday settles near $510: divided by a $170 floor, that is three people. Run the same division down all seven weekdays and the headcount budget drafts itself. No pets, no "we've always run a pair," no shift lead penciling in friends.

Step three — place the shifts where the tickets actually print. The quotient answers *how many*; the tee-off rhythm answers *when*. Chart hourly rounds and concession rings and find the moment golfers genuinely arrive. On most courses the weekday wave breaks after the last school bell and rolls through early evening, while weekends run open-to-dusk with a mid-afternoon crest. That produces a lean opener, a heavy after-school-through-dinner core, and a fading close as the light dies — not a flat wall of staff parked at noon.

Step four — carve out the reserved blocks. Birthday parties, corporate outings, and league nights are known demand you can staff exactly. A party host is not interchangeable with a course marshal; the host is committed to one group for ninety minutes and cannot cover the register. Budget those bodies *on top of* the division's answer, not inside it, or every party night will run short.

Step five — cross-train so the low tiers actually work. A single-person shift only functions if that person can run the register, restock the snack window, and retrieve clubs. Cross-training is what makes the slow-day answer of "one or two" survivable rather than a service failure.

Handoff to whoever builds the schedule when you don't. If a shift lead or manager takes over the build, they need three artifacts, not a verbal explanation: the per-employee target, the weekday margin table, and the hourly demand chart. Without all three they will revert to the availability grid within two weeks. Give them a standing rule for exceptions — for instance, they may exceed the division's headcount for a booked party or a league night without asking, but not for anything else. Explicit exception authority is what keeps the discipline from feeling arbitrary.

Track one number weekly. Actual gross profit divided by actual shifts worked. If that number sits below your target for three consecutive weeks, either the target was set too high for your ticket price or you are carrying hours you cannot justify. If it runs consistently above, you are leaving throughput on the table — you can afford another body, and the queue at the first tee is probably telling you the same thing.

Where this generalizes. The machinery is identical for a batting cage, a go-kart oval, a trampoline park, an axe-throwing venue, or a small ice rink — anywhere a low-ticket, weather- or season-sensitive attraction runs a thin crew against volatile daily traffic. You change the sign over the door and the per-employee dollar figure; the method holds. It is the same demand-to-capacity thinking that RevOps teams apply to sales coverage: divide the pipeline by a per-rep quota to get headcount, then place that headcount against the hours buyers actually answer the phone. Staffing a Course and staffing a territory are the same problem wearing different clothes.

Related questions

What if my course has a full kitchen instead of a vending machine?

Run two per-employee targets. Schedule kitchen labor against food gross profit and course labor against round revenue. Blending them under-staffs the grill on party nights and over-staffs the course on quiet food days. Restaurant-oriented scheduling tools handle the food side natively against a sales-per-labor-hour goal.

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

Build the on-call tier in advance with a stated call-by time — two hours before open is typical. Cutting a scheduled shift the morning of damages trust and, in some jurisdictions, triggers predictive-scheduling penalties. An explicit standby arrangement everyone agreed to beforehand is cleaner than a same-day cancellation.

Does this work for a seasonal course that closes in winter?

Yes, but reset the target at each season open rather than carrying the prior year's number forward. Use the same month from last year as your starting weekday table, then correct it with live data by week three. Shoulder seasons — April and October — need their own pass; they behave nothing like July.

Should I schedule to the average or to the peak day?

Schedule the average as your core crew and staff the peak with an on-call tier plus pre-booked party hosts. Staffing every day to the peak burns margin all week; staffing to the average alone means your best revenue days run short-handed, which is the costlier mistake.

FAQ

How do I pick the right gross-profit-per-employee number for my course?

Start with what one lean shift genuinely produces and how much each person must cover beyond their own wage. Around $170 a shift works as a floor for a low-ticket, thin-crew mini golf operation, but yours hinges on round price, wage rate, and margin mix. Set it with whoever helps run the business, make it a figure you can defend out loud, and revisit it every season.

Do I really need three or more employees on a slow Monday?

Only if your trailing gross profit says so. The formula divides that day's average margin by your per-employee target, so a genuinely dead day with thin margin returns one or two people, not three. The point is letting the money name the headcount instead of guessing — and that cuts both directions.

What if I don't have months of gross-profit data yet?

Use whatever trailing window exists and lean on your read of traffic until the numbers accumulate. Even three or four weeks of daily margin by weekday gives you a rough division to start from. Treat the early rosters as sketches, correct them weekly, and firm them up as the dataset thickens.

Where does this formula break down?

It names how many bodies to schedule, not the exact hour to place them. You still have to slot shifts against live rush windows — after-school and early evening on weekdays, open-to-dusk on weekends, plus party and league blocks. The division sets the budget; your read of tee-off patterns is what spends it.

How often should I rerun the numbers?

Mini golf swings hard with the seasons, so recheck weekday gross profit at least each season and after any real change — new pricing, a new league, or a run of bad weather. A trailing three-to-six-month pull smooths one-off spikes while surfacing genuine trends. Many operators check monthly through the busy months.

Do I need scheduling software to run this method?

No. The arithmetic works in a spreadsheet, and plenty of single-location operators run an entire season that way. Software earns its cost when publishing, swaps, mobile punch-in, and minor-labor compliance start eating your time — or when you want coverage auto-suggested from a POS feed rather than entered by hand.

Sources

• U.S. Department of Labor — Youth & Labor rules for employing minors: https://www.dol.gov/general/topic/youthlabor
• U.S. Department of Labor Wage and Hour Division — Child Labor Provisions (FLSA): https://www.dol.gov/agencies/whd/child-labor
• U.S. Bureau of Labor Statistics — Amusement, Gambling, and Recreation Industries: https://www.bls.gov/iag/tgs/iag713.htm
• U.S. Small Business Administration — Manage your business / staffing guidance: https://www.sba.gov/business-guide/manage-your-business
• IRS — Employment Taxes for Small Businesses: https://www.irs.gov/businesses/small-businesses-self-employed/employment-taxes
• SCORE — Free small business mentoring and templates: https://www.score.org/
• U.S. Bureau of Labor Statistics — Employer Costs for Employee Compensation: https://www.bls.gov/news.release/ecec.toc.htm
• National Federation of Independent Business — Small business workforce resources: https://www.nfib.com/

Related on PULSE

• [How Do I Know Where, When, and How Many People to Schedule at Each of My Multi-Unit Retail Locations?](/knowledge/tl0001)
• [How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?](/knowledge/tl0002)
• [How Do I Know How Many Cooks and Servers to Schedule Each Shift at My Pizza Restaurant?](/knowledge/tl0003)
• [How Many Salespeople Should I Schedule Each Day on My Furniture Store Floor?](/knowledge/tl0004)
• [How Do I Decide How Many Reps to Schedule at Each Store in My Mattress Retail Chain?](/knowledge/tl0005)