Temporary Closure Handover Checklist

A practical temporary closure handover checklist for safe closures, clear comms, and confident reopening.

Cover image for Temporary Closure Handover Checklist

Download your temporary closure checklist

Please fill out the form below to access your free temporary closure checklist download.

About this temporary closure checklist

A temporary closure is where frontline operations get tested: customers want answers, teams need direction, and small gaps turn into big problems. This temporary closure handover checklist gives operations teams a simple, repeatable way to close safely, protect cash and stock, keep comms consistent, and hand over without missing critical steps.

It’s structured around what matters in the moment: preparation checks, in-process checks while you’re closed, clear escalation criteria, and close-out actions for a safe reopening. Stop guessing. Start knowing.

What this temporary closure handover checklist covers

  • Preparation checks — confirm authorisation, ownership, and a realistic review cadence
  • Immediate safety and site control — clear customers, secure entry points, isolate hazards
  • Operational protection — cash, keys, high-value stock, and data security
  • Comms and customer handling — one message, shared fast, with measurable updates
  • In-process checks — quick reviews that keep a short closure from becoming a messy one
  • Escalation criteria — when to stop debating and escalate immediately
  • Handover pack — a clear summary, open actions, evidence, and acknowledgement
  • Close-out and reopening readiness — remove risk, update channels, capture follow-ups

Who it’s for

This checklist is for operations teams who need consistent closure and handover standards across sites and shifts — especially in retail, hospitality, and transport and logistics environments where the pace is high and the cost of ambiguity is higher.

How to use it on shift

  • Assign a closure owner and set the next review time before anything else
  • Work through the checklist in order — it’s laid out to match real-world pressure
  • Use notes and evidence (photos, reference numbers, ticket IDs) so the next team inherits facts, not assumptions
  • If any escalation criteria are met, escalate immediately and record who you contacted
  • End with a handover acknowledgement so responsibility is clear

Why it works

Temporary closures fail in predictable ways: unclear ownership, inconsistent comms, missing evidence, and handovers that rely on memory. This checklist replaces “I think we did that” with a simple audit trail — so you can reopen with confidence and learn what to fix next time.

Want to run closures without relying on manager relay?

Ocasta turns closure updates into targeted operational comms and trackable actions, so the right people know what’s happening — and you can prove what got done, where, and when.

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 temporary closure checklist:

Before you start (5)

Confirm the closure is authorised, safe to proceed, and clearly owned. No guesswork, no gaps.

  • Dropdown

    What is the reason for the temporary closure?

    Choose the primary reason. If there are multiple, note the rest in comments later.

    Options: Planned maintenance, Emergency maintenance, Staffing shortage, IT or system outage, Utilities outage (power, water, gas), Weather or local incident, Security incident, Other
  • Yes/No

    Is the temporary closure authorised by the right person?

    Record who approved it. If approval is pending, do not proceed beyond immediate safety steps.

  • Person

    Who is the closure owner on shift?

    This person coordinates actions, comms, and evidence until handover is complete.

  • Text

    What is the estimated reopen time?

    Use best available information. If unknown, write “TBC” and set the next review time.

  • Text

    When is the next status review due?

    Set a clear time to reassess and update comms (for example, every 30–60 minutes).

Immediate safety and site control (6)

Make the site safe, secure, and clearly closed to customers and non-essential access.

  • Yes/No

    Have all customers been safely cleared from the site?

    Use calm, consistent messaging. Support vulnerable customers and confirm no-one remains in restricted areas.

  • Yes/No

    Are all customer entry points secured and controlled?

    Lock doors or set controlled access. Ensure emergency exits remain compliant and unobstructed.

  • Yes/No

    Is temporary closure signage in place and visible?

    Include the reason (where appropriate), expected reopen time (or “TBC”), and where to get updates.

  • Yes/No

    Have hazards been identified and isolated?

    Examples: wet floors, exposed wiring, broken glass, equipment faults, gas smell, overheating, aggressive behaviour.

  • Dropdown

    What is the current utilities status?

    Select the closest match. Add detail in the notes section later.

    Options: All utilities normal, Power outage, Water outage, Gas issue suspected, Heating or cooling failure, Fire alarm or suppression issue, Unknown — investigating
  • Yes/No

    Are all staff accounted for and safe?

    Confirm who is on site, who has left, and who is expected but not present.

Operational protection (cash, stock, data) (5)

