How to classify and enforce absences in post-acute and long-term care, 5 procedures for HR leaders

Classifying and enforcing absence policies in post-acute and long-term care comes down to five procedures, organized in execution sequence: policy design, point-of-absence classification, documentation and medical review, FMLA intersection safeguards, and progressive discipline. Each specifies prerequisites, ordered steps, and expected outcomes for HR, payroll, and operations leaders at home care, home health, hospice, SNF, and ABA therapy organizations.

Policy design

Absence enforcement is only defensible if the written policy defines every category before any occurrence is recorded. This category contains one procedure, and it runs before any timekeeping code is applied.

How to draft an absence classification policy for post-acute care teams

How to Draft an Absence Classification Policy is the procedure for establishing written definitions and rules for excused, unexcused, unplanned, and protected absences in a post-acute or long-term care organization. It is executed by HR leadership during initial policy build or annual review and produces a signed, distributed policy document. Use this procedure before any attendance-point or discipline system is launched. Prerequisites

• Current employee handbook and any existing attendance policy language
• List of applicable leave laws (FMLA, state sick leave, ADA) for each operating state
• Shift structure and scheduling model (shift-based, per-visit, salaried) for each care setting
• Input from payroll on how absence types map to pay codes in the HCM system

Ordered steps

1. Define absence categories. Draft written definitions for excused, unexcused, unplanned, unauthorized, and protected (FMLA/ADA) absences, including partial-shift and early-departure thresholds.
2. Specify qualifying reasons. List the reasons that convert an unplanned absence to an excused one (e.g., documented illness, bereavement, jury duty, approved PTO) and the documentation required for each.
3. Set the occurrence unit. Define what constitutes one "occurrence," including whether a partial shift (e.g., departing 2+ hours early) counts as a full or half occurrence, and document the threshold in writing.
4. Map absence types to pay codes. Coordinate with payroll to confirm each absence category has a corresponding pay code in the HCM/payroll system so classification decisions flow directly into accurate pay processing.
5. Incorporate leave-law carve-outs. Add explicit language stating that FMLA-designated, ADA-accommodated, and state-protected absences are excluded from attendance-point accrual and discipline eligibility.
6. Define the notice and call-out procedure. Specify how employees must report an absence, the deadline for notification, and the consequence for failing to follow the procedure.
7. Distribute and obtain acknowledgment. Publish the policy in the employee handbook, deliver it to all active staff, and retain signed acknowledgments in each personnel file.

Expected outcome: A signed, distributed absence classification policy that defines every absence category, maps each to a pay code, and includes leave-law carve-outs. Use this when: Launching a new attendance program, or when existing policy language is ambiguous or inconsistently applied. Do not use it as a substitute for legal review in states with complex paid-sick-leave mandates. Common pitfalls

• Defining categories without pay-code mapping. Classification decisions that don't reach payroll create coding errors and wage-and-hour exposure. Align HR and payroll definitions before publishing.
• Omitting partial-shift rules. In 24/7 care settings, early departures are frequent. A policy silent on partial shifts will be applied inconsistently by floor supervisors.

How Viventium supports this step: Viventium's HCM platform supports configurable absence pay codes that mirror policy categories, so classification decisions made by HR flow directly into payroll without manual recode. To set up categories in the system, see the Viventium Absence & Attendance Configuration Guide — configure absence pay codes in Viventium. Related procedures: How to Classify an Absence at the Point of Occurrence · How to Apply FMLA Safeguards to an Attendance Program

Classification and documentation

Point-of-absence classification and documentation review are the two operational steps that determine pay coding and discipline eligibility. This category contains two procedures: one for the supervisor at the moment of absence, one for HR in the days that follow.

How to classify an absence at the point of occurrence

How to Classify an Absence at the Point of Occurrence is the procedure for assigning the correct absence category — excused, unexcused, unplanned, or protected — at the moment an employee fails to report or leaves early in a post-acute or long-term care setting. It is executed by the direct supervisor or charge nurse during the shift and produces a documented, pay-coded absence record. Prerequisites

