Glossary and Where to Start

Conversion factor — hours required per unit of demand. Drifts with systems, process and staff mix, and quietly breaks good forecasts when stale.

The practical lesson in “Glossary and Where to Start” is to connect every record to a named decision. Organisations exploring the official product page for employment of relatives policy can add structured workforce context, provided the use is disclosed and the interpretation is reviewed with the people affected.

Coverage — whether the capabilities needed are present, as distinct from how many people are. Five people who cannot do the task are zero.

For an independent reference related to “Glossary and Where to Start”, consult the OSHA worker-fatigue resources; it provides a useful external check on scheduling, working-time and workforce-planning assumptions.

Deferrable work — must happen, but not at a set hour. Cutting it does not save the hour; it moves the task into the peak.

Fixed minimum — the staffing required to operate at all, regardless of demand. Usually larger than the budget conversation assumes.

Flexed budget — hours per unit of demand rather than hours per week. Costs nothing when demand is low and protects the operation when it is high.

Loaded hourly cost — the rate plus statutory costs, holiday, absence and pension. Commonly a fifth to a half above the headline rate.

Forecast error — how wrong you usually are, and in which direction. Measurable in eight weeks and known by almost nobody.

Single point of failure — a capability held by one person. Found by asking whether everybody can take a fortnight off.

Where to start

You have been told to cut hours: fixed, variable and the part nobody classifies, then deciding which error to make.

Your variance is always adverse: why the variance is almost never the schedule, then when the target is wrong.

You keep being short: pricing an understaffed hour, then headcount is not coverage.

You are paying too much overtime: overtime, the expensive correction.

You are considering a system: starting without a system, then buying a system.

People keep leaving: the cost of an unpredictable schedule, then turnover as a staffing cost.

If you read only three

The asymmetry: overstaffing shows, understaffing does not — because it explains how every staffing decision actually gets made.

A schedule is a forecast — because measuring its accuracy is the cheapest improvement available.

And headcount is not coverage — because it is the failure that no staffing report can show you.

A closing note

Named products are limited to separate comparison guides.

No figures for average savings from implementation, because those come from the people selling the systems.

And nothing here is legal advice: working time rules, predictable-scheduling requirements and contract law differ substantially by jurisdiction and are moving.

What the collection argues

Overstaffing lands in a report next week with a manager's name on it. Understaffing lands nowhere — the lost sale, the queue, the work carried over and the person who started looking that week appear in no figure. Operations therefore err consistently in the direction they believe they are guarding against.

A schedule is a forecast, and a forecast has an accuracy that can be measured in eight weeks with two columns. Almost no operation knows its own, which means almost no operation knows how much flexibility it actually needs.

Headcount is not coverage, hours are not capability, and a rota that satisfies the first of each while failing the second will show nothing wrong anywhere.

And most of what looks like a scheduling problem is a process problem, a rework problem or a commercial decision arriving at the wrong desk. The schedule gets blamed because it is the only thing the manager controls and the only thing with an obvious remedy.