How do you handle a food poisoning report after an event?

Your event finished yesterday. This morning, a ticket buyer emails to say they were sick overnight and thinks the lunch was responsible. They want to know what you're going to do about it. The caterer says nobody else has complained. Your team is already packing the event files away.

The first thing you want to do is take the report seriously and get the right people involved. Help the attendee find appropriate medical advice, record their account without diagnosing it, preserve the relevant event and catering records, and promptly contact the food safety or public health authority responsible for the location. Coordinate with the caterer, but don't make their agreement a condition of seeking advice.

You don't have to decide whether the event caused the illness before doing those things. Equally, taking action doesn't mean telling everyone that your caterer poisoned them. You can acknowledge someone's experience, explain what you're doing and be honest about what remains unknown.

This guide explains how to handle an event food poisoning complaint after people have gone home. We'll work through the first reply, the records to keep, the conversations with your supplier and the decisions about contacting other attendees. There's also a reusable complaint record and a fictional example showing how the response develops as more information arrives.

Start with the person who contacted you

Check first whether the person needs urgent medical help. You can address their customer service complaint once that is underway. Someone saying they feel unwell is different from someone saying they cannot keep fluids down or have become seriously ill. If the person describes an emergency, direct them to local emergency services immediately. Don't leave an urgent message waiting for the account manager who booked the caterer.

For other illness reports, encourage the person to contact an appropriate healthcare professional or local medical advice service. Your team can explain the reporting process and help identify where the event took place. They shouldn't recommend medication, diagnose a pathogen or decide that the symptoms are too mild to matter.

The US Centers for Disease Control and Prevention's food poisoning symptoms guidance identifies warning signs such as bloody diarrhea, frequent vomiting that prevents keeping liquids down and dehydration as reasons to seek medical attention. Use current local medical advice for the person concerned. An organizer's reply should help someone reach care, rather than turn a support agent into a medical assessor.

You can be warm without claiming to know what happened. "I'm sorry you've been unwell, and thank you for telling us" acknowledges the experience. "We're sorry our chicken made you ill" makes a claim you may not be able to support. At the other extreme, "We have no evidence you got sick here" is a defensive opening when someone has just asked for help.

Give the person a named contact and explain the next step. If another colleague will handle the report, transfer the original message internally through the approved restricted route. Don't ask an unwell person to repeat their story across ticket support, venue reception and the caterer's general inbox because nobody has taken responsibility.

There may be a refund request in the same message. Acknowledge it and explain who will review it, but keep the welfare response moving. Someone shouldn't have to settle a financial complaint before you pass a food safety concern to the right authority. The two decisions can proceed together with different owners.

Record an account, not a diagnosis

Start with what the person actually reports. Which event did they attend? When did they eat there? What do they remember eating or drinking, and when did they first feel unwell? Mark approximate times as approximate. A precise timestamp invented by a helpful support agent is worse than an honest gap.

Ask short, neutral questions. "Which foods do you remember eating at the event?" leaves room for the person's account. "Was it the chicken from the buffet?" suggests a conclusion and may influence what they tell you. If they name a particular dish themselves, preserve that detail as their recollection, including any uncertainty.

Timing matters, but it doesn't let you identify the cause. CDC's advice for people who think they have food poisoning explains that the last food eaten may not be responsible and encourages people to note their recent food and activities, retain receipts and report illness to their health department. You can direct attendees to that guidance without collecting their entire medical or dietary history yourself.

Keep three things distinct in the record. The attendee's account is what they told you. Your event records establish things such as which supplier served lunch and when service opened. A finding about the cause needs the relevant investigation. When those categories get merged, a draft support note can become an unsupported public claim.

Suppose the person says, "I had the chicken and some salad, but I don't remember which counter." Record that account. Don't replace it with "Chicken buffet case" as the subject of a message forwarded to the whole team. That wording would imply both a particular exposure and a confirmed classification.

If someone reports that friends were also ill, note that it is a report about other people. Invite those people to use the appropriate direct reporting route, where practical, rather than creating detailed health records about them from secondhand messages. Don't count a screenshot, its forwarded copy and a later email from the same person as separate individuals.

