---
title: "Restaurant Tardiness Write-Up"
description: "How restaurant managers write up employees for being late: clock-in vs. scheduled start, grace windows, same-day FACT language, and a tardiness pattern that survives a hearing."
url: https://www.docu-coach.com/restaurant-tardiness-write-up
markdown: https://www.docu-coach.com/restaurant-tardiness-write-up.md
datePublished: 2026-09-11
dateModified: 2026-09-12
pageType: guide
---

# Restaurant Tardiness Write-Up

> How restaurant managers write up employees for being late: clock-in vs. scheduled start, grace windows, same-day FACT language, and a tardiness pattern that survives a hearing.

## Key takeaways

- A restaurant tardiness write-up is the dated record that a scheduled employee clocked in after the posted start—plus the punch, schedule proof, minutes late, coverage impact, policy citation, and next progressive step.
- Use this page when you manage FOH, BOH, or a bar and someone showed up late but still worked.
- A ghosted shift is a different record: use the restaurant no-call/no-show 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.
- Longer attendance patterns that mix lates with absences belong in how to document employee attendance issues.

## Restaurant tardiness write-up (clock-in vs. scheduled start)

**A restaurant tardiness write-up is the dated record that a scheduled employee clocked in after the posted start—plus the punch, schedule proof, minutes late, coverage impact, policy citation, and next progressive step.** It is not a group-chat vent about "always late," and it is not a Friday memo that bundles three Saturdays after the unemployment letter arrives.

Use this page when you manage FOH, BOH, or a bar and someone showed up late but still worked. A ghosted shift is a different record: use the [restaurant no-call/no-show write-up](/restaurant-no-call-no-show-write-up). For the full floor file (hire packet, guest complaints, alcohol, cash), use the [restaurant employee documentation checklist](/restaurant-employee-documentation-checklist). For write-up language that is not this incident type, see [how to write up an employee](/how-to-write-up-an-employee) and [employee write-up examples](/employee-write-up-examples). Longer attendance patterns that mix lates with absences belong in [how to document employee attendance issues](/how-to-document-employee-attendance-issues). A guest-facing service miss belongs on the [restaurant rude-to-guest write-up](/restaurant-rude-to-guest-write-up). A uniform or appearance miss belongs on the [restaurant dress-code write-up](/restaurant-dress-code-write-up). An unapproved early-out or unauthorized/extended break belongs on the [restaurant leaving-early write-up](/restaurant-leaving-early-write-up). A refused lawful work order belongs on the [restaurant insubordination write-up](/restaurant-insubordination-write-up). A guest photo, public shift or manager complaint, or private workplace post belongs on the [restaurant social media write-up](/restaurant-social-media-write-up). An observed product walkout, unpaid comp, or tip-jar/till taking belongs on the [restaurant employee theft write-up](/restaurant-employee-theft-write-up). A withheld tip-out or tip-pool skim belongs on the [restaurant tip-theft write-up](/restaurant-tip-theft-write-up).

## What tardiness is—and is not

**Tardiness** means the person was on the posted schedule, arrived after the start time your handbook uses, and still worked some or all of the shift. Your handbook should define the clock: punch time, grace window (often 5–7 minutes), and whether a late call-in still counts as late.

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

| Event | What to log | Typical next step |
|-------|-------------|-------------------|
| Late clock-in | Scheduled start, punch time, minutes late after grace | Occurrence; coaching or write-up per ladder |
| Late after a call-in | Call time vs. start, new ETA, actual punch | Still tardiness unless policy treats it as a call-out |
| Mid-shift late return | Break/out time, return punch, station left uncovered | [Leaving-early / break-policy write-up](/restaurant-leaving-early-write-up)—not an open tardy |
| Early-out | Scheduled end, actual clock-out, who released them | Separate occurrence; use the [leaving-early write-up](/restaurant-leaving-early-write-up) |
| True NCNS | Scheduled start, zero contact, never punched | [NCNS write-up](/restaurant-no-call-no-show-write-up), not this form |
| Unapproved swap | Whether the tool showed them on, who worked | Fix the schedule; write up the person who owned the shift |

