Free generator · nothing leaves your browser

Restaurant incident report generator

A restaurant incident report is a factual record of something that happened in the building — a guest conflict, an injury, a cash discrepancy, an alcohol service issue — written while people still remember the times. Fill in the fields below and this builds one with the people, the sequence, the notifications, and the evidence to preserve.

This runs entirely in your browser. Nothing you type is sent to Docu-Coach™ or saved.No account, no upload, no autosave — closing the tab clears it.

Fill in what you observed

When and where
People involved

Everyone in it, plus anyone who saw it. Witness names are the part managers forget and later need.

Person 1

What happened

Sequence with times. Keep conclusions out of it — a reviewer draws those from the facts.

Notifications made

Who above store level heard about this, and when.

Notification 1

Evidence available

Check everything that exists right now, then go save it.

Follow-up

Your document

What a defensible record needs

1/10

  • Date and time of the incidentneeded — missing
  • Location inside the venue — complete
  • People involved and witnessesneeded — missing
  • Observable facts, in orderneeded — missing
  • Immediate action takenneeded — missing
  • Guest impact recorded — missing
  • Notifications logged — missing
  • Evidence identified — missing
  • Follow-up owner and date — missing
  • Manager on duty named — missing

Items marked “needed” are the ones a reviewer looks for first.

INCIDENT REPORT — GUEST CONFLICT
================================
Prepared with the Docu-Coach™ restaurant incident report generator

Date of incident: [not provided]
Time of incident: [not provided]
Location in venue: Dining room
Incident type: Guest conflict
Manager on duty: [not provided]
Authorities / EMS: No — not called

PEOPLE INVOLVED
[List everyone involved and every witness, with their role.]

WHAT HAPPENED (OBSERVABLE FACTS)
[Describe what was seen, said, and done — in order, with times.]

IMMEDIATE ACTION TAKEN
[What did the manager do on the spot?]

GUEST IMPACT
[Comps, refunds, tables moved, guests who left, or none.]

NOTIFICATIONS MADE
[Who above store level was told, and when.]

EVIDENCE AVAILABLE
[Check what exists: POS record, camera footage, ticket, photos, statements.]

FOLLOW-UP
Follow-up owner: [not provided]
Follow-up date: [not provided]

EVIDENCE PRESERVATION
Evidence preservation: camera systems in most restaurants overwrite footage in a matter of days. If footage exists, export and save the clip now — do not plan to pull it later.

Report completed by: ______________________________   Date: ____________
Reviewed by: ______________________________________   Date: ____________

Camera footage is usually the first thing lost. Export the clip before you clock out — most systems overwrite within days.

A generated page only helps if someone can find it in six months. Docu-Coach™ keeps the record, the timestamp, and the employee history in one place.

See how Docu-Coach™ stores incidents

What makes this defensible

An incident report gets read by people who were not there: an insurer, a franchisor, a state agency, or a lawyer. What makes it useful is not length — it is specificity about time, people, and what the manager did.

  • It is written the same shift, while the times and the order of events are still exact.
  • Every person is named with their role — employee, guest, vendor, or witness — instead of “a guest” and “someone from the kitchen.”
  • The sequence is timestamped, so the report answers when the manager arrived and what happened before that.
  • The immediate action taken is recorded, which is often the single most useful line for an insurer or an investigator.
  • Notifications are logged with times, so nobody has to reconstruct who knew what.
  • Evidence is identified while it still exists — POS records, footage, tickets, photos, and written statements.

Preserve the evidence before you finish the shift

Restaurant camera systems are sized for storage, not for litigation. Footage rolls off in days on a busy camera, and the clip nobody exported is gone for good. The same is true of the ticket that got voided, the receipt that went in the trash, and the coworker who quits next week without ever writing a statement.

  • Export the footage window that covers the incident, plus fifteen minutes on either side.
  • Print or screenshot the POS record — the void, the comp, the transaction, the clock-in.
  • Ask witnesses to write what they saw in their own words, dated and signed, while they still work there.
  • Photograph property damage, spill areas, and equipment before anything is cleaned or repaired.

If the incident involves an employee complaint about another employee, read restaurant workplace investigations before you interview anyone.

Common mistakes

  • Waiting until the next day to write it

    Times blur fast. A report written Tuesday for a Saturday altercation loses the minute-by-minute sequence that makes it credible.

  • Planning to pull footage later

    Later is usually after the system has overwritten it. Export the clip on shift, and note in the report that you preserved it.

  • Leaving witnesses out

    The server who saw the whole thing is the difference between one account and a corroborated one. Names and roles, not “a few people saw it.”

  • Writing conclusions instead of observations

    “The guest was aggressive” is an opinion. The words used, the volume, the distance, and who heard it are facts a reviewer can weigh.

  • One report covering three separate events

    A cash discrepancy and a guest injury on the same night are two reports. Bundling them makes both harder to follow and harder to act on.

  • Filing it in a group chat or a camera roll

    Incident records that live in a manager's texts disappear when that manager does. Keep the report and the evidence together in one system.

Keep reading

Frequently Asked Questions

What should a restaurant incident report include?

Date, time, and where in the venue it happened; everyone involved and every witness with their role; the sequence of what occurred with times; the immediate action the manager took; guest impact; whether police or EMS were involved; who above store level was notified and when; what evidence exists; and who owns the follow-up.

How fast do I need to preserve camera footage?

Treat it as hours, not weeks. Many restaurant DVR systems overwrite on a rolling window measured in days, and the busier the camera, the shorter the window. Export the clip covering the incident before you leave, save it with the report, and note in the report that you did.

Who should get the incident report after I write it?

Follow your own escalation path — usually the general manager, then above-store leadership, and your insurance or risk contact for injuries and property damage. The report has a notifications section precisely so the record shows who was told and when, which is the part people forget.

Do I file an incident report or a write-up?

They answer different questions. An incident report records what happened in the building, regardless of fault. A write-up records discipline for an employee. If an incident also warrants discipline, write both and keep them consistent — same date, same times, same facts.

Should I write down what a guest said they would do?

Write the quote, not your reading of it. “The guest said ‘you'll hear from my lawyer' at 9:20 PM and left through the patio door” is a fact. “The guest was threatening” is an interpretation that a reviewer cannot check.

Is any of this sent to Docu-Coach™?

No. The generator runs entirely in your browser and nothing you type is uploaded or saved. Copy, download, or print the report before closing the tab.