Leave Management Software for FMLA Tracking: The Twelve Things It Has to Do, How to Test Them in a Demo, and How to Choose a Vendor (2026)

What should leave management software do for FMLA tracking?

Leave management software that can carry FMLA and state leave has to do twelve things a vacation tracker does not. It must test eligibility at the moment of the request (12 months of service, 1,250 hours in the prior 12 months, 50 employees within 75 miles), count the 12 workweeks in hours against the employee's actual schedule under the 12-month method the employer has chosen, and handle intermittent and reduced-schedule leave in the smallest increment the employer uses for other leave, never more than one hour. It must run the notice clock: eligibility and rights notice within five business days, 15 calendar days for certification with a seven-day cure, a designation notice within five business days of enough information, recertification on a lawful cadence. It must store medical documents apart from the personnel file, designate FMLA, state leave, disability pay and PTO substitution on the same absence at once, apply the state law for the employee's work location, run the return with fitness-for-duty and reinstatement, keep protected absences out of attendance and performance counts, log who did what and when, and report usage per employee for the full window. Test each in a live demo before buying.

Why FMLA breaks a tool built for vacation

A vacation tracker is a ledger. It holds a balance in days, subtracts approved requests, adds accruals, and rolls over at year end. Every design decision follows from that: the unit is the day, the event is the request, the state is approved or not, and the report is a balance. FMLA fits none of those shapes, and the mismatch is not cosmetic.

The unit is wrong first. FMLA entitlement is 12 workweeks, which the regulations convert to hours against the employee's normal schedule, so a person who works 30 hours a week has 360 hours and a person who works 50 has 600. A two-hour absence for a therapy appointment has to reduce that figure by exactly two hours, and a week in which the schedule changed has to be recomputed. Most balance-based tools can be persuaded to hold hours, but they cannot recompute a week that has already been deducted when the schedule behind it changes.

The window is wrong second. Under the rolling backward method that most employers choose, the balance on any given day is 12 workweeks minus every hour of FMLA leave taken in the 12 months before that day. That number changes every day without anyone touching it, because hours used a year ago fall out of the window as the calendar moves. A tool that resets on January 1 or on the anniversary date can only model the two simpler methods, and cannot answer the question a manager actually asks, which is how many hours does this employee have left today and when do the used hours come back.

The lifecycle is wrong third. A vacation request has two states. An FMLA case has a dozen: requested, eligibility checked, notice sent, certification requested, certification received or incomplete, cure period running, designated or denied, in progress, recertification due, return scheduled, fitness-for-duty received, closed. Each transition has a deadline the regulations set and the Department of Labor enforces, and each is a document the employer must be able to produce three years later. A tool with no concept of a case, only of a request, forces all of that into email and a spreadsheet, which is where the missed deadlines live.

The visibility rule is wrong last, and it is the one that produces lawsuits. Protected leave may not be counted under a no-fault attendance policy and may not be held against an employee in a performance review or a layoff selection. A tool that shows managers one list of absences, with FMLA hours sitting next to unexcused ones, makes interference the path of least resistance. The software has to know which absences are protected and keep them out of the counts managers see, not because the manager is malicious but because the attendance report will otherwise do the counting for them.

The twelve requirements

What follows is the list against which to score any tool, whether it is an HRIS module, a dedicated leave platform or the portal your disability carrier offers. Each requirement is a thing the regulations demand of the employer; the software either carries it or leaves it to a person. The table gives the requirement, the rule behind it and the demo question that exposes it; the paragraphs after the table say why each one matters in practice.

Three of the twelve, the notice engine, the segregated medical file and the attendance firewall, are the ones most often missing from tools that call themselves leave management. If a vendor cannot show all three, the rest of the evaluation can stop.

Requirements one to four: getting the arithmetic right

Eligibility is decided as of the date the leave would start, not the date of the request, and it has three parts that come from three different systems: months of service from the HR record, hours worked from payroll or timekeeping, and headcount within 75 miles from the location data. Software that cannot see all three will either ask HR to type the answer, which is fine at 60 employees and untenable at 600, or will skip the test and designate leave for people who were never eligible, which quietly extends the entitlement beyond what the law requires and is very hard to undo.

