The open and the close are the most repeated work a site does and the easiest to let slide, because the people doing them change constantly and the consequences of skipping a step usually arrive later.
Scheduled, not remembered
Set the routine once with a start date and an interval. Every day's occurrence appears on the day it's due, as its own record with its own history. Nobody copies yesterday's list.
Several routines a day
Opens, mid-shift checks and closes can run as separate schedules on the same day, each landing with the shift that's responsible for it instead of all appearing at 9am.
Whoever is on shift
Assign to a team and the routine reaches whoever is actually working, rather than sitting unread in the list of someone who is off. A schedule set up in spring still works after a summer of staff changes, and each occurrence carries the location it belongs to so multi-site groups keep the sites apart.
Handover that carries context
Because each occurrence keeps its own comments and attachments, the closing shift can leave a note on the record itself: a fault, a delivery, something the morning needs to know, and not on a scrap of paper by the till.
What was skipped is visible
A partially completed routine shows which items were done and which weren't, instead of collapsing to "incomplete". That's the difference between knowing you have a problem and knowing what the problem is.
Start with the close
If you are only going to digitise one routine, make it the close.
The close happens with the fewest managers present, carries the most consequences, security, cash, cold chain, gas, waste, and is the one most often compressed when the shift has overrun. It is also the routine whose failures surface at the worst moment: the following morning, to whoever opens. The open is easier to police informally, because someone senior is usually arriving. The close is where a record earns its keep.
Designing a routine people finish at 23:40
The constraint on a closing checklist is not thoroughness. It's that the person completing it wants to go home, and a routine that fights that will be filled in dishonestly, not skipped, and that is worse, because it looks complete.
- Order it as a walk through the building, ending at the door
- Keep it under ten minutes for a normal night
- Ask closed questions that can actually fail
- Require photos only where they settle an argument: the cellar, the fire exit, the cash drawer
- Put detail behind follow-ups, so a clean night is fast and a bad night is thorough
A six-minute close gets done properly on a bad night. A twenty-five minute close gets ticked in the car park.
Comparing shifts over time
Because every occurrence is its own record, the same routine across a month is a dataset, not a stack of forms, which items fail most, which shifts run long, whether Fridays look different from Tuesdays. That's usually where the useful discovery is. An item that fails every Saturday is telling you something about Saturday staffing, not about the person who happened to record it.
Items worth including
The specifics differ by industry, but the routines that hold up tend to cover the same four categories:
Safety
Security
Equipment
Readiness
The last category is the one most often left out and the one staff value most. A close that ends by recording what the morning needs to know turns a checklist into a handover, which is a large part of why people complete it willingly.
When a routine gets skipped
It will. The useful question is what happens next. An incomplete routine stays visible instead of rolling over silently, so the gap is visible the following morning, not a discovery made weeks later. Where the stakes justify it, the routine can require sign-off, so a close that wasn't finished is escalated, not simply recorded as unfinished.
What matters most is the response. A skipped close that nobody mentions teaches the team that the routine is optional, and that lesson spreads faster than any policy. Following up the first time is what makes the next fifty happen.