Why statute of limitations results differ in Canada

The top 5 reasons results differ

If DocketMath’s statute-of-limitations results don’t match what you expected for a Canadian matter, the mismatch is usually caused by one (or more) of five predictable input choices. The goal of this quick diagnostic is to help you pinpoint which assumption is different—so you can adjust your inputs without changing your whole story.

1) Different limitation periods by “cause of action” category

In Canada, the limitation period can depend on the type of claim (for example, contract vs. tort vs. fraud-related claims). Two disputes can look similar, but if they’re categorized differently, the “last day to file” can change.

Common symptoms

• The deadline changes when you switch claim type from “contract” to “injury,” or vice versa.
• Your expected timeline matches a general rule you had in mind, but the tool is using a different statutory category.

2) Province-specific limitation periods (and different starting rules)

Limitations are largely province-driven, so the outcome can change based on which province the calculator ties to your claim. Provinces may differ in:

• the base limitation period (often but not always 2 years),
• the date the clock starts, and
• whether and how extensions/tolling can apply.

Common symptoms

• Same facts, different province selected → different filing deadline output.

3) Discovery/timing mechanics: when the clock starts

Many limitation systems include discoverability concepts—meaning the clock can start when the claimant knew (or reasonably should have known) key facts. If you input different “start” dates (often event vs. discovery), the deadline can shift.

Common symptoms

• One run appears to use “event date,” another uses “discovery date.”
• Your expected start is later/earlier than the tool’s assumption.

Practical note: even a small change near the end of a limitation period can move the “last day” by the same amount.

4) Trigger date mismatch: “breach,” “termination,” “completion,” or “last act”

Even within the same claim category, users may disagree on what the relevant trigger date should be. DocketMath’s results can change if the selected trigger is different, such as:

• breach vs. contract termination,
• last infringing act vs. first act,
• completion of services vs. when defects were identified.

Common symptoms

• The deadline moves “by a lot” when you switch from a termination-based input to a breach-based input (or similar alternatives).

5) Suspension/extension/tolling inputs not aligned

Some situations can involve extension, suspension, or tolling of the limitation clock. If your expectations assume an extension/tolling event—but your DocketMath inputs don’t reflect it (or vice versa), results will diverge.

Common symptoms

• Your expected outcome assumes an extension/suspension, but the tool output doesn’t.
• You selected a “special circumstance” or extension-related option differently (or didn’t select it).

How to isolate the variable

Use a single change at a time approach. That way, you can identify the exact input that caused the result to shift. This is especially effective because limitation discrepancies are often traceable to one date logic (province, discovery start, trigger date, or extension flags).

A quick diagnostic workflow (5-step loop)

1. Fix the claim category first
   Keep all dates constant. Change only the claim category and compare the deadline.
2. Lock the province next
   Keep claim category and dates constant. Switch province and observe what changes.
3. Validate the “clock start” basis
   Confirm whether the calculator is treating the start as event-based or discovery-based. Adjust only the discovery/knowledge input and re-run.
4. Re-check the “relevant trigger date”
   If the tool offers alternatives (e.g., breach vs. termination), test one at a time based on your facts.
5. Toggle extension/suspension conditions
   If there are extension/tolling-related toggles, run once with them off and once with them on.

If you want a repeatable starting point, run the calculator here: /tools/statute-of-limitations.

Mini checklist to compare runs

Output differences: what they usually mean

• Deadline shifts after changing province → province-specific period or start rules.
• Deadline shifts after changing claim category → different classification of the claim.
• Deadline shifts after adjusting discovery-related dates → discoverability/knowledge start logic.
• Deadline shifts after changing “relevant date” → trigger date definition mismatch.
• Deadline shifts after toggling special circumstance → extension/suspension model mismatch.

Next steps

Once you isolate the variable, update your inputs to match the limitation concept that best fits your facts—without rewriting your entire timeline.

1. Record your baseline run
   Write down the province, claim category, and the exact dates you entered.
2. Make one targeted change
   For example: keep province and claim category constant; change only the discovery date.
3. Document the delta
   Note how many days the deadline moves.
4. Align inputs to your factual timeline
   Choose the date that corresponds to the relevant “trigger” for when the limitation clock should start (event vs. discovery vs. termination).
5. Re-run and confirm
   Stop once the calculator matches your expected logic.

Gentle disclaimer: this is a practical diagnostic to help reconcile inputs, not legal advice. If the underlying legal classification or trigger dates are genuinely uncertain, consider getting professional guidance.

Related reading

• Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
• Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator