
TL;DR: A no call no show policy defines what happens when an employee skips a shift without notice. Done right, it protects your operations, keeps the team fair, and gives HR a defensible paper trail. This guide gives you a ready-to-copy template, the legal guardrails in the US, UK, and EU, and the process to enforce it without pushing good people out the door.
Table of contents
Your Saturday bartender doesn't show up. No text. No call. The phone rings straight to voicemail. The line at the door gets longer, the team behind the bar falls behind, and your shift lead is now working doubles. Sound familiar?
If you manage a restaurant, a retail floor, a hotel, or any operation that runs on a schedule, you have already lived this. The question is not whether it will happen again. It will. The question is what your business does when it does.
This guide walks you through exactly that. We will cover what counts as a no call no show, what to put in your policy, where the legal lines sit, and the process that actually gets followed when a shift gets skipped.
A no call no show, often written NC/NS, is when an employee misses a scheduled shift without contacting their manager before the start time. Two conditions both need to be true:
Late arrivals, sick calls made on time, or shifts swapped through an approved channel do not count. A no call no show is specifically the silence.
In some HR frameworks, two or three consecutive NC/NS days trigger what is called job abandonment, which has different legal consequences than a single missed shift. We'll come back to that.
Here's the thing most managers underestimate: the cost of a single no call no show isn't just one empty slot on the floor. It's a chain reaction.
A skipped shift in a kitchen during a Friday service means the sous chef covers. The sous chef covers, so prep for Saturday slips. Prep slips, so Saturday quality drops. Customers notice. Tips drop. Morale drops. And the ones carrying the extra weight start resenting the ones who don't show up.
The US Bureau of Labor Statistics puts the average absence rate for full-time workers at 3.2% across all industries, rising to 4.4% in accommodation and food services (BLS, 2024 Current Population Survey). CIPD's 2024 UK absence survey shows an average of 7.8 days lost per employee per year, the highest in over a decade. That's before you count unannounced absences, which sit on top.
Without a written policy, managers improvise. One shift lead sends home the offender on the spot. Another gives a second chance. A third quietly adjusts the schedule and says nothing. Within six months, you have a team that knows the rules are applied differently depending on who's on duty, and that's where morale starts cracking.
A written policy fixes three things at once. It tells employees what counts as unacceptable. It gives managers a consistent script. And it gives HR the paper trail they'll need if a termination ever gets challenged.
The legal backdrop changes depending on where you operate. Let's cover the main regions a scheduling tool like Shyfter sees.
Most US states run on at-will employment, which means either party can end the relationship without cause. In theory, a single no call no show can trigger termination. In practice, it's rarely that clean. The Fair Labor Standards Act (FLSA) does not regulate attendance directly, but a few things do come into play:
Unauthorised absence is grounds for disciplinary action under the ACAS Code of Practice on Disciplinary and Grievance Procedures. For termination to stand up at an employment tribunal, you typically need at least one written warning, a meeting with the right to be accompanied, and an appeal process. Fairness and consistency matter as much as the rule itself.
In most EU jurisdictions, unilateral termination for a single unjustified absence is hard to defend. Belgian labour law, for example, requires proof of "faute grave" (serious fault) to dismiss without notice, and a single NC/NS rarely qualifies on its own. France's Code du travail demands progressive sanctions. The common pattern is: written warning, final warning, termination with notice. Unannounced absences of three consecutive working days can, in some jurisdictions, be treated as démission implicite (Belgium) or abandon de poste (France), which has different implications than dismissal.
Bottom line: before you finalise a policy, get a local labour lawyer to review it. The template below is a starting point, not a finished product.
A policy that works in the real world answers these seven questions in plain language:
That's it. Seven points. A policy that runs longer than two pages rarely gets read.
Here's a starter template. Adapt the specifics to your jurisdiction, your team size, and your reality on the floor.
No Call No Show Policy, [Company Name]
1. Definition. A no call no show is a scheduled shift that is missed without prior notice. Prior notice means a phone call or message received by your direct manager at least one hour before the shift start time, via [specify channel: Shyfter app, dedicated phone line, etc.].
2. How to notify an absence. If you cannot work a scheduled shift, call your direct manager on [phone number] or send a message through the Shyfter app at the earliest possible moment. Text messages to personal numbers are accepted only if the manager explicitly confirms receipt.
3. Consequences.
4. Job abandonment. Three consecutive no call no show days will be treated as voluntary resignation / job abandonment, in line with applicable local labour law. The company will initiate the corresponding administrative process.
5. Valid exceptions. The following situations do not count as no call no show, provided that notice is given as soon as reasonably possible and that documentation follows within [3] business days:
6. Appeal. Any employee who receives a disciplinary action for a no call no show may request a meeting with HR within [5] business days. The employee has the right to be accompanied by a colleague or, where applicable, a union representative.
7. Acknowledgement. By signing below, I confirm I have read and understood this policy.
Signed: _ Date: ___
Two pages. Signed on the first day. Reviewed when it matters.
Writing the policy is step one. Applying it is where most operations stumble. The erosion we see most often on our side of the screen: a manager lets the first offence slide because the employee is otherwise great. Three months later, a weaker performer does the same thing, gets the written warning, and the claim of unfair treatment writes itself.
At Shyfter, what we see on the ground is simple: a consistent process beats a strict one every time. Here's what consistency looks like:
Document everything in the same place. Not in a WhatsApp chat, not in a manager's notebook, not in three different spreadsheets. One system. Clock-in data from a digital time clock and written incident reports kept together give you the timeline you need if the case ever gets challenged. Shyfter's time clock feature timestamps every clock-in and flags missed shifts automatically; pair that with a written incident log and you have an audit-ready trail.
Use a script. When a no call no show happens, the manager doesn't improvise. The conversation follows the same steps every time: confirm the facts, read the policy clause, hand over the written warning, schedule the HR meeting. A 15-minute script applied every time protects you more than a 15-page policy no one reads.
Train the shift leads. A policy is only as strong as the weakest person enforcing it. Most breaches come from mid-level staff who want to be liked and avoid the confrontation. Put them through a 30-minute role-play twice a year and you fix 80% of that.
Log the outcome. Every warning, every suspension, every termination. Dated, signed, stored. If a tribunal asks, you hand them the folder.
A concrete case: a Brussels café with 18 covers and a team of 11 was losing roughly one Saturday shift a month to no call no shows. The owner introduced the template above, paired it with digital clock-in on every shift, and trained the two shift leads in a single afternoon. Three months later, the rate dropped to one incident in the quarter. No firings. The policy did the filtering for them.
Another one: a retail chain in Wallonia with four locations and 62 staff saw an 11% unannounced absence rate on weekends before the policy rolled out. Six months after, the rate was 3.4%. Two terminations happened in that window. Both were documented cleanly; neither was challenged.
A policy punishes the behaviour. Prevention stops it happening in the first place. A few levers that tend to move the needle:
Publish schedules earlier. Predictive scheduling research from the US (Williams et al., 2022, Shift Project) showed that schedules published two weeks in advance reduced unannounced absences by around 20%. Staff with stable schedules plan their lives. Staff who only see Monday's shift on Sunday night don't.
Make swaps easy. Most no call no shows aren't sabotage. They're panic. A staff member has a crisis, no one to cover, and they ghost because the alternative feels worse. A shift-swap workflow inside the scheduling app removes the panic. Shyfter's scheduling tool lets employees propose swaps and managers approve in two taps.
Track leave properly. A team member who calls in sick three Mondays in a row is telling you something. You won't hear it if the data lives in a shoebox. A proper leave and absence tracker surfaces patterns early, so HR can intervene before it escalates.
Talk to your team. The most common reason for a no call no show, in our experience on the ground, isn't laziness. It's conflict avoidance. The staff member doesn't know how to tell you they hate the split shift, the manager, or the Saturday morning slot. If you ask, they tell you. If you don't, they ghost. See our piece on creative excuses employees give for absences for a sharper look at the signals.
A short question to ask yourself: when was the last time a team member told you something hard, and you listened without defending?
Can I fire someone for a single no call no show?
In the US, technically yes under at-will employment, but FMLA, ADA, and state rules narrow that. In the UK, Belgium, France, Spain, and the Netherlands, a single incident rarely justifies dismissal. Progressive discipline is the safer path.
Is a text message valid notice?
It depends on what your policy says. If the policy requires a phone call, a text doesn't count. If the policy accepts messages through a specific app, a text to a personal number still doesn't count. Be explicit in writing.
How many consecutive no call no show days count as job abandonment?
Most policies set the threshold at three consecutive days. Belgian and French practice often aligns with that; US norms vary by state and employer. Document your number in the policy and apply it consistently.
Do I need to pay an employee who didn't show up?
No, you don't owe wages for unworked hours. But in some US states and under some predictive-scheduling ordinances, you may owe reporting-time pay or premium pay for last-minute schedule changes on your side. Check local rules.
What if the employee has a genuine emergency and couldn't call?
That's what the exceptions clause is for. An employee who was unconscious in an emergency room didn't commit a no call no show. Ask for documentation within a reasonable window, then close the file.
Should the policy be in the employee handbook or a standalone document?
Both, ideally. A standalone one-page version signed on day one, and the same text embedded in the handbook for reference. Make sure every new hire sees it before their first shift.
A written policy handles the disciplinary side. The real reduction comes from better scheduling, clean clock-in data, and easier communication with the team. Shyfter gives you all three in one place, plus the audit trail you need if things ever go to a tribunal.
Fifteen minutes. See how a restaurant team of 20 sets up their policy, their schedule, and their clock-in in under a day.