Skip to main content

Introducing Loss Radar: see which shift cost you money.Learn more

All posts

StationPro playbook

Field-tested workflow
Operator review
11 minute read
Operator economics11 min readPublished

How to build a labor schedule from a sales forecast (and save 8 to 15 percent of labor cost).

Most c-store schedules start with "what we did last week" and adjust by feel. Operators who start with a sales forecast and back into the schedule cut 8 to 15 percent of labor cost without losing service. The forecast inputs, the schedule template, the variance review, and the multi-store rollout.

Written by
StationPro Editorial
Reviewed by
StationPro operator team

Why feel-based scheduling fails at multi-store scale

A single-store operator who has run the same store for 5 years knows the schedule that works. Two cashiers Saturday morning, one cashier afternoon, two graveyard, repeat. Feel works when the same person sees every shift and adjusts as needed.

At 3+ stores, feel breaks down. The owner cannot be at every store every shift. Each store manager has their own feel, and feels vary. One manager over-schedules to avoid stress. Another under-schedules to look good on labor cost. Neither is right.

The replacement: a forecast-driven schedule. Forecast sales by daypart per store, divide by sales-per-labor-hour target, get required labor hours, fill the schedule. Same logic at every store. Consistency lets you benchmark, lets you train, and lets you cut the labor cost outliers.

8 to 15%
Labor cost reduction achievable with forecast-driven scheduling
TimeForge case studies report 8 percent labor savings plus 25 percent manager productivity lift. Logile reports 5 to 10 percent reduction in unplanned hours. For a 10-store independent at $40K/month per store in wages, the savings runs $40K to $75K per month, or $480K to $900K per year.

Step 1: forecast sales by daypart per store

The foundation is a sales forecast at the daypart level. Most c-stores use 4 dayparts (morning rush, lunch, afternoon, evening) plus an overnight window if 24-hour.

For each daypart per store, pull:

  • Inside sales (last 8 weeks, same daypart, same day of week)
  • Fuel volume (gallons sold, same window)
  • Transaction count

Average across 8 weeks. Adjust for:

  • Weather forecast for the upcoming week
  • Events (sports games, school breaks, holidays)
  • Known shifts (a competitor opens, a road construction project starts)

Output: a sales forecast by daypart for the next 1 to 4 weeks per store.

Step 2: set sales-per-labor-hour target

Sales-per-labor-hour (SPLH) is the target metric. It is total sales for a period divided by total labor hours for the same period. C-store benchmarks:

  • Inside sales SPLH: $120 to $180 healthy, $80 to $120 over-staffed, $180+ under-staffed (service quality risk)
  • Combined fuel + inside SPLH: not commonly used because fuel is largely self-serve

Set the target per daypart. Morning rush might run $200 SPLH (busy, fast). Afternoon dead zone might run $100 SPLH (slow but you still need a cashier present).

Step 3: calculate required labor hours per daypart

Required labor hours = forecast sales / SPLH target

Worked example for a Saturday at a typical c-store:

  • Morning rush (6am-10am): forecast $1,200 inside sales / $180 SPLH = 6.7 labor hours = 2 cashiers
  • Lunch (10am-2pm): forecast $1,500 inside sales / $160 SPLH = 9.4 labor hours = 2 cashiers + 0.3 for foodservice prep
  • Afternoon (2pm-6pm): forecast $900 inside sales / $120 SPLH = 7.5 labor hours = 2 cashiers minimum service requirement
  • Evening (6pm-10pm): forecast $1,300 inside sales / $150 SPLH = 8.7 labor hours = 2 cashiers
  • Overnight (10pm-6am): forecast $400 inside sales / $80 SPLH = 5 labor hours, but minimum 1 cashier present = 8 hours of 1 cashier

Total required hours for Saturday: roughly 40 labor hours plus prep time. A schedule with 3 to 4 cashiers rotating through covers it without overtime.

Step 4: build the schedule from the labor hours

With required hours per daypart, build the schedule:

  • Identify minimum service requirements (1 cashier on overnight, 2 cashiers when foodservice is open, etc.)
  • Assign full-time anchor employees to peak dayparts
  • Fill with part-time employees during off-peak
  • Avoid scheduling any employee over 40 hours unless explicitly approved (overtime control)
  • Build in 30 minutes of overlap at shift change for clean handoff

Step 5: track planned vs actual weekly

End of each week, compare planned hours to actual hours per store:

  • Planned: from the schedule
  • Actual: from payroll/timekeeping

Variance over 5 percent is a flag. Common causes:

  • Cashier called out, manager covered (overtime)
  • Sales were higher than forecast (good problem; investigate forecast accuracy)
  • Sales were lower than forecast (bad problem; should have cut hours during the week)
  • Manager did not stick to the schedule (training opportunity)

