How to Deal With a No-Show Employee
A clear, fair process for handling restaurant no-show employees — covering the shift, the conversation that follows, and when to write a formal policy.
When a restaurant employee no-call no-shows, the right first move is covering the shift and getting through service, then having a direct, documented conversation before their next scheduled shift — with a written policy already in place so the consequence is consistent and expected, not decided in the heat of the moment.
First: get through the shift
Have a short list of on-call or flexible staff you can text the moment you realize someone's missing — cross-trained employees who can cover more than one role are the most valuable people to have on that list (see Cross-Training Staff to Improve Flexibility). Don't try to solve the "why" mid-shift; solve the staffing gap first.
Then: have the conversation, in person
Once the immediate coverage problem is handled, talk to the employee before or at the start of their next shift — not over text, and not in front of the rest of the team.
- Ask what happened, directly but without accusation: "You were scheduled Friday and didn't show and didn't call — what happened?"
- Listen for whether this is a one-off (a genuine emergency) or a pattern.
- State the consequence per your written policy, calmly and consistently — this is not the moment to improvise a harsher or softer response based on mood.
Write the policy before you need it
A no-show policy decided in advance protects you from both being too lenient (which signals to the rest of the team that no-shows have no consequence) and too harsh in a single emotional moment (which can look like retaliation if challenged later).
| Occurrence | Typical response |
|---|---|
| 1st no-call no-show | Documented verbal warning, conversation about cause |
| 2nd within 90 days | Written warning, clear statement that next occurrence ends employment |
| 3rd within 90 days | Termination, per your handbook |
| Pattern tied to a real hardship | Consider accommodation before escalating — this protects you and the employee |
Takeaway: Consistency is what makes a no-show policy fair. The exact same offense should get the exact same response whether it's your best server or someone who's struggled all month — otherwise you're not enforcing a policy, you're playing favorites.
Watch for the pattern behind the pattern
Repeated no-shows from an otherwise good employee are sometimes a signal of a scheduling conflict you didn't know about, a transportation problem, or burnout — not just unreliability. A direct conversation ("this is the third time — what's actually going on?") sometimes surfaces something fixable, like a shift that consistently conflicts with a class or childcare pickup.
Build it into your handbook and onboarding
Make sure every new hire is told the no-show policy explicitly during onboarding, not just handed a handbook page to skim — see Onboarding New Hires the Right Way and Creating an Employee Handbook for Your Restaurant for where this policy should live in writing.
Use the worksheet below to log each incident with date, coverage solution, conversation notes, and consequence applied — a clean record protects you if a termination is ever challenged.
Half of no-shows are schedule confusion, not defiance. A scheduling tool that pushes the posted schedule to each employee's phone and sends a shift reminder the day before removes the "I didn't know I was on" excuse entirely — Cobblestone POS includes scheduling and time clock with the POS at no monthly fee, so the schedule, the clock-in record, and the no-show history all live in one place when you have the conversation.
Bottom line
Handle the shift first, the person second. A written, consistent no-show policy applied the same way every time is what keeps the rest of your team trusting that showing up actually matters.
No-Show Incident Log
