Restaurant Employee Write-Up

Restaurant employee write-up, start to finish

A restaurant employee write-up is formal, dated discipline that names a specific behavior, cites the policy it broke, records the operational impact, lists the prior steps, and states what happens next. A coaching note documents a conversation. A write-up documents a consequence.

Most restaurant write-ups fail for the same three reasons: they were written days later, they describe the person instead of the behavior, and they are the only piece of paper in the file. This page fixes all three.

Build one now with the write-up generator, or read the fields first.

The eleven fields

Everything below earns its place because a reviewer will ask about it.

Field	What good looks like
Employee and role	"Marcus T., server, Section 3 — Downtown"
Date and time	"Saturday 3/8, approximately 7:40 p.m." — not "last weekend"
Observable facts	Quotes, clock times, table numbers, ticket times, station
Impact	"Guest left without paying $84 bar tab; table recomped $52"
Policy	"Handbook §4.2 Guest Service, acknowledged 1/12"
Prior steps	"Coaching 2/18 (tone with expo); written warning 2/29 (same issue)"
Action level	Written warning / final written warning / suspension / separation
Employee response	Verbatim, or "declined to comment"
Follow-up date	A real date, not "going forward"
MOD	Who was running the floor
Witnesses	Names, and note which are still employed

The two most commonly missing: prior steps and follow-up date. Without prior steps, a final warning looks invented. Without a follow-up date, the write-up is a complaint with a signature line.

Facts, not labels

This is the whole craft. A label is your conclusion; a fact is what a camera would have recorded.

Do not write	Write
"Rude to table 12"	"Told table 12 'that's not my problem' at 7:40 p.m. when asked to remake a steak"
"Refuses to help the team"	"Asked at 8:15 p.m. to move to expo. Said 'I'm not doing that' and returned to the server station"
"Careless with cash"	"Drawer short $40.25 on 3/8 and $31.00 on 3/15. Voids 6.2% vs. 1.8% store average"
"Sloppy on the line"	"Sent three tickets to expo without the allergen slip on 3/8 between 7 and 9 p.m."
"Bad attitude"	Delete. Describe the sentence, the volume, the audience, or nothing at all

If you cannot convert a label into a fact, you may not have an incident yet — you may have an impression. Coach it and see what the next two weeks show. More conversions in employee write-up examples.

Examples by incident type

Restaurant write-ups cluster into a handful of situations. The facts you need differ by type.

Guest complaint — table number, time, what the guest said and what the employee said, whether it was comped or walked, who else witnessed it, whether a review followed. A verified guest-facing miss is its own restaurant rude-to-guest write-up.

Attendance — scheduled in and out from the labor export, actual clock times, notification and when, who covered, coverage impact. That has its own page: restaurant attendance write-up, plus dedicated versions for a tardiness write-up, a no-call/no-show, and an unapproved early-out or break-policy miss.

Phone use — station, observation times, whether they were clocked in, guest or ticket impact, handbook device section. That is conduct, not attendance: use the restaurant cell-phone write-up.

Dress code / uniform — missing piece, shoes, hair or jewelry, whether a spare was offered, handbook appearance section. That is conduct, not attendance: use the restaurant dress-code write-up.

Cash and voids — drawer count, POS void or comp report cited by number, the shift and register, whether the employee was asked and what they said. Writing the variance without accusing anyone is its own discipline: documenting a cash drawer shortage.

Food safety — the reading or observation, product affected and whether it was discarded, log entry, retraining delivered and by whom.

Alcohol service — the guest, the indicators, whether service was continued or refused, the manager notified, and the time. Treat these as incident reports as well: restaurant incident report.

Insubordination — the specific request, the time, the exact reply, whether it was repeated, who heard it. Never use the word alone as the description. The dedicated version is the restaurant insubordination write-up.

Social media — platform, URL, who is in the frame, exact caption, whether a guest or confidential store information is visible. That is the published post, not the phone in a pocket: use the restaurant social media write-up.

Documented taking — item or amount, how it left, who saw it or which camera, POS or inventory cite. That is an observed product walkout, unpaid comp, or tip-jar/till taking, not a short drawer: use the restaurant employee theft write-up. A withheld tip-out or tip-pool skim is a different record: use the restaurant tip-theft write-up. A count with no observer still belongs on documenting a cash drawer shortage.

Performance — the metric, the standard, the gap, the training already given. If the pattern is skill rather than conduct, a write-up is the wrong tool — use a restaurant performance improvement plan.

Delivering it on a real shift

The document is half the job.

1. Do it privately and off the floor. Office, walk-in hallway, patio before open. Not the pass.
2. Have a second manager present for final warnings, suspensions, and separations.
3. Read the facts, then stop talking. Do not relitigate the behavior or add grievances that are not written down.
4. Ask for their account and write it as given. If it changes the facts, verify before you file — do not argue in the moment.
5. State the follow-up explicitly. What has to be true, by when, and what happens if it isn't.
6. Get the signature or note the refusal. Then file it the same day.

Do not deliver a write-up during a rush, do not deliver one you wrote in front of them, and do not let the conversation become the first time they hear the standard. If it is, that is a coaching failure the file will show later — see restaurant employee coaching.

Mistakes that cost you later

• Writing Saturday's incident on Tuesday from memory
• Bundling three separate incidents into one memo so no single date is provable
• Citing "policy" you cannot name by section
• Adding history that was never documented ("this is the fifth time")
• Labels where facts belong
• No follow-up date, so the next step has nothing to build on
• Filing it in a group chat, a shared folder, or a camera roll
• Different consequences from different MODs for the same behavior
• Letting the write-up be the first paper in a file that ends in termination

Run it this way next time

1. Capture the facts before you leave the floor — time, quote, witnesses, impact.
2. Pull the prior steps from the employee's record before you choose the action level.
3. Draft from your capture, not from memory, using the eleven fields above.
4. Strip every label. Read it once as if the employee's representative is reading it aloud.
5. Deliver privately, log their response verbatim, set the follow-up date.
6. File the same day, then diary the follow-up.

Conclusion

A restaurant write-up is only as strong as the record behind it. Facts with clock times, a policy the employee acknowledged, prior steps that are already dated, and a consequence stated before it is applied.

The write-up generator assembles the document and tells you which fields are still empty. The pillar guide covers the other six record types a restaurant file needs, and the restaurant employee documentation checklist audits what is already in the file. Docu-Coach™ captures the facts on the floor so the write-up is a review rather than a reconstruction — better documentation and more consistent records, not legal advice.

See it against a real shift at /demo.