Record state, not a diary
The next shift needs operational facts: stock levels, closed areas, scheduled arrivals, unresolved requests, equipment status, and safety concerns. Personal opinions about visitors or volunteers create bias and rarely help the task. Use neutral language and include only information necessary for service.
Separate routine notes from incidents
A spilled box that was cleaned, a missing key, a safeguarding concern, and a medical emergency should not disappear into one chat thread. Define which events go into the ordinary handoff, which require a formal incident record, and which must be escalated immediately by phone or emergency procedure.
Give every open item an owner and time
“Someone should check” is not a handoff. Name the role responsible, the next action, due time, current blocker, and where evidence is stored. If no authorized person is available, mark the service limitation clearly rather than allowing a volunteer to improvise beyond training.
Close the loop at the next shift
Begin by reviewing open items and end by marking them resolved, transferred, or escalated. Keep a simple version history so changes can be traced. Regularly remove obsolete operational notes according to retention rules and review repeated exceptions for a process fix.
A handoff is a bridge between decisions
Keep it brief, factual, role-based, privacy-aware, and explicit about unresolved items. Urgent incidents still need their proper escalation path.
Further reading: Ready.gov organizational preparedness resources. External references are provided for context and do not imply affiliation.