The 7 FMLA Data Patterns That Trigger a DOL Audit

When the Department of Labor investigates an FMLA complaint, the investigator isn't hunting for general sloppiness. They're looking for specific patterns in your records: late notices, leave balances that don't add up, a leave year applied one way for some people and another way for others. Each pattern maps to a regulation, and each one can be found in your own HRIS before anyone else finds it.

This article is for HR operations, leave administrators and HRIS owners who want to see their FMLA data the way a Wage and Hour Division (WHD) investigator would, and fix what they find.

Key takeaways

• Most FMLA investigations start with an employee complaint, then widen to see whether the same problem affected other people.
• The two notice deadlines that trip employers up most are both five business days: the eligibility notice and the designation notice.
• Inconsistency is the red flag. A leave year method, tracking increment or notice practice that varies by manager looks systemic, not accidental.
• FMLA records must be kept for at least three years, and willful violations can be pursued for three years, so a 36-month lookback is a sensible self-audit window.
• Every pattern below can be surfaced with a query, not a manual file review.

How do DOL FMLA investigations usually start?

The Wage and Hour Division enforces the FMLA. Under 29 U.S.C. 2617(b), the Secretary of Labor is required to receive and investigate complaints of FMLA violations, using the same process WHD uses for minimum wage and overtime complaints. That's why the most common starting point is a current or former employee who believes their leave rights were violated.

A complaint-driven investigation is targeted at first. The investigator knows which employee and which leave period to look at. But they rarely stop there. If the same late notice or the same rounding problem shows up in one file, they'll pull more files to see whether it's a practice. Complaints are not the only route in, as our article on what triggers compliance audits explains.

The recordkeeping rule also tells you something. Under 29 CFR 825.500, the DOL generally can't require you to submit FMLA records more than once in any 12-month period unless it has reasonable cause to believe a violation exists or is investigating a complaint. In practice, that means your records will be read closely when it matters most: after someone has already complained.

Timing matters too. An FMLA lawsuit generally must be filed within two years of the last event in the alleged violation, or within three years if the violation was willful (29 U.S.C. 2617(c)). That's the reason this article uses a 36-month lookback for every query below. If you want a broader view of how WHD investigations run, from the opening conference to the closing conference, see our guide to responding to a DOL Wage and Hour investigation.

What are the 7 FMLA data patterns investigators look for?

Pattern 1: Designation notices issued more than 5 business days after you had enough information

What the investigator sees: The date you received a completed medical certification (or otherwise had enough information to decide whether leave qualifies) and the date you issued the Designation Notice (WH-382). When the gap is longer than five business days, it stands out.

The rule: 29 CFR 825.300(d)(1) requires the designation notice within five business days of having enough information to determine whether leave is FMLA-qualifying, absent extenuating circumstances. You only need one designation notice per qualifying reason in each applicable 12-month period, but that first one has to be on time.

Why it matters: If your HRIS doesn't record the exact date you had sufficient information, investigators will reconstruct it from email timestamps, fax logs or scanned certification dates. They usually can.

Fix: Make "certification received" a required, date-stamped event before a case can move to designation. Set an alert at business day three. For historical cases, calculate the gap between certification receipt and designation for the past 36 months and write a short explanation for any case over five business days.

Pattern 2: Leave balances that don't reconcile, especially for intermittent leave

What the investigator sees: A leave ledger where designated hours, hours taken and hours remaining don't add up. Intermittent leave is where this usually breaks: two hours on Tuesday, three on Thursday, recorded inconsistently or rounded up by the time system.

The rule: Under 29 CFR 825.205(a)(1), you must track intermittent or reduced-schedule leave in an increment no greater than the shortest period you use for other forms of leave, and never more than one hour. An employee's entitlement may not be reduced by more than the leave actually taken, and you can't charge FMLA leave for time the employee was working.

Why it matters: If your time and attendance system rounds an absence up to a half day, the ledger overcharges the employee every time. That's a straightforward overcharge of FMLA leave, and it often affects every intermittent case at once.

Fix: Confirm the increment your HRIS uses matches your policy and the rule. Check that the time system passes exact time to the leave ledger. Reconcile each case against the employee's entitlement, which is 12 times their normal workweek (480 hours for someone who regularly works 40 hours a week). Correct any overcharges and tell the employee in writing.

