A missed absence call can become a compliance problem long before a leave administrator reviews the file. Understanding what triggers FMLA eligibility helps employers identify potential protected leave at the first report, gather the right facts, and route the case before attendance points, scheduling decisions, or delayed notices create unnecessary risk.
The Family and Medical Leave Act does not apply to every employer, employee, or absence. Eligibility depends on a sequence of facts: whether the employer is covered, whether the employee meets service and hours requirements, whether the employee works at an eligible location, and whether the reported reason may qualify for FMLA leave. For enterprise leave operations, each fact should be captured consistently at intake and validated through a documented workflow.
What Triggers FMLA Eligibility?
FMLA eligibility is often described as an employee taking time away from work for a serious health condition. That description is incomplete. A health-related absence may signal a possible FMLA event, but the employee must also meet statutory eligibility requirements and work for a covered employer.
In practice, a potential FMLA case is triggered when an absence report contains information that could indicate a qualifying reason. The employer then has a duty to assess coverage and eligibility, provide required notices when appropriate, and request certification or other documentation within the applicable process. Employees do not need to use the words “FMLA leave” to start that process.
A report such as “I will be out for surgery,” “my spouse was hospitalized,” or “my doctor has restricted me from working” should not be treated as an ordinary call-off. It should be escalated for leave review. The intake team’s role is not to make a legal determination on the call. Its role is to capture accurate, timely information that allows the leave administrator to make one.
Start With Employer Coverage
A private-sector employer is generally covered by FMLA when it employed 50 or more employees for at least 20 workweeks in the current or preceding calendar year. The 20 workweeks do not need to be consecutive.
Public agencies are covered regardless of employee count. Public and private elementary and secondary schools are also covered regardless of the number of employees. Because coverage is employer-specific, organizations with multiple locations, entities, or shared-service operations should maintain clear ownership rules for FMLA administration.
Coverage is only the first gate. A covered employer may still have employees who are not individually eligible based on tenure, work hours, or worksite size.
The 12-Month Employment Requirement
An employee generally must have worked for the employer for at least 12 months. Those months do not need to be consecutive. Prior employment can count in many circumstances, although a break in service of seven years or more may limit credit for previous service unless an exception applies, such as a written agreement or service obligations under the Uniformed Services Employment and Reemployment Rights Act.
This requirement can create confusion after rehires, acquisitions, payroll conversions, or internal transfers. Accurate employment-history data matters. A leave team should be able to verify dates of service rather than relying solely on a manager’s recollection or an employee’s estimate.
The 1,250-Hour Requirement
The employee must also have worked at least 1,250 hours during the 12 months immediately before the leave begins. These are actual hours worked under Fair Labor Standards Act principles. Paid vacation, holidays, sick time, and other nonworking paid leave generally do not count toward the 1,250-hour threshold.
For nonexempt employees, timekeeping records usually provide the starting point. For exempt staff, employers may need another reliable method to establish hours worked if eligibility is disputed. Inconsistent data across timekeeping, payroll, and HR systems can delay an eligibility determination and complicate a response to an absence that requires prompt action.
The 50 Employees Within 75 Miles Rule
An otherwise qualified employee must work at a location where the employer has at least 50 employees within 75 miles. The measurement is not simply the number of employees assigned to one building. It involves the worksite and other employer worksites within the 75-mile radius, measured by surface miles over public streets, highways, waterways, and airways.
This rule is particularly relevant to distributed operations, field teams, remote employees, and organizations with small satellite locations. The designated worksite for a remote employee is generally the office to which the employee reports or from which assignments are made, not the employee’s home. Employers should have a consistent, documented method for identifying worksites before a high-volume absence event occurs.
A Qualifying Reason Must Also Be Present
Meeting the employer and employee thresholds does not automatically mean an absence is FMLA-protected. The requested leave must be for a qualifying reason. Common qualifying reasons include the birth of a child; placement of a child for adoption or foster care; bonding with a new child; the employee’s own serious health condition; or care for a spouse, child, or parent with a serious health condition.
FMLA also provides qualifying exigency leave related to a covered military member’s deployment. Military caregiver leave may allow an eligible employee to take up to 26 workweeks in a single 12-month period to care for a covered servicemember with a serious injury or illness. The applicable family relationships, documentation rules, and leave calculations can differ from standard FMLA administration.
Not every illness, appointment, or family emergency meets the definition of a serious health condition. A qualifying condition may involve inpatient care, incapacity plus continuing treatment, pregnancy-related limitations, chronic conditions, or other circumstances defined by regulation. Employers should avoid making assumptions based on a diagnosis label or the length of a single absence.
Notice Is the Operational Trigger
Employees generally must provide enough information for an employer to recognize that leave may be covered. For foreseeable leave, they should provide 30 days’ notice when practicable. When leave is unforeseeable, notice should be given as soon as practicable and in line with the employer’s usual call-in procedures, absent unusual circumstances.
The standard is not perfect wording. A caller who says, “I cannot work because my migraine condition has flared up again,” may provide enough information to require further FMLA review, especially if prior certified intermittent leave exists. A caller who says only, “I’m sick,” may require follow-up depending on known facts and the employer’s absence history.
This is why Day 1 absence reporting should use structured questions rather than a generic message-taking script. The goal is to record the reported reason, expected duration, treating-provider or hospitalization information when voluntarily provided, whether the condition involves the employee or a covered family member, prior leave status, and any immediate schedule or safety impacts. Intake specialists should follow client-approved escalation solutions and avoid requesting medical details that are unnecessary for the initial report.
Certification Confirms the Leave, Not the First Call
Once an employer has enough information to identify a potential qualifying event, it can request medical certification. Certification helps confirm whether the condition qualifies, the expected frequency and duration of leave, and any work restrictions. It does not erase the value of timely intake.
A delayed report can affect notice deadlines, payroll coding, staffing plans, disability coordination, and attendance administration. Conversely, treating every absence as approved FMLA before eligibility and certification are evaluated can create avoidable operational confusion. The disciplined approach is to flag the case promptly, issue the appropriate notices, track outstanding documentation, and apply the final determination consistently.
Build Intake Around Facts, Timing, and Escalation
For large employers and third-party administrators, the difference between a compliant process and an inconsistent one often comes down to the first contact. A 24/7 live-answered absence channel can capture an overnight hospitalization, weekend injury, or early-morning call-off when the facts are freshest. Structured intake can then send the event to the right HR, leave, claims, or safety workflow without waiting for manual transcription.
A dependable process should distinguish between a potential FMLA trigger and a final approval. It should also preserve a timestamped record of what the employee reported, when the report was received, who received it, and what escalation followed. These records support leave administration, workforce planning, and defensible compliance decisions.
Actec Systems applies this discipline to Day 1 absence reporting and FMLA intake by operating as an extension of the client’s established workflow, with trained specialists, configurable escalation paths, and structured data capture designed for action rather than simple message transfer.
FMLA decisions require careful application of the law, employer policy, and the facts of each case. The most useful operational discipline is simple: when an absence report suggests protected leave, capture it completely, escalate it quickly, and let a documented leave process determine the outcome before a routine call-off becomes a preventable compliance issue.