Skip to content
All articles

Corporate Catering

Nut-Free Office Meal Safety: How to Vet a Caterer and Protect Special Meals

Plan safer nut-aware office meals with a caterer checklist, cross-contact questions, dietary records, and buffet or individually packaged service guidance.

October 10, 2026 · LunchLink

“Nut-free” is not a complete catering specification. It may mean that peanuts and tree nuts are not intentional ingredients, that the caterer has controls to reduce cross-contact, or both. Before ordering, clarify the required standard with the affected employee’s established workplace contact, then ask the selected caterer to confirm the specific menu, preparation, labelling, packaging, transport, and handoff arrangements.

This distinction matters because a dish name or ingredient list alone does not establish that a meal is protected from cross-contact. Canadian guidance identifies peanuts and tree nuts as priority allergens and recommends preventive controls throughout preparation to prevent allergens from contacting foods where they are not intended ingredients.

Quick summary

• Define whether the request concerns peanuts, tree nuts, intentional ingredients, cross-contact controls, or a combination.

• Disclose requirements before menu selection and obtain confirmation from the selected restaurant, not just a general promise from a booking platform.

• Consider individually packaged, clearly labelled meals when a shared buffet cannot reliably protect a required meal.

• Record each affected guest once within the total headcount, including overlapping requirements in one combined meal record.

• Keep protected meals separate during receiving, setup, and distribution, and pause service if labels, seals, or counts do not match.

What does “nut-free” mean for an office meal?

Start by separating two questions: are peanuts or tree nuts intentional ingredients, and what measures are in place to reduce accidental contact during preparation and service? A meal can contain no obvious nuts in its recipe while still requiring confirmation about shared equipment, preparation surfaces, utensils, storage, and handling.

Health Canada lists peanuts and tree nuts among Canada’s priority allergens, alongside substances such as milk, eggs, sesame, soy, wheat, fish, and mustard. The affected person or their designated workplace contact should specify which allergens are relevant rather than leaving “nut-free” open to interpretation. Canada’s priority allergen guidance provides the relevant terminology.

Labels are important, but they are not a substitute for good food-handling controls. The Canadian Food Inspection Agency explains that precautionary statements such as “May contain” can signal possible cross-contamination, but they do not replace preventive practices. Do not treat a label, menu name, or reassuring description as proof of a risk-free meal.

Set the required safety standard before choosing a menu

Do not ask a caterer to solve an undefined requirement. First, establish the information the affected employee needs to make their own informed choice. A workplace coordinator should not decide what level of allergy risk is medically acceptable, but can make sure the question is documented and communicated accurately.

Your dietary brief should distinguish an allergy from a preference and record the specific concern, such as peanuts, tree nuts, or both. It should also state whether the employee needs ingredient confirmation, information about shared equipment and preparation, a separately packaged meal, clear labelling, or another arrangement identified through the workplace’s established process.

Use a dietary requirements checklist to collect the information consistently. Keep the completed brief with the order rather than relying on a verbal note passed between the office, caterer, driver, and setup team.

How to vet a caterer for nut-aware office meals

A useful caterer review is specific to the selected restaurant, menu, date, and service format. Ask for confirmation before the menu is approved, because changing a dish after preparation or delivery may not be practical.

• Ingredients: Are peanuts or tree nuts used in the dish, sauce, garnish, dessert, condiment, or packaged component? Are ingredient details current for this order?

• Substitutions: If a standard ingredient is unsuitable, what replacement will be used? Has the replacement itself been checked?

• Shared equipment: Are the same fryers, grills, knives, cutting boards, mixers, trays, serving utensils, or preparation surfaces used for foods containing nuts?

• Preparation areas: Can the restaurant describe the relevant kitchen practices and any separation used for the specific meal?

• Cross-contact: What cross-contact risk remains after the restaurant’s preventive measures? Can the restaurant confirm the limitations rather than simply calling the meal “nut-free”?

• Labelling: Will the meal or container identify the intended recipient, relevant dietary requirement, and contents clearly?

• Packaging: Will the meal be sealed or otherwise protected from contact during packing, transport, and office setup?

• Transport: How will the meal be kept separate from other food during delivery, and who will hand it over?

• Responsibility: Which restaurant contact has confirmed the details, and who should the office call if the order arrives with a mismatch?

