Deciding the Service Level

Every staffing number encodes a service level. Almost none of them is stated, which is why they get cut without anyone deciding to reduce service.

The hidden decision

Four people on a Saturday means a certain queue length.

Three means a longer one.

Nobody writes down which queue length is acceptable, so the staffing number gets adjusted for cost reasons and the service change happens silently.

Then a customer complains, and the response is about individual performance rather than about the staffing decision that produced it.

Making it explicit

State the service standard: queue length, wait time, response time, table turn, whatever fits the operation.

Derive the staffing from it, with the ratio.

Then a reduction in staffing is a visible reduction in the standard, and somebody has to agree to it.

Which is the whole point: it moves the decision to where it belongs.

The ratio again

Covers per server, transactions per hour, items per picker.

Test it against outcomes rather than accepting it.

Where the ratio says four and the shift consistently runs badly with four, the ratio is wrong — and it is usually wrong because the work changed and the number did not.

Flexing service deliberately

Closing a section, shortening hours, or accepting a longer queue on a specific day is a legitimate response to a staffing gap.

It is also almost never chosen, because the alternative — calling someone in, or running short without saying so — is easier in the moment.

Deciding in advance which service reductions are acceptable converts a scramble into a choice.

And it removes the pressure that produces on-call arrangements.

What under-staffing costs

Lost sales, which nobody counts.

Errors and rework.

Staff leaving, because a permanently short shift is exhausting.

And the customer who does not return, which is the largest and least measurable.

The measure

A service measure reported alongside labour percentage, on the same page.

By site.

The sites with the best percentage and the worst service are visible immediately, and that comparison is the argument for the whole approach.

Test the ratio against outcomes

Rather than accepting the number you inherited.

Where the ratio says four people and the shift consistently runs badly with four, the ratio is wrong.

It is usually wrong because the work changed — a new menu, a new layout, a different till system — and the number did not.

Ask the people working it. They know within ten minutes of a shift starting.

Connect policy to configuration

The choices in this note can be compared with the integration overview. Enable only the data required for the stated purpose and confirm who can see and change it.