New Shift Takeover Checklist

A practical new shift takeover checklist for consistent handovers, escalation, and clean close-out actions.

Cover image for New Shift Takeover Checklist

Download your new shift checklist

Please fill out the form below to access your free new shift checklist download.

About this new shift checklist

Shift handovers are where good days are won or lost. When key details live in someone’s head (or on a scrap of paper), teams end up guessing — and that’s when standards slip, incidents get missed, and priorities drift.

This new shift takeover checklist gives operations teams a simple, repeatable way to take control of the shift from minute one. It covers preparation checks, in-process checks, clear escalation criteria, and close-out actions so nothing critical gets lost between people, locations, or time.

What this new shift takeover checklist covers

  • Preparation checks — staffing, access, priorities, and known risks
  • Handover review — what changed, what’s pending, and what cannot be missed
  • Safety, security and compliance — confirm the basics are safe and secure
  • Operational readiness — equipment, environment, and service readiness
  • In-process checks — first-hour check and performance control
  • Escalation criteria — remove judgement calls with clear triggers
  • Close-out actions — leave a clean, known state for the next shift

How to use it on shift

Keep it practical: run the checklist at takeover, then complete the in-process checks as the shift settles. If anything hits the escalation criteria, act immediately and record who you contacted, when, and what was agreed. At close-out, update open actions with owners and due times so the next team starts with knowledge — not assumptions.

Why it works for operations teams

Handovers fail when they rely on memory, informal chats, or “you probably know this already”. A consistent checklist replaces guesswork with a shared standard — and creates a clear record of what was checked, what was found, and what was escalated.

If you’re managing multiple sites or rotating teams, this becomes even more important. Consistency is what lets you spot patterns, fix root causes, and improve performance over time.

Stop guessing. Start knowing.

Ocasta turns frontline routines like shift takeovers into real-time visibility. You can standardise what “good” looks like, capture issues as they happen, and make sure actions get owned — without chasing people for updates.

Disclaimer: This checklist is for general guidance only and does not constitute legal, regulatory, health and safety, or professional advice. You are responsible for ensuring compliance with applicable laws, standards, and internal policies.

Included questions

Here's what's included in this new shift checklist:

Shift takeover details (5)

Capture the basics so there’s no ambiguity about who took over, when, and what state the site is in.

  • Text

    Shift start date and time

    Use local time. Example: 26/03/2026 14:00.

  • Text

    Site or location

    Store, branch, depot, or site name.

  • Person

    Incoming shift lead

    Who is accountable for this shift once takeover is complete?

  • Person

    Outgoing shift lead

    Who is handing over?

  • Yes/No

    Was the handover completed face-to-face (or live call)?

    If not, note why and ensure critical info is captured below.

Preparation checks (6)

Get the shift ready before you’re in the thick of it — access, people, priorities, and immediate risks.

  • Yes/No

    Is the team present and fit for work?

    Confirm attendance, role coverage, and any restrictions (e.g. light duties).

  • Yes/No

    Are critical roles covered for the next two hours?

    If not, reallocate now and escalate according to the criteria below.

  • Yes/No

    Do you have access to required systems and keys?

    Include logins, devices, radios, keys, alarm codes, and any permits to work.

  • Text

    What are the top three priorities for this shift?

    Keep it specific and time-bound (e.g. ‘clear delivery by 12:00’).

  • Text

    Known risks or hazards to brief the team on

    Examples: wet floor area, faulty equipment, aggressive customer, weather risk, staffing gap.

  • Yes/No

    Have you checked for overdue actions from the previous shift?

    Look at open tasks, unresolved issues, and anything awaiting approval.

Handover review (5)

Turn the handover into clear knowledge — what happened, what’s pending, and what can’t be missed.

  • Text

    Summary of the last shift

    What went well, what didn’t, and what changed (systems, process, staffing, demand).

  • Dropdown

    Are there any open incidents or exceptions to manage?

    If ‘Yes — major’, escalate immediately and follow your incident process.

    Options: No, Yes — minor (contained), Yes — major (needs escalation)
  • Yes/No

    Are there any customer or client commitments due this shift?

    Examples: promised call-back, delivery time, fix deadline, VIP visit, service level target.

  • Yes/No

    Is there any planned work, visit, or audit during this shift?

    Examples: contractor work, maintenance, stock count, area manager visit, compliance check.

  • Dropdown

    Any stock, supply, or resource constraints that will impact service?

    Be honest here — it’s better to know now than firefight later.

    Options: No constraints, Minor constraints (manageable), Major constraints (service at risk)

