Why service standards fail on the second shift

A general manager once told us his property had excellent standards. He was right — on the morning shift, with the team he had personally trained, when he was on the floor. The afternoon was acceptable. The evening was a coin toss.

This is one of the most common patterns we find. It is rarely described as a standards problem. It is usually described as an attitude problem, or a staffing problem, or a "that's just how the evening team is" problem.

It is a design problem. Here is why.

A standard is not a sentence on a wall

When a business writes "we deliver warm, attentive service", it has written an intention, not a standard. A standard has to survive contact with a tired team at 21:40 on a Friday, when the kitchen is behind, two tables are unhappy, and the supervisor is on a break.

A usable standard answers four questions for the person doing the work:

• What exactly do I do? — specific enough to perform, not to interpret
• In what order, when we are busy? — the priority sequence for peak load
• What do I do when it can't be done? — the fallback when the situation is outside normal conditions
• Who do I tell? — the escalation path, and what they are expected to do with it

Most written standards answer only the first question. The other three are where the second shift quietly falls apart.

The four failure points

When we assess an operation, inconsistent service almost always traces back to one of these.

1. The standard was never taught, only told

A brief at the start of a shift is not training. People learn service behaviour by practising it, being corrected, and practising again. If a new hire's only exposure to the standard is a ten-minute briefing and a laminated card, they will default to whatever they already know — usually what they learned at their last job.

2. No one is authorised to correct

In many operations the supervisor has the responsibility for standards but not the authority to intervene — or has the authority but fears the conflict. Either way, the standard is enforced only by whoever happens to care most that evening. That is not a system; it is a personality.

3. The standard does not survive peak load

This is the most common and most expensive failure. Standards are designed for a comfortable level of covers and then abandoned when the room fills up. If the team has no agreed prioritisation for peak periods — what gets done, what waits, and who decides — they will improvise. Improvisation under pressure is inconsistent by definition.

4. Feedback is absent, so drift is invisible

Standards decay silently. Nobody notices a gradual decline because everyone adapts to it. A simple, honest check — a short observation walk, a guest comment logged and reviewed, a five-minute debrief at shift end — catches drift while it is still cheap to fix.

What actually fixes it

Not a new standards document. The document is usually the easy part. What changes outcomes is the sequence:

1. Rewrite the standard for the worst shift, not the best one. Write it for the busiest, most understaffed, most pressured version of the day.
2. Train to performance, not to awareness. If people have not practised it and been corrected, they have not been trained.
3. Give supervisors explicit authority and a routine. A named person, at every shift, responsible for observing and correcting — with the backing to do it.
4. Make the check routine and boring. Small, frequent and unremarkable beats an annual audit every time.

We have yet to see a shift that improved because a standard was written more beautifully. We have repeatedly seen them improve when the standard was made performable and someone was authorised to hold it.

Back to all insights