The 12-month method is a policy choice the employer makes once, in writing, and must apply uniformly. The software has to support all four methods because the employer may already have chosen one, and it has to show the balance under that method on any date, past or future. The test is simple: ask for the balance of an employee who took four weeks eleven months ago, today and again in six weeks. Under rolling backward the two numbers differ; under calendar year they may not. A tool that gives the same answer under both is not modeling the window.

Hours against schedule is where part-time and variable-hour employees break most tools. The regulation is explicit that a person who normally works 30 hours has an entitlement of 360 hours, and that where the schedule varies the average of the previous 12 months is used. The software has to hold the schedule, recompute the entitlement when the schedule changes, and handle a holiday week correctly (a holiday inside a full week of leave counts against the entitlement; a holiday inside a partial week does not).

Intermittent leave is the single largest source of tracking errors. The increment rule says leave is counted in the smallest increment the employer uses for any other form of leave, and never more than one hour, so a 20-minute late arrival for a treatment can only be charged as 20 minutes if the employer rounds other leave to the quarter hour or finer. The tool has to record the actual duration, apply the employer's increment, deduct from the hour balance, and attach the absence to the certified condition so that the pattern can be compared with the certification's stated frequency. The free intermittent tracker linked from this article does that in a spreadsheet for a small headcount; past a few dozen open cases it needs a database.

Requirements five to eight: the case, not the request

The notice engine is the heart of an FMLA system. From the day the employer learns of a possibly qualifying need it has five business days to send the eligibility notice and rights and responsibilities notice; the employee then has at least 15 calendar days to return a certification; an incomplete one triggers a written list of deficiencies and a seven-day cure period; once the employer has enough information it has five business days to send the designation notice. Recertification may be requested on a cadence the regulations limit. Each of those is a dated document and a countdown. Software that models them as tasks with due dates, generates the notices from templates, and records when each was sent and received turns the most litigated part of the FMLA into a checklist. Software that does not leaves it to whoever remembered.

Medical confidentiality is a hard rule. Certifications and any other medical information have to be kept in files separate from the personnel record, with access limited to those who need it: the leave administrator, and where relevant the supervisor for restrictions, first aid staff and government officials investigating compliance. In software terms that means a document store with its own permissions, not an attachment on the employee profile that every manager with profile access can open. Ask to see the permission model, not the upload button.

Concurrent designation is the requirement that separates tools built for the US market from tools built elsewhere. One absence can be, at the same time, FMLA leave, leave under a state family leave act, a period paid by a state program or a disability policy, and a period during which accrued PTO is being substituted. Each layer has its own clock and its own balance. The software has to hold all of them on one timeline for one absence and count the days against each correctly, which is the only way to answer the question of what happens to the employee's pay and job protection in week nine.

State law by location follows from that. The rule set for an employee is decided by where they work, and a company with people in five states has five rule sets, from California's CFRA at five employees to a state with no leave statute at all. The tool needs a location layer that carries the state's leave statute, its paid program and its sick leave mandate, and it needs the vendor to maintain that layer as the statutes change, which they do every January. Ask how state changes reach the product and when the last one did.

Requirements nine to twelve: the return, the firewall and the record

The return is where most reinstatement disputes start. The software should hold the expected return date, prompt the administrator ahead of it, record whether a fitness-for-duty certification was required (which must have been stated in the designation notice) and received, and store the pre-leave position, pay and schedule so that the equivalence of the returned-to position can be shown. When the employee cannot return on the date the entitlement ends, the case should route to the accommodation process rather than closing.

The attendance firewall is the requirement that is easiest to describe and least often built. Protected absences must not appear in the counts that drive no-fault attendance points, performance ratings or layoff selection. In practice this means the attendance report a line manager can run must exclude FMLA and state-protected hours by default, and the export that feeds a performance or workforce planning tool must do the same. The test is to log in as a manager and run the report.

