Restaurant HR
When Two Employees Fight: Documentation and Statements
Separate them, take accounts one at a time, and write three documents instead of one.
Key takeaways
- Separate the parties first, then take individual written accounts from both employees and every witness the same shift, and build a single incident record from those accounts — keeping your findings out of it until the investigation is done.
- The failure mode is universal: one manager writes one summary of a conversation that happened in a hallway with everyone present, and that summary is the entire file.
- Three artifacts, and they stay separate: the incident record of what happened, the individual statements in each person's own words, and the investigation record of what you did and what you concluded.
- Collapsing them into one document is how you lose the ability to show that you looked before you decided.
- Most altercations between coworkers have a documented history behind them if anyone looks, and the file usually shows nothing because the earlier friction was handled verbally.
- How to document a fight between restaurant employees: separate the parties, take individual statements the same shift, and keep the investigation record clean.
An altercation produces three documents, not one
Separate the parties first, then take individual written accounts from both employees and every witness the same shift, and build a single incident record from those accounts — keeping your findings out of it until the investigation is done. The failure mode is universal: one manager writes one summary of a conversation that happened in a hallway with everyone present, and that summary is the entire file.
Three artifacts, and they stay separate: the incident record of what happened, the individual statements in each person's own words, and the investigation record of what you did and what you concluded. Collapsing them into one document is how you lose the ability to show that you looked before you decided.
The first fifteen minutes
Documentation comes second. In order:
- Stop it and separate them. Different areas, or one sent home with pay for the remainder of the shift. Do not put them in an office together.
- Check whether anyone is hurt. If so, that is also an employee injury record, and care comes before paperwork.
- Manage the room. If guests saw it, note which tables and what you did about it.
- Say nothing about fault to either party, to the staff, or to the floor.
- Ask each person, separately, not to discuss it with coworkers before writing their account.
- Export the camera clip covering the area and the fifteen minutes on either side, before you do anything else administrative.
Only then start collecting accounts.
What to capture before anyone goes home
| Capture | Detail that makes it usable |
|---|---|
| Time and exact location | "Expo window, 8:12 p.m." — sightlines matter |
| Both employees | Names, roles, stations, shift times |
| Physical contact | Whether any occurred, described factually, and what you personally observed |
| Words used | Quotes, in the order spoken, as each account gives them |
| Volume and audience | Who could hear, whether guests were present, which tables |
| Who intervened | Staff, a manager, a guest, security |
| Immediate action | Separation, sent home, station reassignment — with times |
| Injuries | Any reported or observed, and care offered |
| Camera | Exported the same night, noted in the record |
| Individual statements | Both parties and every witness, written separately |
| Prior history | Any documented friction between these two already in the file |
| Notifications | GM, ownership, and — for anything serious — counsel, with times |
That last row is worth its own sentence. Most altercations between coworkers have a documented history behind them if anyone looks, and the file usually shows nothing because the earlier friction was handled verbally.
Collecting accounts without contaminating them
This is the whole craft on this page, and the witness statement form covers the mechanics in full. The essentials:
- One person at a time, in separate spaces, before shift end.
- Their handwriting or their typing, not your summary of a conversation.
- The same instruction to everyone: write what you personally saw and heard.
- Do not tell a witness what anyone else said. Not to prompt, not to correct, not to speed things up.
- Include the people who saw nothing. "I was in the walk-in and heard raised voices but no words" is a real boundary on the event.
- Take both principals' own accounts the same way, in their own words.
- Do not edit. If an account contains something you believe is false, take it as written and record your own observation separately.
A word on what usually goes wrong: the manager, wanting to be efficient, gathers everyone in the kitchen after close and asks what happened. Twenty minutes later there is one agreed narrative and four signatures on it, and it is worth nothing.
What the incident record should say
Not usable:
Marcus and Dana got into it at expo. Marcus was out of line as usual. Sent them both home. Will deal with it Monday.
Usable:
Saturday 3/8, approximately 8:12 p.m., expo window. Marcus T. (server, Section 3, 4:00 p.m.–close) and Dana R. (server, Section 1, 4:00 p.m.–close). I was at the POS terminal six feet from the window and heard raised voices. On turning, I observed the two standing approximately two feet apart at the window. I heard Marcus say "then run your own food" at a volume audible from the terminal. I did not hear what preceded it. I did not observe physical contact. Luis M. (expo) stepped between them at approximately 8:13 p.m. I reached the window at 8:13 p.m. and directed Marcus to the patio and Dana to the office. Guests at tables 9 and 11 turned toward the window; no guest raised it with me. Neither reported an injury. Both were sent home with pay for the remainder of the shift at 8:25 p.m. (Marcus) and 8:30 p.m. (Dana). Individual written statements collected before departure from Marcus T., Dana R., Luis M., and Ale G. (server station), each written separately in the office and the patio; a fifth statement collected from A. Cruz (dish) who reported hearing raised voices and no words. Camera over expo exported 7:55–8:25 p.m., saved to the office drive at 11:20 p.m. Prior documented history between these two: coaching note 2/18 (Marcus, tone with expo). Notified GM R. Owens at 8:45 p.m. No findings reached as of this entry.
The last sentence is deliberate. The incident record ends where the investigation begins.
What not to write down
- Who started it, until the accounts and the footage support a finding — and then it goes in the investigation record, not this one.
- Character. "As usual," "hot-headed," "those two have always hated each other." A reviewer reads that as a manager who decided in advance.
- A paraphrase of what someone told you when you could have had it in writing.
- The rest of the staff's opinions. Only what people observed.
- A finding smuggled into a suspension notice. Keep the notice neutral — see suspension pending investigation.
- Anything about a protected characteristic or a complaint of harassment handled as an ordinary fight. That changes the process entirely; go to your own HR advisor or employment counsel first.
Which documents this becomes
- The incident record — the account above, built with the incident report generator.
- Individual statements on the witness statement form, filed with the incident, not in personnel files.
- A suspension notice for either or both if they are coming off the schedule while you review. Neutral, dated, pay treatment stated.
- An investigation record and a written closure — the finding, the reasoning, and the action or the decision not to act. The process is on restaurant workplace investigations.
- Discipline, if warranted, written after the investigation and consistent with how the same conduct was handled before. Often a final written warning where the file supports it.
Follow-up
Same night: separate, export, collect statements individually, write the incident record, notify.
Next 48 hours: review the accounts and the footage together. Where accounts conflict, note the conflict rather than resolving it by preference. Interview again if needed, separately, and write those notes too.
Close it in writing. Both employees get an outcome, and both outcomes are documented — including "reviewed, no action taken." An investigation that ends in silence teaches everyone that reporting is pointless.
Then look upstream. Two servers fighting at expo on a Saturday is often a station or a process problem wearing a personality costume. Whatever you change, write it down. The full record set is on the pillar guide.
Conclusion
Separate first, collect accounts one at a time before anyone leaves, and keep the finding out of the incident record. Times, quotes, sightlines, who intervened, footage exported the same night, and a written ending for both people.
Build the record with the incident report generator and take accounts on the witness statement form. Docu-Coach™ keeps the incident, the statements, the notice, and the closure in one dated sequence so the file shows a process — better documentation and organized records, not legal advice. Harassment, threats, and anything involving a protected characteristic belong with your own HR advisor or employment counsel before you act.
See it against a real case at /demo.
Frequently Asked Questions
What do I do first when two employees start fighting?
Stop it and separate them physically — different areas of the building, or send one home with pay for the remainder of the shift if that is what it takes. Everything else follows from that. Do not attempt to resolve who was at fault on the floor, do not let them explain themselves to each other, and do not discuss it with the rest of the staff.
Should I take statements from both employees the same night?
Yes, individually and separately, before anyone goes home and before they talk to each other. Ask each one to write what happened in their own words. Accounts taken the same shift and kept apart are the only version of this event that has any evidentiary value; accounts collected on Tuesday record what the group decided happened.
How do I document a verbal altercation that never got physical?
The same way, with more attention to the words. Record what was said, by whom, in what order, at what volume, who was within earshot, whether guests heard it, and whether either person was asked to stop and what happened next. A verbal confrontation in front of a full dining room is a real incident, and the exact words are what distinguish a heated disagreement from something more serious.
Should both employees be suspended during the investigation?
Decide based on facts you can articulate, not on a reflex to be even-handed. Sometimes both come off the schedule, sometimes one, sometimes neither. Whatever you decide, use a neutral pending-investigation notice with dates and stated pay treatment, and do not let the notice imply a finding. Where an allegation is serious, take direction from your own HR advisor or employment counsel before you act.
Can I terminate both employees for fighting?
That decision belongs to you and your own counsel, and consistency is the thing reviewers examine hardest. A zero-tolerance rule applied identically is defensible; a rule applied to one person and not the other is the version that causes problems. Whatever you decide, the file has to show the investigation happened before the decision, not after.
What if the altercation involves a harassment or discrimination allegation?
Stop treating it as a fight and treat it as a complaint. The intake, confidentiality, access, and process obligations are different and they carry real legal exposure. Preserve everything, keep the file restricted, and bring in your own HR advisor or employment counsel immediately rather than running it as an ordinary investigation.
Related Resources
Witness Statement Form for Restaurant Incidents
A blank witness statement form for restaurant incidents, the fields it needs, how to collect accounts separately, and what makes one usable weeks later.
8 min read · September 2026
Suspension Pending Investigation: The Notice
How to write a suspension notice for a restaurant employee: neutral wording, the fields it needs, pay and scheduling, and how it differs from discipline.
8 min read · September 2026
Restaurant Workplace Investigations | Docu-Coach™
Restaurant Workplace Investigations for operators. Industry workflows, compliance, incident examples, and audit-ready records. Book a demo.
2 min read
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.
7 min read · September 2026
Documenting an Overservice Incident
What to record when alcohol service becomes a question: the observations, the pour count and timing, the refusal, the transport offered, and who was told.
7 min read · September 2026
Restaurant Employee Documentation
What restaurant managers should document, how fast, and where it belongs. Record types, FACT language, progressive discipline steps, and a monthly file audit for FOH and BOH.
11 min read · September 2026