🧈 butters

How to write a café opening and closing checklist

Updated August 2026

Most café checklists fail the same way. Somebody writes a thorough one, it goes on the wall, and by week three the team is ticking the whole column at 4pm without reading it. The document was fine. The design was wrong.

Here is what actually holds up in a working café.

Start from the failures, not the tasks

Do not begin by listing everything that happens in a shift. Begin by listing what has gone wrong in the last six months. Milk left out. Fridge door not latched. Grinder not purged. Float short. Back door unlocked overnight.

Every one of those is a checklist item that earns its place. Everything else is a nice-to-have competing for the same attention, and attention is the scarce resource.

Split opening and closing properly

Opening is about readiness. Closing is about safety and the next morning. Mixing them produces a list where half the items are irrelevant at the time somebody is holding it.

Opening: a workable shape

Closing: a workable shape

Fifteen items is the ceiling

Past about fifteen, compliance drops and people start batch-ticking. If your list is thirty items, you do not have a checklist, you have a training document. Split it: the daily list stays short, and the weekly deep-clean items move to their own list on their own day.

Write each item so it can only be done one way

"Clean the fridge" is not a task. It is a topic. Two people will do two different things and both will tick it.

Compare:

Vague: Check the fridge.
Actionable: Record the fridge temperature. It must read between 1°C and 4°C. If it is outside that range, tell a manager before using the stock.

The second version tells somebody what to do, what good looks like, and what to do when it is not good. That third part is the one most checklists miss, and it is the reason problems get ticked past rather than escalated.

Require evidence on the items that matter

For food safety items, a tick is close to worthless on its own. It records that somebody moved a pen.

Photo evidence changes the incentive. A photo of the thermometer reading, attached to the task, means the record shows the actual number rather than a claim. It also means the person doing it has to be standing in front of the fridge, which is most of the battle.

Do not require photos on everything. Three or four items, chosen because getting them wrong costs you, is enough. Requiring photos on twenty items produces the same batch-ticking behaviour in a different form.

Record who, not just what

A paper checklist on a clipboard tells you a task was done. It does not reliably tell you by whom, and it definitely does not tell you when. If a problem surfaces three days later, the trail is a signature at the bottom of a page covering an eight-hour shift.

This is not about catching people out. It is about being able to answer a question. When something went wrong on a Tuesday, you want to be able to look rather than guess.

Review it every quarter, and cut things

Checklists only ever grow. Every incident adds an item and nothing removes one, until the list is long enough that people stop reading it, which causes incidents.

Once a quarter, go through and ask which items have never once been the thing that caught a problem. Cut them. A short list people read beats a complete list people ignore.

Close the loop on what was missed

A checklist that comes in at 18 of 20 is more useful than one that comes in at 20 of 20, provided somebody sees the two. The place that usually happens is the shift report, and it is worth deciding how the unfinished items get there before you need them. See what belongs in a shift report.


Butters runs opening and closing checklists with photo evidence, and records who completed each item and when. See how it works.