pingpong

Business operations

Create a shift handover log for a small team

A handover log lists what is unfinished, what state it is in, what happens next and who owns it. Keep information separate from actions: a note that a customer called is not a task to call back. Mark anything with a deadline.

A text to start with

Our team of [number] works [shift pattern] at [type of business]. Things that usually need to be passed between shifts: [examples]. Design a handover log with fields for task, current state, next step, owner and time sensitivity. Add a way to mark an entry as information only. Give two hypothetical filled-in entries, labeled as examples, so I can see the difference.

Example request. Change the details to fit your situation.

Shift handover log

Date: [ ] Shift handing over: [ ] Shift receiving: [ ] Written by: [ ] Task or topic: [ ] Type (action needed or information only): [ ] Current state: [ ] Next step: [ ] Owner: [ ] Time sensitivity or deadline: [ ] Decision made this shift and by whom: [ ] Carried over from earlier log: [ ] Read by incoming shift (initials and time): [ ] Repeat the item block as needed.

Information or action

The usual failure is a log of entries that read well but never say whether the next person must do anything. Test each entry by asking what the incoming shift does differently after reading it. Check that every action has an owner, even if the owner is whoever opens, and that time-sensitive items show a date or time instead of words like "soon". Old entries need a rule for being closed or carried over, or the log fills with stale items that hide current ones.

Ask another agent to check the result

Read each entry in this handover log as if you were arriving on the next shift. Mark each as clearly information or clearly an action. Flag any entry where you could not tell which it is, any action without an owner, and any deadline that is vague. Quote the entry for each flag.

Use it for a week

Run the log for a short trial and ask each shift what they skipped reading and why. Remove fields nobody uses, and add one only when a real handoff failed without it. Decide where the log lives, who clears finished items and how long entries are kept. Reread a few old entries to see whether they still make sense to someone who was not there.