Labor law does not change on one day a year. It changes on hundreds of days, spread across federal agencies, fifty state legislatures, and city councils. An HR team that checks the news once a quarter will miss something. The fix is not more vigilance. It is a calendar system built around fixed dates, recurring reviews, and named sources you check on purpose.
According to OutSolve, missing a single filing deadline or form submission can cost a company money and its reputation. That is true whether the miss is a federal form or a state-specific wage report. The goal of a compliance calendar is not perfection. It is a system that catches most misses before they become penalties.
This guide walks through how to build that system: what belongs on it, where the dates come from, and how often to check for rules the Department of Labor is still writing.
What actually belongs on a labor law compliance calendar?
A compliance calendar mixes two kinds of dates. Fixed dates repeat every year on the same schedule. Rolling dates depend on when an agency finishes a rulemaking or a court decides a case, and they move.
Fixed dates include IRS payroll tax deadlines, ACA reporting to the IRS, OSHA injury log posting windows, and EEO-1 workforce data reporting. According to HR Service, Inc., OSHA's Form 300A summary must be posted in a workplace common area from February 1 through April 30 each year, and larger employers in certain high-hazard industries must also submit that data electronically to OSHA through its Injury Tracking Application.
Rolling dates are different. They include the effective date of a new overtime rule, the outcome of a Department of Labor rulemaking on independent contractor status, or a Federal Register notice setting a new compliance date for pay transparency. These don't repeat on a schedule. They surface through public comment periods and agency notices, and a calendar has to leave room for them.
Both types belong in the same system, but they need different tracking methods. Fixed dates go on a template you reuse every year. Rolling dates need a standing habit of checking primary sources, not a set-and-forget entry.
Which fixed dates repeat every year?
Most annual HR compliance obligations cluster around a handful of points in the calendar. Knowing the pattern makes the whole year easier to plan.
January carries year-end reporting: Forms W-2 and 1099 to employees, Form 940 for federal unemployment tax, and in some states, updated minimum wage postings. According to Virto Software, the federal minimum wage has stood at $7.25 an hour since 2025, but many states set their own higher floor, and those state minimums often change on January 1.
February and March bring OSHA's injury and illness reporting window and, for applicable large employers, ACA Forms 1094-C and 1095-C to the IRS. Outsolve notes that Form M-1 for Multiple Employer Welfare Arrangements is also due by March 1.
Mid-year deadlines include EEO-1 Component 1 reporting, which HireLevel's 2026 calendar lists with a June filing window, and RxDC prescription drug spending reports submitted through CMS's Health Insurance Oversight System. Outsolve also flags the VETS-4212 veteran hiring report, with its filing portal opening August 1 and closing September 30.
The fourth quarter is when most benefits-related notices go out: open enrollment announcements, Flexible Spending Account reminders, and year-end changes to pay or benefits that take effect the following January. None of these fixed dates require legal interpretation. They require a template and someone assigned to own it.
| Period | Typical recurring task | Source |
|---|---|---|
| January | W-2/1099 distribution, Form 940, state minimum wage updates | Virto Software; HR Service, Inc. |
| February–April | OSHA Form 300A posting window; ACA forms to IRS | HR Service, Inc.; HireLevel |
| June–September | EEO-1 reporting; VETS-4212 filing window | Outsolve |
| October–December | Open enrollment, benefit change notices, year-end audits | Outsolve; HireLevel |
How do you track the rules that don't repeat on schedule?
Fixed dates are the easy half. The harder half is tracking a rule that is still moving through an agency, because its effective date does not exist until the agency sets one.
The overtime salary threshold is the clearest example of how these rules shift over years, not months, a pattern traced in the overtime salary threshold, in five dates. A single rulemaking can also be undone before it takes effect, which is what happened when the Department of Labor moved to rescind its 2024 independent contractor rule, detailed in DOL moves to scrap the 2024 independent contractor rule. A compliance calendar that only tracked the original 2024 effective date would have been wrong twice over.
State legislatures add another layer of volatility. A benefit voters approved by ballot measure can later be repealed by the legislature, as covered in Missouri repeals the paid sick leave voters approved. A calendar entry for "paid sick leave effective date" in one state is not a permanent fact. It needs a recheck date attached to it, not just a start date.
Congress has its own tool for undoing recent agency rules on a short clock, which is why any rule finalized late in a legislative session deserves a flag, as explained in how the Congressional Review Act can void a labor rule. A rule can be final and still not be safe to build permanent policy around for several months.
What should a monthly review actually check?
A calendar only works if someone opens it. The review does not need to be long, but it needs to hit the same sources every time.
- Check the Federal Register for new final rules or proposed rules from the Department of Labor, OSHA, and the EEOC that touch your workforce.
- Check your state labor agency's website for wage rate changes, new posting requirements, or paid leave program updates.
- Review any rulemaking currently in a public comment period and note its expected timeline for a final rule.
- Confirm no pending litigation has changed the status of a rule your policies already assume is in effect.
- Update the calendar entry with a source and date, not just a task name.
That last step matters most. A calendar entry that says "verify overtime threshold" without a source attached will get skipped when someone is busy. A calendar entry that says "check Department of Labor Federal Register notice, last confirmed March 2026" gives the next person something concrete to check against.
What this means for HR teams building the calendar
The practical value of a compliance calendar is not the list of dates. It is the discipline of separating what is confirmed from what is proposed. A rule in a public comment period is not yet binding. A rule with a Congressional Review Act challenge pending is not yet safe. A state benefit passed by ballot measure is not permanently secure from legislative repeal.
Build the calendar in two layers. The first layer holds fixed federal and state filing dates that repeat every year and rarely change. The second layer holds a standing monthly task: check primary sources for anything moving through rulemaking, litigation, or state legislatures that touches your workforce, including questions of which leave law applies when both federal and state rules exist, a distinction laid out in FMLA and state paid leave: which law applies when.
What the evidence here establishes is a pattern: recurring filing deadlines cluster predictably around the calendar year, while substantive rule changes move on agency and court timelines that no calendar template can predict in advance. What remains unknown for any specific employer is which pending rulemakings will finalize, when, and whether a state legislature or Congress will act first. A calendar cannot resolve that uncertainty. It can only make sure someone is checking.