Somewhere in your organization is a colleague who will quietly eat nothing at the next office lunch rather than ask whether the dressing contains sesame. Multiply that by every dietary need on a typical Toronto team — food allergies, celiac disease, halal, kosher, vegetarian, vegan, low-sodium, pregnancy-related restrictions — and you have the difference between an event that feels genuinely generous and one that leaves people nibbling crackers in the corner.
Handling dietary needs well is not about ordering more dishes. It is about gathering better information, designing a menu with clear guardrails, and running the day so the plan actually holds. What follows is a practical, field-tested checklist for office managers, HR teams, event planners and anyone hosting in Toronto and the Greater Toronto Area — from a boardroom lunch in North York to a full all-hands in Vaughan or Mississauga.
Start With the Guest List, Not the Menu
The single most useful tool you have is one well-worded question on the registration form: “Do you have any dietary requirements or allergies we should know about?” followed by a free-text field. Checkboxes only capture the categories you already thought of, and the category you forgot is usually the one that matters. Open text lets someone tell you about a sesame allergy, a medically supervised low-sodium diet, or a child with a nut allergy who will be attending the family-friendly summer social.
Once responses come in, sort them into tiers rather than one long list. Medical allergies always take precedence, because they carry real risk. Next come medically required diets, such as celiac disease or diabetes management. Then religious and cultural requirements, such as halal, kosher, or vegetarian observances. Finally, preferences — keto, pescatarian, “I just don’t eat mushrooms.” Everyone should be fed comfortably, but the tiers help you decide where to spend your attention and budget when trade-offs appear.
Timing matters as much as the question itself. Ask when the invitation goes out, send a gentle reminder about seven to ten business days before the event, and lock your final numbers with your food provider roughly 72 hours ahead so there is time to adjust. For recurring gatherings — the monthly team lunch, the quarterly all-hands, the annual holiday party — keep a short internal dietary register so people do not have to re-declare a serious allergy every four weeks. Ask permission before you keep it, and update it at least once a year.
Handle the responses with care. Route replies to a single coordinator rather than a shared spreadsheet the whole office can browse, and do not print allergy details on a visible seating chart. If someone discloses a serious allergy, a short private conversation is worth more than a form: ask what “safe” means for them, whether cross-contact is a concern, and whether they would rather bring their own meal. Some people will say yes, and that is not a failure of hospitality — it is respect for their judgment.
Build the Menu Around Your Hardest Requirement
The instinct at most offices is to order the crowd-pleaser menu and then bolt on a sad vegetarian option at the end. Flip that. Start with a base that is naturally inclusive — rice or grain bowls with grilled protein, roasted vegetables, lentil or bean dishes, fresh salads with dressings on the side, a fruit platter — and then add the dishes that narrow the field. Menus built this way tend to need fewer special plates, travel better, and taste better for everyone.
Where a specific requirement cannot be met by the main spread, order a small number of individually plated or sealed portions and label them with the guest’s name or a discreet number. This matters most at buffets, where a serving spoon can travel from a shrimp platter to the rice in seconds. Position allergen-free dishes at the start of the line with their own utensils, keep them physically separated from shared items, and resist the urge to stack platters to save table space. If a guest has a severe allergy to a top allergen, consider serving their meal directly rather than having them negotiate a buffet at all.
Label everything, and label it honestly. A tent card listing the actual ingredients of a dish is far more useful than a symbol system nobody can decode. For anything containing a major allergen, say so plainly and in words. Sauces, dressings, and garnishes deserve their own labels because they are the least visible and most frequently forgotten source of nuts, sesame, dairy, and shellfish.
Religious requirements deserve the same precision. Halal and kosher are not interchangeable with “vegetarian,” and a vegetarian dish can still contain fish sauce, gelatin, or animal rennet. When a guest keeps halal or kosher, source certified items in sealed packaging and keep them clearly separated from the rest of the spread. Working with a Corporate event catering provider that already runs an allergy protocol as standard practice can remove a great deal of guesswork, especially when headcounts shift late. Finally, make the plant-based option a real meal — a protein-forward main with texture and flavour — rather than a side salad promoted to entrée status.
Logistics: The Half of the Checklist That Gets Forgotten
A perfect menu collapses without a delivery plan. In Toronto and the surrounding GTA, build in buffer time for downtown traffic, loading-dock restrictions, freight elevator bookings, and security sign-in for outside vendors. A truck that arrives fifteen minutes late in the core can push a lunch back forty. Confirm in writing who receives the delivery, where they should go, and what happens if the contact steps into a meeting.
Assign one point person for the event — someone who knows the dietary list, has the vendor’s phone number, and can make a decision without a committee. Brief the serving team before guests arrive: where the labelled special meals are stored, which platters contain which allergens, and who to speak to if a guest has a question. If your team is self-serving, tape a simple note to the table identifying the allergy-aware zone.
Think about temperature and timing too. Cold items should stay cold until the last practical moment, and hot food should not sit out for the length of a two-hour presentation. If your agenda includes speeches before the meal, either serve after the talking or choose formats that hold up — boxed lunches, individually wrapped portions, and bowl-style service all survive a delayed start better than a composed hot buffet.
A Scenario Worth Planning Around
Picture a quarterly all-hands for eighty people in a Vaughan office with an open-concept lunchroom and one small kitchen. The invitation includes a dietary question; forty-two people respond, six report allergies, four keep halal, eleven are vegetarian, and two are vegan. The coordinator builds a register, flags the allergy cases for a short phone call, and orders a main spread that is dairy-free and nut-free by design, with sealed halal meals, two named gluten-free plates, and a lentil-and-roasted-vegetable main that happens to satisfy the vegan guests too. On the day, allergen-free items sit on a separate table near the kitchen, labelled by name, and the coordinator keeps the vendor’s number handy until the last plate is cleared.
Nothing about that scenario is unusual or expensive. It is simply the result of asking early, sorting carefully, and telling the truth on a label.
The Day-Before and Day-Of Checklist
Confirm headcount and dietary list in writing with your provider, including the names attached to any special meals and the exact nature of each allergy.
Print and place labels the day before if possible, and check spelling against the register so nobody’s meal is announced incorrectly.
Reserve a separate surface for allergen-free and religious-observance meals, with dedicated tongs, spoons, and a clear card explaining what the zone is for.
Brief your team on where special meals live, who is the point person, and how to answer the question “is this gluten-free?” with something better than a shrug.
Plan for leftovers honestly — decide in advance what gets refrigerated within two hours, what gets discarded, and who is responsible.
Close the loop afterwards by noting what worked in your event file, updating the dietary register with permission, and thanking the guests who flagged requirements early. The next office event will be easier because of it.
Lagos-born, Berlin-educated electrical engineer who blogs about AI fairness, Bundesliga tactics, and jollof-rice chemistry with the same infectious enthusiasm. Felix moonlights as a spoken-word performer and volunteers at a local makerspace teaching kids to solder recycled electronics into art.