Quick takeaways

• Workers’ compensation filing deadlines are date-driven and jurisdiction-specific. In many states, the clock starts on the date of injury or the first date you were unable to work because of the workplace injury.
• Notice deadlines often come before claim filing deadlines. Some states require prompt notice to the employer (commonly within days to weeks) even if the formal claim has a later deadline.
• “One missed deadline” doesn’t always end the case—but it can sharply reduce benefits. Several states allow late filing with good cause, but you usually must show more than “we forgot.”
• The definition of “employee” and “date of injury” matters. Injuries with reporting complexity (occupational disease, cumulative trauma, repetitive stress) may have different deadline triggers.
• DocketMath can help you standardize your inputs and document your deadline assumptions. Use it to build a repeatable checklist before you submit anything.

Inputs you need

To run a deadline check in DocketMath, gather the facts that control the deadline trigger in your state. If you’re building a workflow for a team, capture these fields consistently:

Required inputs (collect before you calculate)

• State (jurisdiction): the state where the work occurred (not where the employer is headquartered).
• Injury type:

  • Accident with a specific date (e.g., fall on 2026-03-14)
  • Occupational disease / cumulative trauma (e.g., repetitive strain over months)
• Date of injury:

  • For a specific accident: the date the event occurred
  • For occupational disease/cumulative trauma: the date the issue became known or disabling (state-specific rules)
• Date you notified the employer (if notice was given): exact date or best estimate
• Date you filed the claim (if already filed): exact filing date or date submitted
• Employee status: whether the person qualifies under the state’s workers’ compensation coverage rules (e.g., some states have carve-outs for certain job types)

Helpful inputs (optional but improves accuracy)

• Is this a claim for medical benefits only first? Some processes start with medical authorization before a formal claim.
• Any delay caused by documentation issues? Keep the facts you might need to explain “good cause,” if available.
• Whether the employer accepted liability initially: in some states, employer conduct can affect disputes.

Output you should expect from DocketMath

When you submit these inputs, DocketMath should produce:

• Deadline type(s): notice deadline, filing deadline, or both (depending on your jurisdiction’s rules)
• Calendar dates: latest permissible notice/filing dates based on your trigger date(s)
• A “status” indicator: e.g., “within time,” “approaching deadline,” or “deadline passed” (based on the selected dates)

If you haven’t standardized your inputs yet, open /tools and follow the jurisdiction-aware flow before filling in dates.

➡️ Start with the DocketMath tooling here: /tools

How the calculation works

Different states structure workers’ compensation timing rules differently, but most deadline logic follows a repeatable pattern. DocketMath’s method should be transparent enough for you to verify each step.

Step 1: Determine which deadline clocks apply

Many jurisdictions have at least two categories:

• Employer notice deadlines
  Often short (examples include 10 days, 30 days, or 90 days), but exact periods are state-specific.
• Claim filing deadlines
  Often longer (frequently 1 year for certain injury types, though some states use shorter or longer timeframes; occupational disease can have different windows).

DocketMath should map your state + injury type to the correct deadline categories and identify the trigger date.

Step 2: Identify the trigger date

Trigger dates commonly include one of the following:

• Date of injury (for identifiable accidents)
• Date of “disablement” (first time the injury prevented work)
• Date of awareness for occupational disease/cumulative trauma (when the worker knew the condition was work-related)
• Date the employer had actual knowledge (some states treat employer knowledge differently than worker notice)

DocketMath should select a trigger based on your inputs and the injury type.

Step 3: Count forward using the jurisdiction’s time rule

Once the trigger date is selected, DocketMath should count forward according to the state’s method.

Common counting conventions:

• Days vs. weeks vs. months: a jurisdiction might use calendar months or fixed days.
• Inclusion rules: most deadline computations follow normal calendar counting, but exact rules can differ.
• No automatic “weekend adjustments”: unless the statute/rules explicitly provide for adjustments, a deadline might fall on a weekend/holiday with separate procedural rules. DocketMath should flag uncertainty where the rules require procedural timing.

Step 4: Compare with your actual timeline

Finally, DocketMath compares:

• Your employer notice date vs. notice deadline
• Your claim filing date vs. filing deadline

It then outputs:

• Remaining time (e.g., “15 days left”)
• Late by (e.g., “12 days late”)
• Which deadline is the bigger risk (notice vs. claim)

Step 5: Document assumptions for review

Good documentation reduces rework. DocketMath should produce an audit trail you can keep with your file, such as:

• Trigger date used
• Deadline type selected
• Injury type classification
• Any “unknown” fields you had to estimate

Common pitfalls

Below are recurring errors that cause missed deadlines or flawed calculations.

Misclassifying the injury type

• Accident with a single date vs. cumulative trauma can change the trigger.
• Occupational disease rules may start when you knew it was work-related, not when symptoms began.

Using the wrong “state”

• The correct jurisdiction is usually the state where the work was performed.
• Picking the wrong state will produce the wrong deadlines even if the dates are perfect.

Confusing notice and filing

• A common scenario: notice submitted late, but claim filed on time (or vice versa).
• DocketMath should evaluate both categories so you don’t “pass” one deadline while failing another.

Overlooking employer conduct

• Some states consider whether the employer had actual knowledge or participated in treatment.
• That can affect disputes, especially if you’re trying to justify late notice or filing.

Ignoring multiple injuries or amendments

• If there are multiple reported dates (e.g., new condition after initial accident), deadlines may be evaluated per claim theory and amended paperwork.

Checklist: before you trust the result

• State/jurisdiction matches where work occurred
• Injury type is correctly selected
• Trigger date is supported (incident report, medical record, timekeeping)
• Employer notice date is accurate
• Filing date is the actual submission date (not “when we drafted it”)
• You’re comparing against both notice and filing deadlines (if applicable)

Sources and references

Because workers’ compensation timing rules are jurisdiction-specific and can change, use the statutory text and the state’s workers’ compensation agency guidance for final verification. For a practical baseline, confirm:

• The workers’ compensation act provisions covering:

  • Notice of injury
  • Filing of the claim
  • Time limits for occupational disease / cumulative trauma
• Any administrative rules addressing:

  • Method of filing
  • Date of receipt
  • Exceptions and “good cause” standards

For dynamic, workflow-driven documentation, pair your legal research with a repeatable calculation process in DocketMath (see Next steps below).

Next steps

1. Run a deadline calculation in DocketMath using the /tools workflow so your team captures the same inputs every time: /tools
2. Attach your evidence timeline to the computed results:

   • incident date
   • first medical visit
   • employer notice date
   • claim submission date
3. Re-check injury classification (accident vs. occupational disease/cumulative trauma) if:

   • symptoms evolved gradually
   • the condition appears related to repetitive work
   • the employer disputes that it was a “date of injury” event
4. Store the calculation assumptions with the case file so later reviewers understand:

   • why a particular trigger date was selected
   • how the deadline was counted
   • which deadline type is driving the risk

Related reading

• Why we started the DocketMath blog
• Introducing Explain++: step-by-step calculation breakdowns
• A practical workflow for jurisdiction-aware legal calculations (and how to document them)