Level 3 Food Allergy Management

Module 5: Allergen matrices, recipes and menus

Build evidence-based allergen information, control recipe and menu changes and make final checks so every version matches the food served today.

Video runtime: 11:02

What you will learn in this module
  • Build matrices from checked ingredients and preparation methods and control changes to recipes and specials.
  • Keep menus, labels, websites, ordering systems and training information consistent and current.
  • Communicate real remaining cross-contact risks and complete final checks before sale or service.

Load this video from YouTube. Your browser will connect to YouTube; embedding follows your cookie preferences.

External playback does not record on-page study progress.

Module 5: Allergen matrices, recipes and menus

Module 5: Allergen matrices, recipes and menus

Build evidence-based allergen information, control recipe and menu changes and make final checks so every version matches the food served today.

Records your study progress, not an assessment result or certificate.

Key points

  • Build an allergen matrix from checked evidence, including every component of the dish.
  • A garnish, dressing, substitute or one-off special needs the same control as a regular recipe.
  • Update both kitchen records and every affected customer-facing system when ingredients change.
  • Precautionary information must describe real risk; it cannot substitute for proper controls.
  • Remove obsolete versions and brief staff using the current information.
  • If a final check leaves doubt, resolve it before serving food as suitable.

Lesson guide

Building accurate matrices

An allergen matrix links dishes or products to the regulated allergens they contain. It is a safety tool only when it is accurate, current and based on the actual ingredients and preparation methods. Build it from recipe cards, supplier specifications, labels and checked product information, not from memory or an assumption about a dish's name.

The source's chicken-wrap example shows why all components count: wheat may be in the wrap, egg and mustard in the sauce, soya in the marinade and sesame in the garnish. Check bought-in products, toppings, dressings, spice mixes and compound ingredients as well as the main food. An apparently simple dish can have several separate information sources.

Review the matrix when recipes, suppliers, products, menus or preparation methods change. Train staff to locate and use the current record, including what to do when it does not answer their question. Never fill a gap with a guess merely to finish the chart; confirm the information before it is used to advise a customer.

Controlled recipes and ingredients

A standard recipe uses approved ingredients, quantities and methods consistently. This helps keep allergen information aligned with the food produced. Recipe control must include sauces, garnishes, toppings, marinades, stocks, spice mixes and compound ingredients, not just the item named on the menu.

In the source example, a coleslaw recipe uses mayonnaise containing egg and mustard. A member of staff who swaps the mayonnaise during service may change the dish's allergen information. The same problem can arise from a different roll, dressing or informal garnish. Familiarity with the usual recipe is not permission to make unchecked changes.

Before introducing a replacement or new ingredient, check its label or specification, update the matrix, review menu information and tell the team. Require approval for recipe changes so staff know the information is settled before sale or service. Consistent recipes do not prevent all cross-contact, but they provide a reliable ingredient baseline for the wider control system.

Specials and temporary dishes

One-off items need the same standard as permanent menu dishes. A special may be created quickly and be absent from the usual records, so check its recipe, ingredients, supplier information, preparation method, cross-contact risks and customer communication before offering it. A temporary item is not an exception to normal allergen procedures.

The source illustrates the variety of components that can be missed: a soup's stock powder, a seasonal dessert, cheese or mustard dressing in a summer salad and a temporary sauce. Where the video uses the shorthand 'gluten', record the relevant cereal identified by the actual ingredient information rather than treating that general word as a complete declaration.

Make the special's checked information visible through the business's appropriate temporary record, daily sheet or digital system, backed by a staff briefing. Front-of-house staff need the same facts as the kitchen. If the information cannot be confirmed, do not recommend the dish to an allergy customer; stop and resolve the missing information instead of improvising an answer.

Updating every information channel

Information must agree wherever customers or staff encounter it. The source lists printed menus, allergen charts, websites, online ordering, delivery apps, tills, PPDS labels and staff guidance. Updating only the kitchen recipe card leaves a risk if another channel still describes the former dish.

For example, a new burger sauce contains mustard and egg but the delivery platform still carries the old information. Customers may decide what to buy without speaking to staff. Check the relevant distance-selling requirements, including information before purchase and at delivery, and keep allergy notes connected to the order rather than relying on an old listing.

Assign responsibility for finding and changing every affected information point when a supplier, recipe or ingredient changes. Staff also need a route for reporting mismatches. If a website says dairy-free but the current recipe contains milk, correct the inconsistency before allowing customers to rely on that claim. The same accuracy requirement applies to staff-facing systems.

