Summary
An attendance point system assigns a fixed number of points to each kind of attendance failure, such as a late arrival, an unplanned absence or a no-call no-show, lets points expire after a rolling period, and ties set totals to defined consequences. Done well, it replaces a manager's memory and mood with a rule that applies to everyone the same way, which is what employees in shift-based work say they want. Done badly, it points protected absences, punishes the sick, and generates the disability and leave claims that have made point systems a regular target of enforcement. This guide explains the mechanics, gives a scale that holds up, lists the absences that must never score, covers the legal exposure, and shows how automatic attendance data removes the disputes that hand-kept point logs produce.
E-Monitor's attendance tracking records arrivals, breaks and absences automatically, so the point log is built from timestamps rather than from memory. Sign up →
How a Point System Works
Four elements define any point system, and the policy should state all four in one place.
Occurrences and their points. Each type of attendance failure carries a fixed value. A tardy of a few minutes scores less than a missed shift; a no-call no-show scores most, because it leaves the team uncovered without warning.
A rolling window. Points expire a fixed period after they were earned, usually six or twelve months, so that the total reflects recent behaviour rather than a permanent record.
Thresholds and consequences. Set totals trigger set steps: a conversation, a written warning, a final warning, termination. The steps are published, so that nobody is surprised.
Exemptions. Absences protected by law or by policy score zero, without exception and without a manager's discretion. This element is the one most often missing and the one that decides whether the system survives a legal challenge.
A Fair Scale to Copy
| Occurrence | Points | Notes |
|---|---|---|
| Late by 1 to 15 minutes, or leaving up to 15 minutes early | 0.5 | Grace of a few minutes is reasonable; state it |
| Late by more than 15 minutes, or leaving more than 15 minutes early | 1 | |
| Unplanned absence, with notice before the shift | 1 | Consecutive days for one illness count once |
| Unplanned absence, notice after the shift started | 2 | |
| No-call no-show | 3 | See the no-call no-show guide |
| Protected absence of any kind | 0 | Statutory leave, disability, jury duty, bereavement, approved time off |
| Thirty days with no occurrences | minus 1 | Rewards recovery; floors at zero |
Thresholds that pair with this scale on a twelve-month rolling window: 3 points, documented conversation; 5, written warning; 7, final warning; 9, termination review. The review at the top step exists so that a human checks for a protected cause before the policy's final consequence is applied, which is where most point-system lawsuits start.
Two deliberate features. Consecutive days for one illness count as a single occurrence, because a scale that gives three points to a three-day flu is a scale that punishes being ill. And the recovery credit matters: a system that can only go up tells employees that nothing they do now changes anything, which is the opposite of the behaviour it is meant to produce.
Absences That Must Score Zero
This is the list that keeps the system lawful. Points for any of these have produced claims under the Family and Medical Leave Act, the Americans with Disabilities Act, state sick-leave laws, and their equivalents in the UK and EU.
- Statutory leave: FMLA, state paid sick leave, parental leave, and in the UK and EU all statutory sick and family leave
- Disability-related absence where an accommodation applies or is being assessed
- Pregnancy-related absence
- Jury duty, military service, voting where protected
- Workers' compensation absences
- Bereavement and emergency leave under policy
- Approved time off of any kind, including time off in lieu
- Absences caused by the employer: cancelled shifts, system outages, late schedule changes
The US Equal Employment Opportunity Commission has repeatedly pursued employers whose point systems scored disability-related absences, and the settlements run into the millions. The mechanical answer is a zero-point category that managers cannot override, backed by a leave process that records the reason. The disability compliance guide covers the accommodation side.
Pros and Cons, Honestly
In favour. Consistency: the same lateness gets the same response regardless of who the employee is or how the manager feels. Predictability: employees know where they stand and what comes next. Defensibility: a documented, uniformly applied system is far easier to defend than a manager's judgement. Scale: in operations with hundreds of shift workers, nothing else is workable.
Against. Rigidity: a system that cannot distinguish a car crash from a hangover will eventually fire the wrong person. Legal exposure: every protected absence that slips into the log is a claim. Culture: in knowledge-work teams with flexible hours a point system reads as a factory rule and damages trust out of proportion to any benefit. Gaming: employees learn the thresholds and manage to them, which is behaviour the system produced.
The honest conclusion is that point systems suit shift-based, coverage-critical operations with clear start times, and do not suit roles where attendance is not the measure of the work. The tardiness guide covers the conversation-first approach that fits the second group.
Keeping the Log Accurate
A point system is only as fair as its record, and a record kept by hand from a supervisor's observation is the weakest part of most systems. Disputes about whether someone was eight minutes late or eighteen, whether notice was given before the shift, and whether an absence was ever recorded as protected consume more HR time than the policy saves.
Automatic attendance data removes most of it. Clock-in from a work device or kiosk records the minute; the leave system records the reason; the point log is generated from the two rather than typed. Employees see their own points and occurrences on their dashboard, with the timestamp beside each, and can dispute a record in the week it was made rather than at the final-warning meeting. Attendance tracking in E-Monitor produces the occurrences; the attendance policy template provides the wording for the scale and the exemptions.
Rolling It Out
Announce the scale, the window, the thresholds and the zero-point list together, at least a month before points start accruing, and start everyone at zero on the launch date. Train supervisors on the zero-point list before anything else, because the supervisor who points a protected absence is the single largest risk. Review the system after six months: if more than a small share of occurrences are being disputed, the record is the problem; if the same people are at the top of the scale every window, the roster or the role is. The absenteeism guide covers what a persistent pattern usually means.
A Worked Example: The Warehouse That Scored the Wrong Thing
A distribution centre with 240 shift staff ran a point system that had drifted over a decade. Supervisors logged points from memory at the end of each week, consecutive sick days scored separately, and there was no zero-point category because the original policy predated the state's paid sick leave law. The site's turnover sat above 60 percent and HR spent a day a week on attendance disputes.
The rebuild did three things. Clock-in moved to the time system, so lateness was a timestamp rather than an opinion. The scale was replaced with the one above, with the illness rule and the recovery credit. And every absence recorded as sick leave in the HR system scored zero automatically. In the first six months, disputes fell by three-quarters, two pending disability claims were settled on terms that would not have been available under the old log, and turnover fell by a third, mostly because the people who had been leaving were the ones the old system had been punishing for being ill.
Frequently Asked Questions
1. What is an attendance point system?
A policy that assigns fixed points to each type of attendance failure, such as lateness, unplanned absence or a no-call no-show, expires points after a rolling window of six or twelve months, and ties set totals to defined consequences from a conversation through to termination. Protected absences score zero.
2. How many points should a no-call no-show be?
The highest value on the scale, typically three where a late arrival is half a point and an unplanned absence is one, because it leaves the team uncovered without warning. Consecutive days for the same cause should count as a single occurrence.
3. Are attendance point systems legal?
Yes, provided protected absences never score. Points for FMLA, state sick leave, disability-related, pregnancy-related, jury, military or workers' compensation absences have produced enforcement action and settlements. A zero-point category that managers cannot override is the safeguard.
4. Should sick days count as points?
Not where paid sick leave is a legal right, which now covers most US states and all of the UK and EU. Where an unplanned absence is scored, consecutive days for one illness should count once, and any absence with a medical or statutory basis should score zero.
5. Do point systems reduce absenteeism?
They reduce disputes and inconsistency, and in coverage-critical shift operations they usually reduce unplanned absence. They do not address the causes, so persistent high scorers point to a roster, role or health issue the system cannot fix. Vendor claims of specific percentage reductions are not well supported.
6. How should points be recorded?
From automatic attendance data rather than supervisor memory: clock-in timestamps for lateness, the leave system for reasons, with the point log generated from both. Employees should see their own occurrences and be able to dispute a record in the week it is made.
Points from timestamps, not from memory E-Monitor records arrivals, departures and breaks automatically and shows employees their own occurrences, so the point log is accurate and the disputes disappear. Sign up →