How to build a fair attendance policy with 5 procedures for post-acute and long-term care HR leaders

Building and enforcing a fair attendance policy in post-acute and long-term care comes down to five procedures: designing the policy, tracking occurrences, communicating with your workforce, monitoring attendance, and applying progressive discipline. Each specifies prerequisites, ordered steps, and expected outcomes for HR, payroll, and operations leaders at home care, home health, hospice, SNF, assisted living, and ABA therapy organizations.

The three operational categories

The 5 procedures group into three categories that must be executed in sequence:

• Policy Foundation, 2 procedures that establish the rules and structure before enforcement can occur.
• Activation and Monitoring, 2 procedures that launch the policy and create the data structure for tracking compliance.
• Enforcement and Protection, 1 procedure that applies consequences consistently and excludes legally protected absences.

Policy foundation

How to design a fair attendance policy for care operations

Start by turning attendance expectations into measurable rules HR can enforce consistently. This procedure is used during initial policy creation or annual review and produces a written attendance policy. Use it when launching a new policy or replacing an inconsistently applied legacy policy. Prerequisites

• Current employee handbook and any existing attendance language
• Legal review access
• Time-and-attendance or scheduling system capable of tracking occurrences by employee
• Input from operations and clinical leadership on care-line coverage requirements

Ordered steps

1. Define absenteeism and tardiness. Establish objective thresholds, such as absence = any full missed shift and tardiness = arrival more than 7 minutes after scheduled start.
2. Select a tracking model. Choose occurrence-based tracking or percentage-of-scheduled-hours tracking, and document the rationale.
3. Set occurrence thresholds. Specify the number of occurrences that trigger each disciplinary step, using a rolling 12-month window.
4. Draft protected-leave carve-outs. Exclude FMLA-qualifying absences, ADA-accommodated absences, workers' compensation leave, and applicable state protected leave from occurrence counts.
5. Define the absence notification procedure. Specify how far in advance care staff must call out, who they must notify, and what documentation is required for extended absences.
6. Specify documentation requirements. State what records HR and managers must retain, including occurrence logs, written warnings, and employee acknowledgments, and specify the retention period per policy and applicable law.
7. Route the draft for legal review. Submit the policy to employment counsel before finalizing.
8. Obtain executive sign-off. Secure approval from HR and operations leadership before publishing.

Expected outcome: A signed, legally reviewed attendance policy ready for workforce distribution, with occurrence thresholds, notification procedures, and protected-leave carve-outs defined. When to use / not to use: Use when creating a new policy or replacing an unenforced legacy policy. Don't use as a substitute for legal counsel in states with complex protected-leave stacking rules, such as California, New York, and Illinois. Common pitfalls

• Setting thresholds without legal review. Occurrence counts that penalize protected absences create significant legal exposure.
• Ignoring care-line variation. A policy may treat a home health aide's no-call-no-show differently from an administrative employee's late arrival, but that choice must be documented.

Viventium's HR compliance resources include an attendance policy design checklist for post-acute and long-term care operators. Related procedures: How to Communicate the Attendance Policy to the Workforce; How to Monitor Attendance Using Scheduling and Payroll Data.

How to establish an occurrence-based tracking system

After the policy is written, HR and payroll need a neutral way to count absences. This procedure configures a point-based absence tracking process and produces a live occurrence log tied to each employee's record. Prerequisites

• Finalized attendance policy with defined occurrence thresholds
• Access to time-and-attendance, scheduling, or payroll system with occurrence-tracking capability
• Defined roles for who enters occurrences
• Employee roster segmented by care line and location

Ordered steps

1. Configure occurrence categories. Set up absence types, such as unscheduled absence, tardiness, early departure, and no-call-no-show, with policy-based point values.
2. Set the rolling window. Configure a rolling 12-month calculation, not a calendar-year reset.
3. Map protected-leave flags. Ensure FMLA, ADA, and state-leave designations automatically exclude flagged absences from occurrence counts.
4. Assign entry accountability. Document who logs each occurrence type: manager, HR, or automated system pull.
5. Establish threshold alerts. Notify HR and the direct manager when a care staff member reaches 50%, 75%, and 100% of each disciplinary threshold.
6. Run a baseline audit. Pull occurrence data for the prior 90 days to identify employees already near threshold.
7. Test with a pilot location. Run the system for 30 days at one site before full rollout.

