Lesson guide
Monitoring daily controls
Monitoring checks whether the allergen system works in daily practice. A written procedure or accurate matrix is not enough if a member of staff still answers from memory. Observe questions being handled, orders communicated and food handed over, as well as checking storage, labels, records, supplier changes and cleaning controls.
Use real working conditions, including busy periods and shifts with new staff or rapid packing. The source's example is a manager seeing a server guess instead of consulting an accurate matrix. That observation identifies a procedural failure that a document-only review would miss.
Look for repeated signs of weakness: staff unable to find information, unclear labels or substitutions regularly missed. Correct the immediate unsafe behaviour, then improve the system causing the pattern. Monitoring provides evidence about performance; it is not a permanent guarantee that every later order will be safe.
Opening and closing checks
Before service, check that current information is available, matrices are accessible, labels are correct, ingredients are properly stored and staff know where to seek help. Review changes since the previous shift, including deliveries, substitutes, recipes, specials, missing labels or ingredients transferred into working containers.
A new bread product may introduce sesame or milk. Check its label and update the relevant records before use; an opening checklist is not complete simply because the delivery arrived on time. The check should identify anything that could make yesterday's information wrong today.
At closing, review unanswered questions, wrong labels, near misses, substitutions, complaints and mistakes from the shift. Store ingredients and preserve clear identification for the next team, and remove outdated information from active use. A simple consistent checklist can help, provided it reflects real checks and records action rather than mechanically marking every box.
Menu and label review records
A useful review record shows when information was checked, who checked it, which products or recipes were included, what supplier information was considered and what changed. Menus, PPDS labels, matrices, websites and ordering platforms must all match the food being sold.
If a café changes its cake supplier, check the actual products before sale and update the display, menu, matrix and online listing where needed. For PPDS food, ensure the correct food name, full ingredient list and allergen emphasis match the food inside. Obsolete label templates can create a serious risk even when the new recipe is correct.
Remove old versions from routine use, but retain review evidence appropriately for the business's investigations and records. These are different tasks: an old menu must not remain the customer's information source, while a review history can establish what was available at the time of an incident. Accurate records support accountability and due diligence without guaranteeing a legal outcome.
Training and competence checks
Training records show what instruction a person received; competence checks show whether they can apply it. A staff member who watched a video still needs to demonstrate that they can find the matrix, handle a question, recognise uncertainty and ask the responsible person rather than guess.
Check the skills relevant to each role. A server needs accurate customer communication, a chef needs ingredient and cross-contact controls and a packing worker needs reliable labelling and handover. Scenario questions, service observation and review of allergy notes can help establish how staff respond in practice.
When a person cannot follow the procedure, provide further training and supervision before allowing them to handle the relevant requests alone. Refresh instruction when menus, ingredients, systems or procedures change, and record it honestly. These study questions are formative practice, not an automatic declaration that a learner is competent or has passed a formal assessment.
Corrective action
A control failure requires immediate action on the risk, not only an entry in a log. Examples include a wrong ingredient, outdated matrix, incorrect label, shared utensil or suspected transfer. Stop the affected order or sale and report it to the responsible person while checking whether customers may already be affected.
If cheese is added to a dairy-free order, lifting it off is not an adequate corrective action: milk may already be on the food, utensils, gloves or packaging. Stop the order and remake it safely only if suitable controls can be established. For an incorrect PPDS label, remove affected products from sale and check the label, recipe and stock before allowing them back into sale.
Record what happened and what was done, then investigate why it happened. Consider training, templates, missed substitutes, workload and unclear instructions. Preventing a repeat means fixing the cause as well as the particular meal. Do not serve food as suitable when relevant allergen safety remains uncertain.
Near misses and incident logs
A near miss is a mistake caught before it reaches the customer, such as spotting the wrong sauce on an allergy order before service. Record it even if no food was eaten. Complaints about unclear information, wrong food, missing labels or a possible reaction also need careful recording and investigation; a reported reaction is not itself a diagnosis or proof of the cause.
Include the observed facts, food involved, allergy information received, relevant staff and actions taken, followed by subsequent changes. The source's sesame-bun example shows how a prevented mix-up can still reveal a weakness in tickets, storage, training or final checks.
Review logs for recurring patterns rather than treating each event as an isolated annoyance. Repeated near misses can indicate urgent weaknesses in the system, even though the error was caught each time. The purpose of an honest record is to learn and prevent a future harmful incident, not to hide the warning because the customer did not receive the food.
Stop sale, withdrawal and recall
Stop sale means halt sales of the affected food while the issue is checked. The source distinguishes withdrawal, removing unsafe food from the supply chain before it reaches consumers, from recall, where food may already have reached consumers and advice or action is needed. Follow the appropriate procedure rather than continuing sales while investigating a genuine risk.
If packaged cakes contain undeclared nuts, stop sale immediately. Check whether affected food remains in stock, has gone to another business or has already been sold, because that determines the next actions. Separate stock, preserve labels and records, check batch information and escalate to the appropriate management and supplier contacts.
Follow the applicable authority and incident guidance, including local-authority notification requirements. The further-reading guidance supplies that current official context; this lesson is not a complete legal incident protocol. Protect customers first, preserve the evidence needed to trace affected food and act promptly on any withdrawal or recall instructions.