Restaurant Rude-to-Guest Write-Up

Restaurant rude-to-guest write-up (customer service on the floor)

A restaurant rude-to-guest write-up is the dated record that a scheduled employee said or did something to a guest against a published service standard—plus the table or check, exact words, witnesses, recovery, policy citation, and next progressive step. It is not a group-chat vent about "attitude," and it is not a Friday memo that bundles three dinner complaints after the unemployment letter arrives.

Use this page when you manage FOH, BOH, or a bar and a guest-facing interaction went wrong because of what the employee said or did. This is conduct, not attendance: a late clock-in still belongs on the restaurant tardiness write-up, and a ghosted shift belongs on the restaurant no-call/no-show write-up. A personal device at a working station belongs on the restaurant cell-phone write-up. A uniform or appearance miss belongs on the restaurant dress-code write-up. An unapproved early-out or unauthorized/extended break belongs on the restaurant leaving-early write-up. A refused lawful work order belongs on the restaurant insubordination write-up. A guest photo or public post about the guest belongs on the restaurant social media write-up. An observed product walkout, unpaid comp, or tip-jar/till taking belongs on the restaurant employee theft write-up. A withheld tip-out or tip-pool skim belongs on the restaurant tip-theft write-up. For the full floor file (hire packet, guest complaints, alcohol, cash), use the restaurant employee documentation checklist. For write-up language that is not this incident type, see how to write up an employee and employee write-up examples. Server-specific POS evidence lives on documenting servers.

What rude-to-guest is—and is not

Rude-to-guest means the person was on the posted schedule, on the clock, and a guest (or a coworker who heard the guest exchange) can point to words, tone, or a refused recovery that your handbook already defines. Your handbook should define the clock: greet window, how to handle a remake, who comps, and whether a guest who is already upset still gets the same standard.

Treat these as different records, even when they happen the same week:

Event	What to log	Typical next step
Verified guest-facing words or actions	Table or check, exact quote, who heard it, recovery	Occurrence; coaching or write-up per ladder
Guest unhappy about food or wait, employee handled it	Ticket times, what was 86'd, what the employee offered	Kitchen or hospitality note—not this write-up if the words were professional
Guest unhappy about food or wait, employee made it worse	The food/wait facts plus the employee's words	This write-up; pair a food miss with the food safety write-up only if a holding or allergen standard was also missed
Nameless one-star review	Ticket search, whether you can identify the table and employee	Prompt only until the interaction is verified
Guest alleges harassment or discrimination	Intake, who was told, counsel routing	Harassment complaint documentation, not only this form
Employee refuses a manager's recovery request	The request, the exact reply, witnesses	Insubordination documentation plus this guest record
Two employees argue in front of a table	Separate accounts, who was guest-facing	Altercation documentation

One quoted sentence at table 12 is an occurrence. Three dated guest-facing notes with coaching between them is a pattern. Unemployment boards treat "they are always rude" as a story until the quotes match a named table.

What to document the same day

Capture this before the shift ends—voice note on the floor is fine if it hits the official file the same day.

1. Identity — Employee, role (server, host, bartender, expo if they spoke to the guest), home store if borrowed.
2. Table / check — Table 12, bar seat 4, check #1842. Not "a four-top."
3. Times — Seat time, complaint time, when the MOD was told. POS timeline beats "during rush."
4. Exact words — Guest quote and employee quote. Do not upgrade "that's not my problem" into "she was hostile."
5. Witnesses — MOD, expo, busser, adjacent table if they volunteered. Names still employed.
6. Impact — Comp amount, walk-out, review posted, section coverage while you recovered the table.
7. Policy — Handbook guest-service or hospitality section the employee already acknowledged.
8. Employee explanation — Their words, or "declined to comment."
9. Next step — Coaching, written warning, final warning, or separation per the published ladder.

Skip: "attitude," "doesn't care about guests," "third complaint this month" with no prior dates. Those sentences are what hearing officers discard.

If you are scoring the whole file—not just this interaction—walk the personnel file checklist for handbook and I-9 storage, then the restaurant checklist for floor extras.

Progressive discipline for restaurant guest service

Write the step you are on, and list the prior dated guest-service notes. Do not invent a "final warning" on the day you terminate unless the file already shows the earlier paper.

Step	What belongs in the file	Restaurant miss
Same-day occurrence	Table/check, quotes, witnesses, recovery, MOD	"I told them in the walk-in"
Coaching	Facts from the occurrence, policy cited, follow-up date	"I talked to her by the pass"
Written warning	FACT write-up, prior guest-service dates listed, employee response	First paper appears on termination day
Final warning	Same issue or published guest-service threshold	New issue stacked without dates
Separation summary	Who, when, which guest dates, property/keys, final pay	Termination text with no interaction history

