Why June Reset Matters
By the end of May, you have six months of actual sales and labor data sitting in your P&L — six months that reveal whether your January forecast was directionally correct or systematically off. That drift compounds through the second half if you don't reset. A store that's been running five points below its SPLH target since February will continue bleeding labor cost through December unless you adjust the target, the budget, or both. A mid-year forecast reset prevents this compounding effect by comparing H1 actuals to your original assumptions and recalibrating H2 targets before schedules lock in.
Waiting until late July or August to recalibrate means your July schedules — often built in mid-June — already execute against stale assumptions. There's no buffer. The misalignment bakes into week one of the new half, and catching up mid-quarter becomes a scramble that forces reactive cuts or unplanned overtime.
A mid-year forecast reset is defensive. It prevents the second half from running a race with the wrong map. You compare H1 actuals to the original forecast, identify where sales mix, traffic patterns, or productivity assumptions broke down, and adjust H2 targets before they lock into schedules. Done well, this process becomes a repeatable audit — a mid-year checkpoint that every future forecast can count on.
Labor Spend Variance Review
The first step in any half-year labor planning review is calculating the gap between what you forecasted in January and what actually hit the P&L through June. Compute the variance in absolute dollars and as a percentage of your H1 labor budget. A $15,000 overspend against a $200,000 forecast is 7.5%; the same dollar miss against a $400,000 budget is under 4%. The percentage determines your next move.
Raw variance numbers hide the real story until you decompose them. Did you sell more units than expected, requiring more labor hours to support volume? Did hourly rates climb because of wage increases or a shift toward more senior staff? Did productivity drop — more hours per unit shipped or sold — because training lagged or systems went down? Was overtime higher than budgeted because coverage gaps forced premium pay? Each driver requires a different H2 response. Volume variance may not need a budget change if it flowed through to revenue; rate variance from a wage increase is structural and permanent.
The decision table is simple:
- If total variance sits under 5%, hold your H2 budget; the error falls inside normal forecasting noise.
- If variance lands between 5% and 10%, adjust your H2 spend forecast with confidence — the root cause is clear and you have six months of actuals to build from.
- If variance exceeds 10%, escalate: something structural shifted that January assumptions missed, and H2 planning requires investigation before you commit.
Identifying whether the variance is permanent or temporary — a one-time event, seasonal spike, or structural cost change — determines whether you rebase the budget or treat it as an anomaly. For operators managing variance tied to controllable costs, labor cost reduction strategies offer a roadmap for closing structural gaps without sacrificing coverage.
SPLH Target Accuracy Assessment
Compare the SPLH targets you set in January to the actuals your locations delivered through H1. If your downtown flagship was budgeted at $185 SPLH and averaged $162, that's not a rounding error — it's a 12.4% forecast miss that will echo through July schedules if you don't intervene. Pull the data by location, by week, and by labor pool (sales floor, stockroom, management) to see where targets diverged from reality. This kind of SPLH targets mid-year adjustment process catches misalignment before it cascades through the rest of the year.
Measuring Forecast Error
Forecast error rate is the mathematical spine of your labor forecast accuracy review. Calculate it as (Actual SPLH − Target SPLH) ÷ Target SPLH for each business unit. A forecast error consistently above ±8% suggests your January methodology missed something structural, not seasonal noise. Track error direction, too: chronic under-forecasting (actual SPLH below target) points to sales velocity assumptions that were too optimistic or labor productivity assumptions that were too conservative, while chronic over-forecasting (actual above target) signals the inverse.
Map which locations or labor pools strayed furthest from plan. If stockroom SPLH targets held firm but sales-floor targets collapsed, your January forecast likely misjudged traffic conversion or average transaction value, not warehouse throughput. If weekend SPLH matched targets but weekday SPLH lagged by double digits, your demand-curve shape was wrong. This diagnostic step isolates the variable that drove the miss — sales velocity or labor productivity — so you're not guessing when you rebuild H2 targets.
Recalibrating H2 Targets
Reset your H2 SPLH targets using H1 actual performance as the new baseline. If a location averaged $148 SPLH in H1 against a $170 target, don't anchor H2 at $170 — anchor it at $148, then layer in any known operational changes (new POS system, staffing model shift, category mix evolution). For methodology detail on isolating productivity drift from demand drift, see our Sales Per Labor Hour Optimization Guide. The recalibration protects your four-wall P&L from compounding a known forecasting gap into the second half of the year.
Measuring Forecast Error
Calculate Mean Absolute Percentage Error (MAPE) by taking the absolute value of (actual SPLH minus forecasted SPLH) divided by actual SPLH, then averaging across all H1 months. A MAPE under 5% signals high confidence that your methodology is sound and H2 projections can stand; 5–15% indicates moderate reliability and calls for selective target adjustments; anything over 15% means your forecast engine needs recalibration before you commit H2 labor budgets.
Track which months produced the largest misses and whether the pattern is systematic. If you consistently over-forecast SPLH in March through May, that directional error points to a correctable bias in your volume or productivity assumptions. Random error — where some months run high and others low with no pattern — is harder to fix and suggests noise in your data inputs or shifting operational factors you haven't captured.
Compare error rates across departments or locations to isolate whether the miss is enterprise-wide or concentrated in specific zones, then flag whether your variance tilts directionally or scatters randomly.
Adjustment vs. Hold Decision Tree
Once you've calculated MAPE across H1, the next question is whether to adjust your H2 targets or hold them. The decision tree is simple, organized by error band.
- If MAPE lands under 5 percent. Your forecasting methodology is tracking reality closely — confidence is high, and you should keep your H2 targets unchanged. The January projections were accurate enough that adjustment introduces more noise than value.
- If MAPE falls between 5 and 15 percent. Adjust H2 targets by the observed variance, but validate the operational logic first. If H1 SPLH was 10 percent lower than projected, lower H2 targets by 10 percent, assuming no major changes in sales mix, staffing model, or traffic patterns. Check with operations before locking the adjustment — a percentage shift that makes mathematical sense can still collide with coverage or service requirements.
- If MAPE exceeds 15 percent. Pause H2 execution and investigate root causes. An error band that wide signals a methodology problem or external factor you didn't model — doubling down on flawed projections locks you into deeper misalignment. Document which scenario you landed in and the rationale for your decision. That audit trail becomes the learning foundation for next year's mid-year forecast reset.
Forecast Methodology & Assumptions
Before adjusting H2 targets, examine the assumptions that shaped your January forecasts. Every labor budget rests on three foundational inputs: projected sales growth, expected productivity benchmarks, and anticipated seasonal patterns. When forecasts miss, the error usually traces back to one of these layers, not to execution drift.
Start with sales growth assumptions. If January forecasts assumed 8% year-over-year growth but H1 delivered 3%, your labor budget was built for a revenue scenario that never materialized. Pull the sales projections from your original forecast and compare them month-by-month against actuals. Document the variance in both dollars and percentage terms, then ask whether the gap reflects temporary headwinds or a structural shift in your market.
Next, review the productivity benchmarks embedded in your SPLH targets. Were your January targets based on pre-pandemic productivity levels that no longer reflect current staffing realities? Have turnover rates increased training time per new hire, compressing experienced headcount? Has new point-of-sale technology changed transaction speed? These operational changes alter the productivity baseline, making last year's SPLH targets obsolete even if sales forecasts hold. This dimension of half-year labor spend forecast refinement often gets overlooked but can drive significant accuracy improvements in H2.
Finally, validate your seasonal assumptions. If your forecast assumed March would deliver 12% of annual revenue but it delivered 9%, your staffing curve was wrong from the start. Compare H1 monthly revenue distribution against the seasonal pattern you forecasted. Patterns that worked in 2019 may no longer match post-disruption consumer behavior. Re-baselining these inputs now prevents H2 forecasts from compounding January's methodology errors.
Building Repeatable Reset Process
A one-time June audit is useful. An annual reset ritual is what separates reactive labor planning from strategic workforce management. The process of resetting workforce forecasts mid-year should run to the same calendar every year, owned by the same function, producing the same documented output. Assign ownership clearly — typically the labor planning lead, CFO, or operations director — and set a fixed deadline. By June 15, the audit must be complete so that H2 budgets, SPLH targets, and scheduling assumptions can be locked before the July 1 execution window.
The deliverable is a signed audit document that records H1 variance, forecast error rates, and the specific H2 adjustments made in response. Use a template checklist for consistency: compare actuals to forecast, compute variance by cost component, measure SPLH error using MAPE, decide whether to hold or adjust H2 targets, and document the rationale for each decision. When variance exceeds your established thresholds—whether in budget performance or SPLH forecast accuracy—the checklist should trigger an escalation path that routes the decision to finance leadership or the executive team before H2 plans are finalized.
Close the learning loop with a September post-reset review. After eight weeks of H2 execution, validate whether the June adjustments proved correct. Did the revised SPLH targets align with July and August actuals? Did the labor budget hold? This retrospective confirms the reset process is working and surfaces opportunities to refine thresholds or methodology for the next cycle. The ritual builds workforce confidence — teams see that plans respond to reality — and earns stakeholder trust by proving that forecasts improve over time.