Safety, security and compliance checks (6)

Confirm the basics are safe and secure before the shift ramps up.

  • Yes/No

    Are emergency exits and routes clear?

    No obstructions, doors functioning, signage visible.

  • Yes/No

    Is fire safety equipment present and accessible?

    Extinguishers, alarms, call points, and any site-specific requirements.

  • Yes/No

    Is the first aid kit available and stocked?

    If low or missing, replace or escalate immediately.

  • Dropdown

    Is the security status normal?

    Include alarms, CCTV (if applicable), doors, shutters, and restricted areas.

    Options: Normal, Issue identified (contained), Issue identified (security risk)
  • Yes/No

    Are any high-risk activities planned this shift?

    Examples: working at height, heavy lifting, contractor work, lone working, hazardous materials.

  • Yes/No

    Are any compliance checks due during this shift?

    Examples: temperature logs, cleaning records, vehicle checks, legal signage, age checks.

Operational readiness checks (5)

Make sure the operation can run smoothly: equipment, environment, and service readiness.

  • Dropdown

    Is critical equipment operational?

    Examples: tills, scanners, printers, fridges, tools, vehicles, Wi‑Fi, handhelds.

    Options: All operational, Minor issues (workaround in place), Major failure (service impacted)
  • Yes/No

    Is the site clean, safe, and presentable?

    Focus on customer-facing areas and high-risk zones first.

  • Yes/No

    Is the back-of-house organised and safe to work in?

    Clear walkways, stock stored safely, waste managed, no trip hazards.

  • Yes/No

    Have priority tasks been allocated to named people?

    If it’s everyone’s job, it’s no one’s job — assign owners.

  • Yes/No

    Have you noted expected peak times and coverage plan?

    Plan breaks and rotations around demand, not habit.

In-process checks during the shift (5)

Quick checks to keep performance on track and catch issues early — before they become incidents.

  • Yes/No

    Complete a first-hour check

    Confirm the plan is working: service levels, queue/throughput, workload balance, and any emerging issues.

  • Dropdown

    Is service or output on track right now?

    Use your local measures: queue length, pick rate, jobs completed, call response, etc.

    Options: On track, At risk (needs intervention), Off track (needs escalation)
  • Yes/No

    Are issues being logged as they happen (not at the end)?

    Capture what happened, impact, and what you did about it while it’s fresh.

  • Yes/No

    Has a team brief been completed and understood?

    Cover priorities, risks, any changes, and what ‘good’ looks like today.

  • Yes/No

    Are breaks planned and covered without creating risk?

    Avoid leaving critical roles uncovered or creating lone working where it’s not permitted.

Escalation criteria (6)

Remove guesswork. If any of these are true, escalate immediately through your agreed route.

  • Yes/No

    Is there any immediate safety risk to colleagues or customers?

    If yes: stop the activity, make safe, and escalate now.

  • Yes/No

    Is there a security incident or high theft risk?

    Examples: forced entry, missing keys, alarm failure, aggressive behaviour, suspicious activity.

  • Yes/No

    Is there a major system outage impacting service?

    Examples: tills down, network outage, booking system failure, critical equipment failure.

  • Yes/No

    Is staffing below minimum safe/operational levels?

    If yes: escalate and implement a reduced-service plan if required.

  • Yes/No

    Is there a compliance breach or missing mandatory record?

    Examples: required checks not completed, missing logs, failed audit point, broken seal/lock, expired certification.

  • Text

    Escalation notes (who, when, and what was agreed)

    Record the decision, the time, and the next step so the next shift can pick up cleanly.

Close-out actions (5)

Leave the operation in a known state for the next shift — with clear actions, evidence, and accountability.

  • Yes/No

    Have all open tasks been updated and assigned an owner?

    No vague ‘to do’ items. Every action needs an owner and a due time.

  • Yes/No

    Have incidents and exceptions been logged and handed over?

    Include impact, actions taken, and what still needs doing.

  • Text

    End-of-shift summary for the next team

    What must the next shift know in the first five minutes?

  • Yes/No

    Is the handover ready for the next shift?

    Keys, access, notes, and any required evidence are prepared.

  • Signature

    Shift lead sign-off

    Signing confirms the takeover process was completed and any escalations were actioned or recorded.