An end of shift report closes the loop on the shift. It is short and factual: were the routine checks done, did anything happen that a manager needs to know about, what is running low, and is the area left ready for whoever comes next.
It is not the handover. The handover is written for the next lead and is about what they need to do; the end of shift report is a record for managers. Many teams fill in both in the same few minutes before they leave.
The checklist
- Were all of this shift’s checks done? Yes No means a problem
- If “Were all of this shift’s checks done?” is No:What was missed, and why?
- Did anything happen that a manager should know about? Yes No means a problem
- If “Did anything happen that a manager should know about?” is Yes:What happened?No guest names, contact or health details. Add it to the shift log too if it needs a record.
- Anything running low for the next shift?
- Is the area closed down and left ready? Yes No means a problem
This is the same template OpenHandover teams start from. Edit it to match your own procedures.
Getting it right
- If a check was missed, say why. “Probe broken” leads to a new probe; a blank leads nowhere.
- Anything a manager should know about that might need a record later belongs in the shift log too, written at the time.
- Keep “running low” specific: “two cases of house white left” can be ordered; “wine low” cannot.
Using it in OpenHandover
In OpenHandover the report sits on the shift alongside its checks and log, so a manager can see which checks were missed without asking. Anything that needs fixing can be raised as an issue with an owner from the same screen.