Free template
Handover Form Template
Use this form whenever something accountable changes hands — keys, access, an incident log, or a role — between two named people.
List transferred items individually, not as "usual equipment"
Always name a reason for the handover
Get both signatures before the handover is considered complete
What to include
- Who is handing over to whom, and why (shift change, role change, leave)
- Physical items and access being transferred, listed individually
- Outstanding tasks the incoming person is now responsible for
- A signature or acknowledgment line from both parties — this is what makes it a form, not just a note
The template
| Field | Example |
|---|---|
| Handover date | 2026-07-12 |
| From (name, role) | A. Reyes, Site Supervisor |
| To (name, role) | M. Chen, Site Supervisor |
| Reason for handover | End of shift / Change of role / Extended leave |
| Items or responsibilities transferred | Master key set (3 keys), site radio, incident log binder |
| Outstanding tasks | Submit weekly safety audit by Friday; awaiting vendor callback on order #552 |
| Access / credentials transferred | Building access fob #221, gate code updated |
| Acknowledgment (both parties) | From: signature/date — To: signature/date |
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
When do I need a formal handover form instead of a quick note?
Whenever something accountable is changing hands — keys, credentials, an incident log, a role — not just routine shift information. If a later disagreement about "who had the keys" would be a problem, use a form.
What counts as a valid acknowledgment?
Two signatures (physical or digital) with dates, or an in-app acknowledgment tied to a named account. A verbal handoff isn't a form — it isn't reconstructable later.
Can one handover form cover multiple outgoing/incoming pairs?
Keep it one-to-one. If a whole team is rotating, use one form per person, or a shift handover template instead — the form is for a specific accountable transfer.
Word, Excel, or something else?
Any of them work for one-off handovers. Teams doing this repeatedly outgrow static files because there's no record of who acknowledged what, when.
Get started with the template
Download it as Markdown or CSV, or start running handovers in CrewSignals for free.
Related templates