---
title: "Restaurant Incident Report"
description: "How to write a restaurant incident report the same shift: injuries, guest conflicts, alcohol service, cash, theft, and food safety — plus what evidence to preserve before footage overwrites."
url: https://www.docu-coach.com/restaurant-incident-report
markdown: https://www.docu-coach.com/restaurant-incident-report.md
datePublished: 2026-09-12
dateModified: 2026-09-12
pageType: guide
---

# Restaurant Incident Report

> How to write a restaurant incident report the same shift: injuries, guest conflicts, alcohol service, cash, theft, and food safety — plus what evidence to preserve before footage overwrites.

## Key takeaways

- A restaurant incident report is the dated, factual record of something that happened in your venue: an injury, a guest conflict, an alcohol service problem, a cash discrepancy, a theft, a food safety failure, or an altercation.
- A write-up applies a consequence to an employee.
- Often you file only the report — a guest slipping near the host stand involves no employee discipline at all.
- Generate one now with the incident report generator.
- Camera systems in most venues overwrite on a rolling window — often seven to thirty days, sometimes less on a busy multi-camera setup.
- By the time an attorney's letter or a claim notice arrives, the footage that would have settled it is gone.

Same-shift facts, the evidence that disappears in days, and the notifications you have to be able to prove you made.

## What belongs in a restaurant incident report

**A restaurant incident report is the dated, factual record of something that happened in your venue: an injury, a guest conflict, an alcohol service problem, a cash discrepancy, a theft, a food safety failure, or an altercation.** It answers who was involved, when, where in the building, what was observed, what you did immediately, who you notified, and what evidence exists.

It is not a write-up. A write-up applies a consequence to an employee. An incident report records the event. Sometimes you file both. Often you file only the report — a guest slipping near the host stand involves no employee discipline at all.

Generate one now with the [incident report generator](/tools/restaurant-incident-report-generator).

## Preserve the evidence today, not tomorrow

This is the part restaurants lose. Camera systems in most venues overwrite on a rolling window — often seven to thirty days, sometimes less on a busy multi-camera setup. By the time an attorney's letter or a claim notice arrives, the footage that would have settled it is gone.

The same shift:

- **Export or flag the camera clip** with a few minutes on either side of the incident, and note in the report where it is stored.
- **Save the POS record** — ticket, check number, void, comp, or drawer report.
- **Pull the labor export** showing who was scheduled and clocked in.
- **Photograph the scene** if the condition mattered: the floor, the mat, the equipment, the broken glass, the burn on the fryer station.
- **Take written statements** from witnesses before they compare notes, one person at a time, on a [witness statement form](/restaurant-witness-statement-form).
- **Write down the guest's contact information** if they gave it, and what they said, in their words.

Then write in the report which of these you have. "Camera footage preserved and exported to the office drive 3/8 11:40 p.m." is a sentence that pays for itself.

## By incident type

Different incidents need different facts. These are the ones a restaurant actually generates.

**Employee injury** — burn, cut, slip, strain. Time, station, what they were doing, what they said happened, whether they declined care, whether EMS was called, who took over the station, and the immediate corrective action. Follow your workers' compensation process; the report is not a substitute for it.

**Guest injury** — location, condition of the area, what the guest reported, what you observed, whether they declined care, witnesses, and whether the area was corrected or closed. Do not speculate on cause and do not admit fault in the narrative; record what was observed.

**Guest conflict or ejection** — table or seat, time, what was said by whom, whether alcohol was involved, whether service was refused, who was on the floor, whether police were called, and how the guest left.

**Alcohol service** — the guest, the observable indicators, how many drinks were rung and over what period per the POS, whether service was refused or continued, who made the call, and the time. Liquor boards ask about specifics.

**Cash or void discrepancy** — register, shift, amount, the report cited by name, who had the drawer, and what the employee said when asked.

**Theft or loss** — what is missing, when it was last verified, who had access, camera status, whether police were called, and what has been secured since.

**Harassment or hostile conduct complaint** — take it as a complaint, not a conclusion. Record what was reported, in the reporter's words, the date and time you received it, and what you did next. Then move to a restricted file: [restaurant workplace investigations](/restaurant-workplace-investigations) and [how to document harassment complaints](/how-to-document-harassment-complaints). Do not put an open investigation in the general employee record.

**Food safety** — the reading or observation, product affected, whether it was discarded, log entry, retraining delivered and by whom. When the miss is an employee's and a standard was already acknowledged, the same shift also produces a [food safety violation write-up](/restaurant-food-safety-write-up).

**Fight or altercation** — separate first, document second. Who, where, what was said before it turned physical, injuries, whether police attended, and each participant's account taken separately.

## Structure that survives review

Write in this order. It reads correctly to anyone, and it stops you from leading with a conclusion.

