1
Define the scope and covered employee groups
Insert your company name and specify which employee categories fall under the policy β full-time, part-time, casual, and contractors if applicable. Confirm whether the policy applies to remote and hybrid workers.
π‘ If remote workers are covered, add a sentence clarifying that availability during core hours constitutes 'attendance' for the purpose of this policy.
2
Set your absence categories and definitions
Review the draft definitions for unplanned absence, authorised absence, unauthorised absence, lateness, and no-call/no-show. Adjust the language to match the terminology already used in your employment contracts and employee handbook.
π‘ Consistency with your employment contract terminology prevents employees from arguing that a policy term means something different from the contract.
3
Specify notification requirements in detail
Enter the exact notification deadline (e.g., 30 minutes before shift start), the required contact method (phone call to direct manager), and the fallback if the manager is unreachable.
π‘ Name a specific backup contact (e.g., the department head or HR inbox) for when the line manager cannot be reached β vague fallback instructions are the most common source of first-day notification disputes.
4
Set the self-certification and medical certificate thresholds
Enter the number of days after which a medical certificate is required. The common range is 4β8 calendar days. Confirm who receives the certificate β HR, the line manager, or both.
π‘ Aligning your threshold with statutory sick pay rules in your jurisdiction avoids administrative duplication and signals to employees that the policy is built around compliance, not surveillance.
5
Configure trigger points for management review
Insert the specific numbers for your trigger thresholds β separate absence episodes within a rolling period and total days in a 12-month window. Consider adding a pattern-based trigger (e.g., repeated absence on specific days).
π‘ Pilot the trigger thresholds against last year's absence data before publishing β if more than 20% of your workforce would have hit a trigger, the thresholds are too low.
6
Map the progressive discipline stages
Confirm the number of formal stages and the conditions for escalation. Insert the retention periods for each warning β typically 6 months for a verbal warning, 12 months for a written warning.
π‘ Reference your disciplinary policy or employee handbook here rather than restating the full procedure β this prevents the two documents from falling out of sync.
7
Add the return-to-work interview requirement and attach the RTW form
Confirm that a return-to-work interview is required after all absences (or absences exceeding a minimum duration) and reference the RTW form template managers should use.
π‘ Making the RTW interview mandatory for all absences β not just those over three days β reduces recurrence rates measurably without increasing management burden significantly.
8
Set the policy review date and assign ownership
Enter the last-reviewed date, the next scheduled review date (typically 12 months), and the name or role responsible for maintaining and updating the policy.
π‘ Calendar a reminder 30 days before the review date so the update is never reactive β post-incident rewrites carry less legal weight than proactively maintained policies.