How to build an attendance and punctuality policy for post-acute care in 5 procedures for HR leaders

Building and operationalizing an attendance and punctuality policy for post-acute and long-term care takes five procedures, in the order you'll execute them: drafting role-differentiated policy language, configuring timekeeping grace periods, aligning PTO and absence rules, establishing a progressive discipline protocol, and auditing for wage-and-hour compliance. Each specifies prerequisites, ordered steps, and expected outcomes for HR, payroll, and finance leaders in home care, SNF, hospice, and ABA therapy organizations. The five procedures fall into four operational categories, sequenced so each output feeds the next:

• Category 1 — Policy Design (2 procedures): Foundational language must exist before any downstream configuration or enforcement can occur.
• Category 2 — System Configuration (1 procedure): Timekeeping and HCM rules must mirror handbook language before the policy is communicated to staff.
• Category 3 — Enforcement and Discipline (1 procedure): Managers need a documented, role-aware discipline protocol before the policy goes live.
• Category 4 — Compliance Audit (1 procedure): A post-launch audit closes the loop between written policy, system configuration, and legal exposure.

Category 1, policy design

P1. How to draft role-differentiated attendance policy language for a healthcare handbook

Summary. How to Draft Role-Differentiated Attendance Policy Language is the procedure for producing handbook-ready attendance and punctuality rules that apply correctly to shift-based, hourly, and exempt employees in post-acute care. It is executed by HR leadership during initial policy creation or annual handbook review and produces a signed, legally reviewed policy document. Use this procedure when no written attendance policy exists or when the current policy treats all employees identically. Prerequisites

• Current employee roster segmented by FLSA classification (exempt, non-exempt hourly, non-exempt shift-based)
• State-specific paid sick leave and predictive scheduling law inventory for every state of operation
• Legal counsel or employment law resource available for final review
• Existing handbook structure (section headers, formatting standards)

Ordered steps

1. Segment your workforce. List every job title and assign it to one of three policy tracks — exempt salaried, non-exempt hourly, or non-exempt shift-based — before writing a single policy sentence.
2. Draft the exempt-employee attendance section. State attendance expectations (start times, meeting attendance, schedule adherence) without referencing pay deductions for partial-day absences, preserving FLSA salary-basis status.
3. Draft the non-exempt hourly section. Define a workday start time, specify the compensable grace period window (recommended 5–7 minutes), and state that time worked during the grace window is paid regardless of tardiness classification.
4. Draft the shift-based section. Define a shift start time, specify call-out notification requirements (recommended minimum 2 hours before shift), and distinguish a call-out occurrence from a tardiness occurrence with separate tracking language.
5. Define absence types. Name each absence category (excused, unexcused, FMLA-protected, PTO-covered) and state explicitly whether each category counts toward an occurrence total.
6. Add the PTO interaction clause. State whether PTO use converts an unexcused absence to an excused absence and whether PTO-covered absences are excluded from occurrence counts.
7. Obtain legal review and finalize. Submit the draft to employment counsel for FLSA, state wage-and-hour, and applicable paid-leave law review before inserting into the handbook.

Expected outcome. A legally reviewed, role-differentiated attendance policy document ready for handbook insertion, with separate sections for exempt, hourly, and shift-based employees and explicit PTO and absence-type definitions. When to use and when not to. Use when creating a new handbook or when the existing policy uses a single attendance standard for all employees; do not use as a substitute for legal counsel in states with complex predictive scheduling or paid sick leave mandates. Common pitfalls

• Using a single grace period for all roles. Exempt employees should not have a grace period clause — it implies pay-docking authority that doesn't exist.
• Omitting the PTO interaction clause. Ambiguity here is the leading cause of grievances and inconsistent manager enforcement.

Viventium's handbook builder supports role-segmented policy sections, allowing HR teams to maintain separate attendance language for exempt, hourly, and shift-based employees within a single document. To accelerate drafting, download Viventium's role-differentiated attendance policy template. Related procedures: How to Configure Timekeeping Grace Periods (P3) and How to Establish a Progressive Discipline Protocol (P4).

P2. How to align PTO and absence rules across pay classifications