Expected outcome: A live occurrence-tracking system that flags threshold breaches, excludes protected absences, and produces an auditable log per employee. When to use / not to use: Use when launching an occurrence-based policy or moving from spreadsheets. Don't use if scheduling and payroll systems can't be integrated, since manual tracking requires a different configuration. Common pitfall: Failing to map protected-leave flags before go-live. Occurrences logged before leave flags are configured may need manual reversal, which can undermine manager confidence. Viventium's payroll and time-and-attendance platform supports occurrence-based tracking with automated threshold alerts, making this configuration executable without a separate HR system. See occurrence-based tracking configuration. Related procedures: How to Design a Fair Attendance Policy for Care Operations; How to Monitor Attendance Using Scheduling and Payroll Data.

Activation and monitoring

How to communicate the attendance policy to the workforce

A policy is not enforceable if employees never received it or managers cannot explain it. This procedure distributes the policy, answers questions, and collects acknowledgments across care lines and locations. Prerequisites

• Finalized, legally reviewed attendance policy document
• Employee roster by location and care line, including part-time and per-diem staff
• Confirmed communication channels
• Manager briefing scheduled before employee rollout

Ordered steps

1. Brief managers first. Explain thresholds, the notification procedure, and manager logging responsibilities before employees receive the policy.
2. Distribute the policy document. Push the policy through the employee self-service portal for office-based and hybrid staff; provide paper copies with supervisor signature for field-based home care and home health aides.
3. Conduct a live Q&A session. Hold a brief all-hands or team-level meeting, virtual acceptable for distributed care staff, to walk through the key elements and answer questions.
4. Collect signed acknowledgments. Require every employee to sign or digitally acknowledge receipt and understanding, and retain the acknowledgment in the employee file.
5. Document non-respondents. Flag employees who have not acknowledged within 14 days and escalate to their manager.
6. Update the employee handbook. Publish the policy in the current handbook and note the effective date.
7. Confirm new-hire onboarding inclusion. Verify that the policy is included in orientation and acknowledgment is collected on Day 1.

Expected outcome: 100% of active employees have received, reviewed, and signed the attendance policy; acknowledgments are filed; managers are prepared to apply it consistently from the effective date. When to use / not to use: Use at every policy launch or material revision. Don't treat a handbook update alone as sufficient communication. Common pitfalls

• Skipping the manager briefing. Managers who learn the policy with their staff cannot answer questions and may apply it inconsistently.
• Excluding per-diem and agency staff. Per-diem employees are subject to the same attendance expectations; excluding them creates enforcement gaps.

Viventium's employee self-service portal supports digital policy acknowledgment collection, giving HR a timestamped, auditable record of every employee's receipt confirmation. See digital policy acknowledgment. Related procedures: How to Establish an Occurrence-Based Tracking System; How to Monitor Attendance Using Scheduling and Payroll Data.

How to monitor attendance using scheduling and payroll data

Once the policy is live, HR needs a weekly review rhythm. This procedure uses scheduling and payroll data to identify threshold breaches, absence patterns, and discrepancies before payroll closes. Prerequisites

• Occurrence-tracking system configured and live
• Scheduling and payroll systems integrated or exportable to a common report
• Defined report recipients
• Baseline occurrence data established

Ordered steps

1. Pull the weekly exception report. Extract all unscheduled absences, tardiness events, and no-call-no-shows from the prior 7 days by location and care line.
2. Flag threshold-proximity employees. Identify care staff at 75% or above of any disciplinary threshold and notify their manager.
3. Identify pattern absences. Review Monday/Friday, post-holiday, overnight, or weekend patterns that may signal scheduling or morale issues.
4. Cross-reference payroll data. Confirm flagged absences appear correctly in the current pay period's time records. Discrepancies indicate a data-entry or sync error that must be corrected before payroll runs.
5. Review protected-leave flags. Verify that any absence flagged for FMLA or ADA accommodation is correctly excluded from the occurrence count before any discipline begins.
6. Distribute the report. Send the exception report to location managers and operations leadership with a summary of employees approaching or at threshold.
7. Document the review. Log the date, reviewer, and actions taken in the HR system.