Step 6: review and adjust monthly

Once a month, review:

  • Labor as percentage of inside sales by store
  • SPLH by daypart by store
  • Overtime hours by employee and by store
  • Forecast accuracy (planned vs actual sales)

Adjust SPLH targets per store based on what worked. Some stores genuinely need higher service levels (urban store with high transaction count) and lower SPLH is the right answer. Others have drifted because nobody watched.

$480K to $900K
Annual labor savings for a 10-store operator switching from feel-based to forecast-driven scheduling
Based on $40K/month per store in wages and 8 to 15 percent reduction (per TimeForge and Logile case studies). Net of software cost, ROI is typically 6 to 15x in the first year.

The 5 mistakes that keep labor costs high

1. Scheduling from last week instead of the forecast

Last week is not next week. If last week had a sports event that drove a busy Saturday afternoon, scheduling the same staffing for this Saturday (no event) means over-staffing.

2. Letting managers schedule without an SPLH target

A manager who is not measured on SPLH will schedule for their own convenience, which usually means over-staffing during their own shift and under-staffing the shifts they do not work.

3. No overtime visibility until payroll

Overtime that shows up at payroll is too late. Mid-week alerts when an employee is on track to hit 40 hours by Wednesday give the manager time to send them home or shift hours to a part-timer.

4. Same schedule for every day of the week

Tuesday is not Saturday. A schedule that uses 3 cashiers on a Tuesday afternoon (because that is what works Saturday) wastes 4 to 8 labor hours per day.

5. Not training cashiers on multiple stations

A cashier who only runs the register cannot help with foodservice prep, restocking, or cleaning during slow moments. Cross-trained cashiers let you cut a separate prep person and absorb the prep work into the slow side of the cashier shift.

Multi-store rollout

  1. Set the SPLH target. Most operators start with $150 inside SPLH as a baseline and refine per store.
  2. Pilot at 1 store for 4 weeks. Confirm the forecast is accurate (within 8 percent of actual). Confirm the schedule cuts labor without hurting service.
  3. Roll out to 3 more stores. Build the multi-store dashboard showing labor % by store. The high-cost stores get coaching first.
  4. Standardize the schedule template across all stores. Per-store adjustments happen at the daypart level, not the framework level.
  5. Monthly review with each store manager. Stores hitting target get autonomy. Stores missing target get a deeper review.

Frequently asked questions

What is sales-per-labor-hour at a c-store?

Total sales divided by total labor hours for the same period. C-store inside SPLH benchmark: $120 to $180 healthy, $80 to $120 over-staffed, $180+ under-staffed (service quality risk). Set targets per daypart because morning rush economics differ from afternoon dead zone.

How do I forecast sales by daypart?

Average inside sales for each daypart across the last 8 weeks, same day of week. Adjust for weather (10 to 15 percent reduction for predicted rain in tourist markets), events (sports games, school breaks), and known shifts (competitor opens, road construction).

How much can a c-store save with forecast-driven scheduling?

8 to 15 percent of labor cost is typical based on TimeForge and Logile case studies. For a 10-store operator at $40K/month per store, that is $480K to $900K per year. ROI on scheduling software is usually 6 to 15x in year one.

How do I prevent overtime?

Set a 38-hour soft cap and require manager approval for any shift that would push an employee over 40 hours. Mid-week alerts (employee on track for 42 hours by Wednesday) give the manager time to adjust. Most overtime is preventable with mid-week visibility.

Should I cross-train cashiers on foodservice?

Yes, in most cases. Cross-trained cashiers let you absorb foodservice prep into slow cashier time instead of having a separate prep person. Saves 14 to 20 labor hours per week per store. The training investment (2 to 4 hours per cashier) pays back in the first month.

What is the right SPLH target?

Start at $150 inside SPLH as a baseline. Adjust per store based on local conditions: urban stores with high transaction count may need lower SPLH ($120 to $140) for service quality. Rural stores with low traffic may run higher ($170 to $200). Tune over 8 to 12 weeks.

How often should I update the schedule?

Build 2 weeks out, post 1 week in advance for employees, adjust during the week as actuals come in. Weekly review of planned vs actual. Monthly review of overall labor percentage and SPLH per store.

Sources & methodology

This playbook draws on operator workflows observed in StationPro pilot stations and on anonymized product data from live pilot tenants. Figures are illustrative examples, not promises about your stores. Procedures were reviewed against the workflows of the StationPro operator team before publication. Questions or corrections: talk to the team.

Written by

StationPro Editorial

The operator team behind StationPro. We write the procedures we ship: every playbook comes from real close, reconciliation, and loss-attribution workflows in pilot stations.

See where your station is leaking money.

A 30-minute call. We build the demo around your stations, not a generic deck.