One 12-minute late is an occurrence. Three dated late punches with coaching between them is a pattern. Unemployment boards treat "they are always late" as a story until the punches match the POS schedule.

## 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, line, dish, bartender), home store if borrowed.
2. **Schedule proof** — Date, scheduled in, source (7shifts, HotSchedules, POS labor). Cite or attach the export.
3. **Punch** — Actual clock-in from the time clock or POS. Write clock time, not "around 10:20."
4. **Grace window** — Handbook minutes allowed; minutes late after that window.
5. **Notification** — None / called MOD at X:XX / text after the station was already collapsed.
6. **MOD and coverage** — Who ran the station until they arrived; who opened the door or the line.
7. **Impact** — Guests waiting at a locked door, section sat late, tickets +N minutes, bartender solo. Numbers beat adjectives.
8. **Policy** — Handbook attendance or punctuality section the employee already acknowledged.
9. **Employee explanation** — Their words, or "declined to comment."
10. **Next step** — Coaching, written warning, final warning, or separation per the published ladder.

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

If you are scoring the whole file—not just this late—walk the [personnel file checklist](/personnel-file-checklist) for handbook and I-9 storage, then the restaurant checklist for floor extras.

## Progressive discipline for restaurant tardiness

Write the step you are on, and list the prior dated lates. 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 | Schedule vs. punch, minutes late, coverage, MOD | "I mentioned it in pre-shift" |
| Coaching | Facts from the occurrence, policy cited, follow-up date | "I talked to him in the alley" |
| Written warning | FACT write-up, prior lates listed, employee response | First paper appears on termination day |
| Final warning | Same issue or published tardiness threshold | New issue stacked without dates |
| Separation summary | Who, when, which late dates, property/keys, final pay | Termination text with no punch history |

A first late is often coaching even if expo was slammed. A third late 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."

Publish the window itself, too. A count of three occurrences means little without a stated 60-, 90-, or 180-day rolling window, which the [restaurant attendance write-up](/restaurant-attendance-write-up) page walks through alongside the other occurrence types.

If your handbook is zero-tolerance for opening-shift tardiness (host or keyholder late, guests at a locked door), say so in the write-up and attach the signed acknowledgment. Inconsistent enforcement—night MOD writes it up, day MOD waves it—hurts more than a missing adjective.

For a longer mix of lates and no-shows, use the [progressive discipline policy guide](/progressive-discipline-policy-guide) for the ladder and the [chronic attendance Pattern Coach Plan](/blog/chronic-attendance-restaurant) after you file this write-up.

## Unemployment-defense angle

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

- Did the employee know the scheduled start and the grace window?
- Can you show the punch versus the posted schedule?
- Did you document the late the same day—or after the claim?
- Were prior lates dated, coached, and delivered?
- Did you apply the same rule to other employees on the same shift type?

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

If two of these boxes are empty, coach and document before you separate—unless the published opening-shift rule and a same-day investigation support immediate action.

## Example tardiness write-up structure

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

**Employee:** [Name], [server / line / host], [store]  
**Date of incident:** [Saturday, date]  
**Scheduled:** [10:00 a.m. start], source [7shifts / POS labor export]  
**Actual:** Clocked in at [10:18 a.m.] (time clock). [11] minutes late after a [7]-minute grace window.  
**Notification:** [None / called MOD at 10:11 a.m. / text after door was already open].  
**Impact:** Host stand uncovered 10:00–10:18; [6] guests waited at a locked door; first seating delayed.  
**Policy:** Handbook §[Attendance / Punctuality], acknowledged [date].  
**Prior steps:** Coaching [date] for 14-minute late; written warning [date] for late clock-in on [prior date].  
**Action:** [Coaching / written warning / final warning].  
**Employee response:** [Quote or "declined to comment"].  
**Follow-up:** Next tardiness in [window] results in [next step]. Follow-up date [date].  
**MOD:** [Name]. Witnesses still employed: [names].

That is a write-up. "Employee is unreliable and ruined Saturday" is not. Pull FACT replacements from [employee write-up examples](/employee-write-up-examples) if you catch yourself reaching for a label.