Use your event incident report template to connect this complaint to the wider operational record. Keep sensitive personal information separately, with a reference that authorized colleagues can follow. Most of the event team needs to know who is managing the response and what actions are required. They don't need the attendee's symptoms in the general group chat.

Contact the appropriate authority promptly

Don't wait for a second complaint, a laboratory result or permission from the caterer before asking the relevant authority how to proceed. You are reporting a concern and seeking advice. Explain what is known, what is uncertain and whether any related food service is continuing. The authority can tell you what information it needs and how the report should be handled locally.

The route depends on where the event happened. In the UK, the government's local food safety team finder directs food hygiene and suspected food poisoning concerns to the local council. Give the event address and identify any offsite preparation location you know about. If another authority needs to be involved, ask who will arrange the referral and record the answer.

In the US, the CDC guidance above directs people reporting suspected foodborne illness to their local or state health department. For Australia, Food Standards Australia New Zealand explains that food complaint investigations are handled by state or territory authorities or local councils. Don't assume that contacting a national agency is the same as reaching the team responsible for your event location.

Prepare a concise account for the call. Include the event name, site address, date, food service details, the nature of the report and whether further dates or deliveries are planned. Identify yourself as the organizer and explain which business prepared or supplied the food. Say when information comes from an attendee rather than your own observation.

Ask for a reference number, the contact's name or team, the information they require and any immediate instructions. Read back instructions that affect service, communication or evidence. If you cannot reach the normal contact, use the published urgent or out-of-hours route appropriate to the concern. Record attempts and keep trying through the correct channels; a voicemail doesn't establish that the issue has been assessed.

Reporting roles can overlap. The attendee may contact a health department directly, the caterer may notify its regulator, and you may seek advice about the event. Tell the authority about known reports so it can connect them. Don't tell the attendee that only the organizer is allowed to report, or assume the caterer's call has discharged every obligation your own business might have.

Ask your adviser to clarify any reporting duties that apply to your actual role. An organizer selling a catered package, a venue running its own kitchen and an organizer hosting independent traders may have different responsibilities. Put the facts to the authority rather than selecting the description that seems most convenient commercially.

Bring the caterer in and check what is still happening

Contact the caterer's named operational lead with the relevant facts. Make clear that the cause is unconfirmed and that you need their food safety response, records and authority contact. Send a written account after an urgent call so the request doesn't depend on somebody remembering what was said between bookings.

Ask whether the same food, ingredients, preparation batch or service arrangements could still affect anyone. Yesterday's leftovers may be under the supplier's control. A second conference may be starting in the same venue. A vendor may have taken remaining stock to another site. Don't assume the concern ended when your ticket holders left.

When a concern could involve continuing service, escalate it immediately to the responsible food business and authority and arrange appropriate protective action. Your team shouldn't improvise the technical scope of a withdrawal or authorize food to be served because cancelling lunch would be expensive. Equally, an instruction to hold a particular product shouldn't be casually translated into a claim that every vendor at the event is implicated.

The Food Standards Agency's food incident, withdrawal and recall guidance, which applies to England, Northern Ireland and Wales, explains the actions food businesses should take when they believe supplied food is unsafe, including withdrawal or recall and notification of the competent authority. Establish who is taking those actions where relevant. Scotland and other countries have their own routes.

Keep requests practical. Ask the caterer to identify the responsible person, confirm receipt of the concern, preserve the records and items relevant to it, and explain what has been reported. Ask for confirmation of completed actions. "The chef knows" doesn't tell you whether anybody checked remaining stock or contacted the right office.

If the caterer disagrees that its food could be involved, record that position without turning the conversation into an argument about blame. It can provide its account and evidence to investigators. Your attendee response and authority contact should continue. Good cooperation means preserving useful information and acting on competent advice, even when the businesses have different views about the cause.

If the supplier's contact doesn't answer, use the agreed deputy or management contact and continue trying. Tell the authority what you have been unable to establish, especially if related service may still be happening. Record an unanswered request as unanswered. Don't let a supplier's absence become an accidental decision that no action is needed.

