Attendance Policy

An attendance policy answers a narrower set of questions than it is usually asked to.

• What hours are expected, and whether they are fixed, flexible within a band, or defined by a roster.
• How presence is recorded, and what an employee should do when the recording method fails.
• What lateness means, whether there is a grace period, and what happens beyond it.
• How partial days, short hours and early departure are treated.
• Who can approve an exception, and how far.

The question it should not try to answer is what counts as acceptable absence, which belongs in the absenteeism policy. Documents that merge the two end up applying disciplinary language to ordinary lateness.

Most attendance policies are written as though time present, time worked and work delivered are interchangeable. For a good deal of work they are not, and the policy reads as mistrust wherever the mismatch is obvious to the employee.

A single organisation frequently needs more than one of these. Applying the shift-work measure to the whole workforce because it is easier to administer is the usual cause of an attendance policy that people resent.

How attendance is captured shapes behaviour more than the clause about lateness does.

Biometric and access-controlled capture is accurate and removes argument about whether someone was there. It also records only the building, which is why it handles field work, client visits and hybrid arrangements badly, and it carries data obligations that a spreadsheet does not.

App and location-based capture covers field roles, and it raises questions about tracking outside working hours that are worth answering in the policy rather than in a grievance.

Self-declared attendance is the lightest to run and depends on the relationship being sound. It works well until it is used as evidence in a dispute.

Whichever is chosen, the clause most often missing is what an employee does when the system fails. Devices break and networks drop, and a policy with no stated fallback converts a technical failure into an attendance mark against someone who was at work.

Every organisation has a grace period. In most it is unwritten, which means it varies by manager and by mood, and the employee who is marked late after four minutes has watched someone else arrive at ten.

Stating it removes the inconsistency and costs nothing that was not already being given away. What follows beyond it should be proportionate and stated: a conversation before a deduction, and a deduction before anything formal.

The exception path matters more than the rule. Traffic, weather, transport failures, a sick child and a delayed shift handover are ordinary and recurring, and a policy with no route for them generates either dishonesty or resentment. Name who can approve an exception and how far, and let managers use it without a business case.

Where lateness is persistent and concentrated, treat it the way absence is treated: look for the cause, and look at the roster and the commute before looking at the person.

For shift-based work the attendance clause is the smaller half of the problem. What determines whether attendance holds up is the roster.

• How much notice is given of a shift, and whether it can change after publication.
• Whether swaps are permitted, who approves them, and how quickly.
• The minimum rest between shifts, and whether the roster ever breaches it.
• How overtime is offered and recorded, and whether refusing it carries consequences.

Attendance problems on shift patterns are usually roster problems presenting as attendance problems. A pattern of absence concentrated on particular shifts, or in the week following a run of long ones, is telling you about the schedule.

Rest periods and hour limits for many establishments are set by the applicable state enactment or the Occupational Safety, Health and Working Conditions Code rather than left to the employer, so the roster has a floor under it that policy cannot lower.