Labour analytics · 6 min read
Labour bloat vs under-staffing: how to tell the difference
A headcount number alone can't tell you whether a shift is over- or under-resourced. You need to compare it against demand.
Why headcount alone is misleading
"We had 12 people on shift" tells you nothing about whether 12 was the right number. Twelve people during a quiet Tuesday morning is bloat. Twelve people during a Saturday evening peak might be under-staffed. The number only means something next to a demand estimate for that same period.
What labour bloat and under-staffing actually look like
- Bloat: scheduled headcount consistently exceeds forecasted demand for a shift or period
- Under-staffing: scheduled headcount consistently falls short of forecasted demand
- Both usually hide in aggregate reporting — they show up at the shift level, not the weekly total
- Left unaddressed, bloat erodes margin quietly; under-staffing erodes service quality and burns out staff
How Inside surfaces this
Inside's Labour Demand Forecasting tokenises demand into worker-output units, then compares that against the actual roster shift by shift — not just in aggregate. That comparison is what flags a specific evening service as "bloat: 3 excess" or an afternoon peak as "under-staffed by 2," with a productivity score attached, instead of leaving managers to eyeball a weekly headcount total.
Frequently asked questions
What is labour bloat?+
Labour bloat is when more staff are scheduled for a shift than the actual demand requires, creating excess labour cost without a corresponding increase in output.
How can I tell if I'm over-staffed or under-staffed?+
Headcount alone doesn't show this — you need to compare the demand forecast (e.g. tokenised worker-output requirements) against the actual roster for the same period. A gap in either direction is a signal to adjust.