For future bookings, include a usable incident contact and cooperation process in your event catering contract. A contract clause is useful when it helps you reach someone and obtain records. It won't substitute for making the call when a report arrives.

Preserve the records before they disappear

The first request to your own team should be specific enough to act on. Preserve the original complaint, the event's food service information and the relevant communications. Tell the people holding those records what to retain and who will coordinate access. A general message saying "keep everything" often leaves important material scattered across personal phones.

Your event file may include the final menu, approved substitutions, supplier and venue details, service locations, opening times, delivery arrangements and the names of the people responsible. Keep the version used at the event. A revised menu downloaded today may no longer show what was offered yesterday.

Ask the food business to preserve its relevant preparation, delivery, storage and service records through its procedures and the authority's instructions. The exact material will depend on what happened. Request original records, with any later explanation clearly dated. Don't ask someone to recreate missing temperature readings or complete an unsigned checklist as though it had been completed during service.

Preserve relevant packaging, labels and remaining food under the food business's safe arrangements and authority advice. Don't taste food to see whether it's fine, pass samples around the office or transport material in an ordinary bag to be helpful. Ask how items should be stored, identified and handed over. Record who has them and any transfer or disposal instructions.

There is a distinction between preserving an item and keeping it available for service. Make sure the responsible business has separated anything held for investigation from food that could be sold or distributed. Your event's leftover donation plan should not carry on by default when the relevant food is under review.

Ticket and meal records also need careful interpretation. A lunch-inclusive ticket establishes an entitlement. A meal voucher scan may establish a redemption. Neither necessarily proves which dish a person ate, and a general admission scan proves even less about food. Explain the limits when supplying records, rather than presenting a clean export as a complete list of everyone exposed.

Record missing information openly. If there was no dish-level record, say so. If a supplier has already disposed of leftovers under its usual procedure before hearing about the complaint, record when it says that happened. You can still preserve labels, documents and accounts. Altering the history to make the event appear better documented would damage the investigation and your own review.

Collect only the personal information you need

A food poisoning complaint may contain health information, contact details and information about other attendees. Decide who needs access before copying it into the tools your whole team uses. You want a useful response record without creating an unrestricted file of people's illnesses.

For a UK event, the Information Commissioner's Office explains that health information receives extra protection as special category data, alongside a lawful basis under the UK GDPR. Its guidance is under review following legislative changes. Have the person responsible for privacy establish the current lawful arrangements, necessary safeguards and retention approach. Don't assume an attendee's willingness to email you makes every later use permissible.

In practice, the person answering the complaint usually needs a way to contact the attendee, the event involved and enough information to pass on the concern appropriately. Detailed medical history, test results and clinical assessments should normally go through healthcare professionals or the investigating authority. If an authority asks you to collect particular information, clarify the purpose, secure route and access before setting up a form.

Explain what you're doing in ordinary language. Tell people who is managing the report, how the relevant information may be shared and where to find your privacy information. A hidden sentence in an old ticket confirmation is a poor explanation when you are asking someone about an illness now.

Keep personal details out of the supplier-wide email chain. A caterer may need information through an appropriate route to cooperate with the investigation; that doesn't mean every subcontractor needs a copy of the original complaint. Confirm the recipient, purpose and secure method. Verify unexpected requests for bulk attendee data through a known authority contact before sending anything.

Protect the records without making them impossible for authorized people to use. Name a deputy, set appropriate access and make sure the response doesn't stop when the lead goes offline. Keep a record of what was shared, with whom, when and why. Avoid duplicating sensitive attachments in every handover.

Set a review date for retention with the relevant advisers. Investigation needs, legal claims and ordinary customer service records may have different requirements. Don't promise to delete everything immediately after replying, or keep everything indefinitely because there might someday be another question. Document the reason for keeping each type of record and review it when the situation changes.

Use a complaint record your team can maintain

You don't need a complicated system to begin, but you do need a consistent record. Adapt the fields below to your authority's requests and your privacy arrangements. Leave unknown information marked unknown. The record helps your team coordinate; it isn't a medical assessment or an official investigation form.

Report and event details

• Record reference and event name, date and full venue address.

