Define the basics in one page
Start time, end time, break rules, late thresholds, absence reporting line. One page. If it takes more, the policy is doing too many jobs and people stop reading at the second. The one-page constraint is not a stylistic preference; it is the only test that reliably produces a policy people actually internalise. Anything beyond the basics goes into a separate process document or a manager's handbook.
Triggers and conversations, not points
Modern policies have moved away from rigid point systems toward trigger-based conversations: 'after X absences in Y weeks, your manager will have a structured conversation.' Lower tribunal risk, better retention, same outcome. Point systems create a sense that absences are a transactional currency, which damages culture; trigger-based conversations preserve the manager's discretion within a documented framework. The Bradford Factor and similar metrics can still be used as triggers, but they should not be the policy.
How time is recorded
Be explicit: which system records time, how to report exceptions, who signs off. Ambiguity here is the single biggest cause of payroll disputes. A named system, a named approver, a named cadence. If the policy says 'time is recorded in the time system', specify which system, where to find it, and what to do when it is down. Specificity prevents the 'I didn't know' defence in any subsequent dispute.
Sickness and self-certification
Up to 7 calendar days, employees self-certify (Form SC2 or equivalent); beyond 7 days, a fit note is required. State the company's expectations for sickness reporting (who, when, by what channel) and the consequences of not following them. Be careful with the consequences — repeated short absences with no fit note evidence are a performance conversation, not a disciplinary issue, and treating them as the latter creates Equality Act risk.
Long-term absence and return-to-work
The policy should reference the return-to-work conversation (mandatory after any absence) and the long-term-absence process (occupational health referral after 4 weeks). The conversations are what reduce repeat absence; the policy just sets the expectation. The Equality Act 2010 duty to make reasonable adjustments applies throughout, and the policy should mention it explicitly to demonstrate awareness.
Annual leave and TOIL interaction
Cross-reference the holiday policy and the TOIL/overtime policy. Employees should not have to read three documents to understand what to do when they want a day off. A single sentence — 'see the holiday policy for annual leave and the time-tracking policy for TOIL' — closes the loop without duplicating the content.
Review and version control
Date the policy, version it, and review it annually. Publish the change log to the team so they can see what changed. The shift from 'document' to 'product' is the single most underrated improvement in HR policy management — and it costs nothing.
An attendance policy is a contract for how the team works. Make it short, make it fair, and back it with a system people trust — and the policy mostly enforces itself.