Pattern 3: A leave year method applied inconsistently

What the investigator sees: Some employees' 12 weeks measured against the calendar year, others against a rolling 12 months, others from the date their first leave began.

The rule: 29 CFR 825.200 lets you choose one of four methods: the calendar year, any fixed 12-month leave year, 12 months measured forward from the first FMLA leave, or a rolling 12 months measured backward from each date leave is used. Whatever you choose must be applied consistently and uniformly to all employees. To change methods you must give at least 60 days' notice, and if you never selected a method, the one most favorable to each employee applies.

Why it matters: Variation suggests nobody is controlling the setting, or worse, that the method is chosen case by case.

Fix: Write your method into your FMLA policy and enforce it as a system-level setting, not a per-case field. If you run leave in Workday, it helps to understand how leave types and time off plans are configured, since that's where the 12-month period is usually defined. Recalculate a sample of recent cases using your stated method and send any case where an employee lost leave to counsel.

Pattern 4: Missing or late eligibility and rights notices

What the investigator sees: Leave that was approved and designated with no Notice of Eligibility and Rights and Responsibilities (WH-381) on file, or a WH-381 dated well after leave began.

The rule: 29 CFR 825.300(b)(1) requires the eligibility notice within five business days of the employee's request or of the employer learning the leave may qualify, absent extenuating circumstances. Under 825.300(c), the rights and responsibilities notice must go out each time the eligibility notice does. If leave has already started, it should be mailed to the employee's address of record.

Why it matters: Under 825.300(e), failing to give required notices may count as interference with FMLA rights. Remedies can include lost pay and benefits, other monetary losses, and equitable relief such as reinstatement. If an employee was never told about their rights, any attendance points or discipline during that period become very hard to defend.

Fix: Make WH-381 issuance a mandatory, date-stamped step before a case can be classified as FMLA. Cross-check every designated case from the past 36 months against your notice log.

Pattern 5: Asking for more medical information than FMLA allows

What the investigator sees: Custom certification forms, emails or HR notes asking for information beyond what the rules permit, such as full medical records sent directly by a physician or details about conditions unrelated to the current leave.

The rule: 29 CFR 825.306 lists what a certification may include: the provider's contact details, when the condition started and how long it will likely last, the medical facts supporting the need for leave, and information about the employee's ability to work or the need for intermittent or reduced-schedule leave. The medical facts may include symptoms, diagnosis, hospitalization and treatment. What you can't do is require information beyond what 825.306 through 825.308 specify, and the information must relate only to the serious health condition behind the current leave request.