• Published absence classification policy (see P1) accessible to supervisors
• HCM or timekeeping system access for the supervisor on shift
• Call-out log or absence reporting tool (app, call-out line, or paper log)
• Knowledge of which employees have active FMLA or ADA accommodations on file

Ordered steps

1. Receive and log the absence report. Record the employee's name, scheduled shift, time of notification (or time absence was discovered if no call-out occurred), and the reason stated by the employee.
2. Apply the policy's category definitions. Match the stated reason and documentation status against the written policy to assign a preliminary category: excused, unexcused, unplanned, or flag for protected-leave review.
3. Check for active leave designations. Verify in the HCM system whether the employee has an active FMLA certification, ADA accommodation, or state-leave designation before assigning an unexcused or unplanned code.
4. Enter the absence code in the timekeeping system. Record the appropriate pay code immediately so the shift record is accurate for payroll processing — use a "pending review" code if protected-leave status is unconfirmed.
5. Notify HR of any absence requiring documentation follow-up. Flag absences where the employee provided no reason, where a pattern is emerging, or where a protected-leave trigger may apply.
6. Document the supervisor's classification rationale. Record in the absence log why the preliminary category was assigned, including any statements made by the employee — this note is the first line of defense in a discipline dispute.

Expected outcome: A timestamped, pay-coded absence record in the timekeeping system with a documented classification rationale, ready for HR documentation review and payroll processing. Use this when: Every absence event at the shift level. Do not treat it as the final classification when a protected-leave trigger or extenuating-circumstance claim is present. Common pitfalls

• Coding "unexcused" before checking active FMLA designations. This is the most common source of FMLA retaliation claims. Always check leave status before assigning a punitive code.
• Skipping the "pending review" code. When protected-leave status is unclear, a "pending" code preserves accuracy while HR completes review.

How Viventium supports this step: Viventium's timekeeping module supports supervisor-level absence coding with a configurable "pending HR review" status, preventing premature unexcused designations from flowing into payroll. Related procedures: How to Draft an Absence Classification Policy · How to Conduct a Documentation and Extenuating-Circumstance Review

How to conduct a documentation and extenuating-circumstance review

How to Conduct a Documentation and Extenuating-Circumstance Review is the procedure for evaluating employee-submitted documentation — including doctor's notes, personal statements, and third-party verification — before finalizing an absence classification or initiating discipline in a post-acute or long-term care organization. It is executed by HR within 3–5 business days of the absence and produces a final classification decision with a documented rationale retained in the personnel file. Prerequisites

