A checklist that is too long gets ticked without being read, which is worse than no checklist at all. Aim for the things you would actually stop service over or that an inspector would care about.
The goal of your first checklist is not to capture every possible task. It is to create something short enough that the team will actually complete it properly, every time, on a busy shift.
Start with one checklist only
Choose either Opening or Closing for your first checklist — not both. Get one working well on real shifts before you build the second. Most sites find that starting with the checklist that currently causes the most problems on paper gives the quickest win.
Item types explained
CrewByte gives you several item types. Use the simplest one that does the job:
- Tick — Simple done / not done. Best for most tasks.
- Temperature — Linked to a specific appliance. The reading is automatically checked against the target range you set. Out-of-range readings can force a corrective action.
- Number — For anything you need to count (covers, portions left, cleaning chemical levels, etc.).
- Note — Free text. Useful for short observations or explanations.
- Photo — Requires the person to take a photo. The image is stored securely on the server and location data is stripped. Ideal for evidence of cleaning, stock condition, or probe displays.
- Signature — A typed name that applies to the whole checklist run. Used at the end to confirm who completed and signed off the checks.
Critical items
You can mark any item as critical. If a critical item is failed or left incomplete, the checklist cannot be signed off until a written corrective action is added.
Use this only for things that genuinely matter — the issues an Environmental Health Officer would write you up for. If you mark everything as critical, the team will stop taking the flag seriously and the feature loses its power.
Writing good checklist items
- Keep the wording short and clear. The person completing it is usually in the middle of a busy shift.
- Use the same language your team already uses on the floor.
- Put the most important food-safety items near the top.
- Avoid combining multiple tasks into one item. “Clean and sanitise prep surfaces and check fridge seals” should be two separate items.
- If an item needs a temperature or a photo, make that obvious in the wording.
Scheduling the checklist
Once the checklist is built, you set the days and times it should appear. CrewByte will automatically create a new run on those days.
If a run is not completed by its due time it is marked as missed. Missed runs appear clearly on the manager dashboard and in reports. This is deliberate — the real value is often in seeing what did not get done.
Versioning and editing
You can edit a checklist template at any time. Important rule: editing the template never changes runs that have already been completed or signed off. Those runs keep the exact wording and structure that was in front of the person at the time. This is what makes the records defensible in an inspection.
If you are moving from paper, send us your existing laminated sheet or Word document. We will build the first version of the checklist for you so you start by editing something familiar instead of a blank screen.
Practical advice for your first checklist
- Keep it short — 8 to 15 items is usually enough to start.
- Test it yourself on a phone before you give it to the team.
- Run it for two or three real shifts, then ask the people who used it what felt awkward or missing.
- Make small improvements quickly rather than waiting for a “perfect” version.
- Only after the first checklist is running smoothly should you build the next one.
A good first checklist is one that the team actually completes properly on a Friday night, not one that looks impressive on paper but gets ignored in practice.