Why it matters: This shows up most in organizations that built their own forms instead of using the optional DOL forms (WH-380-E for the employee's own condition, WH-380-F for a family member). Over-collection also creates a confidentiality problem, because 825.500(g) requires FMLA certifications and medical histories to be kept as confidential medical records, separate from regular personnel files.

Fix: Compare every certification form in your workflow against WH-380-E and WH-380-F. Have counsel review custom forms. Confirm medical documents are stored in a restricted location, not attached to the general employee profile.

Pattern 6: Similar employees treated differently

What the investigator sees: Two employees in similar situations, same department and similar leave reason, where one got proper notices and protection and the other got attendance points, a poor review or a termination during or after leave.

Why it matters: This is the pattern most likely to support an interference or retaliation claim. Investigators may compare FMLA records with discipline, performance reviews and terminations. A common example: an employee with several intermittent leave periods gets a performance improvement plan citing "reliability." That's a high-risk fact pattern even if the manager meant well. Our article on whether you can fire someone while they're on medical leave covers where the legal lines sit.

Fix: Compare post-leave discipline, review scores and terminations for employees who took FMLA leave against a similar group that didn't, controlling for department and tenure. Also check notice issuance rates by manager. Gaps there usually point to individual managers who aren't routing leave requests to HR.

Pattern 7: Records disposed of before the three-year mark

What the investigator sees: A request for records from a specific period and a response that they no longer exist.

The rule: 29 CFR 825.500(b) requires FMLA records to be kept for at least three years. Under 825.500(c), those records include basic payroll and identifying information, the dates FMLA leave was taken, hours of leave when taken in less than full days, copies of notices given to or by the employer, benefit and leave policy documents, premium payment records, and records of any dispute over designation.

Why it matters: Missing records leave you unable to prove you did things right. The usual cause isn't deliberate destruction. It's an automatic purge rule or a system migration that left old leave cases behind.

Fix: Confirm no archive or deletion job touches FMLA records inside three years. If you migrated systems recently, check that pre-migration cases are present and searchable. When state rules call for longer retention, see our guide to resolving conflicting records retention rules across states.

What should you be ready to produce on day one?

Requests vary by case, but if you build your self-audit around these categories, you'll be ready for most of them:

• A list of employees who requested or took FMLA leave in the review period, with start and end dates
• Copies of the notices issued to them (WH-381, WH-382, and any military family leave forms)
• Medical certifications received, kept in their separate confidential file
• Your written FMLA policy as it stood during the period, including your leave year method
• Time and payroll records for those employees
• Discipline and termination records for employees who took leave
• Records of any FMLA-related complaint or designation dispute

If you can produce these quickly and completely, without rebuilding them by hand, you're in a much better position. Slow or partial production invites more follow-up requests and more scrutiny.

Which HRIS queries should you run for a self-audit?

Pattern	Query logic	Flag when
1. Late designation	Join certification received date to designation notice date for all cases in 36 months	Gap over 5 business days
2. Balance math	For intermittent cases: entitlement minus hours taken minus hours remaining	Result isn't zero, or increments over 1 hour
3. Leave year	Group cases by the leave year method applied	Any case not using the stated method
4. Missing notices	Left join designations to the notice log on employee ID and leave ID	No WH-381, or WH-381 dated more than 5 business days after request
5. Medical over-collection	List all forms and document types attached to leave cases	Custom forms or records stored in the general personnel file
6. Disparate treatment	Compare discipline, review scores and terminations for leave takers vs. a matched group	Meaningful difference by group or manager
7. Retention	Find the earliest FMLA case still in the system	Earliest case is newer than 36 months, but you had leave before then

A common mistake is running these once and stopping. The better habit is a quarterly run, with results sent to the leave administrator and HR leadership. If your HRMS handles leave natively, many of these checks can be built as saved reports; we explain the setup options in how an HRMS improves leave and attendance management.

Frequently asked questions

How far back does a DOL FMLA investigation look?

There's no single fixed window, but two rules set practical limits. Employers must keep FMLA records for at least three years, and an FMLA claim generally must be brought within two years of the last violation, or three years if the violation was willful. That's why most self-audits review the past 36 months.

What penalties apply to FMLA violations?

The FMLA's only civil money penalty is for willfully failing to post the required general notice, and it's adjusted for inflation each year. Most exposure comes from remedies instead: back pay, lost benefits, other monetary losses and equitable relief such as reinstatement. Retaliation and interference findings can also feed private lawsuits by affected employees.

Can we ask for a diagnosis on an FMLA certification?

The regulation allows the medical facts on a certification to include symptoms, diagnosis, hospitalization and treatment. What you can't do is require information beyond what 29 CFR 825.306 through 825.308 specify, or information unrelated to the condition behind the current leave. Using the DOL's optional WH-380-E and WH-380-F forms is the simplest way to stay inside those limits.

What to do next

• Run the seven queries in the table above against the past 36 months of leave data and log every exception with an owner.
• Lock your leave year method and tracking increment as system settings, and add a business-day-three alert for both notice deadlines.
• Audit where medical certifications are stored and move any that sit in general personnel files.
• Send any case where an employee may have lost leave or faced discipline during leave to counsel before you change the record.

This article is general information, not legal advice. Talk to employment counsel about your specific facts.

Sources

• 29 CFR 825.300: Employer notice requirements, Legal Information Institute, Cornell Law School
• 29 CFR 825.200: Amount of leave and the 12-month period, Legal Information Institute, Cornell Law School
• 29 CFR 825.205: Increments of FMLA leave for intermittent or reduced schedule leave, Legal Information Institute, Cornell Law School
• 29 CFR 825.306: Content of medical certification for leave, Legal Information Institute, Cornell Law School
• 29 CFR 825.500: Recordkeeping requirements, Legal Information Institute, Cornell Law School
• 29 U.S.C. 2617: Enforcement, Legal Information Institute, Cornell Law School

Last reviewed: October 2026.