NCNS Meaning: No Call No Show Explained for Employers

NCNS stands for no call, no show. If you are reading this because somebody did not turn up this morning and is not answering their phone, you do not have to decide anything yet. I build an HR platform for small businesses, and my advice to the owner or manager in that spot is to find out why before deciding what the absence means.

The reason this needs more than a definition is that the obvious response is frequently the expensive one. A missed shift with no warning feels like a clear-cut case, and in most states you are legally allowed to treat it as one. But some of these absences turn out to involve something the law protects, and discipline applied before you know which kind you are dealing with is difficult to unwind.

This guide covers what the term means, what counts as one, the check to run before you do anything, and the line between a missed shift and job abandonment. It also covers what to write down so that a termination holds up if it is ever questioned. It is written for someone running a small business without an HR department, because that is who is usually handling this alone and at short notice.

What NCNS means

NCNS is an abbreviation for no call, no show. It describes an employee who misses a scheduled shift and does not notify the employer through the expected process, so the absence is discovered when the shift starts rather than in advance.

The distinction from an ordinary absence explains why policies treat the two differently. When somebody calls out, however late and however unconvincing the reason, a manager has some window to move people around, call in cover, or accept the gap knowingly.

With a no call no show, the first anyone knows is when the work is not being done. Most of the operational damage comes from the lack of warning rather than from the missing labor.

What counts as a no call no show, and what does not

Whether an absence counts comes down to three questions: was notice given, did it reach the required person in time, and was the absence already authorized or protected? A surprising amount of confusion comes from policies that never defined the term, which then get applied inconsistently and become useless in a dispute.

The third row is where most policies fail. If your policy says employees must call before their shift starts, then a call at nine thirty for a nine o'clock shift is technically a violation. If you have never enforced it as one, you cannot start with the employee you happen to be annoyed with. Pick a grace window, write it down, and apply it the same way every time.

The second row catches people out too. Telling a coworker is genuinely how a lot of employees think notice works, particularly younger and newer staff, and it is not unreasonable of them. If your policy requires notice to a named person or number, say so plainly in the policy and again during onboarding, because otherwise you will be enforcing a rule that the employee believed they had followed.

What it actually costs

A no call no show costs more than the wages it removes, and because absence never appears as a line item, it tends to be tolerated for longer than it should be.

According to the Centers for Disease Control and Prevention journal Preventing Chronic Disease (April 2009), citing the American Productivity Audit (2003), productivity losses tied to personal and family health problems cost US employers $1,685 per employee per year, or $225.8 billion annually. Read that number for what it is: it covers absence and reduced performance while at work, not missed shifts alone.

The absence rates come from the Bureau of Labor Statistics Current Population Survey. The 2025 annual figures are eleven-month averages that leave out October, because the federal shutdown stopped collection that month, so they are not strictly comparable with earlier years.

One methodological note changes how you read the national number: the federal absence rate counts full-time wage and salary workers who put in fewer than thirty-five hours for reasons including illness, injury, childcare problems, and family obligations, and it excludes vacation, holidays, and personal days. It mostly measures unplanned absence rather than time off generally, which is the number an employer actually cares about.

National figures are useful for scale and useless for a decision, so it is worth doing the arithmetic for your own business once. The components are the same everywhere: the overtime premium paid to whoever covers, the manager hours consumed finding that person, the output that did not happen, and in customer-facing work, the revenue that walked out.

For a small business a single uncovered shift costs well beyond the wages it removes once all four are counted. A recurring weekly pattern adds up across a year without anyone ever reviewing the total.

Doing that calculation once is worth more than any benchmark, because it converts an irritation into a number you can weigh against the cost of fixing the process. Owners who run it often find the figure is larger than they assumed, and that the largest component is their own time rather than wages.

The first 24 hours

This is the part that decides your options later, and it is almost always done badly because it happens in the middle of a shift somebody now has to cover.

The last step is the one worth internalizing. There is no advantage to announcing a consequence before you know what happened, and there is real downside, because a warning issued on Tuesday for what turns out on Thursday to have been a qualifying medical emergency is a document you now have to explain.

Steps one to three only count if they are written down while they are happening. The log below is deliberately narrow: it records the shift, the attempts you made, what it cost to cover, and the reason once you have it. It says nothing about consequences, because on the day you make it you do not yet know what the consequence should be. Keep it open on your phone or your desk and fill it in as you go.

If this just happened and you have no policy