LunchLink’s corporate catering process reflects this sequence: customers share allergies before menu selection, and the selected restaurant partner confirms ingredients, substitutions, kitchen practices, and cross-contact risk. Its nut-aware options are not presented as a universal allergen-free guarantee, so the specific arrangement still needs to be confirmed.

Questions to ask before approving the order

Send the caterer a short written script so the answer is tied to the actual order:

“This order includes a guest with a peanut and/or tree-nut allergy. Please confirm the ingredients and substitutions for the proposed meal, the relevant shared equipment and preparation practices, the remaining cross-contact limitations, how the meal will be labelled and sealed, and how it will be kept separate during delivery and office service. If you cannot confirm these details, please say so before the order is accepted.”

Ask the restaurant to identify uncertainty clearly. “We cannot confirm” is useful information because it allows the office to pause, change the format, or consult the affected employee’s established workplace contact. A vague assurance is not a substitute for a specific answer.

Buffet or individually packaged meals: which format fits?

Neither a buffet nor an individual meal is automatically safe. The preparation and handling plan matters more than the format name. However, the format changes how many opportunities there are for shared utensils, spills, mistaken identification, and contact between foods.

A buffet may suit a seated team meal with enough space for separate serving utensils, clear labels, supervised setup, and a receiving plan. It is more difficult to control when guests serve themselves quickly, dishes are crowded together, utensils move between trays, or the office cannot keep a protected meal separate.

An individually packaged, clearly labelled meal can simplify identification and distribution, particularly for staggered breaks, desk meals, training days, or a protected meal alongside a general spread. Packaging does not remove preparation or kitchen risk, so the selected restaurant still needs to confirm the specific meal and handling arrangement. LunchLink’s guidance recommends requesting an individually packaged option when a shared buffet cannot reliably protect a required meal.

A practical format comparison

FormatWhen it may workRisks to confirmOffice receiving requirementShared buffetGuests eat together and the office has space, time, labels, and controlled serving.Shared utensils, spills, tray contact, unclear portions, and guests mixing serving tools.Set up labels and dedicated utensils, keep dishes in their planned positions, and brief anyone serving food.Individually packaged mealsPeople eat at desks, breaks are staggered, or one or more protected meals need clear identification.Unconfirmed kitchen practices, incorrect labels, damaged seals, or contact during delivery.Match the named meal to the recipient, inspect the packaging, and keep it separate until distribution.Mixed arrangementA general buffet is provided while specific meals are prepared and packaged separately.Protected meals being placed on the buffet, mistaken identity, or shared storage and utensils.Receive the protected meals first or identify them immediately, then assign one person to control their placement and handoff.

If the caterer cannot confirm the controls needed for a buffet, do not assume that placing one labelled plate at the end of the table solves the problem. Change the service plan or request a separately prepared and packaged arrangement that the restaurant can actually confirm.

Build the dietary brief without double-counting guests

Start with the total headcount, then identify the affected meals within that number. For each person, record the name or discreet identifier used by the workplace, the relevant allergy information, the required meal format, and any additional dietary requirements.

One person may be both vegan and allergic to tree nuts, for example. Keep those requirements in one combined meal record so the guest is counted once and the kitchen receives one consistent instruction. Special meals are part of the total allocation, not extra meals added after the headcount is finalized.

Your brief should also include:

• Total guests and the number of meals requiring specific confirmation.

• Peanut, tree-nut, or other allergen details supplied through the workplace’s established process.

• Menu, substitutions, packaging, and labelling requirements.

• Delivery date, arrival window, building entrance, room, and access restrictions.

• Name of the receiver and the person responsible for setup and distribution.

• What to do if a meal is missing, unsealed, incorrectly labelled, or different from the confirmed order.

Receiving and distributing protected meals at the office

Safety planning continues after the food leaves the kitchen. Assign one receiver who knows which meals require protection and can compare the delivery with the written order.

• Receive the order: Confirm the delivery location, meal count, and named contact before unpacking food.

• Inspect protected meals: Check labels, names or identifiers, seals, containers, and visible condition. Do not serve a meal that does not match the confirmed arrangement.

• Separate immediately: Place protected meals away from the shared buffet and general unpacking area. Keep them in their original packaging until handoff.

