What belongs in a shift report, and what to leave out
Most shift reports fail in one of two directions. Either they are a single number texted to the owner at close, which tells nobody anything they can act on. Or they are a long free-text box that the closing shift lead fills in properly for about three weeks and then stops.
Both failures come from the same place. Nobody was clear about who the report is for.
It has two readers, and they want different things
The next shift wants to know what is different today. The espresso grinder is behaving oddly. There is one case of oat milk left. A customer is coming back at 2pm about a cake order.
The owner or GM wants to know whether the day went as expected, and whether anything needs a decision. Sales against a normal day. Anything that got missed. Anything that cost money.
A report written for only one of them reads as noise to the other. That is usually why it stops getting written. The person filling it in cannot tell what counts.
What to include
- What did not get done, and why. The most useful line in any shift report. A closing checklist that came in at 18 of 20 with a reason is worth more than one that says 20 of 20 because somebody ticked the last two on the way out.
- Anything broken or running low. With a photo where a photo helps. "The grinder sounds wrong" travels badly in text.
- Anything a customer is expecting. Orders, collections, complaints that are not finished.
- The number. Sales, covers, whatever you track. One line, not a paragraph.
- Who closed. Not to assign blame. So that whoever reads it tomorrow knows who to ask.
What to cut
Anything the system already knows. If your checklist app records who ticked what and when, the shift report should not ask somebody to retype it at 10pm. Asking a tired person to duplicate data is how you get a report that says "all good" for four months.
Staffing gossip, too. It ends up in a record that gets read by more people than the writer expected.
The timing matters more than the template
A shift report written at the end of the shift is written by somebody who wants to go home. You will get "all good" and a number.
The fix is to let it be filled in across the shift rather than at the end of it. If the grinder played up at 11am, that is when somebody will describe it properly. By close it has become "grinder a bit weird".
This is also why a good shift report is mostly assembled rather than written. If the tasks, the counts and the flagged problems are already recorded as they happen, the report is a summary of things that exist, and the only free text needed is the part a person actually has to judge.
Who reads it, and when
Decide this before you design the form. A report nobody reads until Monday should not be phrased as a handover. A report the opening shift reads at 7am should lead with what changed, not with yesterday's sales.
The common mistake at two or more locations is sending every report to everybody. The Vancouver opening team does not need Richmond's close. Within a month people stop opening any of them, including the one that mattered.
A short test
Take last night's report. Ask two questions.
- Could the person opening tomorrow act on it without asking anybody a question?
- If something had gone wrong, would it be in here?
If the answer to the second one is "probably not, they would have called me", the report is decoration. That is fine at one site with five staff. It stops being fine at the point you are not there for every close.
Butters builds the shift report from the day's actual records. Tasks completed and missed, counts filed, and anything flagged, with the free text kept to the part that needs a person. It goes to the people at that store rather than everybody. See how it works.