A large share of people reading this are in a specific situation: it is happening today, there is no written attendance policy, nobody has ever been disciplined for this before, and a decision is needed reasonably soon. You still have options, and that case deserves its own answer rather than a pointer to a policy you do not have.

In at-will states you may still act, and no law requires a written policy before addressing attendance. What the absence of a policy does is make the outcome depend on your consistency instead of on your documentation, which is a weaker position but not an impossible one.

The practical sequence for today is short. Make and log your contact attempts. Find out the reason before saying anything about consequences. If the reason is not protected, have a documented conversation, put a short written summary in the file, and tell the employee plainly what happens if it recurs. Then write the policy this week, while the incident is fresh and the gaps in your process are obvious.

Resist the temptation to make this employee an example of a rule that did not exist when they broke it. That is the version most likely to produce an unemployment claim you lose and a story the rest of your team hears. A documented conversation plus a policy going forward puts you in a materially stronger position for the next incident, which is where the leverage actually is.

The check to run before disciplining anyone

Before disciplining anyone, check whether the absence could be protected by law. This is the section most treatments of the subject handle in a sentence, and it is where the actual legal exposure sits for a small employer.

No federal law makes a no call no show unlawful and none tells you how to respond to one. What federal law does is constrain your response depending on why the absence happened.

An absence that looks identical from the outside can be an ordinary policy violation or a protected leave, and you cannot tell which until you know the reason. The main frameworks are below, including USERRA, the Uniformed Services Employment and Reemployment Rights Act, which protects military service.

The Family and Medical Leave Act (FMLA) point is the one that catches employers out. An employee having a medical emergency cannot always give notice beforehand, and leave can be designated after the employer learns the reason. Someone who was unconscious in an emergency room on Monday has not committed an attendance infraction in any sense that will survive scrutiny, however the Monday looked at the time.

The FMLA binds private employers with 50 or more employees in 20 or more workweeks of the current or previous calendar year, according to the Department of Labor's FMLA fact sheet (revised March 2025). A smaller business sits outside it, though the Americans with Disabilities Act (from 15 employees) and state sick leave laws can still reach the same absence.

The federal regulation is specific about the notice question. Under 29 CFR 825.303, an employee whose need for leave is unforeseeable must give notice as soon as practicable, and must follow your usual call-in procedure absent unusual circumstances. The rule's example is an employee in emergency medical treatment, who need not follow the call-in procedure until stabilized and able to use a phone.

The disability angle is subtler and less widely understood. The Equal Employment Opportunity Commission has published guidance on employer-provided leave and the Americans with Disabilities Act setting out how leave can function as a reasonable accommodation. Where a pattern of absence connects to a condition an employer knows about or reasonably should suspect, applying an attendance policy mechanically without any consideration of accommodation is where problems begin.

When a missed shift becomes job abandonment

A missed shift becomes job abandonment when the employee stops coming to work and does not return, once the consecutive days set in your written policy have passed. The two get used interchangeably and are legally different, and the difference matters most at exactly the moment people are least careful about it.

The practical consequence is that classifying a single missed day as abandonment is an error with a cost. Abandonment is a conclusion about intent, drawn from a sustained absence with no contact, and applying the label to a one-day incident can lose an unemployment hearing and undermine the rest of the file. If the employee is going to come back, it was not abandonment.

No federal statute sets the number of days; your written policy does, and where a state fixes a number it does so for unemployment purposes. New Jersey is the clear case: under N.J.A.C. 12:17-9.11, an employee absent five or more consecutive work days who without good cause fails to notify the employer has abandoned the job and is disqualified from benefits for voluntarily leaving.

Employers with New Jersey staff can write five days into their own policy, so that the attendance rule and the benefits rule point the same way. Whichever number you use, it needs to be in the written policy, because a threshold you applied but never published is a threshold you will struggle to defend.

What a policy needs to contain

Six elements cover what a small business actually needs: a definition, a notification rule, consequences by incident, an abandonment threshold, a protected-leave carve-out, and a signed acknowledgment. Plenty of small employers are running with no written attendance policy at all, which is how an ordinary missed shift turns into an argument about what the rule was.

The last row is the one to fix first if you have nothing. A policy that exists in a handbook nobody signed is considerably weaker than one with an acknowledgment on file, because the question in any dispute is not whether a rule existed but whether the employee knew about it.

Keep the attendance section inside your employee handbook rather than as a loose document, so that a single acknowledgment covers it along with everything else.