Reduce loss, protect sensitive assets, and leave a clear audit trail for the next team.

  • Dropdown

    What cash handling has been completed?

    Follow your local cash policy. If anything is incomplete, record what and why.

    Options: No cash on site, Cash secured in safe, Cash count completed and recorded, Cash count not possible — escalated, Other — see notes
  • Yes/No

    Is high-value stock secured and access restricted?

    Examples: locked cabinets, secure room, cages, key control, restricted access list.

  • Yes/No

    Are keys, fobs, and access codes controlled?

    Confirm who holds keys now, and where spares are stored. Change codes if compromise is suspected.

  • Yes/No

    Are POS and IT systems secured?

    Lock terminals, log out users, secure devices, and protect customer data. Record any outages and ticket references.

  • Dropdown

    How have deliveries and collections been managed?

    Make sure nobody turns up to a closed site without instruction.

    Options: No deliveries or collections due, Suppliers notified and rescheduled, Deliveries redirected to another site, Awaiting confirmation — escalated, Other — see notes

Comms and customer handling (4)

Make the closure visible, consistent, and measurable — so teams are not relying on word of mouth.

  • Yes/No

    Has an internal update been sent to the right teams?

    Include: reason, start time, expected reopen time (or TBC), escalation owner, and next review time.

  • Dropdown

    Which customer-facing channels have been updated?

    Select the best match. If you cannot update a channel, record who you asked and when.

    Options: In-store signage only, Signage and website, Signage and Google or maps listing, Signage and social channels, All relevant channels updated, Unable to update — escalated
  • Yes/No

    Is there a clear script for customer queries?

    Keep it short: what’s happening, what customers should do next, and when you will update them.

  • Dropdown

    What is the plan for refunds, reservations, or appointments?

    Choose one and add details in notes (who is actioning, by when).

    Options: Not applicable, Handled on site before closure, Handled by central team, Customers redirected to another site, Pending decision — escalated

In-process checks during closure (4)

Keep control while the site is closed. These checks stop ‘temporary’ becoming ‘unclear’.

  • Yes/No

    Has the scheduled status review been completed on time?

    If not, record why and reset the next review time.

  • Yes/No

    Has a quick site walk been completed to confirm ongoing safety and security?

    Check doors, hazards, alarms, and any areas affected by the incident or fault.

  • Dropdown

    If applicable, is temperature-sensitive stock protected?

    Use this for food, medicine, or any products with temperature limits.

    Options: Not applicable, Within limits and monitored, Moved to safe storage, At risk — escalated
  • Yes/No

    Has the incident log been updated with actions and timestamps?

    Write what happened, what you did, who you spoke to, and what happens next.

Escalation criteria (5)

If any of these are true, escalate immediately. This section removes doubt under pressure.

  • Yes/No

    Is there any immediate danger to people (injury, fire, gas smell, violence, structural risk)?

    If yes: follow emergency procedures first, then notify the duty lead and log actions.

  • Yes/No

    Has there been a security breach or suspected theft?

    Preserve evidence, restrict access, and follow your reporting process.

  • Yes/No

    Is there any risk to customer or company data?

    Examples: lost device, unauthorised access, system compromise, suspicious emails on site terminals.

  • Yes/No

    Is the closure likely to exceed the agreed threshold (for example, more than 2 hours)?

    Use your local policy threshold. If unsure, escalate early to avoid missed comms and staffing impacts.

  • Dropdown

    Who has been contacted for escalation?

    Select all that apply over multiple submissions, or choose the closest match and add notes.

    Options: Area or regional manager, Facilities or maintenance, IT service desk, Security, HR or people team, HSE or compliance, Emergency services, Not escalated

Handover pack for the next team (5)

Leave the next shift with answers, not assumptions.

  • Text

    Write a handover summary for the next team

    Include: what happened, what is safe/unsafe, what’s been completed, what’s outstanding, and the next review time.

  • Text

    List open actions with owners and deadlines

    Example: “Facilities to attend — ETA 15:30 — ticket 12345 — owned by Alex”.

  • Yes/No

    Have you captured the key evidence needed?

    Examples: photos of signage, hazard area, fault codes, supplier messages, incident reference numbers.

  • Yes/No

    Have keys and access been handed over to the next responsible person?

    If not, state where keys are secured and who can access them.

  • Signature

    Handover acknowledgement

    The receiving person confirms they understand the current status and next steps.

Close-out and reopening readiness (4)

Close the loop properly so the site reopens safely and the business learns from the event.

  • Text

    What is the confirmed cause of the closure (or best current understanding)?

    Keep it factual. If unknown, write what you are waiting on and from whom.

  • Yes/No

    Have reopening checks been completed and signed off?

    Examples: hazards removed, utilities stable, systems working, staffing in place, customer areas ready.

  • Yes/No

    Have internal and customer channels been updated with the reopen status?

    Remove closure signage and publish the new status with times.

  • Yes/No

    Have follow-up actions been created to prevent repeat issues?

    Turn lessons into actions: maintenance, training, process change, or supplier escalation.