An operational checklist is the short list a shift lead works through at 6:55 in the morning: fridges at temperature, signage lit, floor clear, till float counted. Set the Kind to Checklist when you build the template.
They are different from visits in tone and in cadence. Keep them short, keep them unscored, and expect them daily.
One per shift, per day
- Build the checklist template with the Kind set to Checklist. There is no pass threshold to set — the field is hidden for this kind, because checklists are not scored.
- Add a schedule under Compliance Settings and set Every to Daily.
- In Shifts, list the shifts — Open, Close.
- Leave Every active tribe on unless only some formats run it.
One checklist is then created per tribe per shift per day, named after the shift, so the opening and closing lists never get confused with each other.
Seeing who is doing them
The Checklists page lists every checklist run across the network, with its status and who completed it. Filter by status to Scheduled and turn on Overdue only to see the ones that were never done.
The value is in the pattern, not the individual day. A tribe that has not opened a checklist in a week is telling you something no single missed morning does.
Keeping them useful
- Ten items, not forty. A long daily checklist gets ticked without being read.
- Ask for a photograph only where it genuinely proves something — the fridge display, the front of house at open.
- Do not score them. A percentage on a daily checklist invites gaming.
- Do raise corrective actions from the few items that really matter, such as a temperature out of range.