Every kitchen checklist app demos well. You watch a manager tap through a clean opening checklist on a tablet in a quiet room, everything ticks green, and it looks like the paperwork problem is solved.
Then you roll it out, and six weeks later the closing team is back to signing a paper sheet because the app was “a faff on a Saturday”.
The difference between a checklist app that survives and one that gets quietly abandoned is rarely the feature list. It is a handful of small decisions about what happens when things go wrong: when a shift changes halfway through a list, when the answer to a question is no, when somebody forgets. Those decisions do not appear on pricing pages, so here is what to actually look for.
Why paper checklists fail first
Worth being clear about the baseline, because “paper works fine” is a reasonable starting position for a small site.
Paper fails in three predictable ways. The sheet lives in the office and the chef is in the walk-in, so the closing list gets done from memory an hour later or not at all. There is no timestamp, so an Environmental Health Officer (EHO) cannot tell whether Tuesday's sheet was filled in on Tuesday or on Friday afternoon with the rest of the week. And when the inspector asks for the last six months, they are in a box under the desk.
A digital checklist fixes those three things by default. We went through the trade-offs in more detail in paper diary vs a digital food safety app. Everything below is about whether an app fixes them without creating new problems.
The five things that decide whether it gets used
1. Can a half-finished checklist survive a shift change?
This is the one most apps get wrong, and it is the one that kills adoption fastest.
A weekly deep-clean list gets started by the chef on Tuesday and finished by someone else on Thursday. An opening checklist gets half done, then a delivery arrives. If the app treats a checklist as a single sitting that must be completed or lost, your team learns within a fortnight that starting one is a risk, and they stop starting them.
What to look for: the ability to save progress and resume, with the part-finished list visible to whoever picks it up next. Not saved to one person's phone. Shared across the team, so the next person on shift sees exactly what is outstanding.
2. What happens when the answer is no?
A checklist where everything is always yes is a checklist nobody is reading. Real kitchens have failures: the probe reads two degrees out, the extraction filter did not get done, a delivery came in warm.
The question is what the app does with a no. If it just records a red cross, you have captured the problem and lost the response, which is the half an EHO actually cares about. Under HACCP, the corrective action matters as much as the finding.
What to look for: answering no should open a note field immediately, in the moment, next to the item. Not a separate form somebody fills in later. The note is what turns “the filter was not cleaned” into “the filter was not cleaned, booked the contractor for Thursday, used the backup extraction in the meantime”, and that second version is a due-diligence record.
3. Can a completed record be edited afterwards?
This is the whole compliance argument, and it is worth understanding properly.
If an app lets an owner go back and change last month's checklists, then digitally it is no better than a pencil and an eraser. An inspector who knows the software can edit history treats those records with the same scepticism as a paper diary in one biro.
What to look for, specifically:
- Completed runs are immutable. Not “we do not recommend editing”. Actually cannot be changed, by anyone, including the account owner.
- Timestamps come from the server, not the phone. A phone clock can be changed. A server clock cannot, which means a month of checklists cannot be back-filled the night before an inspection.
- The person who signed off is snapshotted onto the record. If they change their display name or leave the business, the historical record still shows who completed it on the day.
- Edits to a template do not rewrite history. If you add an item to your closing checklist in June, May's completed runs should still show May's items, not the new ones.
That last point is subtle and most people never think to ask about it. It matters because without it, every template edit silently changes what your historical records appear to say.
4. How long does it take on the worst night of the week?
Not on the demo. On a Saturday at half eleven, with one exhausted KP.
A checklist that takes fifteen minutes gets done. A checklist that takes fifty gets skipped, and then invented. This is partly the app and partly the checklist itself: if your closing list has forty items, the app cannot save you.
What to look for: one-tap answers rather than typing. A visible progress counter so the person can see how much is left. And crucially, the ability to complete a checklist with some items unanswered, recorded honestly as not filled, rather than being blocked from signing off at all. A part-finished list is better data than a list nobody starts, and an app that refuses to accept anything less than perfect completion trains people to lie.
5. Who is allowed to complete one?
If only the manager can sign off checklists, then checklists happen when the manager is there, which is not the same thing as when the work happens.
What to look for: any team member can run and complete a checklist, while only owners and managers can create, edit or archive the templates. That split is the right one. The chef on shift records what they did; the manager decides what gets recorded.
What a good set of pre-loaded checklists looks like
Most kitchens do not want to write checklists from scratch, and should not have to. A decent app ships with the standard UK set ready to use.
The five that cover most of a small kitchen's needs:
- Weekly EHO checklist. The one inspectors recognise, covering training, personal hygiene, cleaning, pest control, temperature control and cross-contamination. This should be on by default and, ideally, not editable, because its value is that it matches the format an inspector expects.
- Opening checks. Probe calibrated, food date-labelled, handwash stations stocked, prep surfaces clean. Four items, two minutes.
- Closing checks. Cooked food cooled and stored, cooling done inside 90 minutes before refrigerating, surfaces sanitised, waste out, fridges closed and running, raw and ready-to-eat separated.
- Weekly deep clean. Fridges including door seals, freezers defrosted, oven and fryer and grill, extraction hood and filters, boards, floors and drains, bins, dry store.
- Monthly hygiene audit. HACCP records up to date, training records, probe calibration, date labelling, allergen information, pest control, cleaning evidence, supplier and delivery records.
What most checklist apps oversell
Three things get promised more often than they get delivered.
Push reminders. Lots of apps market notifications that nudge the team when a check is due. Some genuinely have them. Ask specifically whether they are shipped, because it is a common roadmap item that appears in marketing early. If reminders matter to you, do not take the website's word for it.
Photo upload and signature capture. Useful when they exist, but check whether you would actually use them. Most kitchens that ask for photo evidence never upload a single photo after week two.
Analytics and completion-rate dashboards. Genuinely valuable for a fifteen-site group. Almost entirely irrelevant for a single site, where the manager already knows whether the closing checks got done. Do not pay for a tier to get reporting you will open twice.
Full offline mode. Worth being precise here. Most apps sync when the signal returns and stay usable through a brief drop-out, which is fine for a kitchen with patchy WiFi. That is not the same as full offline operation, and vendors are often loose with the distinction. If you are in a basement with no signal at all, ask a direct question and get a direct answer.
Where Lemon fits
Lemon is our app, so treat this section accordingly. If you want the wider market first, we mapped it in the best food safety apps for UK kitchens in 2026.
Checklists in Lemon do the five things above. Daily, weekly, monthly or anytime frequencies. Save progress and resume across shifts and staff. A no opens a note field for the corrective action. Completed runs are immutable and timestamped from the server, with the signer's name snapshotted onto the record. Any team member can complete one; owners and managers control the templates. The five pre-loaded checklists above ship with the app, and four of the five are editable with a reset-to-default if you go too far.
Checklists are one of four record types, alongside fridge and freezer temperatures, food temperatures, and deliveries. All four come out in a single PDF for the last 7, 14 or 30 days, or a custom range, with every checklist item, its answer, and any note attached to a no.
£19 per month per location, everything included, unlimited team members, 14 days free without a card. Sign up at app.getlemon.app and add your first location, which takes about five minutes.
One practical note if you are on iPhone: create your account on the web first, then download the iOS app and sign in. Android and web can sign up directly.
The short version
Ignore the feature list. Ask five questions instead. Can a half-done checklist survive a shift change? What happens when someone answers no? Can completed records be edited afterwards? How long does it take on a bad Saturday? And can the person actually doing the work sign it off?