A first verified guest miss is often coaching even if Saturday was slammed. A second verified interaction inside the handbook window is often a written warning. A documented pattern with the first steps dated and acknowledged is the unemployment-defense version of "we gave fair notice."

If your handbook is zero-tolerance for slurs, refused recovery, or walking off a table, say so in the write-up and attach the signed acknowledgment. Inconsistent enforcement—night MOD writes it up, day MOD comps and forgets—hurts more than a missing adjective.

A first conversation that states the next step is still a verbal warning if you said a further occurrence becomes a write-up. For the ladder itself, use the progressive discipline policy guide.

Build the document with the write-up generator if you want the fields held in one place. The field definitions live on the restaurant employee write-up page.

Unemployment-defense angle

States differ on misconduct, but the questions are boring and predictable:

• Did the employee know the guest-service / hospitality rule?
• Can you show what was said or done at a named table or check?
• Did you document the interaction the same day—or after a review or a claim?
• Were prior guest-service steps dated, coached, and delivered?
• Did you apply the same rule to other employees on the same station type?

A charged claim is a tax event, not a morality play. Price it with the unemployment claim cost calculator. Build the hearing pack with how to defend an unemployment claim. Restaurants that fail with a "complete" hire packet usually have no same-day guest notes; that failure mode is spelled out in how restaurants lose unemployment claims.

If two of these boxes are empty, coach and document before you separate—unless the published guest-service rule and a same-day investigation support immediate action. Confirm the threshold with your own HR advisor or employment counsel.

Example rude-to-guest write-up structure

Copy the headings. Replace the brackets. Do not add personality.

Employee: [Name], [server / host / bartender], [store]
Date of incident: [Saturday, date]
Table / check: [Table 12 / bar seat 4 / check #1842]
On duty: Clocked in [4:02 p.m.]; assigned [Section 3].
Guest report: Guest told MOD at [7:52 p.m.] that the employee said "[quote]."
Observed / heard: [Expo / busser / MOD] heard "[quote]" at [7:40 p.m.] from [the window / the well].
POS timeline: Seated [7:05 p.m.]; remake requested [7:38 p.m.]; entrée recomped $[52].
Recovery: [What was offered; whether the employee refused to return to the table].
Review / walk-out: [Review posted / guest left unpaid bar tab / none verified].
Policy: Handbook §[Guest Service / Hospitality], acknowledged [date].
Prior steps: Coaching [date] for tone with expo; verbal warning [date] for a guest remake.
Action: [Coaching / written warning / final warning].
Employee response: [Quote or "declined to comment"].
Follow-up: Next verified guest-service miss in [window] results in [next step]. Follow-up date [date].
MOD: [Name]. Witnesses still employed: [names].

That is a write-up. "Employee is rude and ruined Saturday" is not. Pull FACT replacements from employee write-up examples if you catch yourself reaching for a label.

Common guest-service mistakes

• Logging Friday because Saturday was too busy
• Bundling three dinners into one "attitude" memo
• Writing "rude to a guest" with no table, check, or quote
• Treating a nameless review as the write-up
• Skipping the employee's explanation
• Writing the first formal note on the day of termination
• Letting a transferred MOD take the coaching history with them
• Filing the write-up in camera roll or Slack, not the official record
• Calling a late greet tardiness instead of using the tardiness write-up when the only fact is the clock-in
• Calling a refused recovery "attitude" instead of using insubordination documentation

How to run this the next time a guest complains about an employee

1. Get the table or check number before the guest leaves, if you can.
2. Log the interaction within two hours: quotes, witnesses, recovery, MOD.
3. Pull the POS timeline the same night—seat, fires, close, comp reason.
4. File it to the official record the same day.
5. Draft the write-up from that note using the structure above—not from memory on Tuesday.
6. If this is occurrence two or three, pull the prior dated guest-service notes before you talk termination.
7. If they refused a direct order to recover the table, add the insubordination record—do not merge the two.
8. If a claim is already filed, export the pack and follow how to defend an unemployment claim.

Conclusion

Restaurant rude-to-guest documentation is a same-day habit: table or check, exact words, witnesses, recovery, and a progressive step the employee already knew. This page is the write-up for one guest-facing interaction. The restaurant employee documentation checklist is the rest of the floor file. The personnel file checklist still covers hire packets and I-9 storage. Docu-Coach™ timestamps the capture so the write-up is a review, not a reconstruction.

Book a demo or start a 30-day trial at /demo.