Free generator · nothing leaves your browser

Restaurant employee write-up generator

A restaurant employee write-up is a dated record of one incident: what was observed, which policy it touches, what was already tried, and what happens next. Fill in the fields below and this builds one you can print, sign, and file before you leave the building.

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

Who and when

The shift clock matters more than the calendar day.

What happened

Write it the way a camera would record it: what was said, to whom, at what time, and what happened next.

Name the section number and title. A write-up with no policy behind it reads as personal.

Prior documented steps

Every coaching conversation or warning already on file for this issue. Blank rows are ignored.

Prior step 1

Action and follow-up

Their words, not your summary. If they declined to respond, write that.

Your document

What a defensible record needs

0/9

  • Employee, role, and locationneeded — missing
  • Date and time of the incidentneeded — missing
  • Observable facts, not labelsneeded — missing
  • Handbook policy citedneeded — missing
  • Business or guest impact — missing
  • Prior documented steps — missing
  • Employee response recorded — missing
  • Follow-up date set — missing
  • Witnesses or MOD named — missing

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

EMPLOYEE WRITE-UP — WRITTEN WARNING
===================================
Prepared with the Docu-Coach™ restaurant write-up generator

Employee: [not provided]
Role: Server
Location / store: [not provided]
Date of incident: [not provided]
Time of incident: [not provided]
Incident type: Guest complaint
Manager on duty: [not provided]
Witnesses: None identified

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

BUSINESS AND GUEST IMPACT
[What did this cost the shift, the guest, or the team?]

POLICY REFERENCE
[Cite the handbook section or standard this violates.]

PRIOR DOCUMENTED STEPS
No prior documented steps on file at the time of this write-up.

ACTION TAKEN
Level: Written warning

EMPLOYEE RESPONSE
[Recorded in the employee's own words, or note that they declined to respond.]

FOLLOW-UP
[Set a date to review whether the standard is being met.]

ACKNOWLEDGEMENT
My signature confirms this document was reviewed with me. It records the discussion and the expectation going forward. It does not require me to agree with it.

Employee signature: ______________________________   Date: ____________
Manager signature: ______________________________   Date: ____________
[ ] Employee declined to sign. Manager initials: ________  Witness: ________________  Date: ____________

Print or download it the same shift. A write-up written four days later reads like a reaction to something else.

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™ files this

What makes this defensible

A write-up is not paperwork for its own sake. It is the record a hearing officer, a franchisor, or the next general manager reads when nobody remembers the shift. Six things carry that weight.

  • It is dated and timed to the shift the incident happened on, not the day you found time to type it.
  • It describes behavior a camera could have recorded — words, times, and actions instead of conclusions about character.
  • It names the handbook section, so the standard existed before the incident rather than after it.
  • It lists prior documented steps in order, which is what makes the current step look like a ladder rather than a jump.
  • It records the employee's response in their words, including a refusal to respond.
  • It sets a follow-up date, so the file shows what happened next.

Common mistakes

  • Writing it up Tuesday for a Saturday incident

    By Tuesday the times are fuzzy and the write-up reads as a reaction to something else. If you truly cannot do it on shift, note the date you documented it and why.

  • Bundling three incidents into one memo

    A single document covering a no-show, a cash drop, and a guest complaint is impossible to sign or to defend. One incident per write-up; prior events belong in prior steps.

  • Labels instead of facts

    “Bad attitude” tells a reviewer nothing. The sentence the employee said, who heard it, and what happened after the direction tells them everything.

  • No policy citation

    Without a handbook section, discipline reads as personal preference. Cite the section number and title, and make sure the employee's acknowledgment of that handbook is on file.

  • First paper on termination day

    If the file is empty until the separation memo, the record starts on the worst possible day. Coaching notes and warnings are what make the last document look consistent.

  • Filing it in a group chat or your camera roll

    A photo of a signed page on a manager's phone leaves with that manager. Keep signed documents in one system the next GM can actually search.

Labels to behavior, in practice

The generator flags conclusory words while you type. This is what the rewrite looks like on the floor.

“Rude to a guest”
At 7:45 PM the guest at table 21 asked for the check a second time. The employee said “you already asked me” and walked to the server station. The guest flagged me down at 7:52 PM.
“Always late”
Clocked in at 5:18 PM for a 5:00 PM shift on March 4, 5:22 PM on February 28, and 5:14 PM on February 21.
“Insubordinate”
I asked the employee to restock the well before cut. They said “that's not my job” and clocked out at 10:40 PM with the well unstocked.

The pattern is the same every time: a time, a quote, and what happened next. If you want the longer version, read how to write up an employee.

Keep reading

Frequently Asked Questions

What has to be in a restaurant employee write-up?

The employee and role, the store, the date and time of the incident, what was observed in behavior terms, the business or guest impact, the handbook section it touches, any prior documented steps, the action level you are applying, the employee's response, and a follow-up date. A signature line for both parties completes it.

How soon after the incident should I write it up?

Same shift whenever you can. Contemporaneous records carry weight because they were written before anyone knew there would be a dispute. A write-up dated four days after the shift invites the question of what changed in between.

What if the employee refuses to sign the write-up?

Note it. The generated document includes a line for that: the manager records that the employee declined to sign, with a witness and the date. A signature confirms the conversation happened, not that the employee agrees with the content — say that out loud when you hand it over.

Why does the tool flag words like “rude” or “unprofessional”?

Because they are conclusions, not observations, and a reviewer cannot verify them. “Rude” becomes defensible when it reads “at 7:45 PM the employee told the guest at table 21 ‘you already asked me’ and walked away.” The warning never blocks you — it just names the word and asks for the behavior.

Can I put several incidents in one write-up?

Keep it to one incident per document. Bundled memos are hard to follow, hard to sign, and hard to defend, because a disagreement about one item taints the whole page. Reference earlier events in the prior-steps section instead.

Can this generate a final written warning?

Yes. Choose “Final written warning” as the action level and the form adds the three fields that level needs: the measurable standard the employee has to meet, how long the warning stays active, and a review date. The document then states explicitly that further occurrences may result in separation. It is the same generator because it is the same document with stricter requirements, not a different one.

Does anything I type here get sent to Docu-Coach™?

No. The generator runs entirely in your browser with local React state. There is no upload, no autosave, and no account. Closing the tab clears everything, so copy, download, or print before you leave.