The audit trail and the reporting are the last two, and they are what a Department of Labor investigator or an opposing lawyer will ask for. Records must be kept for three years and must show dates and hours of leave, copies of notices, documents describing benefits and policies, premium payments and any dispute. A tool that keeps that as an exportable case history has done the work; one that keeps it in a mix of email, calendar entries and a shared drive has not. The reporting requirement is the same data turned forward: every open case, hours used and remaining, the next deadline, and the exposure across the company, which is the report a finance lead needs to plan cover.

Leave administration vendors: the three models

The market for this problem has three shapes, and a company usually ends up with one of them by accident rather than choice. Knowing the shape before the search saves most of the demos.

The first is the leave module inside an HRIS or payroll suite. It is already paid for, it already knows the employee's hire date, hours and location, and the data does not have to be integrated. Its weakness is depth: the module is one feature among hundreds, it was usually built for the vendor's home market, and the notice engine, the medical file permissions and the attendance firewall are the parts most often missing or shallow. It is the right answer for a company whose leave volume is low and whose HR team is willing to run the deadlines by hand.

The second is a dedicated leave or absence management platform. It is built around the case lifecycle, it carries the state law layer as a maintained product, and it integrates with the HRIS for the employee record and with payroll for hours. Its costs are the integration, a second system for employees and managers to learn, and a per-employee price on top of the suite. It is the right answer once intermittent cases or multi-state headcount make the module's gaps expensive.

The third is outsourced leave administration, usually offered by the insurance carrier that writes the company's short-term disability policy, sometimes by a specialist third-party administrator. The carrier's staff run eligibility, notices, certification and designation, and the employer receives a status feed. The appeal is that the carrier already handles the disability claim for the same absence, so one intake covers both. The costs are control and visibility: the employer remains legally responsible for FMLA compliance, the carrier's decisions are made on the carrier's timeline, and the status feed rarely reaches the attendance and performance systems where the firewall has to live. It is the right answer for a company that has more leave than HR capacity and a carrier relationship it trusts, and it still needs a system of record on the employer's side.

None of these is wrong. The mistake is choosing the carrier's portal because it was free and discovering, at the first interference claim, that the employer's own records consist of what the carrier chose to send.

How to evaluate: the demo script

Vendors run demos on the cases that flatter the product. The way to evaluate leave software is to bring your own eight scenarios and ask the presenter to work through them live, in the product, with no slides. The eight below map to the twelve requirements and take about an hour.

Scenario one: an employee hired eleven months ago requests six weeks of leave starting in six weeks. The tool should show the eligibility test, note that the employee will pass the 12-month test by the start date, and hold the request until then rather than denying it.

Scenario two: an employee who took four weeks of FMLA leave ten months ago requests ten weeks starting next month. Under rolling backward the tool should show eight weeks available at the start and the four used weeks returning as they fall out of the window during the leave, so that the employee can complete the ten weeks; it should also say on which dates they return. Ask for the same case under the calendar year method and confirm the answer changes.

Scenario three: a part-time employee working 24 hours a week records a 90-minute intermittent absence for a certified migraine condition. The tool should show an entitlement of 288 hours, deduct 1.5 hours under a quarter-hour increment, and attach the absence to the certification so that the frequency can be compared with what the provider stated.

Scenario four: a certification was requested 16 days ago and nothing has arrived. The tool should show an overdue task, the letter it proposes to send, and the consequence path: delay of designation until certification is received, or denial if the employee was told the consequence and had a reasonable chance to comply.

Scenario five: a California employee with a due date in three months. The tool should build one timeline with pregnancy disability leave and state disability pay for the disability period, CFRA bonding leave and paid family leave after it, and FMLA running with the disability portion, and it should show what is left of each entitlement at each phase.

Scenario six: an employee reaches the end of 12 weeks and their provider says they need four more. The tool should not close the case or generate a termination task; it should route to the accommodation process with the FMLA history attached.

Scenario seven: log in as a line manager and run the attendance report for a team that includes someone on intermittent leave. The protected hours must be absent from the count, and the manager must be able to see that the person is on approved leave without seeing why.

Scenario eight: ask for the complete file of a closed case as a Department of Labor investigator would: every notice with its date, the certification and who accessed it, the hours by date, the designation, the return. If it takes more than a few minutes to produce, the audit trail is not real.

