No-Call No-Show Policy Template for Small Businesses

A no-call no-show policy solves a specific, recurring problem: an employee stops showing up, doesn't respond, and the business is left not knowing whether to hold the position, fill it, or wait — and for how long. Without a written threshold, that decision gets made under pressure and inconsistently, which is exactly the setup for a dispute later.

What the policy needs to define

The threshold. How many consecutive missed shifts with no contact counts as voluntary resignation or job abandonment. Two to three consecutive days is the most common default in small businesses — long enough to rule out a one-day emergency, short enough that the position isn't held indefinitely.

What counts as contact. A text, a call, an email — specify which channels count and whether a message through a coworker satisfies it. Vague policies ("failure to notify") generate arguments about what "notify" actually required.

The documentation trail. Every missed shift, every attempted contact, and the outcome, timestamped. This is what protects the business if the absence later turns out to have a legally protected cause.

The exceptions. A no-call no-show policy needs an explicit carve-out for situations the policy shouldn't punish: a documented medical emergency, jury duty, a situation covered by leave law where the employee genuinely couldn't communicate. Building this in up front is far better than arguing it after the fact.

The sequence that protects the business

1. First missed shift, no contact. Attempt to reach the employee through every channel available — phone, personal email, emergency contact on file. Document each attempt with a timestamp.
2. Second missed shift. Repeat contact attempts. If your policy's threshold is two days, this is typically where a decision point is reached, but confirm no response has come through any channel first.
3. Threshold met. If your written policy specifies three days and that point is reached with zero contact and no exception applies, document the decision to treat the position as voluntarily abandoned, referencing the specific policy clause.
4. Written confirmation. Send a letter or email to the employee's address on file confirming the abandonment determination and the effective date — this is the record that matters if the situation is ever disputed.

Where this goes wrong

No written threshold at all. Deciding case by case, after the fact, whether someone "should have called" is where inconsistent treatment — and the appearance of discrimination — creeps in, even unintentionally.

Skipping the exception check. The employee who didn't call because they were unconscious in a hospital is exactly the case a rigid, exception-free policy handles badly, and exactly the case that turns a routine HR decision into a legal one.

Confusing this with performance-based termination. A no-call no-show policy exists specifically for unexplained absence with no contact. If someone has been calling out sick with a pattern you suspect is not genuine, that's a different, harder conversation — a written attendance policy with clear expectations, addressed directly, not resolved through the job-abandonment threshold.

Applying it inconsistently across employees. If one employee's two missed days is quietly overlooked and another's triggers immediate termination, the written threshold stops protecting the business and starts working against it.

A simple policy template

Threshold: [Two / three] consecutive scheduled workdays with no contact from the employee, through any of the channels below.

Accepted contact methods: [Phone call to manager, text to manager, email to HR — list specifically.]

Contact attempts required before determination: At least [two] attempts across [two] different channels, each documented with date and time.

Exceptions: Documented medical emergency, legally protected leave, or other circumstance genuinely preventing contact, evaluated case by case once known.

Effective date of separation: The [third] consecutive missed day, once contact attempts and the exception check are complete.

The relationship to your PTO policy

A no-call no-show policy and a PTO policy solve adjacent but different problems — one handles unexplained absence, the other handles requested and approved time away. Where they intersect is call-out procedure for sick time: if your PTO policy requires notice before a certain hour for a same-day sick call, cross-reference that requirement here so the two documents don't quietly contradict each other.

Communicating the policy before anyone needs it

A no-call no-show policy only works as a deterrent and a protection if employees actually know it exists before the situation arises. Introducing it for the first time after an incident already happened — effectively writing the rule to fit what just occurred — is both legally weaker and obviously unfair to the employee involved. Cover it explicitly during onboarding, include it in the handbook, and reference the specific day threshold rather than vague language, so there's no argument later that the rule wasn't known or wasn't clear.

How this interacts with progressive discipline

Some small businesses fold no-call no-show handling into a broader progressive discipline policy — a verbal warning, then written, then termination — rather than treating it as an automatic, threshold-based separation. Either approach can work, but they shouldn't be mixed without being clear about which applies. If the policy states a fixed day threshold triggers automatic separation, applying progressive discipline instead in one case and not another is the kind of inconsistency that undermines the policy's defensibility rather than making it more lenient in a way that helps anyone.

The short version

A no-call no-show policy needs a specific day threshold, a defined list of what counts as contact, a documented attempt sequence, and an explicit exception for circumstances the policy shouldn't punish. Written down in advance and applied the same way every time, it turns an uncomfortable judgment call into a straightforward, defensible process.