• Date and time the report arrived, the channel used and the colleague who received it.

• Named response lead, deputy and restricted location of the original message.

• Attendee contact reference and preferred contact method, stored with appropriate access.

• Event attendance or booking reference where available, without making it a barrier to reporting.

Someone may attend on a group booking, use a transferred ticket or contact you through a companion. You can record and escalate a concern while checking the attendance details separately. A missing order number doesn't justify ignoring a health report.

What was reported

• The person's account in their own words or a faithful attributed summary.

• Food and drinks they recall, supplier or counter if known, and approximate service time.

• When they say symptoms began, with uncertainty preserved and only necessary details retained.

• Whether the report concerns them directly or includes secondhand information about others.

• Any welfare signposting provided and whether an urgent response was required.

Don't insert a diagnosis into these fields unless it is a relevant, clearly attributed clinical finding provided through an appropriate route. "Attendee says a doctor confirmed a diagnosis" and "We received an authority finding" are different statements. Preserve the source and avoid collecting documents you don't need.

Response and evidence

• Caterer and venue contacts, when contacted, their response and the person responsible for follow-up.

• Authority contacted, reference, time, instructions and any requested reporting route for attendees.

• Whether related food service or stock remains active, who is checking it and what action is confirmed.

• Relevant records or items, their holder, preservation request and confirmation received.

• Decisions about attendee communication, the approver and the exact version sent.

• Open questions, owner, next action and next promised update time.

An action should change status only when someone has confirmed it happened. "Asked supplier to preserve records" can become "Supplier confirmed records preserved" with the time and source. Those statements are not interchangeable. Keep the first entry and add the confirmation so the sequence remains understandable.

Financial follow-up and closure

• Refund or reimbursement request, amount if stated, reviewer and response due.

• Relevant insurer or broker notification and adviser instructions, where applicable.

• Approved response costs and unresolved commitments, kept separate from potential recoveries.

• Outstanding authority requests, individual replies and evidence or retention decisions.

• Closure decision, who made it, what remains open elsewhere and the review date.

Use a short operational handover drawn from this record. It might say that the authority has been contacted, the supplier is preserving records and the next update is due that afternoon. Keep health details in the restricted record. Your evening support colleague needs a reliable action list, not a forwarded stack of private conversations.

Reply clearly while the cause is unknown

The first reply should acknowledge the report, help the person reach appropriate care and explain what you are doing. It should also make clear what you need from them and when they can expect to hear from you. Don't promise a final answer by a deadline you don't control.

Here is wording to adapt after checking the medical signposting and local reporting route for your event. The promised update is a commitment about your communication, not an investigation deadline.

Example first reply

I'm sorry you've been unwell, and thank you for contacting us about Saturday's event. If you need urgent medical help, please contact local emergency services. For other medical concerns, please contact your healthcare professional or local medical advice service.

I'm Maya, and I'll coordinate our response. We have recorded your report, contacted the caterer and asked the local food safety team for advice. We do not yet know what caused the illness you describe.

Could you tell us which foods and drinks you remember having at the event, roughly when you had them and when you first felt unwell? Approximate information is fine. Please don't send detailed medical records to this inbox. The investigating team may ask you for information directly through its own process.

We'll update you by 4pm today, even if we are still waiting for further information. We have also recorded your refund request, which our customer service lead will review separately. You do not need to wait for our response before seeking medical advice or reporting your concern directly to the relevant authority.

Before you send it

Check every claimed action before sending. If you have only attempted to contact the authority, say that. If Maya isn't the lead, change the name and contact arrangement. Templates become misleading when staff copy the verbs without checking whether the work happened.

You may need to reply again before there is a finding. Say what has changed, what is still unknown and what you can do next. "We're still waiting for the authority's advice on attendee communication; I will contact you again tomorrow" is more useful than a vague reassurance that the matter is receiving attention. If a promised time becomes unrealistic, contact the person before it passes and reset it honestly.

Decide who else needs to hear from you

Ask the authority what further contact is needed and who should receive it. The answer may depend on the suspected exposure, the information already available and whether there is any continuing risk. Don't turn an organizer's desire to reassure everybody into an unrequested medical survey.