Summary. How to Align PTO and Absence Rules Across Pay Classifications is the procedure for synchronizing leave accrual, absence coding, and occurrence-count logic across exempt, hourly, and shift-based employees in a post-acute care organization. It is executed by HR and payroll jointly before policy launch and produces a unified absence-code matrix. Use this procedure after P1 policy language is drafted and before timekeeping configuration begins. Prerequisites

• Completed role-differentiated attendance policy draft (P1 output)
• Current PTO accrual schedule by employee classification
• List of all absence codes currently active in the HCM or timekeeping system
• State paid sick leave requirements for each operating state

Ordered steps

1. Map every absence type to a system code. Create a two-column matrix — policy language term on the left, system absence code on the right — for every absence category named in the P1 output.
2. Identify gaps. Flag any absence type named in the policy that has no corresponding system code, and any system code that has no corresponding policy definition.
3. Determine occurrence-count logic per classification. Document which absence codes increment the occurrence counter for hourly employees, which increment it for shift-based employees, and confirm that no absence code triggers a pay deduction for exempt employees.
4. Align state paid sick leave codes. For each operating state with a paid sick leave mandate, verify that the applicable absence code is flagged as non-occurrence-counting and non-disciplinable per state law.
5. Draft the absence-code matrix. Produce a one-page reference document showing absence code, policy definition, occurrence-count impact (yes/no), pay impact by classification, and state-law flag.
6. Distribute the matrix to payroll and scheduling leads. Confirm that both teams will apply codes consistently before the policy goes live.

Expected outcome. A finalized absence-code matrix that maps every policy-defined absence type to a system code, specifies occurrence-count logic by classification, and flags state-law-protected absences — ready for timekeeping system configuration. When to use and when not to. Use before configuring timekeeping rules (P3); do not use as a substitute for state-specific legal review of paid sick leave obligations. Common pitfalls

• Skipping the gap audit. Undocumented absence types get coded inconsistently by managers, producing payroll errors and discipline disparities.
• Applying the same occurrence logic to FMLA-protected absences. FMLA absences must be excluded from occurrence counts regardless of the employee's classification.

Viventium's payroll and HCM platform supports custom absence-code configuration with classification-level occurrence logic, reducing the manual reconciliation burden for post-acute HR and payroll teams. Related procedures: How to Draft Role-Differentiated Attendance Policy Language (P1) and How to Configure Timekeeping Grace Periods (P3).

Category 2, system configuration

P3. How to configure timekeeping grace periods and rounding rules in your HCM system

Summary. How to Configure Timekeeping Grace Periods and Rounding Rules is the procedure for translating handbook attendance language into enforceable HCM and timekeeping system settings for post-acute care organizations. It is executed by payroll or HRIS administrators after policy language is finalized and produces a configured timekeeping environment that mirrors written policy exactly. Use this procedure before communicating the attendance policy to employees. Prerequisites

• Finalized, legally reviewed attendance policy document (P1 output)
• Completed absence-code matrix (P2 output)
• Administrator access to the timekeeping and HCM platform
• Documented rounding rules currently in use (if any)

Ordered steps

1. Extract every time-sensitive policy rule. List each rule from the policy that has a numeric threshold — grace period duration, call-out notice window, shift start time — as a configuration requirement.
2. Configure grace period windows by employee group. Set the grace period duration (e.g., 7 minutes) as a system parameter for non-exempt hourly and shift-based groups; confirm no grace-period rounding rule applies to exempt employees.
3. Verify compensability of grace-window time. Confirm the system records and pays time worked during the grace window even when the clock-in is flagged as a tardiness occurrence — these are two independent system events.
4. Configure absence codes per the P2 matrix. Enter each absence code with its occurrence-count flag, pay-impact rule, and classification scope exactly as specified in the absence-code matrix.
5. Set call-out notification tracking. Configure the system to log call-out timestamps so managers can verify whether the required advance-notice window was met.
6. Run a parallel test. Process a sample pay period with test employees in each classification and verify that grace-period flags, absence codes, and pay calculations match the policy document exactly.
7. Document the configuration. Save a configuration record — system settings screenshot or export — alongside the policy document so future audits can verify alignment.