Keep the language plain. Attendance policies written in corporate legalese are not read by the people they apply to, and a rule nobody understood is a rule you will end up arguing about. A page of clear sentences beats four pages of defensive drafting for a business of this size.

Progressive discipline in practice

There is no legally required number of incidents before termination. The progressive pattern is common because it is defensible and because it gives people a chance to correct, not because anything requires it.

Two things make this work or fail. Consistency is the first: applying the sequence to one employee and not another for the same conduct is the most common way an otherwise reasonable process becomes evidence of something else.

A rolling window is the second, such as twelve months, so that incidents eventually age out. Without one, an employee with a single lapse three years ago sits permanently one step from termination, which is neither fair nor useful.

If you are considering a numeric approach instead of a narrative one, the attendance point system is a different model worth understanding before you commit to either. Points are easier to apply consistently and harder to apply with judgment, which is a real trade rather than an obvious improvement.

Terminating, and documenting it properly

Employment is at-will in every state except Montana, which requires good cause after a probationary period. In an at-will state you may generally terminate for a no call no show, including a first one. The question is not whether you can but what the file looks like afterward.

The reason to care is unemployment. State agencies generally deny benefits where separation followed misconduct, and repeated unexcused absence after clear warning frequently qualifies. Successful claims raise an employer's experience-rated unemployment tax, so this is not an abstract concern. What decides these hearings is almost never the employer's recollection of events; it is what was written down at the time.

On the mechanics: final pay deadlines vary by state, because federal law does not require an immediate final paycheck, and several states require payment considerably sooner than the next regular payday, particularly for involuntary separations.

State rules that change the answer

Attendance is largely unregulated at federal level, which pushes the variation down to the states. These are the ones that most commonly change what a small employer should do.

Michigan writes the number into statute. Under section 29(1)(a) of the Michigan Employment Security Act, as amended effective April 2, 2025, an employee absent three or more consecutive work days without contacting the employer is rebuttably presumed to have quit without good cause attributable to the employer, which disqualifies them from benefits. The employee can rebut it, so your same-day contact log still matters.

The paid sick leave point deserves emphasis because it has spread quickly and quietly. In states with accrual-based sick leave, an employee who misses a shift and later attributes it to illness may be entitled to use accrued time to cover it, and in some states, Washington among them, disciplining them for the absence is prohibited outright. That converts what looked like a straightforward no call no show into a protected absence retroactively.

NCNS on a remote or hybrid team

Most attendance policies were written for people who physically arrive somewhere, and the concept does not transfer cleanly to remote work.

The underlying problem is definitional. In shift work, showing up is unambiguous and observable. In remote work it is neither: an employee who is online but unresponsive, or offline during core hours but delivering work, or simply quiet on a day nobody needed them, does not map onto a policy built around a punch clock. Applying shift-based language to that situation produces either a rule that catches everyone or one that catches nobody.

The last row is the serious one. In an office, somebody notices immediately when a person does not arrive. On a distributed team, an employee can be genuinely unreachable for a day or more before anyone treats it as unusual, which is a safety matter and not only an attendance matter.

If you employ remote staff, decide now how long silence goes on before someone calls, and write that down alongside the rest.

If you are the employee

This page is written for employers, but some readers are on the other side of it, and the honest answers are short.

The single most useful thing an employee can do after a missed shift is make contact quickly and in writing, giving the actual reason. Employers have far more discretion than most people assume, and most of them use it based on whether the person engaged or disappeared.

This section is general information rather than legal advice, and anyone facing termination in a situation involving health, disability, or protected leave should speak to an employment attorney or their state labor agency.

Reducing how often it happens

Repeat no call no shows are usually a symptom rather than a character trait, and the causes are more tractable than they look. Four of them account for most of what a small business can actually fix.

The second row is underrated. If reporting an absence requires calling a manager who will interrogate you about it, a proportion of people will simply not call, and you have converted call-outs into no-shows through the design of your own process. Reporting should be easy and consequence-free at the point of reporting; whatever follows is a separate conversation.

The fourth row is the one to take seriously if the pattern is concentrated. Absence clustering in a particular shift, location, or reporting line is rarely about the individuals involved.

The conversation when they come back

The conversation when the employee comes back is the only part of this process where anything can actually change. It has three jobs, and they have to happen in order: establish what happened, state the consequence, and agree what is different next time.

Establishing what happened comes first because everything else depends on it, and it should be an open question rather than an accusation. Someone who was in an emergency room will say so if asked plainly and may not volunteer it if the conversation opens with a warning. Someone who overslept will usually admit it, and the admission is worth more to you than a defensive account extracted later.

