These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Food Safety & HACCP
- Features
- Hygiene Checks
Hygiene Checks
Submit a kitchen check, review its revision and control release.
OverviewPending Hygiene Checks×
Food Safety & HACCP · Hygiene Checks
New
Pending Hygiene Checks
Approval conditions
| Parent | Status | Revision | Table code | Sent at | Guest count | |
|---|---|---|---|---|---|---|
| PB-58609 | Submitted | 580 | TC-172 | 04 Oct | 33 | |
| PB-30233 | Submitted | 80 | TC-188 | 12 Oct | 8 | |
| PB-53103 | Submitted | 250 | TC-191 | 06 Oct | 2 | |
| PB-82139 | Submitted | 950 | TC-717 | 10 Oct | 33 | |
| PB-43840 | Submitted | 830 | TC-858 | 13 Oct | 24 |
6 of 6 records
TC-172Hygiene checks · HC-75866
SubmittedParentPB-58609
Revision580
Sent at04 Oct
Guest count33
Delivery referenceDR-118
What you can do
Follow the operating record
A hygiene check belongs to a production batch and operating organization. Kitchen Lead enters the table code, time sent, guest count and delivery reference where they apply, then submits the current revision. Submission freezes the material the Quality Reviewer will examine. A later edit must not turn an earlier decision into approval of a changed check.
The Quality Reviewer compares the submitted details with the attached evidence and the batch lines. The decision is recorded against the same parent and source revision. Approval, rejection and return are different decisions with a reason and decision time. The kitchen can correct and resubmit a returned check; it cannot use that return as permission to release.
For a batch headed to an outlet, the reviewer can check that the destination and delivery reference refer to the same service event. If the guest count differs from the prepared scope, the reviewer returns or rejects the check with an explanation. Release happens only after the independent decision and the corresponding effect has been persisted. The completed state belongs after that effect, not immediately after the reviewer clicks approve.
How the work is organized
- Submit one revision. Kitchen Lead enters the applicable table, time, guest count or delivery reference and submits the check for review.
- Decide independently. Quality Reviewer examines the submitted version and records a reason against the same parent and revision.
- Separate decision from effect. Operations Lead releases approved scope; Reconciliation Analyst confirms that the release effect persisted before completion.
What to agree during setup
Choose a Quality Reviewer who did not prepare the check. Agree which details and attachments must accompany a dining-room or delivery case. Set the rule for correcting a returned check: Kitchen Lead submits a new revision, and the earlier decision cannot authorize it. Give the reviewer access to the parent batch and its evidence.
Check the handoff on an actual case
For an order going to an outlet, Kitchen Lead enters the table code and guest count, then submits the check. Quality Reviewer compares those details with the batch and its attachment. Return the revision with a reason if the destination evidence differs. After correction, review the new revision independently. Approve it only when the evidence agrees. Then follow the release receipt: an approval with a failed effect stays unresolved until Reconciliation Analyst verifies what persisted.
What your team sees
- Pending Hygiene Checks — Show submitted checks awaiting an independent decision.
- Hygiene Review Decisions — Compare reasons and source revisions for decisions linked to a batch.
Follow the work through
See the related process and the data model before rehearsing the handoff. The implementation plan sets the order for loading people, products and live batches.
What it keeps track of
Data model- Hygiene checks
- Kitchen tickets submitted for review and release against a meal order.
- Production batches
- Customer orders accepted and fulfilled by the kitchen and service team.
- Corrective actions
- Independent reviewer decisions on submitted revisions.
- Record attachments
- Files and evidence attached to operational records.
Who uses it
Permissions- Kitchen Lead
- Submits the check.
- Quality Reviewer
- Makes the independent decision.
- Operations Lead
- Applies approved release, and Reconciliation Analyst verifies the resulting effect.
Set up Food Safety & HACCP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.