Opening and Closing Checklists: How to Build Ones That Get Done

An opening and closing checklist is the pair of short, sequenced lists that bookend every trading day: the opening list verifies the site is safe, compliant, and customer-ready before doors open; the closing list verifies cash, equipment, cleaning, and security before the last person leaves. The ones that get done share four traits — they are short (under 20 items), sequenced in the order the building is walked, owned by a named role, and checked by someone the next morning. The ones that don't get done are usually long, unordered, unowned, and unread.

Why these two lists matter more than any others

Opening and closing are where the day's risk concentrates. Nearly everything that can quietly go expensive — an unarmed alarm, an unlogged fridge running warm overnight, a fryer left on, an uncounted till, a back door on the latch — happens at the edges of the day, when the manager may not be present and staff are either not yet switched on or already halfway home.

They are also the two moments with a natural deadline. "Clean the storeroom this week" can drift; "doors open at 9:00" cannot. That deadline is your ally: an opening checklist has a built-in completion time, which makes misses unambiguous and same-day follow-up possible.

If your operation runs only two checklists, run these two.

Anatomy of a list that gets done

Short. Every item you add taxes attention from every item already there. Fifteen items done honestly beat forty done in one scribble at the end. If the full routine genuinely needs forty, split it — kitchen opening and front-of-house opening as separate lists with separate owners.

Sequenced by geography, not category. Order items in the sequence a person physically moves through the building: back door, stockroom, kitchen, floor, front door. A list that ping-pongs across the site gets reordered in practice and then trusted in neither order.

Verifiable. Each line names a condition someone can check true or false. "Floor clean and dry" works. "Ensure high standards of cleanliness" does not — see checklist design best practices for the wording craft.

Owned by a role. "Opening keyholder" and "closing manager" survive rota changes; "Priya" does not. The record should still capture the individual who ran it, for accountability and for the audit trail.

Time-boxed. The opening list is due before doors open; the closing list before the alarm sets. State the deadline on the list itself.

A sample opening checklist (adapt, don't adopt)

Written for a small café; swap the specifics for your operation.

1. Unlock staff entrance, disarm alarm, note anything unusual.
2. Walkthrough: check for leaks, pest signs, anything disturbed overnight — pass/fail plus note.
3. Switch on lights, ventilation, and equipment per startup order.
4. Record walk-in cooler temperature (1–4°C / 34–39°F).
5. Record freezer temperature (−18°C / 0°F or below).
6. Check date labels on prepped stock; discard and log anything expired.
7. Handwash stations stocked: soap, paper towels, hot water.
8. Sanitise food-contact surfaces and front counter.
9. Restock front-of-house: cups, lids, napkins, condiments.
10. Photo: counter and seating area, customer-ready.
11. Count float, open till, confirm card terminal online.
12. Unlock front door on time; flip signage.

Twelve items, walked back-to-front, two numeric readings, one photo, done in the natural course of opening. The checklist adds perhaps three minutes to work that was happening anyway — that ratio is the target.

A sample closing checklist

Closing lists fail more often than opening lists, because the deadline is "whenever we finish" and the audience for failure is tomorrow's opener. Compensate by making evidence heavier here.

1. Last customer out; front door locked; signage flipped.
2. Till counted, reconciled, and logged; cash to safe.
3. Equipment shutdown per order: fryers off, coffee machine backflushed, hot-hold emptied.
4. Perishables covered, dated, and stored; nothing left in the danger zone (5–60°C / 41–140°F).
5. Record end-of-day cooler and freezer temperatures.
6. Floors swept and mopped; bins out.
7. Photo: kitchen line, clean and shut down.
8. Photo: front of house, reset for tomorrow.
9. Dishwasher run and emptied; sinks clear.
10. Back door locked and bolted.
11. Lights off except security; thermostat set.
12. Alarm armed; exit; final door check.

Items 7 and 8 are deliberate: the most commonly skimped items (cleaning) carry the photo requirement, and tomorrow's opener becomes the natural verifier of tonight's honesty.

Why they don't get done — and the fix for each

• The list is a wall. Forty unordered items invite the single-scribble tick-all. Fix: cut to under twenty, split by area or role.
• Nobody looks at the result. Staff learn within two weeks whether completed lists are read. If they vanish into a binder, effort follows. Fix: someone reviews completion every morning — a two-minute habit that sustains the whole system.
• No consequence attaches to skipping. Not punishment — just acknowledgement. A miss that nobody mentions is a policy decision. Fix: same-day, low-drama follow-up: "Closing list wasn't done last night — what happened?"
• The items are impossible or irrelevant. One unfulfillable item ("check roof access" when the ladder is broken) teaches people the list is theatre, and the disease spreads to honest items. Fix: prune quarterly; delete or fix anything nobody can genuinely verify.
• It's pure memory and paper. The sheet ran out, the pen walked off, the new hire never knew the list existed. Fix: schedule it so it arrives on its own — the case made in paper vs digital checklists.

The deeper pathology — people ticking boxes without doing the work — deserves its own treatment; the short version is that visible review and targeted photo evidence remove most of it.

Scaling from one site to many

At one site, the owner's morning walkthrough substitutes for a lot of system. At five sites it cannot. The multi-site version of this discipline needs three things: one central template per list (so every site opens to the same standard), scheduling per location in its own timezone, and a single view showing which sites completed, which missed, and which logged an out-of-range reading — before mid-morning, not at month end. That visibility layer is what turns two good lists into a network-wide standard, whether you run restaurants or a retail chain.

Where software fits

This is the specific job Task10x was built around: opening and closing templates with pass/fail items, temperature readings with min/max limits, and required photos, scheduled daily to the right role at each location in its local timezone. Missed lists are flagged visibly the same day, failed items create tracked corrective actions, and a live dashboard shows every site's status at a glance — in any browser, no app install.