Closing The Loops
Notes on compliance, operations, and the work between the work.

FMLA Doesn't Create Chaos. Disconnected Work Does.

A supervisor on the production floor sees a "no-call, no-show" for the third time this month.

The attendance policy is clear. The employee has hit the point limit. The supervisor walks to HR and says, "We need to let them go. They're killing our line."

The HR manager looks at the file. She sees a medical certification for intermittent FMLA filed three weeks ago. She knows the termination is a legal landmine. The supervisor had no idea.

The supervisor didn't fail. The system failed.

The Belief We're Attacking

Most companies believe that FMLA creates chaos. Intermittent leave is unpredictable. It's hard to track. It disrupts the production line.

That's not accurate.

FMLA doesn't create chaos. It creates obligations. The chaos comes from disconnected work. The supervisor manages attendance. HR manages leave. These two systems don't talk to each other. The gap between them is where the chaos — and the liability — lives.

The EEOC consistently reports that retaliation is the most common charge filed. In manufacturing, these charges often start with attendance-based terminations that should never have happened.

What Actually Goes Wrong

The Supervisor Doesn't Know

The most common FMLA failure in manufacturing is simple: the supervisor doesn't know the employee has protected leave.

Intermittent leave is especially tricky. According to Unum, approximately 35% of all FMLA leaves involve intermittent absences. These are unpredictable — sometimes just an hour or two at a time.

A supervisor sees a pattern of absences. They see a person who "keeps calling out." They apply the attendance policy. They don't know they're disciplining someone for a protected absence.

The Data Gap Is the Risk

The Department of Labor requires employers to provide specific notices at specific times. The eligibility notice must be sent within five business days. The rights and responsibilities notice must be sent with the eligibility notice. The designation notice must be sent within five business days of sufficient information.

These are deadlines. Deadlines require action. If the supervisor's data and HR's data aren't connected, those deadlines get missed. And missed deadlines are evidence of a broken process.

The "Micro-Absence" Problem

Intermittent leave creates micro-absences. Two hours here. Three hours there. These are harder to manage than a continuous leave because they don't look like "leave." They look like "tardiness" or "partial absence."

If the system only tracks the total hours used, it misses the context. It misses the fact that these micro-absences are protected. It misses the pattern that suggests a chronic condition.

The Story

Here's what a connected FMLA process looks like:

An employee calls in sick. The system checks for an active FMLA certification. If one exists, the absence is automatically flagged as protected. The supervisor sees a notification: "This employee has active intermittent FMLA leave. This absence is covered."

The system tracks the hours used against the certification. It alerts HR when recertification is needed. It flags patterns that deviate from the certification — like absences that always happen on Fridays — so the employer can use their recertification rights.

The supervisor manages the floor. HR manages the compliance. The system connects them.

The Insight

FMLA doesn't create chaos. Disconnected work does.

Every absence is an employee event. Every employee event creates obligations. Every obligation has a deadline. If the person who sees the absence isn't connected to the person who manages the obligations, the loop stays open.

An open loop is where the chaos lives.

Where InfraNet Fits

InfraNet HR is not an FMLA hour tracker. It's an event-driven platform that connects the moment an employee calls in sick to the FMLA certification, the notice deadlines, and the supervisor's attendance view.

When an absence is reported, InfraNet checks for protections, routes the notification, and ensures the supervisor knows what they need to know — without exposing the employee's medical details.

The system doesn't replace HR. It makes sure the handoff between the floor and the office never breaks.


FMLA didn't create the chaos. The gap between the floor and the office did.

See how InfraNet HR connects attendance data to FMLA compliance.

Sources: