Restaurant Attendance Write-Up

Attendance is a pattern problem, not an incident problem

A restaurant attendance write-up records one specific occurrence — a no-show, a late arrival, a late call-out, an unapproved early out — against the posted schedule, the actual clock times, and the coverage impact. One occurrence rarely ends employment. The pattern does, and the pattern only exists if each occurrence was written down when it happened.

This is where most restaurant files break. Everyone on the management team knows a server is unreliable. The file shows one termination memo.

Build the document with the attendance write-up generator, which computes minutes late and holds the prior-occurrence list for you.

Name the occurrence type

Six distinct events, six different records. Do not blend them.

Occurrence	Defining fact	Typical first step
No-call/no-show	Zero notice by the policy deadline	Written warning — see NCNS write-up
Late arrival	Clocked in past the grace period	Coaching — see tardiness write-up
Late call-out	Notified, but after the deadline	Occurrence logged, coaching
Unapproved early out	Left before released or before side work done	Coaching, then written — see leaving-early write-up
Walk-out mid-shift	Left during service without release	Conduct, not attendance
No-show on a picked-up or swapped shift	Accepted the shift, did not work it	Depends on whether the swap was approved in the system

The last one causes more arguments than any other. Verify the schedule in your scheduling tool before you write anyone up — if the swap was approved and the schedule was never updated, that is a management error and the write-up will not survive it.

Phone use on the line is not one of these six. File it on the restaurant cell-phone write-up. Guest-facing rudeness is not attendance either; file it on the restaurant rude-to-guest write-up. A missing name tag or non-slip shoes is not attendance; file it on the restaurant dress-code write-up. An unapproved early-out or unauthorized/extended break that is not a walk-out belongs on the restaurant leaving-early write-up, not bundled into this pattern page. A refused lawful work order is not attendance; file it on the restaurant insubordination write-up. A guest photo or public workplace post is not attendance; file it on the restaurant social media write-up. An observed product walkout, unpaid comp, or tip-jar/till taking is not attendance; file it on the restaurant employee theft write-up. A tip-pool or tip-out dispute is not attendance; file it on the restaurant tip-theft write-up.

Cite the source, don't describe it

Every attendance write-up needs three pieces of proof, each named:

1. Posted schedule — "Scheduled 10:00 a.m.–4:00 p.m. per the 3/3 posted schedule."
2. Actual clock times — "No clock-in. / Clocked in 10:22 a.m. per POS labor export."
3. Notification — "No contact as of end of shift. / Texted MOD at 10:14 a.m., 14 minutes after scheduled start."

Then the impact and the policy. That is the whole spine. Attach or reference the export rather than paraphrasing it, because "everyone knew they were on" is not a record.

Write impact in numbers

Coverage impact is the field managers weaken most, because it is where frustration wants to live.

Weak	Usable
"Left us completely slammed"	"Section 2 collapsed. Remaining server carried 8 tables 11:30 a.m.–1:00 p.m."
"Kitchen was a disaster"	"Sauté ran uncovered for 40 minutes. Ticket times 14 to 26 minutes during the window."
"Had to scramble"	"Called in an off-schedule cook at 4.5 hours overtime. AM manager worked expo."
"Guests were upset"	"Three tables comped, $118 total. Two guests left before entrees."

Numbers do two things: they are hard to dispute, and they explain to a reviewer why the behavior mattered operationally rather than emotionally.

The ladder, and the rolling window

State the step you are on and list the prior dated steps. Never invent one.

Step	What the file must already show
Occurrence logged	Schedule proof, notification, impact, MOD
Documented coaching	The occurrence, the expectation, a follow-up date
Written warning	Prior coaching with its date, policy cited, consequence stated
Final written warning	Prior written warning, same issue or published threshold hit
Separation	Every prior step dated, plus a summary that lists them

Publish the rolling window and use it. "Four occurrences in 90 days" is a policy. "Four occurrences" with no window means an employee with four spread over two years is treated like one with four in a month. Reviewers notice.

Where a run of lates and no-shows has become a genuine pattern, work the whole picture rather than one more form: the chronic attendance approach covers the conversation and the plan.

Before you discipline a call-out, ask

Some absences may be protected — paid sick leave, family or medical leave, a disability-related accommodation, jury duty, and other categories that vary widely by state and city. Protections and thresholds differ enough that a rule from one market can be wrong in another.

Practically: document the attendance facts as you would any occurrence, then check with your HR partner or employment counsel before applying a step to a medical, leave-related, or accommodation-related absence. Docu-Coach™ does not provide legal advice, and neither does this page. The safe habit is to keep the record accurate and get the classification confirmed before the write-up is delivered.

Mistakes that flatten an attendance file

• Logging Saturday's no-show on Tuesday, so the "same-day" claim is gone
• Bundling a month of lates into one memo with no individual dates
• No schedule export cited, only the manager's recollection
• No rolling window in the policy, so the count means nothing
• Treating a text to a coworker as notice to the store without saying whether policy allows it
• Coaching that happened verbally and was never written, leaving the written warning unsupported
• The same lateness excused on days and written up on nights
• Applying a step to a medical absence without checking first
• Prior occurrences that live in three managers' phones instead of the employee's record

Run it this way

1. Confirm the posted schedule and any approved swap before you assume an occurrence.
2. Log the occurrence within a couple of hours: type, times, notification, coverage, MOD.
3. Pull the employee's prior occurrences with dates before choosing the step.
4. Write impact in numbers, cite the policy section, set a follow-up date.
5. Deliver privately, record their response verbatim, note the acknowledgment or refusal.
6. If the absence is medical or leave-related, confirm classification before delivery.

Conclusion

Attendance discipline is arithmetic the file either supports or it doesn't. Schedule proof, actual times, notification, coverage in numbers, and a step the employee already knew was next.

The attendance write-up generator does the minutes-late math and holds the occurrence history. The pillar guide shows how attendance records sit next to coaching, incidents, and separation. If a claim is already filed, go to restaurant unemployment claim documentation.

Docu-Coach™ keeps occurrences in one searchable history so the pattern is visible while you can still coach it — better documentation and more consistent records, not legal advice. See it at /demo.