Skip to contentBuilt for the next shift.Explore OpenHandover’s early access

Guide

Opening and closing checklists your team will actually finish

Start from the walk, not the wish list

The quickest way to write a checklist nobody finishes is to list everything that could possibly be checked. The checklist grows to forty lines, takes too long on a busy morning, and people start ticking without looking.

Instead, walk the opening yourself and write down what you actually look at, in the order you look at it. That is your first draft. Then remove anything that does not need doing every single day and put it on a weekly or monthly list.

Group by place, in the order the job is done

People work through a space, not a list. Group the checklist into steps that match where they are standing, such as “walk the kitchen”, “fridges and freezers”, “hand-washing”, with the items for each step underneath. Put the slow jobs first: switch on the glasswasher or the coffee machine at the start so it is ready by the time you need it.

Readings, not ticks

A tick beside “fridge OK” tells you someone ticked it. “Fridge 1: 4°C” tells you the fridge was at 4°C. Wherever a check is really a measurement, ask for the number and show the target beside it.

Ask what happened when something is wrong

The most useful line on a checklist is the one that only appears when something fails: “What did you do about it?” A reading out of range, an exit blocked, food past its date. The record of the fix is worth more than the record of the problem, and asking for it every time makes fixing it the normal thing to do.

Keep daily, weekly and monthly apart

  • Daily: opening, closing, temperature readings, the pre-service check.
  • Weekly: deep cleaning, the glasswasher descale, the health and safety walk-round, stock rotation.
  • Monthly: the ice machine clean, the first aid kits.

Mixing them makes the daily list long and the less frequent jobs easy to skip.

Know who did it

A checklist signed “kitchen” cannot be followed up. Each check should record the person who did it and when. On a shared tablet, a personal PIN does this without everyone needing their own device.

Make a failed check someone’s job

A problem found at closing is the opening team’s problem unless it is handed to someone tonight. When a check fails, it should become a piece of work with one owner and a next action, not a note that hopes to be read.

Review them after a month

Look back at a month of records. Items that are always fine and never matter can go. Items that are often skipped are usually in the wrong place or the wrong time. Items that often fail need a fix, not a checkbox.

Free starting points: the kitchen opening checklist, kitchen closing checklist, bar opening checklist, bar closing checklist and café opening checklist.

Free templates for this

Every shift starts knowing what is still open.

OpenHandover keeps checks, issues and handovers together, so the next shift always knows what is still open, who owns it and what happens next.

Get started with OpenHandover