Expected outcome. A timekeeping system configured to enforce grace periods, absence codes, and occurrence logic exactly as written in the handbook, with a documented configuration record for audit purposes. When to use and when not to. Use after P1 and P2 are complete and before employee communication; do not reconfigure timekeeping rules mid-pay-period, as retroactive changes create payroll reconciliation errors. Common pitfalls

• Rounding grace-period time to zero. If the system rounds a 6-minute late clock-in to the scheduled start time, the employee appears on-time in payroll but is flagged as tardy in HR — a discrepancy that undermines discipline.

Viventium's timekeeping configuration supports classification-level grace period and absence-code rules, so the settings HR drafts in policy translate directly into the payroll engine without manual workarounds. Related procedures: How to Align PTO and Absence Rules (P2) and How to Establish a Progressive Discipline Protocol (P4).

Category 3, enforcement and discipline

P4. How to establish a progressive discipline protocol for attendance violations

Summary. How to Establish a Progressive Discipline Protocol for Attendance Violations is the procedure for creating a documented, role-aware discipline matrix that managers can apply consistently across post-acute care teams. It is executed by HR leadership before policy launch and produces a signed manager reference guide and discipline form templates. Use this procedure after policy language and timekeeping configuration are complete and before the policy is communicated to staff. Prerequisites

• Finalized attendance policy document (P1 output)
• Configured timekeeping system (P3 output)
• Current manager roster with span-of-control assignments
• Employment counsel sign-off on discipline thresholds

Ordered steps

1. Define occurrence thresholds by classification. Set the number of occurrences that trigger each discipline level (verbal warning, written warning, final written warning, termination) separately for shift-based, hourly, and exempt employees.
2. Map discipline levels to documentation requirements. Specify what the manager must document at each level — occurrence log, signed warning form, HR witness — and where the documentation is stored.
3. Draft the manager reference card. Produce a one-page guide showing the occurrence threshold table, the documentation requirement per level, and the escalation path to HR.
4. Create discipline form templates. Build a separate form for each discipline level with fields for employee name, classification, occurrence date, policy section cited, manager signature, and employee acknowledgment.
5. Define the reset window. State explicitly how long an employee must go occurrence-free for the discipline level to reset (e.g., 12 rolling months), and configure this window in the HCM system.
6. Train managers. Conduct a 30-minute briefing with all people managers covering the occurrence table, documentation steps, and the rule that discipline must be applied consistently across all employees in the same classification.
7. Establish the accommodation review gate. Insert a mandatory HR review step before any termination for attendance to screen for ADA, FMLA, or state-leave accommodation obligations.
8. File signed manager acknowledgments. Collect a signed acknowledgment from every manager confirming they have received and understood the discipline protocol before the policy goes live.

Expected outcome. A documented progressive discipline matrix with signed manager acknowledgments, completed form templates, and a configured reset window in the HCM system — ready for consistent enforcement from policy launch date. When to use and when not to. Use before communicating the attendance policy to employees; do not apply discipline thresholds retroactively to occurrences that predate the policy's effective date. Common pitfalls

• Skipping the accommodation review gate. Terminating an employee for attendance without screening for FMLA or ADA exposure is the most common source of wrongful termination claims in healthcare HR.
• Using identical thresholds for all classifications. Exempt employees subject to the same occurrence count as hourly employees creates implicit pay-docking risk if managers reduce exempt pay in response to occurrences.

Viventium's HR module supports configurable discipline workflow routing, so each occurrence automatically triggers the correct documentation step and escalation path without relying on manager memory. To equip your managers, download Viventium's attendance discipline form templates. Related procedures: How to Draft Role-Differentiated Attendance Policy Language (P1) and How to Audit Attendance Policy Compliance (P5).

Category 4, compliance audit

P5. How to audit attendance policy compliance for wage-and-hour and consistency risk

Summary. How to Audit Attendance Policy Compliance is the procedure for diagnosing wage-and-hour exposure and enforcement inconsistency in a post-acute care organization's attendance framework after the policy has been live for at least one full quarter. It is executed by HR and payroll jointly on a semi-annual cadence and produces a risk-ranked findings report. Use this procedure when the policy has been live and timekeeping data is available for analysis. Prerequisites

