How to write an employee attendance policy (with example rules)
An attendance policy turns "be on time" into rules everyone can check the same way. Without written rules, managers judge lateness differently, disputes turn personal, and month-end reports can't be trusted. This guide covers the rules almost every policy needs and gives starting numbers you can adjust.
This is general guidance, not legal advice. Working-time, overtime and break rules vary by country and sometimes by contract. Check local law before you publish a policy.
1. Define the working day
Start with the facts the other rules depend on: the scheduled start and end time, the working days, and any unpaid break. If different teams work differently — an office team 9–5, a warehouse on rotating shifts — write each schedule down separately rather than forcing one rule on everyone.
2. Set a grace period for lateness
A grace period is the window after the start time in which a clock-in still counts as on time. It absorbs traffic, a slow lift, or a queue at the time clock, and stops managers arguing over two minutes.
- Common starting point: 5–10 minutes.
- Be explicit that the grace period is not extra paid time and not a new start time.
- Decide what "late" triggers. Many teams only act on a pattern — for example, more than three late arrivals in a month — rather than every single one.
3. Decide what counts as a half day
Hours worked can fall anywhere between "full day" and "absent". Two thresholds make this unambiguous:
| Hours worked | Status |
|---|---|
| At or above the full-day minimum (e.g. 8h) | Present |
| Between the half-day and full-day minimums | Short day |
| At or above the half-day minimum (e.g. 4h), below full | Half day |
| Below the half-day minimum or no clock-in | Absent |
Whatever numbers you choose, publish them. People accept a rule they can calculate themselves far more readily than a judgement call.
4. Treat early leaving like lateness
An early-leave tolerance mirrors the grace period at the end of the day. Without it, a policy that polices arrivals but ignores departures feels arbitrary.
5. Overtime: when it starts and who approves it
- Threshold: overtime usually starts after the scheduled hours, sometimes with a small buffer (e.g. 15–30 minutes) so a few extra minutes finishing a task don't count.
- Approval: say whether overtime must be approved in advance, or can be claimed afterwards and approved by a manager.
- Record it separately from normal hours so it can be paid or given back as time off correctly.
6. Missed punches and corrections
People forget to clock out. Your policy should say how to fix it: who can request a correction, the deadline (for example, within 3 working days), and who approves it. Keep the original record and the correction together, so there is always an honest trail of what changed and who approved it.
7. Remote days, leave and holidays
Say how work-from-home days are requested and recorded, and make sure approved leave and public holidays never show up as absences. Nothing erodes trust in an attendance system faster than being marked absent on an approved day off.
8. Consequences, fairly applied
Describe what happens when the rules are broken — a conversation first, then written warnings — and apply it consistently. Allow for genuine exceptions such as medical appointments or emergencies.
Putting the policy into practice
The best policy fails if it's applied by hand. Whatever tool you use, it should calculate each rule the same way for everyone, show employees their own record, and let managers approve corrections without spreadsheets. In DeskAttend, every rule above is a setting: grace period, early-leave tolerance, half-day and full-day hours, and the overtime threshold, with corrections and work-from-home handled through approval requests.