Pricing models and what they leave out

Leave software is priced in three ways. HRIS modules are usually included in the suite price or sold as an add-on per employee per month. Dedicated platforms charge per employee per month or per employee per year, sometimes with a minimum, sometimes with a separate fee per leave case. Carrier administration is often bundled with the disability premium and presented as free, which it is in the sense that the price is inside the premium rather than on a separate line.

Four things sit outside the headline price on almost every quote. Implementation, which for a dedicated platform includes the HRIS and payroll integrations and the migration of open cases with their used hours and window dates, is typically a one-time fee that can equal a year of subscription. State law maintenance is sometimes a tier: confirm that statute updates are included and how quickly they ship. Notice templates and document storage are sometimes metered. And the integration to the attendance or performance system, the one that makes the firewall real, is often not in scope at all and has to be built.

The right comparison is not the per-employee price but the cost of the first interference claim the software would have prevented. Defending one such claim costs more in legal fees than any of these models costs in a year, before any award or settlement. Against that, every model on the market is cheap; the question is which one actually prevents the claim.

Build, spreadsheet or buy: the headcount thresholds

Under 50 employees the FMLA does not apply, but state leave laws often do (California's CFRA at five employees, Connecticut's at one, several paid leave programs at one), and the ADA applies at fifteen. A company this size needs a leave of absence policy and a way to record cases; a well-designed spreadsheet and the HRIS's document store are usually enough, provided one person owns the deadlines.

Between 50 and about 200 employees a spreadsheet still works for continuous leave and fails at the first intermittent case, because the rolling window arithmetic for hourly deductions across many dates is exactly what spreadsheets get wrong quietly. The free intermittent FMLA hours tracker linked below is built for this band: one workbook per employee, quarter-hour entries, the rolling balance and the return dates computed. It is a bridge, not a destination.

Above 200 employees, or with headcount in more than two states, or with more than a handful of open intermittent cases at once, the case volume and the state layer justify a system. At that point the choice between an HRIS module, a dedicated platform and carrier administration is the one the previous sections were about. Building in-house is rarely the right answer: the state law layer alone changes several times a year and is a maintenance burden no internal team wants.

Whatever the size, the one thing to buy or build first is the case record. A complete, dated file for every leave, kept for three years, is the single artifact that decides most disputes, and it is the requirement that costs least to meet.

Where Time-Out Zone fits, honestly

Time-Out Zone is a leave management system, and this guide would be dishonest if it pretended otherwise. What it is built around is configurable leave types with their own eligibility, accrual, pay and approval rules; a policy layer that resolves by location, department, team, tag and person so that the state addendum follows the employee's work location; approval workflows with deputies and coverage rules; and an audit trail that records who requested, approved, changed and closed each absence and when. Those are the foundations the twelve requirements sit on, and they are the parts of the list a vacation tracker lacks by design.

What you should do with that information is the same thing you should do with every vendor on your list: bring the eight scenarios to the demo and ask to see each one worked through in the product. The comparison pages linked below set Time-Out Zone next to the other leave and absence management tools on the market with the same scrutiny, and they are the place to go for the vendor pick. This page is the requirements list; use it on everyone, including us.

Implementation: the first thirty days

The first decision is the 12-month method, made in writing before any case is loaded, because every balance in the system depends on it. Employers changing method must give 60 days' notice and let employees keep the more generous entitlement during the transition, so most companies load the method they already use and revisit later.

The second is the migration of open cases. Every employee currently on or recently returned from leave needs their case loaded with the hours used by date, so that the rolling window is correct from day one. This is the step most implementations skip, and it produces balances that are wrong for a year.

The third is the policy layer: one rule set per state where the company has employees, with the state statute, the paid program and the sick leave mandate, plus the company's own leave of absence policy on top. The fourth is the notice templates, which should be the DOL model forms or the company's counsel-reviewed versions, loaded once and versioned. The fifth is the attendance firewall, which usually means an integration or a report change in a different system and should be scheduled, not assumed.

Then run one full cycle in parallel with the old process, compare the balances and the deadlines, and only after that turn the old process off. A month of double entry is cheaper than a year of wrong balances.