• Preliminary absence record from the supervisor (P2 output)
• Employee-submitted documentation (doctor's note, court summons, written statement, or other)
• Written policy specifying which documentation types qualify for excused status
• Knowledge of any active FMLA certification, ADA accommodation, or state-leave designation for the employee

Ordered steps

1. Request documentation within the policy window. Contact the employee in writing to request supporting documentation within the timeframe in the policy (typically 3–5 business days from return to work).
2. Evaluate the documentation against policy criteria. Assess whether the submitted documentation meets the policy's stated requirements for excused status — a doctor's note confirms a provider visit but does not automatically trigger excused classification unless the policy says so.
3. Assess for FMLA or ADA trigger. Determine whether the absence reason, duration, or pattern suggests a serious health condition or disability. If yes, initiate the P4 FMLA safeguard procedure before finalizing classification.
4. Evaluate extenuating circumstances. If the employee cites extraordinary circumstances (domestic emergency, natural disaster, acute family crisis), document the claim and apply the policy's standard consistently — compare to how similar claims were handled for other employees.
5. Make and document the final classification decision. Record the final absence category (excused, unexcused, or protected), documentation reviewed, and rationale. Retain the record in the personnel file.
6. Update the timekeeping and payroll record. Change any "pending review" codes to the final classification and confirm the correct pay code is applied before payroll closes.
7. Notify the employee of the final classification. Communicate the decision in writing, including whether attendance points were assessed and whether the employee has a right to appeal under the policy.

Expected outcome: A finalized absence classification with documented rationale, updated timekeeping record, and written notification to the employee. Use this when: Documentation was submitted, a protected-leave trigger was flagged in P2, or the employee cited extenuating circumstances. Do not use it as the routine point-of-absence step. Related procedures: How to Classify an Absence at the Point of Occurrence · How to Apply FMLA Safeguards to an Attendance Program

Compliance safeguards and enforcement

FMLA intersection and progressive discipline are the highest-risk steps. They require their own procedures to prevent protected-leave miscoding and wrongful-discipline exposure.

How to apply FMLA safeguards to a post-acute care attendance program

How to Apply FMLA Safeguards to a Post-Acute Care Attendance Program is the procedure for identifying, designating, and excluding FMLA-qualifying absences from attendance-point accrual and disciplinary eligibility in a care organization. It is executed by HR whenever an absence pattern or employee statement suggests a qualifying serious health condition and produces a documented FMLA designation decision that protects the organization from retaliation liability. Prerequisites

• Active FMLA policy and employee eligibility data (12 months of employment, 1,250 hours worked, 50+ employees within 75 miles)
• Absence records flagged for potential FMLA review from P2 or P3
• DOL-issued FMLA Notice of Eligibility and Rights (Form WH-381) and Certification of Health Care Provider (Form WH-380-E or WH-380-F)
• HCM system access to apply FMLA pay codes and exclude designated absences from attendance-point calculations

Ordered steps

1. Identify the FMLA trigger. Determine whether the absence reason, duration (3+ consecutive days), or pattern (recurring absences tied to a chronic condition) meets the threshold for FMLA notice — the employer's obligation begins when it has reason to believe a qualifying condition may exist.
2. Provide Notice of Eligibility within 5 business days. Deliver DOL Form WH-381 to the employee within 5 business days of learning the absence may be FMLA-qualifying, regardless of whether the employee used the words "FMLA."
3. Issue the appropriate certification form. Provide the applicable health care provider certification form (WH-380-E for employee's own condition, WH-380-F for family member) and allow the statutory 15-calendar-day return window.
4. Review the completed certification. Assess whether the certification establishes a serious health condition as defined by the FMLA. If incomplete, send one written request for clarification within 7 days.
5. Designate the leave in writing. Issue a written FMLA Designation Notice (DOL Form WH-382) within 5 business days of receiving sufficient certification, specifying whether leave is continuous, intermittent, or reduced-schedule.
6. Apply FMLA pay codes in the HCM system. Update all past and future absences covered by the designation to the FMLA pay code and remove any attendance points assessed for those absences.
7. Exclude designated absences from discipline eligibility. Confirm in the employee's discipline record that no step in the progressive discipline procedure was triggered by an FMLA-designated absence. Reverse any steps that were.
8. Document the full designation timeline. Retain all notices, certifications, and designation decisions in a confidential medical file separate from the personnel file, as required by the FMLA's confidentiality rules.

Expected outcome: A documented FMLA designation decision with all required notices issued, attendance points corrected, and a confidential medical file established. Use this when: Any absence pattern or employee statement suggests a serious health condition, even if the employee doesn't request FMLA by name. Do not use it for absences that clearly don't involve a health condition or family care need. Common pitfalls

• Waiting for the employee to request FMLA. The employer's designation obligation is triggered by knowledge of a qualifying condition, not by the employee's request — failure to designate is an FMLA interference violation.
• Failing to retroactively correct attendance points. Points assessed before a designation is made must be removed from the record once the designation is confirmed.

How Viventium supports this step: Viventium's absence management workflows include configurable FMLA pay codes and designation-status flags that automatically exclude protected absences from attendance-point calculations, reducing manual correction risk. Related procedures: How to Conduct a Documentation and Extenuating-Circumstance Review · How to Execute Progressive Discipline for Unexcused Absenteeism

How to execute progressive discipline for unexcused absenteeism in care settings

How to Execute Progressive Discipline for Unexcused Absenteeism is the procedure for applying a consistent, documented sequence of disciplinary steps when an employee accumulates unexcused absences beyond the policy threshold in a post-acute or long-term care organization. It is executed by HR in coordination with the direct supervisor and produces a defensible discipline record that supports termination if the threshold is reached. Prerequisites

• Finalized absence classification records from P2 and P3 (no pending or protected-leave flags)
• Written progressive discipline policy specifying the point thresholds for each disciplinary step
• Confirmation from P4 that no absences in the employee's record are FMLA- or ADA-designated
• HR and supervisor alignment on the employee's current point total and discipline history

Ordered steps

1. Confirm the point total and absence record. Pull the employee's complete absence history from the HCM system and verify all records are finalized, correctly coded, and free of protected-leave designations before calculating the discipline-eligible point total.
2. Identify the applicable discipline step. Match the employee's point total to the progressive discipline schedule in the policy (e.g., verbal warning at 3 points, written warning at 5, final written at 7, termination at 9) and confirm no prior steps were skipped.
3. Conduct the discipline meeting. Schedule a private meeting with the employee and their direct supervisor, present the absence record, state the policy threshold that has been reached, and issue the appropriate written notice.
4. Document the meeting and employee response. Record the date, attendees, points discussed, disciplinary step issued, and any response or explanation offered — have the employee sign the notice or document refusal to sign.
5. Provide the employee a copy and retain the original. Give the employee a copy of the discipline notice at the meeting; retain the signed original in the personnel file with the supporting absence records.
6. Set the review period and next threshold. Communicate the next point threshold that would trigger the following disciplinary step and the review period (if any) during which points may be reduced — document this in writing so the employee has clear notice.

Expected outcome: A signed discipline notice in the personnel file, supported by finalized absence records and a documented meeting. Use this when: Only after P3 documentation review is complete and P4 FMLA/ADA safeguards have been applied. Do not initiate discipline while any absence carries a "pending review" or protected-leave flag. Common pitfalls

• Skipping discipline steps. Inconsistent application of the progressive schedule (e.g., jumping from verbal to termination) is the most common basis for wrongful-termination claims. Follow the schedule exactly.
• Disciplining without a clean absence record. Initiating discipline before all pending-review and protected-leave flags are resolved creates FMLA retaliation and ADA discrimination exposure.

How Viventium supports this step: Viventium's HR module supports point-balance tracking and discipline-step logging so HR leaders at SNFs, home health agencies, and ABA therapy organizations can generate a complete, audit-ready absence and discipline record at any step in the process. Related procedures: How to Apply FMLA Safeguards to a Post-Acute Care Attendance Program · How to Draft an Absence Classification Policy for Post-Acute Care Teams

How to sequence these procedures

Execute these five procedures in order — each depends on the output of the one before it. Begin with P1 (policy design) before any absence is recorded; a classification system applied without a written policy is unenforceable. Once the policy is published, P2 (point-of-absence classification) runs at the shift level every time an absence occurs. When an employee submits documentation or cites extenuating circumstances, P3 (documentation review) runs within 3–5 business days of return. If P2 or P3 flags a potential FMLA trigger, pause classification and run P4 (FMLA safeguards) before finalizing any code or discipline step. Only after P3 is complete and P4 has cleared the record should P5 (progressive discipline) be initiated. Running P5 before P3 and P4 are resolved is the single most common source of FMLA retaliation and wrongful-termination claims in post-acute care.

Apply the absence classification policy

For HR leaders at post-acute and long-term care organizations, the absence classification policy is the foundation every other procedure in this guide depends on. Without written definitions, point thresholds, and leave-law carve-outs in place before the first occurrence is recorded, every downstream classification and discipline decision is legally exposed. Viventium supports care organizations in building absence policies that map directly to HCM pay codes — so the decision an HR leader makes in P1 flows automatically into payroll accuracy and audit-ready records in P5. To configure absence categories and pay codes in Viventium's platform, see the Viventium Absence & Attendance Configuration Guide. To build the FMLA designation workflow that protects your attendance program, see the Viventium FMLA Tracking and Designation Workflow Guide.

• Viventium Absence & Attendance Configuration Guide — configure absence pay codes in Viventium
• Viventium FMLA Tracking and Designation Workflow Guide — configure FMLA designation tracking in Viventium