Attendance and working hours policy: a practical guide

An attendance policy defines when people are expected to work and what happens when reality intervenes — lateness, absence, overtime, schedule changes. It is the most frequently consulted policy in most companies and the most operationally sensitive: too rigid and it manufactures conflict over every train delay; too vague and scheduling fairness collapses into per-manager improvisation. Working-time rules are also heavily legislated everywhere — maximum hours, rest periods, overtime pay — so this article stays jurisdiction-neutral and informational, not legal advice; the legal layer must be confirmed locally.

Schedules and expectations

• How schedules are set and communicated — fixed hours, shift rosters, or flexible bands; who publishes them, how far in advance, and how changes are requested from both sides. Advance-notice discipline for rosters is the single biggest fairness lever in shift work.
• What "present" means per work mode — on-site start times, remote availability windows, and how the two are treated equivalently.
• Breaks and rest — what the law mandates plus what the company adds, stated concretely so nobody learns their break rights from rumor.

Lateness and absence: procedure over punishment

The policy’s core is procedural clarity: whom to notify, by when, through which channel, with what information — for lateness, unplanned absence, and sickness (including when certification is required, per local rules). Then define how occurrences are recorded and when patterns trigger a conversation: occasional life-happens lateness handled with proportion, repeated patterns addressed through the normal feedback and, if needed, disciplinary process — the same way for everyone, which is the entire point of writing it down. Absence records belong in the HR system as dated entries, because attendance disputes are always about specific dates and the side with contemporaneous records wins them.

Overtime and time recording

Define whether overtime is permitted, who approves it in advance, and how it is compensated (pay or time off, at what rates — usually a legal floor exists). Unmanaged overtime is a triple hazard: a legal exposure, a budget leak, and the leading indicator of burnout (see our burnout guide) — approval-in-advance is the control that keeps all three visible. Time recording itself should be stated honestly: what is recorded, how, and what it is used for; in many jurisdictions working-time records are mandatory, with retention periods. Whatever the mechanism, the records need the same discipline as all HR data — accurate at the time, retained on schedule, access-controlled.

Enforcement with fairness

Attendance policies collapse when enforcement varies by manager or by favorite: the same lateness pattern must produce the same response in every team, which requires central visibility of the records and occasional audits of how the policy is being applied. Acknowledgment discipline applies as with every policy — communicated at onboarding, re-acknowledged on change, stored per employee (in EmployDB, in the employee file with dates). A fair attendance policy, consistently applied and properly recorded, is invisible most of the year — which is exactly what success looks like.