Attendance and working hours policy: rules, grace periods and overtime

At month end, an HR executive opens the attendance export and finds forty-one rows with a missing logout. Six people are marked late on a day the server was down. One engineer worked from a client site for a week with no entry at all. Payroll cannot close until each row is explained. A written attendance policy decides in advance how every one of those rows gets settled.

The policy sets the working schedule, how time is recorded, and what happens when the record and reality disagree. It protects the employee from arbitrary deductions and protects the company from disputes over pay. It also feeds directly into loss-of-pay and overtime, so errors here become errors in salary.

State the scope by group. Office staff, field staff, remote staff, shift workers and managers rarely follow the same rules. Say which clauses apply to which group, or write a short annexure for each.

• Work schedule: the working days, the weekly off, the daily hours and the reporting window.
• Breaks: the length and timing of lunch and rest breaks, and whether they count as working time.
• Attendance system: biometric, mobile app, web check-in, manual register, or a mix.
• Flexible-hours rules: core hours when everyone is reachable, and the band within which start times may move.
• Shift arrangements: who sets rosters, how swaps work and how much notice a change needs.
• Overtime approvals: who is eligible, who authorises it beforehand and how it is paid or compensated.

The attendance system choice has a practical consequence. Biometric devices give clean data at one location but fail for field and remote staff. A mobile check-in with location works for the field but invites questions about employee privacy, so say exactly what is captured and why. If you use more than one method, name which record wins when they differ.

Flexible hours trade control for trust. A fixed start time is simple to audit. Core hours with a flexible band suit teams that work across time zones, but managers must then judge output, not presence.

Grace period for late arrival is a choice, not a requirement. If you allow one, say its length as [number] minutes, how many times a month it can be used, and what happens after that. Repeated lateness needs its own paragraph: a conversation first, then a written note, then a link to the disciplinary process. Do not leave managers to improvise.

Define the marks your system will use. A late mark is raised when the first punch falls after the grace window. Three late marks in a month could become a half-day mark, if you choose that rule. Decide whether a swipe-in without a swipe-out counts as a full day, a half day or a pending entry. A geo-fence on the mobile check-in should be stated with its radius as [number] metres, so a client-site visit does not reject itself.

Watch for tardiness hidden by workarounds. Fingerprint terminals invite tailgating through the entrance, where one person badges in for another. Selfie check-ins can be taken from a car park. A split-shift pattern, with a long gap midday, needs its own clocking rule so the gap is not read as a missed punch. A kiosk at reception, a daily stand-up and a supervisor's tally sheet each work as a cross-check.

Early departure and short absences need a permission route. Decide whether a message to the manager is enough or whether a system request is needed. Unauthorised absence needs a definition and a trigger, for example a number of consecutive days without information, after which HR writes to the employee.

Weekly offs and holidays: say whether work on those days is allowed, who may ask for it, and whether the return is a premium or a day in lieu. Days in lieu need a comp-off register that carries a lapse date, or balances pile up unnoticed. Night shifts need a handover log between outgoing and incoming leads, and a rule on rest before the next roster. Overtime should never be assumed. Make prior written approval the rule, so that nobody learns at month end that a team has been staying late for weeks.

1. 1

   Employee notes the gap

   The employee files a regularisation request in the attendance system within [number] working days, naming the cause and the hours worked.

2. 2

   Manager verifies

   The manager checks the claim against the project log, the roster or the client visit plan, then approves or rejects with a comment.

3. 3

   HR checks the pattern

   HR reviews repeat requests from the same person and flags those that look like habit or misuse.

4. 4

   Record is locked

   On the payroll cut-off date HR locks the month, and later corrections go through the payroll correction route.

5. 5

   Report goes out

   HR sends the attendance summary to managers, with late marks, unregularised days and pending overtime for sign-off.

This feeds the leave and holiday policy for absence and the salary and payroll policy for deductions. Keep the cut-off dates identical in all three documents.

The policy should name its records: the attendance register or system export, the regularisation request, the overtime approval form, the roster and the exceptions log. Say how long each is kept. Each employee signs or clicks a receipt that confirms reading and acceptance, stamped with the date and the version held.

Reporting and escalation also need an owner. A weekly summary to managers and a monthly one to the leadership team is usually enough, with unauthorised absence escalated to HR on the day it is noticed.

Test the draft against a bad week. Take last quarter's muster data, apply your late-mark ladder, and count how many people would have crossed each threshold. If half the floor trips the rule, the rule is wrong, or the commute, the shuttle timing or the stand-up hour is. Adjust the rule or the cause before you publish.

Review it every year, and again whenever you change the attendance system, add a location or introduce shifts. Record each change under a new version number, and re-issue the acknowledgement. Remote arrangements are covered in the work from home and hybrid policy, which should refer back to this one for recording rules.

1. Title and ID: Attendance and Working Hours Policy, HR-POL-002, version [number]
2. Purpose: to set working hours and a consistent way to record and correct time.
3. Scope: [employee groups] at [locations], including remote and field staff under annexure [letter].
4. Definitions: working day, core hours, late arrival, unauthorised absence, overtime, regularisation.
5. Policy statements: standard hours are [number] a day; the grace period is [number] minutes, up to [number] times a month; overtime needs prior approval from [role].
6. Procedure: attendance is recorded in [system]; gaps are regularised within [number] days; the manager approves.
7. Roles: employee records time, manager verifies, HR audits and locks, payroll uses the locked record.
8. Exceptions: only [role] can grant one, in writing, with a stated cause.
9. Violations: repeated lateness and false entries follow the disciplinary policy.
10. Forms: regularisation request, overtime approval, roster.
11. Effective date, version, review: every [number] months.
12. Sign-off: I confirm I have read this policy, understood it and agree to follow it. Name, date, version held.

For process design around attendance, shifts and leave, GullyHR builds this kind of attendance, shift and leave process, and drafts the policy text itself as part of HR policies and governance.