If wider contact is required, establish what your records can actually identify. You may know who held a lunch-inclusive ticket but not who collected food. The buyer of a group order may be your only contact for several attendees. Staff, performers, traders and suppliers may have eaten the same meal without holding public tickets at all. Explain those gaps so the communication plan can address them.

Write the message around the action recipients need to take. Identify the event and date, describe the concern in the agreed terms, provide the appropriate medical or reporting route and explain where confirmed updates will appear. Avoid naming an individual attendee, blaming a supplier or describing a diagnosis that hasn't been established.

Have the relevant specialists review health instructions and the authority-related wording. The event lead should check the event details, intended recipients and links. Give the support team the approved version and escalation contact so a careful email isn't contradicted by a casual reply on social media.

For an event-wide update, Loopyah's attendee email tools let you send event information to ticket holders and test the email before sending it. Use that capability for the approved message. Check its audience against the people you need to reach, and arrange additional contact for people outside those ticket records. The software can't establish who ate a particular meal.

Review the test on a phone. Can someone see the event name, understand what is known and reach the reporting route without hunting through promotional content? Remove next-event offers and unrelated sales messages. A health-related update should let the recipient deal with the issue they were contacted about.

If people post publicly, acknowledge the concern and direct personal reports to the appropriate private or official route. Don't ask them to publish symptoms or order details in the comments. You can explain that you are cooperating with the relevant team without debating an individual's experience in public. Correct a material error in your own statement promptly and retain the previous version in the response record.

When a journalist or sponsor asks for an answer

A public question can create pressure to speak more confidently than the evidence allows. Put one person in charge of coordinating the organization's factual response and make sure they can reach the event lead. They should confirm completed actions, protect personal details and check any proposed health advice with the relevant specialists.

If asked whether your event caused food poisoning, say what you actually know. You have received reports, you are cooperating with the appropriate authority and the cause has not yet been established, if those statements are accurate. Don't call the incident isolated because only one person has emailed, or say there is no risk because no further reports arrived overnight.

A sponsor may need an operational update about a future activation or meal service. Answer that specific question through the responsible team. It doesn't need a list of the complainants. Ask partners to refer further reports to the agreed contact so the information doesn't remain in a salesperson's inbox.

Keep a copy of each approved statement with its date and the facts checked at that time. If the position changes, update the relevant recipients. A statement that was accurate yesterday can become misleading when a new instruction or finding arrives. Your communication owner needs a handover as much as the colleague managing the complaint.

A worked example after a paid conference

Consider a fictional event, the Independent Retail Forum, held on a Saturday for 240 delegates. Lunch was included in the delegate ticket. The same caterer also supplied 20 crew meals. These invented details show how an organizer might coordinate a response; the timings and decisions are not official response standards or findings about a real event.

On Monday at 8:20am, an attendee emails to report illness and says they ate chicken and salad at lunch. Maya, the event lead, takes responsibility for the response. She checks the message for urgent welfare concerns, replies with appropriate medical signposting and asks neutral questions through the restricted complaint process. She records the food account as the attendee's recollection.

At 8:35am, Maya contacts the caterer's operational lead and the venue manager. She asks them to preserve relevant records and establish whether any related stock or service could still affect people. She also contacts the local food safety team for advice, stating the event address, service date and current information. She records the contact and follows its instructions. This example doesn't prescribe how that authority would investigate.

The caterer says its planned service for another client uses separately prepared food. Maya records that as the caterer's statement and passes relevant information through the agreed route. She doesn't turn it into "all other food is safe" in an attendee email. Any continuing concern goes to the responsible food business and authority for assessment.

At 9:10am, another attendee writes about being unwell. Their message includes a forwarded screenshot of the first attendee's social post. Maya opens a separate account for the second person's own report and links the screenshot as supporting material. She now has two direct illness reports from attendees. The screenshot adds no further person to that count.

The second person doesn't remember eating chicken. That detail stays in the record. Maya resists the temptation to make both accounts match a theory the team has already discussed. The authority receives the relevant updates through its requested process and decides what further information is needed.

