Free template
Security Shift Handover Template
Use this template at every security shift change — post, patrol, or SOC — to hand off incident status, access control changes, and equipment checks.
Assign every incident an ID so it can be tracked across multiple shifts
Report equipment issues immediately, don't wait for the end of shift
Log patrol observations even when nothing rises to a formal incident
What to include
- Open incidents with current status and the next required action
- Access control changes made this shift (new badges, revoked access, temporary visitor access)
- Equipment and system checks (cameras, alarms, radios) with anything flagged as down
- Patrol notes covering anything unusual, even if it didn't rise to a formal incident
The template
| Field | Example |
|---|---|
| Shift date & time | 2026-07-12, Night (22:00–06:00) |
| Outgoing / incoming officer | Outgoing: M. Okoro → Incoming: J. Vance |
| Open incidents (ID, status) | INC-0472: attempted after-hours entry, north dock — under review, camera footage pulled |
| Access control changes | Contractor badge #1187 issued 20:00–08:00, expires automatically |
| Equipment / system status | Camera 14 (loading dock) offline since 21:40 — IT ticket filed |
| Patrol notes | Perimeter fence gate 3 latch loose — flagged for facilities |
| Incoming officer acknowledgment | Reviewed incident log and equipment status before taking post |
How CrewSignals replaces the static template
A downloaded template works until more than one shift needs it at once. CrewSignals keeps the same fields — priority alerts, open issues, follow-ups — as a structured, searchable record, with acknowledgment tracked automatically instead of chased down after the fact.
FAQ
What's the difference between a security shift handover and an incident report?
An incident report documents one specific event in full detail for records or investigation. The shift handover is the broader handoff — it references open incidents by ID but focuses on what the next shift needs to actively watch or continue.
How long should an incident stay on the handover?
Until it's formally closed — carry it forward on every handover with its current status, even if that status hasn't changed, so nothing silently drops before resolution.
Should equipment issues go on the handover or straight to a ticket?
Both — file the ticket immediately for tracking, but also note it on the handover so the incoming shift knows not to rely on that equipment (e.g. a dead camera) during their coverage.
Is this suitable for a SOC (security operations center) as well as physical guard posts?
Yes — swap "patrol notes" for monitoring/alert notes and the same structure (open incidents, access changes, system status, acknowledgment) covers both physical and SOC shift handoffs.
Get started with the template
Download it as Markdown or CSV, or start running handovers in CrewSignals for free.
Related templates