Food safetyCleaning and hygiene
Opening and closing cleaning checks: avoid duplicating the same task
Separate the work that must be done from the checks that confirm readiness for the next shift. A closing task and an opening verification may be linked without presenting them as two unrelated cleaning jobs.
At a glance
Separate the work that must be done from the checks that confirm readiness for the next shift. A closing task and an opening verification may be linked without presenting them as two unrelated cleaning jobs.
Define the decision behind the record
Define the handover between shifts. If the closing team reports a problem, the opening team should see it before assuming the area is ready. Do not let a new day reset an unresolved finding to a blank, apparently normal checklist.
Give closing work and opening verification separate purposes
Map the tasks normally performed at closing and the conditions checked before opening. Identify the area, instruction and accountable roles for each purpose. Avoid copying a generic list twice without deciding whether the second team is repeating work, checking readiness or taking over an unresolved issue.
Record closing completion against its actual task and event. At opening, capture the condition observed and any outstanding restriction or new finding. Link an incomplete closing task to the receiving owner rather than allowing a fresh day’s checklist to hide it. The record should explain what changed between the two observations.
During review, compare task completion, readiness and open actions as distinct information. Test a complete close with a new opening finding and an incomplete close that is explicitly handed over. A useful export retains both histories without awarding two completion marks for a single task or treating yesterday’s pass as today’s observation.
Worked example
The evening team records cleaning completion and a damaged surface. The morning team sees the open defect and performs the required readiness check. The cleaning completion remains recorded, but the defect follows its own action and review.
Build a usable record
Use the fields below to capture the facts needed for this particular decision. Keep the actual observation separate from any later correction or approval.
- Area and shift identifiers
- Completed work and time
- Outstanding issue reference
- Next-shift readiness observation
- Handover and escalation
Example record and review decision
Fictional record example: CLOSE-01: scheduled cleaning and completion evidence; OPEN-02: readiness verification and any newly observed condition.
Decide which task is performed at closing and which condition is verified at opening. Keep separate ownership and purpose.
Duplicating the same task on both forms can create two completion marks for one event while leaving readiness unexamined.
Test the review, not just the form
Simulate an unresolved issue at a date change. Check whether it appears to the next team and whether the original observation remains available. Review the schedule for duplicate tasks that produce extra ticks without new information.
A few useful answers
Should each shift start a completely new history?
Start the next scheduled check, but preserve links to outstanding issues and the previous handover.
Should the opening team simply copy the closing result?
No. Define the opening check’s purpose and record the actual observation required. The previous result is useful context, but it does not create a new readiness check or resolve an action that remains open.
Sources and further reading
MarkdownExplore starter templates
Start with a useful checklist
English
