One Point for the Shift. It Doesn't Matter If the Shift Was Twenty-Four Hours.

You wake up sick. You make the call. Somebody covers it.

Two days later you find out it cost you a point.

Not a warning, not a conversation. A number, added to a ledger, that will sit there for a year and then quietly fall off. Nobody explains the arithmetic, and most people never see the policy document until they are already close to the line.

Attendance point systems get talked about as a discipline issue. They are really a scheduling issue, and the reason is a single design choice almost nobody names out loud: the point attaches to the occurrence, not to the hours.

The same policy is a different policy depending on your line

Say your employer runs a common setup: four points and you get a written warning, eight and you are out. Points fall off twelve months after the day they were earned.

Now put four different workers under that identical rule.

Same policy. Same eight-point ceiling. But the person on 24/48 hits it in ten absences spread over a year, and the person on 5 x 8 has more than twice as many opportunities to be sick before the same thing happens.

Put it the other way round and it is starker. Eight points on a 5 x 8 line is roughly 64 hours of missed work. Eight points on a 24-hour line is roughly 192 hours — and it costs you your job at the same number.

This is not anybody being singled out. It is what happens when a counter is denominated in events and the events are wildly different sizes. The policy did not decide to be harsher on long shifts. It just never asked how long a shift was.

Occurrence, not day: the clause worth finding first

The most valuable sentence in most attendance policies is the one that defines an occurrence.

Under a lot of policies, consecutive days out for the same illness count as one occurrence, not one per day. Three days with the flu is one point, not three. Under others, every scheduled shift missed is its own point.

The gap between those two readings is enormous, and it is usually settled in a single clause that nobody reads until they need it.

Two follow-ups are worth having ready, because the definition often stops short of your situation:

• Does the chain break on a day off? If you are out Monday and Tuesday, off Wednesday, and still sick Thursday, is that one occurrence or two? On a 3 x 12 with days off scattered through the week, this decides almost everything.
• How does it read a 24-hour shift that crosses midnight? "Consecutive days" is written for people who work days. A shift that starts Tuesday and ends Wednesday can be counted as one absence or two depending on nothing but how the clerk enters it.

Neither of these is an argument. Both are questions with a written answer somewhere.

The rolling window means "how many do I have" has no fixed answer

Two window designs are common, and they behave completely differently.

Calendar year. Everything resets on January 1. Simple, predictable, and it makes December the most dangerous month of the year and January the safest.

Rolling twelve months. Each point falls off on its own first anniversary. Nothing ever resets. Your total on any given day depends on which day it is.

The rolling version is more common now, and it has a property worth understanding: a bad stretch follows you for exactly one year, and then it unwinds in the same shape it accumulated. If you had a rough February, you are carrying that weight through the following January, and you will get it back in February — not all at once, but in the same order it arrived.

That makes one question genuinely worth asking your supervisor: not "how many points do I have," but "when does my next one drop off?" The first question gets you a number that will be wrong next week. The second gets you a date you can plan around.

Which record does the call-off land in?

Here is the part that catches people who did everything right.

Calling off usually has to reach two different systems that are run by two different people:

1. Coverage. Somebody has to fill the hole in the roster. This is a scheduler, a charge nurse, a battalion, a dispatcher.
2. The attendance ledger. Somebody has to record what kind of absence it was — sick, personal, protected, approved, unexcused. This is usually payroll or HR.

Telling a coworker solves neither. Telling a shift supervisor at 0430 usually solves the first. The second one is where the point comes from, and it is often filled in by default when nobody categorized it.

Which is why the useful version of a call-off is short and specific rather than detailed and apologetic. Not the symptom list — the category. "Calling off my Tuesday, sick, using my accrued sick time." An explanation invites a conversation. A category lands in a field.

What federal law actually says

Two things are worth knowing precisely, because they get repeated wrong in both directions.

FMLA leave cannot be counted under a no-fault attendance policy. This is not an interpretation, it is written into the regulation. 29 CFR 825.220(c) states that employers "cannot use the taking of FMLA leave as a negative factor in employment actions, such as hiring, promotions or disciplinary actions; nor can FMLA leave be counted under no fault attendance policies."

That matters most for people whose absences are episodic rather than continuous. 29 CFR 825.115(c) defines a chronic serious health condition as one that requires periodic visits for treatment, "continues over an extended period of time (including recurring episodes of a single underlying condition)," and "may cause episodic rather than a continuing period of incapacity (e.g., asthma, diabetes, epilepsy, etc.)." Scattered single days are exactly the pattern a point system is built to catch, and exactly the pattern intermittent FMLA exists to protect.

But the call-in procedure still applies. 29 CFR 825.303(c) is blunt about it: when the need for leave is not foreseeable, "an employee must comply with the employer's usual and customary notice and procedural requirements for requesting leave, absent unusual circumstances," and if they do not, and nothing unusual explains it, "FMLA-protected leave may be delayed or denied."

So protection is real, and it is procedural. The leave is covered; the phone call is still yours to make, through whatever channel the policy names.

State paid-sick-leave laws add another layer, and they are written at a different altitude. California Labor Code section 246.5(c)(1), for example, says an employer "shall not deny an employee the right to use accrued sick days, discharge, threaten to discharge, demote, suspend, or in any manner discriminate against an employee for using accrued sick days." Whether a point counts as discriminating is the seam, and it varies by state. Worth looking up your own rather than assuming either way.

None of this is legal advice, and none of it should be acted on without asking someone qualified. It is the vocabulary, which is the part that is hard to find.

The one thing point systems have going for them

It is easy to read all of this as bad news. There is a genuine upside, and it is worth naming.

Most attendance expectations are unwritten. "You've been calling out a lot." "We had a talk about this." Those are impossible to check, impossible to appeal, and they shift depending on who is saying them and what kind of week they are having.

A point system is the rare attendance rule that is written down and countable. There is a number, a document that defines how the number moves, and a date attached to every entry. That makes it the one version of this conversation you can actually audit.

Which is a good reason to read it early, while it is still just arithmetic.

Five things worth knowing before you need them

1. What counts as one occurrence — per illness, or per shift missed, and whether a day off breaks the chain.
2. Calendar year or rolling twelve months — and if rolling, the date your next point falls off.
3. Whether points scale to shift length at all — most do not, and knowing that changes how you read the ceiling on a long line.
4. Which channel records the category — the person who fills your hole is usually not the person who codes your absence.
5. What is excluded — FMLA, jury duty, bereavement, approved leave, protected sick time. And how you flag an absence as excluded at the time, rather than arguing about it later.

Print the policy. Not because anyone is out to get you, but because the counter runs whether you read it or not, and the version in your head is almost never the version in the document.

Sources referenced: 29 CFR 825.220, 29 CFR 825.115, 29 CFR 825.303, California Labor Code 246.5.