Checking the potential contact group

Maya checks the event records before discussing a wider message. There were 240 delegate lunch entitlements and 20 crew meal allocations. That gives 260 meal entitlements or allocations to reconcile. It doesn't establish that 260 people ate, that everyone ate the same food or that any particular number became ill.

The delegate bookings contain 214 contact addresses because some buyers booked for groups. Maya flags that limitation. An email to those addresses cannot be described as confirmed direct contact with all 240 delegates. She checks how group attendees can be reached and obtains the crew contact route from the production manager, following the agreed privacy arrangements.

At noon, the response record contains the original reports, the authority contact, the caterer's preservation confirmation, the final menu and the known limits of the attendee data. The cause remains unknown. Maya's 4pm update to the first attendee can explain those completed actions without pretending that a conclusion has arrived.

If the authority requests wider communication, Maya prepares it for the appropriate audience and gets the relevant wording checked. If it asks to contact attendees directly, she follows the agreed data-sharing route. She doesn't send her own survey first because she wants to be seen doing something. The next action follows the actual advice received.

Keep financial decisions separate from findings

Your event business needs to track refunds, supplier discussions and response costs. It also needs to avoid treating those decisions as conclusions about the cause. Refunding a ticket doesn't establish which food made someone ill. Refusing a discretionary payment doesn't settle the safety concern or remove the need to cooperate.

Review the attendee's actual request and the applicable terms, consumer rights and advice. A refund for an undelivered meal, a goodwill payment and a claim for injury or other loss are different matters. Don't require a release of claims or withdrawal of a report as a condition of receiving the information or assistance needed for the safety response.

If a claim or incident may trigger insurance notification, contact your broker or insurer under the policy's actual requirements. Ask what notices and records are needed. Don't promise that the caterer's insurance will pay, that your own cover applies or that an attendee has to deal with somebody else's insurer before you can acknowledge their complaint.

Track approved costs as they arise. Staff time, communication costs, external advice, replacement service and customer payments may belong in different categories. Keep possible supplier credits and insurance recoveries separate until confirmed. A hoped-for reimbursement won't fund a payment due today.

In the fictional conference example, suppose the organizer approves $480 in additional support wages and $720 for external response assistance. It also approves 12 goodwill payments of $25, costing $300. All amounts are invented USD figures, not market rates or suggested compensation. The selected additional costs total $1,500 before other items, taxes or claims.

If the organizer had set aside $4,000 in available response funds after existing event commitments, those selected costs would leave $2,500. That amount isn't a forecast of the incident's final cost or permission to limit required action. Claims, further advice and other obligations may still be unresolved. Keep those open items visible when deciding how much cash the business needs.

A caterer's proposed credit should have its own record showing the amount, terms and whether it has been agreed or paid. Don't subtract an unconfirmed proposal from the costs already incurred. Obtain appropriate advice before accepting settlement wording, and keep the authority response independent of the commercial negotiation.

Close the response with evidence of completed actions

The event being over doesn't mean the report is closed. Before handing it back to ordinary customer service, check who still expects a reply, which authority requests remain outstanding and who holds the relevant records. Assign a named owner to each unresolved action and make sure they accept it.

Your closing account should distinguish what was established from what remains unknown. If an authority provides findings, describe them accurately and respect any limits on disclosure. If no cause is established, say that. Don't rewrite the original complaint as "unfounded" simply because there wasn't enough information to reach a conclusion.

Review how your response worked even when the cause remains uncertain. Could the attendee reach a person? Did the caterer answer the emergency contact? Were final menus and substitutions available? Did the group booking records reveal a contact gap? You can fix those weaknesses without inventing an explanation for the illness.

Update the event's food safety arrangements where the review identifies a necessary change. That might mean a better incident contact, a clearer preservation request or a tested way to reach crew after the show. Give each change an owner and check that it has been made before the next catered date.

Before your next event, ask the person covering the support inbox what they would do with an illness report arriving on the following morning. Have them find the event lead, caterer contact, local reporting route and restricted record without relying on the founder's phone. If one of those is missing, fix it while the event is still being planned.