The consequence comes second and should be stated once, clearly, without relitigating. If it is a documented conversation, say that and say it will be in the file. If it is a written warning, hand it over. What undermines this step is delivering it apologetically or burying it in a longer conversation about performance generally, which leaves the employee genuinely unsure whether anything happened.

The third part is where repeat incidents actually get prevented, and it is usually skipped. Ask what would have made calling in possible, and listen to the answer.

Often the answer is something you can fix in an afternoon: they did not have a number that works after hours, they did not know texting counted, they were afraid of the conversation they are now having. Fixing that is cheaper than the next incident.

On the administrative side, most of what makes this manageable is having the policy signed, the warnings filed, and the acknowledgments retrievable when somebody asks for them. FirstHR handles that layer for teams without an HR function, starting with onboarding and e-signature so the policy is acknowledged on day one.

Document management and employee records do the rest, keeping the file complete and the history findable. None of it decides anything for you. The next step is the same whatever you use: write the policy, get it signed, and keep your same-day contact log where you can find it.

Frequently Asked Questions

What does NCNS mean?

NCNS stands for no call, no show: the employee is scheduled, does not come in, and does not tell the employer through the expected channel, so nobody knows until the shift begins or the work goes undone. It is used most in shift-based work including healthcare, retail, hospitality, and contact centers. It differs from a call-out, where the employee does report the absence, however late.

How many no call no shows before termination?

There is no legal number. Many written policies are progressive: a documented warning on the first incident, a written warning on the second, and termination on the third within a rolling twelve-month period. Some employers terminate on a first incident, which is generally lawful in at-will states. What matters more than the number is that the threshold is written down, communicated in advance, and applied consistently.

Can you be fired for one no call no show?

In most of the United States, yes. Employment is at-will everywhere except Montana, and missing a shift without notice is not protected activity. The caution is that lawful and advisable differ: terminating on a first incident without establishing whether the absence involved a medical emergency or protected leave creates real exposure, and inconsistent enforcement creates more. Find out why first.

How many days of no call no show is job abandonment?

No federal law sets the number; your written policy does. For unemployment purposes, New Jersey regulation treats five or more consecutive work days without good cause or notification as abandonment, and Michigan presumes a voluntary quit after three consecutive work days without contact, which the employee can rebut. The distinction matters because abandonment is generally treated as a voluntary resignation while an attendance termination is involuntary, and unemployment proceedings handle them differently.

Does FMLA cover a no call no show?

It can if your business is covered, which under the Family and Medical Leave Act means 50 or more employees in 20 or more workweeks of this year or last. An employee having a qualifying medical emergency may be unable to give notice beforehand, and leave can be designated retroactively once the employer learns the reason. Someone hospitalized or caring for a person in crisis has not committed an ordinary policy violation. Establish the reason before applying discipline.

Is a no call no show illegal?

No. No federal law makes it unlawful or governs how employers respond. It is a violation of employer policy rather than of any statute. What is regulated is the employer response: federal leave and disability law, Title VII, military service protections, and state paid sick leave laws all constrain what you may do, depending on why the absence happened. See our guide to at-will employment.

What is a valid excuse for a no call no show?

The reasons carrying legal weight are narrower than the sympathetic ones. A medical emergency preventing communication, hospitalization, a serious health condition under federal leave law, a disability-related need, military service, and in some states use of accrued paid sick leave can all convert an apparent no call no show into a protected absence. A dead phone or oversleeping is not protected, though it may still warrant a proportionate response.

How do you write a no call no show policy?

Six elements: define what counts including any grace window, state the notification method and deadline precisely, set consequences by incident number, define your job abandonment threshold in consecutive days, state explicitly that legally protected absences are excluded, and collect a signed acknowledgment at hire.

Can an employee get unemployment after being fired for a no call no show?

Sometimes, and it usually turns on documentation. Agencies generally treat misconduct as grounds to deny benefits, and repeated unexcused absence after a clear warning often counts. What loses these cases is no written policy, no signed acknowledgment, no dated warnings, and no log of contact attempts. Successful claims raise your experience-rated unemployment tax. Requirements vary by state.

What is the difference between a no call no show and a call-out?

Notice. In a call-out the employee reports they cannot work, however late, giving a manager some window to arrange coverage. In a no call no show there is no report, so the gap surfaces when the shift begins. That is why most policies treat them separately and why a no call no show carries heavier consequences: the damage comes from the lack of warning as much as the missing hours.