Precautionary allergen information

Precautionary information concerns possible unintended allergen presence from cross-contact. It is not the same as declaring an ingredient that is deliberately used. The source discusses statements such as 'may contain' and warns against using a blanket warning as a convenient replacement for proper control.

First assess the real risk and improve separation, cleaning, dedicated equipment or procedures where those measures can control it. The bakery example concerns a remaining realistic risk of nut traces despite controls, not automatic permission to label every product and stop trying. Use appropriate, clear precautionary information for the actual residual risk and follow current official guidance.

Explain that a warning does not say the allergen is definitely present, but it does communicate a possible risk important to an allergy customer's decision. Retain and assess relevant supplier warnings rather than dismissing them. Staff must not promise safety by ignoring a warning or allow precautionary wording to conceal a poorly managed preparation process.

Version control

Version control means staff can identify and use the latest correct information. Matrices, recipes, menus, PPDS labels, online listings and supplier specifications all change, so replacing one file is insufficient if old copies remain in use. The system must withdraw obsolete information and make the current version clear.

The source's pizza example adds milk powder to the dough. Although the matrix is updated, an old printout at the till could lead a server to call the base milk-free. Check paper locations and digital displays, including delivery platforms, so an old version does not survive where staff or customers still rely on it.

A manageable system can use a version number, date, responsible person and review date. Remove old copies and brief staff whenever a relevant change occurs. Training materials need the same review: teaching from an outdated chart can recreate the very mistake the new version was intended to prevent.

Final checks before service

A final check is the last opportunity to catch a mistake before food reaches the customer. Define checks for allergy orders, PPDS products, takeaways and deliveries rather than assuming that earlier preparation guarantees the handover. For a prepared order, confirm the allergy information, ingredients, method, packaging or label and the correct customer.

For PPDS food, check that the label is readable, allergen emphasis is correct and the information matches the product inside. For delivery or takeaway, keep allergy notes visible and verify the containers and order identity. Similar-looking meals must not be mixed up: the video uses two burgers, one prepared for a sesame-allergy customer, to show why a final handover matters.

If the check raises uncertainty, do not serve the food as suitable while someone guesses at the answer. Pause, establish the facts and resolve the issue. Managers should make this stop-and-check expectation explicit so staff know that checking is part of the job, even when service is busy.

In practice

The complete chicken wrap

Source teaching example rewritten for practice

The kitchen records only wheat from a wrap but has not checked the sauce, marinade or sesame garnish.

Can that entry be used to advise customers?

Check each component and the preparation method before completing and using the matrix.

The source shows egg, mustard, soya and sesame may be introduced by components other than the wrap itself.

Pizza information at the till

Source teaching example rewritten for practice

Milk powder has been added to pizza dough. The matrix is updated but an old printout remains at the till.

What remains to be fixed?

Withdraw the obsolete copy, check other information channels and brief staff on the current version.

An accurate new document cannot protect customers if the staff still use the old one.

Two similar burgers

Source teaching example rewritten for practice

Two burgers look alike, but one belongs to a customer whose sesame allergy was checked during preparation.

What should happen at handover?

Confirm the allergy note, packaging and order identity so the checked meal reaches the correct customer. Stop if there is any doubt.

Preparation controls must survive packing and handover; appearance cannot prove which meal is which.

Reflect on your learning

Which is a reliable basis for an allergen matrix?

Select one answer.

A chef introduces a temporary soup. Which approach fits the lesson?

Select one answer.

What is the role of precautionary allergen information?

Select one answer.

A new recipe contains milk while the website still says dairy-free. What should staff do?

Select one answer.

For your own learning — not the certification assessment.

FAQs

Does a matrix need toppings and garnishes?

Yes. Check every component, including bought-in products, sauces, toppings, dressings, spice mixes and compound ingredients. An allergen may enter through any of them.

When should a matrix be reviewed?

Review it when ingredients, recipes, suppliers, products, menus or preparation methods change, before staff use the affected information to advise customers.

Can daily specials bypass the normal checks?

No. Check, record and communicate the ingredients and relevant preparation risks before offering the special, just as for a regular menu item.

Does 'may contain' mean definitely contains?

Not necessarily. It communicates a possible unintended presence that may matter to the customer. Explain it honestly and do not use it instead of appropriate allergen controls.

What makes a version-control system usable?

Staff can identify the current information, obsolete copies are removed, digital channels are checked and the team is briefed. A version, date, responsible person and review date can help.

What if the final handover check raises doubt?

