The Week You Were Fully Staffed

There was a week where the rota was full, nobody called in, and the nights ran properly.

Nobody looked at it. Bad weeks get discussed at length; the good one passed without comment, and with it the only clean measurement you had.

Why the good week matters

It is the only time you see the real numbers. Service times, turnover, spend — without the distortion of being short.

It tells you what "enough" is. ⚠️ Most venues do not know their own adequate staffing level, because they are almost never at it.

It separates staffing from everything else. If the week still had problems, those problems are not about numbers. That is worth knowing and it is otherwise unknowable.

It gives you a target that is real rather than aspirational — you have done it, so it is achievable.

What to capture while it is happening

⚠️ It has to be captured during the week, because a fortnight later it is a vague memory of things going well.

Who was on, by night and by hour. The actual configuration, not the plan.

The service numbers. Time to seat, time to first order, table turn — whatever you can measure without effort.

Takings per head and per cover. ⚠️ Frequently higher in a well-staffed week, and that comparison is the entire economic argument for staffing properly.

What did not happen. No complaints, no waits, no jobs deferred. Absence is the finding, and absence is what nobody records.

What it is worth against a short week

Compare the two directly. Same night of the week, one fully staffed, one short.

⚠️ The gap is usually larger than the wage difference, and this is the number that settles the recurring argument about whether the extra person pays for themselves.

And look at the non-financial side. ⚠️ Complaints, errors, and how the team was at the end of the night — the costs that never appear in a wage calculation but produce resignations.

The trap

Assuming the good week was luck.

Some of it was. Much of it was a specific configuration — who was on, together, in which sections — and that is repeatable if anybody wrote it down.

⚠️ Pairings matter more than headcount. Two people who work well together outperform three who do not, and this is visible only in the weeks that went well.

Making it repeatable

Write down the configuration. Not just numbers — who, where, with whom.

Ask the team what was different. ⚠️ They will know immediately, and it is frequently something small that nobody in management would have identified.

Then treat it as the standard, rather than as an unusually good week. The framing matters — a good week is an accident; a baseline is a target.

Three to hold

Takings per staff hour, good week against short week. ⚠️ The comparison that ends the argument, in whichever direction it points.

The configuration of the good week. Written down while it is still accurate.

Weeks per quarter at full staffing. ⚠️ If it is one, the plan is not the plan — the plan is what happens when you are short, and that is worth admitting.

Where the record has to sit

Comparing a good week to a short one needs staffing and takings on the same record, by night. If the rota is discarded once worked and takings live in a monthly total, the good week leaves no trace and cannot be compared to anything.

tasteck keeps shifts and takings on the same records by day, so a week that went well can be opened up rather than remembered.

Nothing went wrong that week, so nobody looked. It was the most informative week of the quarter and it is already gone.