Most FMLA disputes are not about whether an employee had a serious health condition. They are about arithmetic: how much leave the employee had left on the day they asked, which absences were counted, and whether the employer can prove it. That proof lives in the tracker, and a tracker is only as good as two decisions made before the first row is entered: which 12-month period the employer uses, and what unit the entitlement is measured in.
This guide covers both decisions and then builds the tracking spreadsheet itself, column by column, with the formulas that make a rolling 12-month period workable. It is written for the HR or payroll administrator who owns the leave log, whether that log is a spreadsheet, a module in the HRIS, or both. If your problem is specifically intermittent absences (increments, rounding, partial-day pay for exempt staff), our guide to calculating pay during intermittent FMLA leave covers that ground; this post is about the year method and the record that sits underneath every type of FMLA leave.
The Family and Medical Leave Act regulations at 29 CFR 825.500 do not prescribe a form or a system. They say no particular order or form of records is required and that employers do not have to rebuild their payroll systems to comply. What they do require is that a covered employer with eligible employees can produce, for at least three years, records showing:
Two details in that list shape the spreadsheet. First, the record must show leave designated as FMLA, not just an absence. A row that says "sick, 8 hours" proves nothing about FMLA. Second, the regulation says leave designated as FMLA in the records may not include leave required under state law or an employer plan that is not also covered by FMLA. If an employee takes state family leave to care for a grandparent, that time does not belong in the FMLA column, even though it may belong in a state leave column next to it.
Medical information is separate again. Certifications, recertifications and medical histories created for FMLA purposes must be kept as confidential medical records, in files separate from the usual personnel file. Your tracker should record that a certification was requested, received and found sufficient, with dates. It should not contain the diagnosis.
The entitlement is 12 workweeks of leave in a 12-month period (26 workweeks in a single 12-month period for military caregiver leave). The regulations at 29 CFR 825.200(b) let the employer choose how that 12-month period is measured. There are four options.
|
Method |
How the year is defined |
Stacking risk |
|
Calendar year |
January 1 to December 31 |
High: 12 weeks in December, 12 more in January |
|
Fixed leave year |
Fiscal year, a year required by state law, or the employee's anniversary year |
High at each boundary |
|
Measured forward |
12 months starting on the date the employee's first FMLA leave begins |
Moderate: a new year opens on the first use after the prior year ends |
|
Rolling backward |
At each use, look back 12 months from that date |
Low: the balance is always what is left from the preceding 12 months |
These are the easiest to administer because every employee's balance resets on the same date. They are also the most generous. The regulation itself gives the example: an employee can take 12 weeks at the end of one year and another 12 weeks at the beginning of the next. For an employee with a long recovery that straddles the reset date, that is 24 consecutive weeks of job-protected leave.
The employee's personal year starts the first day they take FMLA leave. The next 12-month period begins the first time they take FMLA leave after that year ends. This reduces stacking but does not eliminate it, and it gives every employee a different year that the tracker must store.
Each time the employee uses FMLA leave, the available balance is 12 weeks minus whatever was used in the immediately preceding 12 months. The regulation walks through the mechanics: an employee who used four weeks starting February 1, four starting June 1 and four starting December 1 has nothing left until the following February 1, and then recoups leave day by day in the same pattern it was used. If that employee needs six weeks starting the next February 1, only the first four are FMLA-protected.
Rolling backward is the method most employers choose for one reason: it is the only one that makes back-to-back 12-week blocks impossible. The cost is administrative. Every request requires a fresh look-back calculation, and employees "fall in and out" of FMLA protection as old usage ages off. That is exactly the problem a well-built tracker solves.
Put the chosen method in writing, in the handbook or leave policy, and cite it in the rights and responsibilities notice you give with each eligibility determination. The notice regulation at 29 CFR 825.300(c) requires the notice to state the applicable 12-month period. An undocumented method is, in practice, no method.
The regulations say the actual workweek is the basis of the entitlement. An employee does not accrue FMLA leave at an hourly rate; they are entitled to 12 of their own workweeks. For tracking, convert that to hours using the employee's normal schedule:
|
Normal weekly schedule |
12-week entitlement in hours |
|
40 hours |
480 |
|
37.5 hours |
450 |
|
32 hours |
384 |
|
24 hours |
288 |
Three rules from 29 CFR 825.205 decide what "normal schedule" means:
Permanent schedule changes count. If the employer made a permanent or long-term change to the schedule for reasons other than FMLA, before the notice of need for leave, the new schedule is the basis.
Variable schedules use an average. Where the schedule varies so much week to week that you cannot tell how many hours the employee would have worked, use the weekly average of hours scheduled over the 12 months before the leave began, including hours for which the employee took any kind of leave.
Required overtime counts; voluntary overtime does not. If an employee would normally be required to work overtime and cannot because of an FMLA reason, those missed required hours count against the entitlement. Voluntary overtime the employee does not work cannot be charged.
Holidays also need a rule in the tracker. Under 825.200(h), a holiday falling in a week of continuous FMLA leave does not change anything: the whole week counts. But when leave is taken in increments of less than a week, the holiday does not count against the entitlement unless the employee was scheduled and expected to work that day. Plant shutdowns and other periods when employees generally are not expected to report do not count either.
A workable tracker has two tabs: an employee/case tab with one row per leave case, and a usage log with one row per absence. Keep medical details out of both.
The notice regulations treat all absences for the same qualifying reason within the 12-month period as a single leave. That makes the "case" the natural unit for the first tab.
|
Column |
What goes in it |
|
Case ID |
Unique key, for example EMP1043-2026-01 |
|
Employee ID |
Payroll ID, not name, so the log can be shared narrowly |
|
Leave reason category |
Own health, family member's health, birth/bonding, placement, qualifying exigency, military caregiver |
|
Leave type |
Continuous, intermittent or reduced schedule |
|
Date of notice of need |
When the employee (or spokesperson) told you |
|
Eligibility determined |
Eligible / not eligible, with the reason if not |
|
Eligibility and rights notice sent |
Date (five business days is the benchmark) |
|
Certification requested / due / received |
Three dates; due date is at least 15 calendar days after the request |
|
Certification status |
Sufficient, incomplete or insufficient (cure sent), not returned |
|
Designation notice sent |
Date and outcome (designated / not designated) |
|
Paid leave running concurrently |
PTO substitution, STD, workers' comp, state program, none |
|
Normal weekly hours |
Used to compute the entitlement in hours |
|
Entitlement hours |
Normal weekly hours x 12 |
|
Fitness-for-duty required |
Yes/no, and whether essential functions list was provided |
|
Expected return / actual return |
Dates |
|
Column |
What goes in it |
|
Case ID |
Links back to the case tab |
|
Employee ID |
Duplicated so look-back formulas can run without a lookup |
|
Date of absence |
One row per date, even for continuous leave |
|
FMLA hours charged |
In the smallest increment you use for any other leave |
|
Paid leave applied |
PTO, sick, STD, comp hours applied to the same absence |
|
Concurrent state leave hours |
If a state law also covers the absence |
|
Holiday / shutdown flag |
So the hours are excluded where the rules say so |
|
Source |
Timesheet, call-in record, approved request |
|
Entered by / date entered |
Audit trail |
Logging continuous leave one date per row looks wasteful, but it is what makes rolling-backward math reliable. A single row saying "March 3 to April 25, 320 hours" cannot be partly aged off when the look-back window moves.
With one row per date, the hours used in the 12 months before a given request date can be computed with a SUMIFS. In Excel or Google Sheets, assuming the usage log has Employee ID in column B, date in column C and FMLA hours in column D:
=SUMIFS(Log!D:D, Log!B:B, [EmpID], Log!C:C, ">="&EDATE([RequestDate],-12), Log!C:C, "<"&[RequestDate])
Available hours on the request date are the entitlement hours minus that result. Two cautions. Decide and document how you treat the boundary day (whether usage exactly 12 months earlier is inside or outside the window) and apply it the same way every time. And re-run the calculation for every day of a requested block of leave, not just its first day, because hours used a year ago age off as the new leave proceeds. That is the mechanism the regulation describes when it says an employee "recoups" leave in the pattern it was used.
For calendar or fixed years, replace the EDATE window with the start and end dates of the leave year. For measured-forward, store each employee's current year start on the case tab and use it as the window start.
Many absences count against more than one bank at once: FMLA, a state family or medical leave law, a local sick leave ordinance, company PTO, a disability plan. Each has its own eligibility, its own year and its own definition of family member. Track each in its own column and never derive one balance from another. When a state law covers a reason that FMLA does not (a broader definition of family member is common), that time draws down the state bank only.
The state layer changes often. Our state paid family leave roundup and paid sick leave laws by state track the programs, and the state rules for paid sick leave reference page covers accrual and use requirements state by state.
The designation regulation at 29 CFR 825.300(d)(6) requires the employer to tell the employee how much leave is being counted against the entitlement. Where the amount is known when the leave is designated, the hours, days or weeks go in the designation notice. Where it is not known (unforeseeable intermittent leave is the usual case), the employer must provide the amount on the employee's request, no more often than once in a 30-day period and only if leave was taken in that period. Oral notice must be confirmed in writing by the following payday (or the one after, if the next payday is less than a week away), and the regulation expressly allows that written confirmation to be a notation on the pay stub.
That pay stub option is worth building. If your payroll system can carry an "FMLA hours used / remaining" memo field fed from the tracker, every pay statement becomes a running confirmation, disputes surface early, and the employer has a dated record of what it told the employee.
Spreadsheets drift. Run these checks quarterly, and every time the timekeeping or HRIS configuration changes:
If you inherit a tracker with no documented year method, assume none was chosen. The most-beneficial-to-employee default applies, balances may be understated, and the fix is a policy decision with a 60-day notice, not a formula change. Our FMLA, ADA and workers' comp overlap guide covers the related problem of absences that sit in more than one regime at once.
The rolling 12-month period measured backward is the most common employer choice because it prevents an employee from taking 12 weeks at the end of one leave year and another 12 at the start of the next. It requires a new calculation every time leave is requested, so it works best with a per-date usage log and a look-back formula. The calendar year is simpler but allows stacking. Whatever you choose must be applied uniformly to all employees, written into policy and stated in the rights and responsibilities notice.
The entitlement is 12 of the employee's own workweeks in the applicable 12-month period, not a fixed number of hours. Convert it using the normal weekly schedule: 480 hours for a 40-hour employee, 360 for a 30-hour employee. Where the schedule varies so much that normal hours cannot be determined, use the weekly average of scheduled hours over the 12 months before the leave began, including hours on any type of leave. Required overtime the employee cannot work counts; voluntary overtime does not.
Each time the employee uses FMLA leave, you look back 12 months from that date and subtract whatever FMLA leave was used in that window from the 12-week entitlement. The remainder is what is available. Because old usage ages off continuously, the employee regains leave day by day in the same pattern it was used a year earlier. For a long block of leave, check availability for each day of the block, since part of the requested leave may be protected and part may not.
Yes, with at least 60 days' notice to all employees. During the transition employees must keep the full benefit of 12 weeks under whichever method is most favorable to them, and the change cannot be made to avoid the Act's requirements. If no method was ever selected, the method most beneficial to each employee applies until a method is chosen and the 60-day notice period has run.
In the same workbook, yes; in the same column, no. The FMLA recordkeeping rule says leave designated as FMLA in the records may not include leave required by state law or an employer plan that is not also covered by FMLA. Keep a separate column and balance for each state or local entitlement, each with its own year method if the state requires one. Where an absence qualifies under both, record it in both columns so each balance is drawn down correctly.
At least three years under 29 CFR 825.500, and they must be available to the Department of Labor for inspection and copying on request. Records relating to certifications, recertifications and medical histories must be kept as confidential medical records in files separate from ordinary personnel files. State leave laws and other federal laws may set their own retention periods, so check the longest one that applies before purging anything.
A tracker records decisions; it does not make them. Eligibility determinations, notice timing, certification follow-up and designation all feed the spreadsheet, and an error in any of them shows up later as a balance nobody can defend. The Leave Management Compliance Suite is built for teams that administer leave across federal, state and company programs, and the PTO and vacation policy checklist helps align the company policy layer that runs alongside FMLA.
Choose your 12-month method in writing, log every absence by date in hours, keep each entitlement in its own column, and audit the log against timekeeping before an employee or investigator does it for you.

