Restaurant Incident Report Template: How to Document What Happened (and Protect Your Business)

When something goes wrong in a restaurant — a guest gets sick, an employee gets hurt, a piece of equipment fails spectacularly — the first instinct is to deal with it. Fix the problem, help the person, get service back on track.

That instinct is right. Handle the situation first.

But after it's handled, you need to document exactly what happened. Not because you enjoy paperwork, but because incidents that aren't documented become he-said-she-said situations, insurance complications, and liability exposure.

An incident report is your objective record of what occurred, when, who was involved, what was done about it, and what needs to follow up. It protects your team, your business, and — in the case of customer incidents — your guests.

When to File an Incident Report

Not every bad moment during service requires a formal report. A guest sending food back because it wasn't what they expected is normal restaurant operations. But certain categories of incidents should always be documented.

Customer injuries. A guest slips on a wet floor. Someone has an allergic reaction. A child is burned by a hot plate. Any incident where a guest is physically harmed — no matter how minor it seems — gets documented.

Employee injuries. Burns, cuts, slips, falls, repetitive strain complaints. Anything that could result in a workers' compensation claim or an OSHA inquiry should be documented immediately.

Foodborne illness complaints. A guest calls back saying they got sick after eating at your restaurant. Whether or not your food was the actual cause, document the complaint with every detail you can gather.

Significant customer complaints. Not the routine "my steak was overcooked" feedback — the kind of complaint that might lead to a negative review, a demand for compensation, or potential legal action. A guest who discovers an allergen in their food after being told it was allergen-free. A guest who finds a foreign object in their meal.

Property damage. A guest's clothing or belongings damaged by a spill. Damage to the building or equipment from an accident.

Safety and security incidents. Theft, altercation between guests, harassment, threats. Anything involving law enforcement or that might require law enforcement involvement later.

Equipment failures with operational impact. A cooler failure that resulted in food disposal. A fire suppression system discharge. Anything that disrupted operations significantly or had food safety implications. These may also be logged as equipment issues for ongoing tracking.

What to Include in an Incident Report

Capture the facts. Not opinions, not assumptions, not blame — facts. You're creating a record that might be reviewed by insurance adjusters, attorneys, health departments, or OSHA inspectors. Accuracy and objectivity matter.

Basic Information

Date and time of the incident. Be as specific as possible — "approximately 7:45 PM" is better than "during dinner service."

Location within the restaurant. "Kitchen, near the fryer station." "Dining room, table 14." "Parking lot, near the rear entrance."

Manager on duty who handled the incident and completed the report.

What Happened

A clear, factual description of the incident. What occurred, in what sequence. Describe what you observed or what was reported to you. Avoid interpretation.

Good: "Guest at table 8 reported difficulty breathing approximately 10 minutes after receiving their entree. Guest stated they have a tree nut allergy and had informed the server. Manager checked the dish with the kitchen and confirmed it contained walnut oil, which was not noted on the menu."

Not good: "Guest had an allergic reaction because the kitchen messed up."

Who Was Involved

Names and roles of all people involved: the guest(s), the employee(s), and any witnesses. For guests, note the name and contact information if voluntarily provided. For employees, note their full name and position.

If emergency services were called, note the time of the call, which agency responded, and the names or badge numbers of any responding personnel.

Injuries or Damages

Describe any physical injuries or property damage. Be specific and factual. "Guest reported swelling in lips and throat" — not "guest had a severe allergic reaction." Let medical professionals make medical assessments.

If photos were taken, note that. If an ambulance was called, note the time and the hospital the guest was transported to if known.

Actions Taken

What did the manager and team do in response? Step by step.

"Server was alerted. Manager visited the table immediately. First aid kit was retrieved. 911 was called at 7:52 PM. Guest's companion administered the guest's personal EpiPen. Paramedics arrived at 8:01 PM. Guest was transported to the hospital. Manager provided contact information to the guest's companion."

Include any compensation provided: comped meals, gift cards, refunds. Note whether the guest was satisfied with the response.

Follow-Up Required

What needs to happen next? Follow-up phone call to the guest. Insurance notification. Review of allergen communication procedures. Equipment repair. Staff retraining.

Assign each follow-up item to a specific person with a target completion date. This becomes the action plan, and it should be tracked until everything is resolved.

How Incident Reports Protect Your Business

Documentation matters in three specific scenarios.

Insurance claims. If a guest or employee files a claim, your insurance company will ask for your documentation of the incident. A contemporaneous written report — completed the day of the incident — is far more credible than a verbal recollection weeks later.

Legal proceedings. If an incident leads to a lawsuit, your incident report becomes a key piece of evidence. The report's objectivity, specificity, and timeliness all affect its value. A report written the same day carries more weight than one reconstructed from memory later.

Operational improvement. Incident reports reveal patterns. If you're logging guest allergic reactions, you might discover that the same dish is involved repeatedly — pointing to a menu labeling problem or a kitchen communication failure. If employee injuries cluster around a specific station, you might identify a safety hazard that can be corrected.

Common Mistakes in Incident Reporting

Waiting too long. Complete the report the same day — ideally within an hour of the incident. Details fade and perspectives shift with time.

Including opinions or blame. "The server should have checked the allergen list" is an opinion. "The server did not verify the allergen information with the kitchen" is a factual observation. Keep the report objective.

Being vague. "Guest complained about food" tells you nothing useful. "Guest at table 14 reported finding a small piece of glass in their Caesar salad at approximately 8:20 PM" is actionable information.

Not getting contact information. If a guest is involved in an incident, politely ask for their contact information for follow-up.

Not following up. An incident report without follow-up is just a record of a failure. The value is in the corrective actions that prevent recurrence.

Connecting Incidents to Shift Handoffs

Every incident that occurs during a shift should be summarized in the manager log so the incoming shift has context. The full incident report is a separate, more detailed document — but the log ensures the next manager knows something happened and can access the full report if needed.

For incidents that require multi-day follow-up (insurance claims, guest callbacks, staff retraining), add them to your issue tracking system so they stay visible until resolved.

For incidents related to a health inspection failure, our guide on [what to do after a failed health inspection