1. **Identifiers** — date, clock time, location within the venue, MOD, report author.
2. **People** — everyone involved, with roles: employee, guest, vendor, witness, bystander.
3. **Narrative** — what happened, in sequence, in observable terms. Quote what you can. No adjectives about character.
4. **Immediate action** — what you did in the first few minutes: closed the area, sent someone home, called EMS, comped the check, refused service, secured the drawer.
5. **Impact** — guest, service, product, property. Numbers where they exist.
6. **Notifications** — each person notified, method, and clock time.
7. **Evidence** — each item preserved and where it lives.
8. **Follow-up** — the owner of the next step and the date.

A narrative that starts "Server was being careless and a guest got hurt" has already lost. "At approximately 8:12 p.m. a guest at table 6 reported slipping near the server station. Floor was wet from a spilled water pitcher reported at 8:09 p.m. Area was dried and coned at 8:14 p.m." is the same event, correctly recorded.

## Common failures

| Failure | Why it hurts |
|---------|-------------|
| Report written the next day | Times, quotes, and ticket detail are already approximations |
| Conclusions instead of observations | Gives the other side something to argue about |
| Camera clip never pulled | The best evidence overwrites itself while you wait |
| No notification times logged | Cannot show escalation happened at all |
| One report covering three events | No single incident is provable |
| Investigation notes filed in the general employee record | Confidentiality problem and a discovery problem |
| Guest injury narrative that admits fault | Not your call to make in an incident report |
| Report exists only in a manager's phone | Effectively gone when that manager transfers |

## Where the report goes

Incident reports belong in the official record — the venue's incident log, and where an employee is involved, that employee's history too. Investigation material stays restricted. Medical detail is stored separately per your counsel's guidance.

The reason to keep them together and searchable is pattern. One drawer short is a bad night. Four in six weeks on the same register during the same shift is something else. One guest complaint about a server is noise; five in a quarter is a coaching conversation with evidence behind it. Pattern is invisible when reports live in five managers' phones — that is what [restaurant employee incident tracking](/restaurant-employee-incident-tracking) is for.

If an incident later becomes a separation, the report is what makes the [termination documentation](/restaurant-termination-documentation) hold up, and it is a core piece of the [unemployment claim pack](/restaurant-unemployment-claim-documentation).

## Conclusion

**An incident report is written the same shift or it is written from memory.** Facts in sequence, immediate action, notifications with times, and evidence preserved before the camera loop erases it.

Use the [incident report generator](/tools/restaurant-incident-report-generator) to assemble it, [employee incident report examples](/employee-incident-report-examples) for narrative language, and the [pillar guide](/restaurant-employee-documentation) for how reports sit alongside the other records in a restaurant file. Docu-Coach™ captures the account on the floor and time-stamps it — better documentation and more consistent records, not legal advice.

See it on a real shift at [/demo](/demo#trial).
## FAQ

### What is a restaurant incident report?

A restaurant incident report is a dated, factual record of something that happened in the venue — an injury, a guest conflict, an alcohol service problem, a cash discrepancy, a theft, a food safety failure, or an altercation. It records who, when, where in the building, what was observed, what was done immediately, who was notified, and what evidence exists.

### When should a restaurant incident report be written?

Before the shift ends. Ticket times, who was on the line, the guest's actual words, and the clock time of each step are all available during service and gone by the next day. If service will not allow a full report, capture the facts in the moment and complete the report after close.

### What is the difference between an incident report and a write-up?

An incident report records what happened. A write-up applies discipline to an employee for it. Some incidents produce both — a cash discrepancy might generate an incident report and a written warning. Many produce only a report: a guest slipping on a wet floor is an incident with no employee discipline attached.

### What evidence should you preserve after a restaurant incident?

Camera footage first, because most restaurant systems overwrite within days or weeks. Also preserve the POS or ticket record, the labor export showing who was scheduled, the register or void report, photos of the scene or equipment, any written statements taken the same day, and the receipt or check involved. Note in the report that you preserved each item and where it is.

### Who needs to be notified about a restaurant incident?

That depends on the incident and your own escalation policy — typically the GM or owner, and beyond that your district manager, insurance carrier, or workers' compensation administrator for injuries. Record every notification with the name, the method, and the clock time. Follow your operator's policy and your counsel's guidance on regulatory reporting.

### Should an employee injury report include the employee's own account?

Yes, in their words, on the day it happened. Write what they said about how the injury occurred, whether they declined care, and what they were doing at the time. An account taken a week later, after the employee has talked to other people, is worth much less than one recorded the same shift.

### Do you still write an incident report if nobody was hurt?

Yes when something happened that you would need to explain later — a near miss on a slip, a guest who was refused service and became aggressive, a walk-out mid-shift, a broken piece of equipment that caused a service failure. Reports on incidents that resolved cleanly are what establish that your venue documents consistently rather than only when there is a claim.

### Is there a free restaurant incident report generator?

Yes. The Docu-Coach™ restaurant incident report generator builds a structured report from fields written for a venue — location within the restaurant, incident type, people involved, evidence available, and notifications made. It runs in your browser and nothing you type is sent anywhere or saved.

---
Start a 30-day free trial: https://www.docu-coach.com/demo.md
More pages for AI agents: https://www.docu-coach.com/llms.txt