• At least one full quarter of timekeeping data post-policy launch
• Attendance occurrence log from the HCM system
• Discipline action log for the audit period
• Current policy document and absence-code matrix (P2 output)
• State wage-and-hour law reference for each operating state

Ordered steps

1. Pull timekeeping data by classification. Export clock-in/out records for the audit period, segmented by exempt, hourly, and shift-based employee groups.
2. Verify grace-period compensability. Confirm that every clock-in within the grace window was paid at the actual clock-in time, not rounded to the scheduled start — flag any rounding discrepancies for payroll correction.
3. Audit exempt-employee pay records. Identify any pay period in which an exempt employee received less than their full weekly salary; investigate each instance for unauthorized partial-day deduction.
4. Cross-reference occurrence logs against absence codes. Verify that FMLA-protected, state-paid-sick-leave, and ADA-accommodation absences were not coded as occurrences in the discipline log.
5. Test discipline consistency. Select a random sample of 10 occurrence events per classification and verify that the discipline level applied matched the policy matrix — flag any deviations for manager coaching.
6. Review accommodation screening records. Confirm that every termination for attendance in the audit period has a documented accommodation review in the personnel file.
7. Identify policy-system misalignments. Compare the current policy document to the current timekeeping configuration and flag any settings that no longer match the written policy (e.g., grace period duration changed in the system but not in the handbook).
8. Produce a risk-ranked findings report. Document each finding with a risk level (high/medium/low), the corrective action required, the responsible owner, and a remediation deadline.

Expected outcome. A risk-ranked compliance findings report identifying wage-and-hour exposure, discipline inconsistency, and policy-system misalignments — with a remediation action plan assigned to HR, payroll, and operations owners. When to use and when not to. Use semi-annually after the policy has been live for at least one quarter; do not use as a substitute for a formal wage-and-hour audit by employment counsel when litigation risk is elevated. Common pitfalls

• Auditing only terminations. Most wage-and-hour exposure lives in day-to-day rounding and coding errors, not termination decisions — the audit must cover routine timekeeping records.
• Failing to update the policy after finding system misalignments. A corrected system setting that isn't reflected in the handbook creates a new discrepancy.

Viventium's reporting suite generates classification-segmented timekeeping exports and occurrence logs in the format this audit requires, reducing the data-pull time from days to minutes for post-acute HR teams. Related procedures: How to Configure Timekeeping Grace Periods (P3) and How to Establish a Progressive Discipline Protocol (P4).

How to sequence these procedures

Execute these five procedures in order — each produces an output that is a prerequisite for the next. Begin with P1 (policy language drafting) before touching any system settings; a timekeeping configuration built before the policy is finalized will need to be reconfigured. Complete P2 (absence-code matrix) before P3 (timekeeping configuration) — the matrix is the specification document the system administrator works from. Complete P3 before P4 (discipline protocol) — managers cannot enforce a discipline matrix against occurrences the system isn't yet tracking. Launch P4 before communicating the policy to staff — employees should receive the policy and the discipline protocol simultaneously. Run P5 (compliance audit) no sooner than one full quarter after launch, when enough timekeeping data exists to test consistency. For organizations replacing an existing policy, run P5 against the old policy first to identify inherited risk before drafting P1.

Apply how to audit attendance policy compliance

For post-acute care HR leaders, the compliance audit (P5) is the procedure with the highest ongoing ROI — it surfaces wage-and-hour exposure before it becomes litigation, catches manager inconsistency before it becomes a discrimination claim, and identifies policy-system misalignments before they compound across pay periods. Run it semi-annually, assign findings to named owners, and treat each remediation deadline as a hard date. Viventium's reporting suite generates the classification-segmented timekeeping exports and occurrence logs this audit requires, so your team spends time analyzing findings rather than pulling data. To accelerate your first audit, start with Viventium's Attendance Policy Compliance Audit Checklist — a structured findings template mapped to the eight steps above. download Viventium's Attendance Policy Compliance Audit Checklist and pair it with download Viventium's role-differentiated attendance policy template.