No call, no show: writing a policy before you need it

The shift was at six. It is twenty past. The phone goes to voicemail, the message thread shows nothing, and you are one person short on a Saturday.

What happens next is usually decided badly, in a hurry, by whoever is angriest. A written policy is worth having for exactly that reason: not because it makes the morning easier, but because it means the decision was made on a calm day.

What counts as a no call, no show

Three things get lumped together and they are not the same:

• Late. The person turns up. This is an attendance issue and it belongs in a different paragraph of your handbook.
• Called out. The person gave notice, however short. You may not like the notice, but you got it.
• No call, no show. The shift starts, nobody arrives, and nobody told you.

Only the third is what this policy is about, and the line between the second and third is your own notice window. If you never wrote one down, you do not have one, and every argument about it will be about what is reasonable rather than about what was agreed.

The number everyone quotes, and where it comes from

Three missed shifts and it counts as quitting. You will find that number in nearly every handbook in the country, and a lot of people believe it is law.

It is not. No federal statute sets a number of missed shifts. The FLSA governs what you pay and how you count hours; it does not tell you when to end an employment relationship. The three-day rule is a policy convention that spread because it is reasonable, not because anyone legislated it.

That is good news and bad news. You can choose your own number. You also have to actually choose it, write it down, and apply it the same way to everyone, because a rule you improvise per person is the one that gets challenged.

The mistake that costs real money

For an hourly employee, a no-show is simple: hours not worked are not owed. For a salaried exempt employee, it is a trap, and it is the single most expensive part of this subject.

The salary basis rule is blunt: "An exempt employee must receive the full salary for any week in which the employee performs any work without regard to the number of days or hours worked" (29 CFR 541.602(a)).

There is a permitted deduction, and it is narrower than people assume: "Deductions from pay may be made when an exempt employee is absent from work for one or more full days for personal reasons, other than sickness or disability". The regulation gives its own example: an employee absent for one and a half days for personal reasons can be docked for the one full day only.

So a manager who deducts four hours from a salaried manager who vanished for a morning has made an improper deduction. The risk is not the four hours. It is that a pattern of improper deductions can put the exemption itself in question, and an employee who is not properly exempt is owed overtime, retroactively.

If in doubt on a salaried employee, discipline the absence and leave the paycheck alone.

Before you treat it as a resignation

A no-show is a fact. What caused it is not yet known, and three things are worth checking before the policy runs its course:

1. The absence may be protected even though nobody called. Federal leave and disability rules, and state sick leave laws, all contain situations where notice is excused or arrives late. A hospital does not hand you a phone. Treat the first no-show as a question.
2. Termination is not the same as resignation. Calling it job abandonment does not automatically make it a voluntary quit, and the difference shows up later in unemployment claims and in final paycheck timing. Several states set a deadline for the final paycheck, and some of them are short. Check yours.
3. Write down what you did. Times you called, messages you sent, who you spoke to. This costs two minutes on the day and is the entire case six months later.

A policy that fits on one page

1. Define the notice window. For example, at least two hours before the shift starts, to a named person or number. Pick one and publish it.
2. Say who to contact and how. A policy that says "notify your manager" and nothing else fails at 5am.
3. Set your number, and say what happens at each step. First, second, third.
4. Say what happens to the pay. Hourly, unworked hours are not paid. Salaried exempt, deductions only for full days, and only for personal reasons.
5. Say how someone can explain themselves, and by when.
6. Apply it identically. The exception you make once becomes the standard everyone else expects.

The part that prevents most of them

A surprising share of no-shows are not defiance. They are people who did not know they were on.

Schedules change after they are posted. A swap gets agreed verbally and never recorded, so two people each think the other has Saturday. A shift is added on Thursday and the person never sees it. If your schedule lives in a printout in the break room or in a spreadsheet emailed once, you will keep generating this.

The fix is dull and it works: one schedule, updated the moment anything changes, on everyone's phone without them having to ask. It removes the most common defence, which is that nobody knew. See also shift swapping, because an unrecorded trade is the most frequent cause of a no-show that was nobody's fault.

Watch what the cover itself creates. The person who answers the phone at six in the morning is often the one who closed the night before, which quietly builds a clopening nobody rostered.

One more thing worth watching: covering a no-show pushes someone else's hours up, sometimes past 40. The absence costs you twice if nobody checks. Overtime pay and the 40-hour rule covers how that is counted.

The mirror image of the missed shift is the shift that gets recorded but not worked. Time clock fraud covers that side, buddy punching included.

In practice

Write the number down before you need it. Deduct nothing from a salaried employee for a partial day. Ask before you conclude. And keep the schedule somewhere the whole team can see it, because the cheapest no-show is the one that never happens.