Pause and resolve the uncertainty before serving the food as suitable. Confirm that the checked preparation, packaging, allergy notes and order identity belong to the correct customer.

Further reading

  • Allergen guidance for food businesses (opens a new tab)

    Supplementary official context for ingredient records, precautionary information and distance selling.

    Food Standards Agency. Applicable jurisdiction: England, Wales and Northern Ireland; Scottish businesses should use the applicable Scottish guidance.. Supplementary reading; checked 2026-10-07.

  • Introduction to allergen labelling for PPDS food (opens a new tab)

    Checks for current ingredient labels on food correctly classified as PPDS.

    Food Standards Agency. Applicable jurisdiction: England, Wales and Northern Ireland; Scotland has its own PPDS guidance.. Supplementary reading; checked 2026-10-07.

  • Prepacked for direct sale (opens a new tab)

    Scottish PPDS label requirements and practical route to further guidance.

    Food Standards Scotland. Applicable jurisdiction: Scotland.. Supplementary reading; checked 2026-10-07.

Jump to a key moment
Transcript

[0:00] Welcome to lesson 5.1 building accurate
[0:03] allergen matrices.
[0:05] An allergen matrix is a document or
[0:06] system that shows which dishes,
[0:08] products, or menu items contain the 14
[0:11] regulated allergens.
[0:13] At level three, managers and supervisors
[0:15] need to understand that an allergen
[0:17] matrix is only useful if it is accurate,
[0:19] current, and based on real ingredients.
[0:22] A good allergen matrix should be built
[0:24] from recipe cards, supplier
[0:25] specifications, ingredient labels,
[0:28] product information, and confirmed
[0:29] preparation methods.
[0:31] It should not be built from memory or
[0:33] assumptions.
[0:35] For example, a chicken wrap may appear
[0:37] simple, but the wrap could contain
[0:39] wheat, the sauce could contain egg and
[0:41] mustard, the chicken marinade could
[0:42] contain soya, and the garnish may
[0:44] contain sesame.
[0:46] All of this information must be checked
[0:48] before the dish is added to the matrix.
[0:51] Managers should also include bought-in
[0:53] products, sauces, toppings, garnishes,
[0:56] dressings, spice mixes, and compound
[0:58] ingredients.
[1:00] These are common places where hidden
[1:01] allergens are missed.
[1:03] The matrix should be reviewed whenever
[1:05] recipes, suppliers, products, menus, or
[1:08] preparation methods change.
[1:11] Staff should also know where the matrix
[1:13] is kept and how to use it correctly.
[1:15] If there is uncertainty, the matrix
[1:17] should not be guessed or completed
[1:19] quickly just to fill a gap.
[1:21] The information must be checked before
[1:23] it is used to advise customers.
[1:25] The key message is an allergen matrix is
[1:27] a safety tool.
[1:29] It must be built from reliable evidence,
[1:31] kept up to date, and used properly by
[1:33] trained staff.
[1:35] Welcome to lesson 5.2, recipe control
[1:38] and standardized ingredients.
[1:41] Recipe control is essential for allergen
[1:43] management because allergen information
[1:44] depends on the ingredients actually
[1:46] used.
[1:47] If staff change ingredients without
[1:49] updating records, the allergen
[1:51] information may become wrong.
[1:53] This can put customers at serious risk.
[1:57] A standardized recipe means the dish is
[1:59] made the same way each time using
[2:01] approved ingredients, approved
[2:03] quantities, and approved preparation
[2:05] methods.
[2:06] This helps the business give consistent
[2:08] allergen information.
[2:10] For example, if a cafe standard recipe
[2:12] for coleslaw uses mayonnaise containing
[2:14] egg and mustard, those allergens can be
[2:16] recorded accurately.
[2:18] But if a staff member swaps to a
[2:19] different mayonnaise during service, the
[2:22] allergen information may change.
[2:24] Managers should make sure recipes
[2:26] include all ingredients, including
[2:28] sauces, garnishes, toppings, marinades,
[2:31] spice mixes, stocks, and compound
[2:33] ingredients.
[2:35] Recipe changes should be controlled.
[2:38] Before a new ingredient is used, the
[2:40] label or specification should be
[2:42] checked, the allergen matrix should be
[2:44] updated, menu information should be
[2:46] reviewed, and staff should be told.
[2:49] Staff should not make informal changes
[2:51] such as using a different sauce, adding
[2:53] a garnish, changing a bread roll, or
[2:55] replacing a dressing without approval.
[2:58] The key message is accurate allergen
[3:00] information depends on controlled
[3:01] recipes.
[3:03] Managers must make sure approved
[3:05] ingredients are used consistently and
[3:06] any changes are checked before food is
[3:08] sold or served.
[3:10] Welcome to lesson 5.3, specials,
[3:13] seasonal menus, and temporary dishes.
[3:16] Specials, seasonal menus, and temporary
[3:19] dishes can create allergen risks because
[3:21] they may be introduced quickly and may
[3:22] not be included in the usual allergen
[3:24] records.
[3:26] At level three, managers must make sure
[3:28] temporary food items go through the same
[3:30] allergen checks as regular menu items.
[3:33] This means checking the recipe,
[3:35] ingredients, supplier information,
[3:37] preparation method, cross contact risks,
[3:40] and customer communication before the
[3:42] dish is sold.
[3:43] For example, a chef may create a soup of
[3:46] the day using a stock powder that
[3:47] contains celery, milk, or gluten.
[3:50] If front of house staff do not have this
[3:52] information, they may give customers the
[3:54] wrong answer.
[3:56] Seasonal dishes can also introduce new
[3:58] allergens.
[4:00] A Christmas dessert may contain nuts,
[4:02] milk, egg, gluten, or sulphites.
[4:05] A summer salad may include sesame,
[4:07] mustard dressing, or cheese.
[4:10] A temporary sauce may contain soya,
[4:12] fish, or celery.
[4:14] Managers should make sure specials are
[4:16] recorded clearly.
[4:17] This could be through a temporary
[4:19] allergen sheet, updated daily specials
[4:21] board, kitchen briefing, menu note, or
[4:24] digital system.
[4:26] Staff should also know that a special
[4:27] that does not mean normal allergen
[4:29] procedures can be skipped.
[4:31] If allergen information cannot be
[4:33] confirmed, the dish should not be
[4:34] recommended to customers with allergy
[4:36] concerns.
[4:38] The key message is temporary dishes
[4:40] still need permanent standards.
[4:42] Specials, seasonal items, and one-off
[4:45] dishes must be checked, recorded, and
[4:47] communicated before they reach
[4:48] customers.
[4:50] Welcome to lesson 5.4, updating menus,
[4:53] websites, and ordering platforms.
[4:56] Allergen information must stay
[4:58] consistent across every place the
[4:59] customer sees or receives it.
[5:02] This includes printed menus, allergen
[5:04] charts, websites, online ordering
[5:07] platforms, delivery apps, till systems,
[5:10] PPDS labels, and staff guidance.
[5:13] At level 3, managers must make sure
[5:15] updates happen everywhere, not just in
[5:17] the kitchen.
[5:19] For example, if a restaurant changes its
[5:21] burger sauce and the new sauce contains
[5:23] mustard and egg, the recipe card may be
[5:25] updated, but the printed menu, allergen
[5:27] matrix, and delivery platform may still
[5:30] show old information.
[5:32] This creates a serious risk.
[5:34] Online and distant selling orders need
[5:36] particular care because customers may
[5:38] make decisions before speaking to staff.
[5:41] Allergen information must be available
[5:43] before purchase and when food is
[5:45] delivered where required.
[5:47] Managers should use version control and
[5:49] a clear update process.
[5:51] When a recipe, supplier, or ingredient
[5:53] changes, someone should be responsible
[5:56] for checking all affected menus, labels,
[5:58] and systems.
[6:00] Staff should also know what to do if
[6:01] they notice a mismatch.
[6:03] For example, if the website says a dish
[6:05] is dairy free, but the kitchen recipe
[6:07] now contains milk, the item should be
[6:09] checked and corrected before customers
[6:11] rely on the wrong information.
[6:14] The key message is allergen information
[6:16] must match across all customer-facing
[6:18] and staff-facing systems.
[6:20] One outdated menu, website, or delivery
[6:23] listing can put customers at risk.
[6:26] Welcome to lesson 5.5, managing may
[6:28] contain and precautionary allergen
[6:30] information.
[6:32] Precautionary allergen information is
[6:33] used when an allergen may be
[6:35] unintentionally present because of
[6:36] cross-contact risk.
[6:38] Common phrases include may contain, not
[6:41] suitable for people with a particular
[6:42] allergy, or made in an area that also
[6:45] handles.
[6:46] At level three, managers need to
[6:48] understand that precautionary allergen
[6:50] information should not be used as a lazy
[6:52] replacement for proper allergen control.
[6:55] It should be based on a real risk that
[6:57] cannot be fully controlled.
[6:59] For example, if a bakery uses nuts in
[7:01] the same preparation area as other
[7:03] cakes, and despite cleaning, there is a
[7:05] realistic risk of nut traces,
[7:07] precautionary allergen information may
[7:08] be needed.
[7:10] However, if the risk can be controlled
[7:12] through separation, cleaning, dedicated
[7:14] equipment, or better procedures, the
[7:16] business should control the risk rather
[7:18] than simply adding a warning.
[7:20] Managers should also train staff to
[7:22] explain precautionary information
[7:24] honestly.
[7:25] A "may contain" warning does not always
[7:27] mean the allergen is definitely present,
[7:29] but it does mean there is a possible
[7:31] risk.
[7:32] Customers with allergies may need that
[7:34] information to decide whether the food
[7:36] is suitable.
[7:37] Staff should never remove or ignore
[7:39] precautionary warnings from supplier
[7:41] products when giving allergen
[7:42] information.
[7:44] The key message is precautionary
[7:45] allergen information must be honest,
[7:47] risk-based, and clearly communicated.
[7:50] It should support safe customer choices,
[7:53] not cover up poor allergen management.
[7:56] Welcome to lesson 5.6, version control
[7:59] for menus, labels, and allergen records.
[8:02] Version control means making sure staff
[8:04] are using the latest correct version of
[8:06] allergen information.
[8:08] This is important because menus,
[8:10] recipes, labels, supplier products, and
[8:12] allergen records can change.
[8:15] If old information remains in use, staff
[8:17] may give customers the wrong answer.
[8:20] At level 3, managers should control
[8:22] versions of allergen matrices, menus,
[8:24] recipe cards, PPDS labels, online
[8:28] listings, and supplier specifications.
[8:31] For example, a business may update its
[8:33] pizza dough recipe to include milk
[8:35] powder.
[8:36] The allergen matrix is updated, but an
[8:38] old printed copy remains at the till.
[8:41] A server using the old copy may wrongly
[8:43] tell a customer that the pizza base is
[8:45] milk-free.
[8:47] Managers should remove outdated
[8:48] documents, clearly date new versions,
[8:51] and make sure staff know which version
[8:53] is current.
[8:54] Digital systems should also be checked
[8:56] so old information is not still visible
[8:58] online or on delivery platforms.
[9:01] Version control is also important during
[9:03] training.
[9:05] Staff should not be trained using old
[9:06] menus or outdated allergen charts.
[9:10] A simple system can work well.
[9:12] For example, each document can have a
[9:14] version number, date, responsible
[9:16] person, and review date.
[9:19] When changes happen, old copies are
[9:21] removed, and staff are briefed.
[9:23] The key message is allergen records are
[9:25] only safe if staff use the current
[9:27] version.
[9:28] Managers must control updates, remove
[9:31] old information, and make changes clear
[9:33] to the team.
[9:34] Welcome to lesson 5.7, final checks
[9:37] before food is sold or served.
[9:40] Final checks are the last opportunity to
[9:42] catch allergen mistakes before food
[9:44] reaches the customer.
[9:46] At level 3, managers should make sure
[9:48] the business has clear final checks for
[9:50] allergen sensitive orders, PPDS
[9:52] products, menu changes, takeaway orders,
[9:55] and delivery orders.
[9:57] For prepared food, the final check may
[9:59] include confirming the customer's
[10:00] allergy, checking the ingredients,
[10:02] confirming the correct preparation
[10:04] method, checking the packaging or label,
[10:06] and making sure the correct meal goes to
[10:08] the correct customer.
[10:10] For PPDS food, the final check should
[10:13] confirm that the food has the correct
[10:14] label, the label is readable, allergens
[10:17] are emphasized, and the label matches
[10:19] the product inside.
[10:21] For takeaway or delivery, the check
[10:22] should confirm that allergy notes are
[10:24] visible, the correct containers are
[10:26] packed, and the order is not mixed with
[10:28] another customer's food.
[10:30] For example, if two burgers look
[10:32] similar, but one is prepared for a
[10:33] customer with a sesame allergy, the
[10:35] final handover check is essential.
[10:38] Without it, the wrong burger may be
[10:40] served or packed.
[10:42] Managers should also make it clear that
[10:43] if the final check raises doubt, the
[10:45] food must not be served until the issue
[10:47] is resolved.
[10:49] The key message is final checks protect
[10:51] customers by catching mistakes before
[10:53] sale or service.
[10:55] If allergen safety cannot be confirmed,
[10:57] stop, check, and do not serve the food
[10:59] as suitable.