Opening, mid-shift and closing
Each station has its checklists. A lead or manager signs them off, and temperatures are checked against food-code limits as they are entered.
Case study · Magnolia Synergy
In a counter-service store, one tablet on the counter is shared by everyone on shift. We built Magnolia Synergy's station checklists for that tablet: each one belongs to the store's business day, saves as it is filled in, and becomes a closed record once a lead approves it.
IRIS (Integrated Reasoning & Intelligence Steward) is our planning assistant. The scoping page saves your answers to your own computer as a file, then offers a link to email them to us.
The problem
A shared tablet is put down mid-task, picked up by someone else, and sometimes left asleep. Two quick taps can race each other to the server. A closing checklist is often finished after midnight, when the calendar date has already moved on.
Each of those is a way to lose an answer, or to bring yesterday's answers back onto this morning's checklist.
What we built
Each station has its checklists. A lead or manager signs them off, and temperatures are checked against food-code limits as they are entered.
Each checklist belongs to the store's business day, not the calendar date, so a closing checklist finished after midnight is still last night's.
A checklist can be saved as pending and appears in a list the whole shift sees, including one saved on another tablet.
Once a lead approves a checklist it is a closed record. The server refuses any later change, and the screen does not offer one.
How we built it
Which checklist to resume, which count as today's and when a day has ended are small functions, each tested by behaviour rather than through the screen.
Answers are sent one save at a time, in the order they were given. A save that fails takes the one waiting behind it with it, so the screen never stores an answer it has just said did not save.
The hour a day ends is the server's own number, and a test reads it from the server's source so the tablet and the server cannot disagree.
The result
Measured 6 October 2026, from our main engineering repository as it stood that day.
Describe your systems, your reports and where the time goes on the IRIS scoping page. You keep a copy, and an engineer reads it before we talk.