A manager’s log book is the running record of a shift: what happened, what was noticed and what was done, written at the time. It is the page you turn to when someone asks next week why the terrace closed early or when the engineer arrived.
This template uses three kinds of entry. An event is something that happened, such as a delivery arriving late. An observation is something noticed that might matter later, such as a damp patch on the ceiling. An activity is something done, such as a fire alarm test. Corrections are new entries, never crossings-out, so the record stays trustworthy.
The log
| Time | Event, observation or activity | What happened | Action raised, and who owns it | Initials |
|---|---|---|---|---|
This is the same log OpenHandover teams start from. Edit it to match your own procedures.
Getting it right
- Write the time it happened, not the time you wrote it, if they differ.
- If an entry needs someone to do something, raise an action from it straight away and note who owns it.
- Keep personal details of guests and staff out of the log. Describe what happened, not who it happened to.
Using it in OpenHandover
In OpenHandover the shift log is linked to the running shift, every entry keeps its own time, and an action raised from an entry becomes an issue that links back to it. The shift’s log entries are shown in its handover, so the next lead sees them too.