Completion percentage is usually the first number people look at on the dashboard, and it is often the least useful.
A site that shows 100% completion every day for several weeks is more likely to have a checklist that is being ticked without being properly read than a perfect operation. High completion on its own tells you very little about whether the checks are meaningful.
What is actually worth watching
The more valuable signals are:
- Missed runs — Checklists that were due but never completed or signed off.
- Failed items — Individual checks that were marked as failed or out of range.
- Open issues — Failures that still need a proper corrective action and closure.
These numbers tell you where the real problems are and whether the team is dealing with them.
Why missed and failed matter more
A site that occasionally misses a checklist or fails an item, then records a clear corrective action and closes the issue, is usually in better shape than a site that never shows a single failure.
Consistent perfection often means one of three things:
- The checklist is too easy or too vague.
- People are completing it from memory at the end of the shift.
- Staff are reluctant to record problems because they think it will reflect badly on them.
None of those situations improve food safety or inspection readiness.
How to use this in practice
When you look at the dashboard or reports, ask these questions:
- Which checklists are being missed most often, and on which days?
- Which items fail regularly?
- Are the corrective actions specific and useful, or are they vague?
- How long do issues stay open?
Then act on the answers. Change the wording, adjust the timing, retrain if needed, or simplify the checklist. The goal is not to eliminate every failure — it is to make sure failures are visible and dealt with.
A site that fails something twice a week and closes it out properly is working. A site that never fails anything is probably not being asked hard enough questions.
Practical tip
Once a week, spend five minutes looking only at missed runs and open issues across your sites. Ignore the overall completion percentage for that short review. You will usually spot the real risks faster this way.
CrewByte is built to surface what did not happen and what went wrong, because that is the information that actually helps you manage the operation.