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.

The good week is the only clean measurement you get

A short week  tells you what breaks under strain
A full week  tells you what the operation is actually capable of

⚠️ You cannot separate a staffing problem from an operational one until you have seen a week without the staffing problem — and most venues never write down what they saw.

Which is why it feels like nothing happened

⇒ ⚠️ A good week produces no incidents, so it produces no record. The weeks that get documented are the bad ones, which means the file describes only the failure modes.

---

Measure it while it is still true

Written during the week  what it looked like at full strength
Reconstructed afterwards more flattering, and less specific

⚠️ Three numbers, taken on the night, are worth more than a review a fortnight later.

Which three

Turnaround   how long a room or table took to be ready again
Waiting    how long anyone stood at the door
The last hour  what you were still able to serve at closing

⇒ ⚠️ All three degrade first when you are short, which is exactly why their full-strength values are the ceiling you are measuring against.

---

Putting a value on the difference

A short week  usually described as "we coped"
The gap    revenue, plus the part that never appears — the guest who left

⚠️ The guest who walked out of the door is not in any of your numbers. 　 ⇒ The good week is where you find out how many there normally are, 　 　 by seeing what the total looks like when nobody leaves.

The comparison that survives an argument

⇒ ⚠️ Same weekday, same season, both weeks. Anything looser gets dismissed, correctly, as not comparing like with like.

---

The trap in a good week

Read as "we are fine now"  and the hiring stops
Read as "this is the ceiling" and the hiring continues

⚠️ A good week is the most dangerous time to relax recruitment, because the pressure that motivates it has temporarily gone.

---

Making the good week repeatable

What was different  usually one or two things, not everything
What was luck    a quiet Monday, a returning regular

⚠️ Separate the two before you try to repeat it, or you will faithfully reproduce the luck and miss the method.

One page, written on the Friday

⇒ ⚠️ Who was on, in what combination, and what they did differently. This is the only week that is worth writing down, and it is the one week nobody thinks to.

---

---

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.

---

Read next

• Two Venues, One Person
• What The Weather Does To Your Week
• What Your Quietest Hour Is Telling You
• The Weekend That Costs You Monday