Employee Attendance Tracking

Attendance tracking is straightforward to set up and easy to get legally wrong. The mechanics take an afternoon. The part that causes trouble is what happens to the numbers afterwards, and specifically the point systems that treat every absence the same. Attendance recording is one of the five processes of workforce management.

This page covers what to record, where the ADA and FMLA cut across a no-fault policy, and which patterns in the data are worth acting on.

What to record

Less than most systems capture. Six fields answer every question anyone actually asks.

Note what is not there: the reason. Recording a diagnosis, a family situation or anything medical in an attendance system creates an obligation to protect it and a discrimination question you did not need. The category and the protected flag carry all the operational information without any of that.

The notice field is the one people skip and then wish they had. An absence with notice and an absence without notice are different events with different consequences, and a system that cannot tell them apart forces managers to keep the distinction in their heads.

Where point systems go wrong

A no-fault attendance policy assigns points per occurrence and triggers discipline at a threshold, regardless of the reason. Its appeal is consistency: nobody has to judge whose excuse is better. That is also exactly where it fails.

The EEOC enforcement guidance on reasonable accommodation is direct on this. An employer must modify a no-fault attendance or maximum leave policy as a reasonable accommodation where an employee with a disability needs additional leave, unless another effective accommodation exists or the modification would be an undue hardship. A policy applied uniformly is not a defense; uniform application is the mechanism of the violation.

FMLA-protected absence cannot be counted at all. Assigning points for FMLA leave and then disciplining on the total is a straightforward interference claim, and it is a common way an otherwise reasonable policy becomes a liability.

The practical consequence is a required exception path. If the system has no way for an absence to be marked protected and excluded from the count, it will eventually produce a disciplinary decision built on absences the law says you may not count.

Designing one that survives contact

Five rules, all of which are about what the count excludes rather than how it accumulates.

1. Protected leave never enters the total. FMLA, ADA accommodation, jury duty, military leave, and state sick leave where it is protected. Flag at intake, not at the disciplinary review.
2. HR sets the flag, not the line manager. Managers should not be deciding what is protected, both because it is a legal judgment and because it puts them in possession of medical information.
3. Points expire. A rolling twelve months is standard. Without expiry, a long-tenured employee accumulates a permanent record of an unremarkable year.
4. There is a documented exception route. One that a person can invoke, in writing, and that has a named owner.
5. Thresholds trigger a conversation before a consequence. The first threshold should produce a discussion, because most attendance patterns have a cause that a conversation can address and a point total cannot.

A system with those five is doing what the count was supposed to do in the first place: surfacing situations that need attention, rather than automating a decision nobody has looked at.

Attendance policy wording you can copy

The policy is shorter than most drafts of it. Everything below is operative; anything longer tends to be reassurance, and reassurance is what makes a policy ambiguous.

Two lines carry most of the weight. "You do not need to give a reason" prevents managers collecting medical information they should not hold. "The purpose is to find out whether something can be changed" makes the threshold a trigger for a conversation rather than for a consequence, which is what keeps the policy out of trouble.

Where attendance data feeds pay, the rate overtime is owed on is not always the base wage. Our overtime calculator covers the regular rate.

The patterns worth looking at

A running total is the least informative view of attendance data. Four patterns tell you more, and each points at a different cause.

The team concentration is the one most often misread. When absence clusters under one manager, the individual records look like a series of unrelated personal problems, and a point system will process them that way to its logical conclusion. Gallup reported in 2026 that global engagement fell for a second consecutive year, with the sharpest decline among managers, which is worth holding in mind before reading a team's attendance as a set of individual failures.

If attendance times come from a door badge rather than a timesheet, the system carries its own questions about retention and about where access control becomes movement tracking. Our page on RFID employee tracking covers them.

Two definitions sit underneath this. Whether overtime is owed at all turns on exempt versus non-exempt status.

Attendance data is employment data

Two habits keep this clean. Record the category rather than the reason, and keep whatever medical information you do receive separate from the attendance record and the personnel file.

The second is an ADA requirement rather than good practice: medical information must be kept in separate confidential files. In practice the failure is rarely a filing decision. It is a note in a comment field, written by a manager trying to be helpful, that puts a diagnosis in a system forty people can read.

Attendance is also a record you must keep for your own protection. 29 CFR 516.2 requires hours worked each workday and each workweek, and an attendance record is often the evidence that supports it when a pay dispute arrives. Our timesheet template covers the hours side and what has to be retained.

Key takeaways

• Record the category and whether notice was given. Never record the reason or anything medical.
• The EEOC requires no-fault attendance and maximum leave policies to be modified as an ADA accommodation absent undue hardship.
• Uniform application is not a defense for a point system. It is the mechanism of the violation.
• FMLA-protected absence cannot be counted at all, and counting it is a straightforward interference claim.
• HR sets the protected flag, not the line manager, who should not be holding medical information.
• Points must expire on a rolling window, or long-tenured staff carry a permanent record of one bad year.
• Write "you do not need to give a reason" into the policy. It is what stops managers holding medical information.
• When absence clusters under one manager it is a team problem, and a point system will process it as a series of individual failures.