## Common tardiness mistakes

- Logging Friday because Saturday was too busy
- Bundling three lates into one "attendance problem" memo
- Writing "always late" with no punches
- Skipping the grace window your handbook actually publishes
- Treating a late call-in as a call-out without saying so
- Skipping schedule proof ("everyone knew they were on")
- 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 never-arrived shift tardiness instead of using the [NCNS write-up](/restaurant-no-call-no-show-write-up)

## How to run this the next time someone clocks in late

1. Confirm the posted start before you assume a swap.
2. Log the late within two hours: scheduled start, punch, minutes late, coverage, MOD.
3. File it to the official record the same day.
4. Draft the write-up from that note using the structure above—not from memory on Tuesday.
5. If this is occurrence two or three, pull the prior dated lates before you talk termination.
6. If they never arrived, stop and use the [restaurant no-call/no-show write-up](/restaurant-no-call-no-show-write-up).
7. If a claim is already filed, export the pack and follow [how to defend an unemployment claim](/how-to-defend-an-unemployment-claim).

## Conclusion

**Restaurant tardiness documentation** is a same-day habit: punch versus schedule, minutes late, coverage impact, and a progressive step the employee already knew. This page is the write-up for one late clock-in. The [restaurant employee documentation checklist](/restaurant-employee-documentation-checklist) is the rest of the floor file. The [personnel file checklist](/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](/demo#trial).
## FAQ

### What counts as restaurant tardiness vs. a no-call/no-show?

Tardiness is a scheduled employee who clocked in after the posted start (or after your published grace window) and still worked the shift. An NCNS is a scheduled shift they never worked and never notified the store about by the handbook deadline. A 22-minute late clock-in is a tardiness write-up. Never arriving is an NCNS write-up. Do not merge them into one 'attendance' memo.

### What should I document the same day someone is late?

Same shift: employee name and role, scheduled in from POS or 7shifts/HotSchedules, actual clock-in, minutes late after any grace window, who covered the station until they arrived, guest or ticket impact, MOD on duty, handbook attendance section, and the employee's explanation. Cite or attach the schedule export and the time-clock punch.

### Is one late arrival enough for a written warning?

Only if your published policy says so and you apply it the same way to other employees. Many restaurants coach the first late, write up a pattern (for example three lates in 30 days), then move to a final warning. A single opening-shift late that left guests at a locked door can support a first-offense write-up if the handbook already said so.

### How do I write up someone for being late without sounding emotional?

Use FACT language: date, scheduled start, clock-in time, minutes late, coverage impact, prior dated lates, and the next consequence. Do not write 'always late,' 'doesn't care,' or 'ruined brunch.' Those labels lose hearings. The write-up process is in how to write up an employee; swap labels for facts using employee write-up examples.

### What if the employee says the schedule changed or they swapped?

Pull the scheduling tool before you write. Record whether a swap was approved, who owned the shift, and what the posted start showed at open. An unapproved verbal swap is still their shift. If the tool shows a later start than you remembered, fix the schedule first—do not invent a tardiness.

### How does tardiness documentation help in an unemployment hearing?

Hearing officers ask whether the employee knew the start time, broke it, and had fair notice. One undated 'always late' termination looks sudden. Dated clock-ins matched to the schedule, with coaching between them, look like a pattern. That pack belongs next to the personnel file checklist items: handbook ack, prior steps, and a same-day separation summary.

### Where does a tardiness write-up live in the file?

In the employee's official record with the punch and schedule proof—not in a group chat or the MOD's camera roll. Use the restaurant employee documentation checklist for the floor-level pack and the personnel file checklist for hire docs and I-9 storage.

### How do I see Docu-Coach™ for tardiness write-ups?

Book a demo at docu-coach.com/demo or email hello@docu-coach.com for a 30-day trial walkthrough. Same-shift voice capture timestamps the late clock-in before the section is reset.

---
Start a 30-day free trial: https://www.docu-coach.com/demo.md
More pages for AI agents: https://www.docu-coach.com/llms.txt