• Control the setup: Use the planned serving utensils and keep utensils from moving between dishes. Do not let guests rearrange labelled meals or trays.

• Brief the team: Tell the setup and event leads which meals are protected, where they are located, and who handles questions.

• Escalate discrepancies: If a seal is broken, a label is missing, a count is wrong, or the delivered meal differs from the confirmation, pause distribution and contact the caterer and workplace contact.

Keep the process discreet and respectful. Share only the information needed by the people responsible for ordering, receiving, setup, and the affected employee’s established support process.

How a managed catering workflow can support the process

For a Toronto or GTA workplace, a managed catering workflow can keep the menu, dietary notes, delivery details, payment, and invoicing connected. LunchLink coordinates one-time and recurring workplace meals through approved restaurant partners, but the partner selected for the order remains responsible for confirming the specific food and kitchen arrangement.

The practical workflow is straightforward: disclose the requirements early, shortlist a suitable menu, ask the selected restaurant to confirm ingredients, substitutions, kitchen practices, and cross-contact risk, then document the agreed packaging and handoff plan. This is a coordination process, not a promise that every meal is allergen-free or zero-risk.

What to do when the caterer cannot confirm the controls

Treat uncertainty as a decision point. Do not infer that a meal is suitable because no nuts appear in its name, because a menu says “healthy,” or because a label does not mention an allergen.

Ask whether the restaurant can provide a different menu, separately prepared and packaged meal, or another arrangement with clearly stated limitations. If the required information still cannot be confirmed, pause the order and involve the affected employee’s established workplace contact in deciding what option is acceptable. A different caterer may be needed if the current provider cannot answer the questions relevant to the request.

Frequently asked questions

Does “nut-free” mean no peanuts or tree nuts, or controlled cross-contact too?

It can mean either or both, which is why the requirement must be clarified. Ask whether the concern is intentional ingredients, cross-contact during preparation and service, or a particular combination of controls. Canadian guidance notes that preventive measures are needed throughout food preparation, and that precautionary statements do not replace those measures.

Are individually packaged office meals safer than a buffet?

They may reduce some service and identification risks, especially when meals are sealed, clearly labelled, kept separate, and distributed to named recipients. They are not automatically safe because preparation and kitchen practices still need to be confirmed by the selected restaurant.

What should an office ask about shared equipment?

Ask whether the proposed meal uses equipment, utensils, surfaces, fryers, trays, or storage areas shared with foods containing peanuts or tree nuts. Also ask what preventive practices are used and what cross-contact limitations remain. Request an answer tied to the specific menu and order date.

What should we do if the caterer cannot confirm the controls?

Do not guess. Pause the order, ask whether a different menu or separately packaged arrangement can be confirmed, and involve the affected employee’s established workplace contact. If the relevant information remains unavailable, choose an option with a process the caterer can explain and document.

How should overlapping dietary requirements be counted?

Count each person once within the total headcount and record all their requirements in one combined meal record. For example, a guest with a tree-nut allergy and a vegan requirement needs one meal with both specifications, not two separate meals unless the workplace has explicitly requested an additional serving.

Conclusion: make the requirement specific before you order

Safer nut-aware office catering starts with a precise brief, not a menu label. Clarify whether the requirement concerns peanuts, tree nuts, intentional ingredients, cross-contact controls, packaging, or all of these. Then obtain specific confirmation from the restaurant preparing the meal, choose a service format that supports the agreed controls, and keep each affected guest accurately recorded within the total headcount.

For the office, the final safeguard is a controlled handoff: inspect labels and seals, keep protected meals separate, brief the setup team, and stop service when the delivery does not match the confirmation. Toronto and GTA workplaces can ask LunchLink to coordinate a corporate catering plan with complete allergy information, while the selected restaurant partner confirms the specific ingredients, preparation practices, cross-contact limitations, and delivery arrangement.

Optional, privacy-first analytics

LunchLink can use Google Tag Manager and a short allowlist of conversion events to understand public-page and request-path performance. Analytics and advertising storage stay denied until you choose otherwise. Advertising measurement can connect an accepted request to its campaign and build consented audiences; form answers are never placed in the data layer. Essential features work either way. Read the website privacy notice.

No analytics choice has been saved.