Shift Handover Log Template

Give the incoming shift the context the outgoing shift has in its head. This template gives manufacturing, utilities, healthcare, and facilities teams a structured pass-down record for each shift — what happened, what is still open, what is unsafe, and what still needs doing — instead of a whiteboard photo or a verbal handover in a noisy corridor. Each log names both leads and records acknowledgement by the person taking over. It turns shift change from a gap in the record into part of it.

Use Template
Riverside Ops
Shift Handover
Shift Schedule
Locations
Shift Handover Log1 waiting for acknowledgement MRJLTKStatus BoardNew handover
AskSearchFilterSortGroups (3)
Draft(1)
Line 2 — Night
Out: T. Kane
Mar 17
Riverside Plant
Submitted(1)
Line 2 — Swing
Out: J. Lee
Mar 17
2 open issues
Acknowledged(46)
Line 2 — Day
In: J. Lee
Mar 17
Acknowledged
Line 1 — Night
In: M. Reyes
Mar 16
Acknowledged

How the Shift Handover Log Workflow Works

Open the handover

Create a record with the Handover Title, Handover Date, the Shift — Day, Swing, or Night — and the Location / Area it covers, naming the Outgoing Lead and the Incoming Lead.

Line 2 — SwingDraft
ShiftDaySwingNight
Handover DateMar 17, 2026
Outgoing LeadJLJordan Lee
Incoming LeadTKTomas Kane

Write the pass-down

Shift Summary covers what happened, Open Issues to Carry Over covers the problems the next shift inherits, and Safety Notes / Incidents covers near misses and hazards, with Attachments for readings, photos, or printouts.

Pass-down
Shift SummaryRan 14,200 units, 40 min down
Open IssuesBelt tracking drift on conveyor 2
Safety NotesOil on floor near press 1, cleaned

Hand it over and acknowledge it

Pending Tasks holds the checklist of work still to be done, and Acknowledged By and Acknowledged Date record who picked it up, with Status moving from Draft to Submitted to Acknowledged.

Pending TasksAcknowledged
Swap filter on press 1
Recheck belt tracking at 11pm
Acknowledged ByTKTomas Kane · 10:04pm

Benefits of This Shift Handover Log Workflow

  • Start every shift with full context

    The incoming crew reads what happened rather than reconstructing it, so a problem that started at 2am does not get rediscovered at 10am.

  • Make the handover accountable

    Named outgoing and incoming leads plus an acknowledgement on the record mean a handover has actually been received, not just written and left on a clipboard.

  • Keep a searchable history of shift-level events

    Safety notes and open issues accumulate as records rather than disappearing with the whiteboard, so recurring problems on one line or one shift show up over time.

What’s Included in This Workflow

The handover record

Handover Title, Shift, Handover Date, Location / Area, both lead fields, the three narrative fields, a Pending Tasks checklist, Attachments, and the two acknowledgement fields.

  • Outgoing Lead
  • Incoming Lead
  • Open Issues to Carry Over
  • Pending Tasks

Status tracking across Draft, Submitted, and Acknowledged

A Status Board and a List View both group handovers by status, so anything written but never picked up is visible.

  • Status Board
  • List View

A pass-down structure that fits any operation

The three narrative fields separate what happened from what is outstanding from what is a safety concern, which is the division most operations already make informally.

  • Shift Summary
  • Open Issues
  • Safety Notes / Incidents

Customize the Workflow for Your Team

The Shift list ships as Day, Swing, and Night and is the first thing most teams change, whether that means four crews, an A/B rotation, or named shifts. Location / Area is a link you point at your existing locations workspace so handovers roll up by line, ward, building, or plant. Coast AI can set up a recurring handover so a blank log appears for every shift, notify the incoming lead on submission, or add fields for equipment status and staffing counts.

Use Template

FAQs About Shift Handover Log

What happens when I add this workflow to Coast?

You get one Shift Handover Log workspace. Each record holds Handover Title, Status, Shift, Handover Date, Location / Area, Outgoing Lead, Incoming Lead, Shift Summary, Open Issues to Carry Over, Safety Notes / Incidents, Pending Tasks, Attachments, Acknowledged By, and Acknowledged Date, with a Status Board, a List View, and a handover record layout.

How can Coast AI help with this workflow?

Coast AI can set up a recurring handover on your shift pattern, add notifications when a log is submitted, build views by line or crew, and answer questions from your stored logs — such as which issues have carried over more than three shifts running.

How is this different from a shift schedule?

A schedule says who is working. A handover says what they need to know when they arrive. Teams usually run both, with the schedule setting the roster and the handover carrying the operational detail between crews.

Can I import our existing handover notes?

Yes. Past logs can be brought in and mapped to the summary, open issues, and safety fields so the history stays searchable in one place.

Use Template

More Documents & Knowledge templates