Expected outcome: A weekly exception report distributed to operations leadership, with threshold-proximity employees flagged, patterns identified, and payroll-scheduling discrepancies resolved before the pay cycle closes. When to use / not to use: Use weekly once the policy is live. Don't substitute monthly reporting, since one week of unmonitored absences can create a coverage gap that requires agency fill-in before HR is aware. Viventium's integrated payroll and time-and-attendance platform surfaces attendance exception data in the same workflow as payroll processing, eliminating the manual cross-reference step that causes discrepancies in disconnected systems. See attendance exception reporting. Related procedures: How to Apply Progressive Discipline for Attendance Policy Violations; How to Establish an Occurrence-Based Tracking System.

Enforcement and protection

How to apply progressive discipline for attendance policy violations

Discipline should begin only when the confirmed occurrence count reaches a policy threshold. This procedure gives managers and HR a consistent process for delivering and filing each step. Prerequisites

• Attendance policy with defined disciplinary thresholds in effect
• Occurrence log showing the employee's current count and threshold reached
• Confirmation that no flagged absences in the count are FMLA-, ADA-, or state-leave-protected
• HR business partner available to review the action before delivery
• Disciplinary notice templates (verbal warning, written warning, final written warning, termination)

Ordered steps

1. Confirm the occurrence count. Pull the employee's current occurrence log and verify the count against the policy threshold.
2. Screen for protected absences. Review every absence with HR to confirm none qualify for FMLA, ADA, or state-leave protection. Remove any that do and recalculate the count. Reference the DOL FMLA employer guide for federal designation requirements.
3. Select the correct disciplinary step. Match the confirmed count to the policy's ladder: verbal → written → final written → termination.
4. Prepare the disciplinary notice. Complete the template with the employee's name, occurrence dates, threshold reached, and next threshold.
5. Conduct the disciplinary meeting. Deliver the notice privately with the manager and an HR witness; explain the threshold, consequences of further occurrences, and the employee's right to respond.
6. Obtain the employee's signature. Have the employee sign acknowledging receipt, not agreement. If the employee refuses, document the refusal with the witness present.
7. File the notice. Retain the signed notice in the personnel file and enter the action date in the tracking system.
8. Set a follow-up reminder. Schedule a 30-day check-in to review whether attendance has improved.

Expected outcome: A signed, filed disciplinary notice delivered at the correct threshold, with a record that supports any later discipline or termination decision. When to use / not to use: Use at every threshold breach without exception. Don't use this procedure to discipline an employee whose absences are predominantly FMLA- or ADA-protected without first consulting employment counsel. Common pitfalls

• Delivering discipline before screening for protected leave. Disciplining an employee for protected absences is an actionable error; the screening step is non-negotiable.
• Allowing managers to delay action at their discretion. Every threshold breach must trigger the next step on the same timeline for all employees.

Viventium's HR compliance support includes disciplinary notice templates calibrated for post-acute and long-term care environments, with built-in FMLA/ADA screening prompts to reduce protected-leave errors at the point of discipline. See progressive discipline notice templates. Related procedures: How to Monitor Attendance Using Scheduling and Payroll Data; How to Design a Fair Attendance Policy for Care Operations.

How to sequence these procedures

These five procedures are stage-dependent. Begin with P1 (Design), since no other procedure is executable without a finalized policy. Move to P2 (Occurrence-Based Tracking) in parallel with or immediately after P1, because the system must be configured before the policy goes live. Execute P3 (Communication) only after both P1 and P2 are complete, so care staff receive a policy that is already trackable. Activate P4 (Monitoring) on the effective date and run it weekly. Reserve P5 (Progressive Discipline) for employees who reach a documented threshold in P4's exception reports. Never initiate discipline before the data confirms the threshold and protected-leave screening is complete.

Apply the monitoring procedure as the operational linchpin

For HR and payroll leaders at post-acute and long-term care organizations, the monitoring procedure (P4) is the operational linchpin of the entire attendance framework. A well-designed policy that is never monitored produces no behavioral change and no legal protection. Weekly exception reporting, cross-referenced against payroll data before each pay cycle, converts a policy document into an enforcement system. Viventium's integrated payroll and time-and-attendance platform makes this procedure executable without manual data exports or spreadsheet reconciliation. To implement P4 in your organization, start with Viventium's attendance exception reporting configuration guide in the Viventium HR Resource Center, and see integrated payroll and scheduling data on the Viventium Payroll + Time & Attendance Integration page. This piece is an operational reference, not legal advice. State-specific protected-leave stacking, particularly in California, New York, and Illinois, requires jurisdiction-specific employment counsel.