Worked example: statute of limitations in Maine

6 min read

Published April 8, 2026 • By DocketMath Team

Example inputs

Run this scenario in DocketMath using the Statute Of Limitations calculator.

This worked example shows what a statute of limitations (SOL) calculation can look like in Maine (US‑ME) using DocketMath. It uses the general/default SOL rule only—because the jurisdiction data provided did not identify any claim-type-specific sub-rule. (So the “general/default” period below is the one we apply.)

Quick note: This is an illustrative example, not legal advice. SOL rules can depend on claim type, procedural posture, and other facts, so use this as a template for thinking through the timeline.

Scenario (hypothetical)

  • Event date (accrual / violation occurred): March 1, 2024
  • Filing date (complaint filed): December 15, 2024
  • Claim type: Not specified
    • Because no claim-type-specific rule was provided, we apply the general/default period.

Maine rule used (general/default)

We use Title 17‑A, § 8 as the general/default SOL rule:

Note: This example uses only the general/default period. If a specific SOL applies to a particular claim type, the outcome could be different.

What you’ll enter into DocketMath (inputs)

Use the following inputs as the basis for the calculator workflow:

  • Tool / link: /tools/statute-of-limitations
  • Jurisdiction: US‑ME (Maine)
  • SOL basis: General/default (from 17‑A, § 8)
  • SOL length: 0.5 years (6 months)
  • Start date (accrual/event): 2024-03-01
  • End date / filing date: 2024-12-15

Key “date math” concept (how 0.5 years is treated)

A SOL of 0.5 years is treated as 6 months. In practical terms, the deadline is the date 6 months after the start/accrual date (or an equivalent date computation depending on the tool’s internal date-handling rules). For readability, you can think of the deadline as:

  • March 1 → September 1

If your case has a different “start” date than the event date you chose here, the deadline shifts accordingly—so it’s worth checking which date DocketMath is using as the start date for your workflow.

Example run

Run the Statute Of Limitations calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

Step 1: Compute the SOL deadline

  • Accrual / event date: March 1, 2024
  • General SOL period: 0.5 years = 6 months (per 17‑A, § 8)
  • Computed SOL deadline: September 1, 2024

This deadline represents the “last day to file” under the general/default rule as computed from the start date and the 6‑month SOL period. (Whether the exact cutoff is inclusive/exclusive can depend on how dates are handled in the tool and applicable procedural rules, so treat this as a modeled estimate and double-check in the tool output.)

Step 2: Compare the filing date to the deadline

  • Filing date: December 15, 2024
  • Deadline: September 1, 2024

Because December 15, 2024 is after September 1, 2024, the filing falls outside the general/default SOL window.

Output summary (what DocketMath would report)

Input / OutputValue
JurisdictionMaine (US‑ME)
SOL basisGeneral/default period (Title 17‑A, § 8)
SOL length0.5 years (6 months)
Start date2024-03-01
SOL deadline2024-09-01
Filing date2024-12-15
ResultTime-barred under the general/default rule

Pitfall to watch: “0.5 years” can mislead people into expecting something closer to a year. In this rule, 0.5 years = 6 months, so a delay of just a few extra months can switch the result from “within” to “outside.”

Sensitivity check

This section shows how sensitive the SOL outcome can be to changes in dates. These mini-scenarios are designed to help you sanity-check your timeline before relying on a calculator result.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity 1: Filing 1 month earlier (still outside)

Keep the accrual date the same (March 1, 2024) and change only the filing date.

  • Deadline: September 1, 2024
  • New filing date: November 15, 2024 (instead of December 15, 2024)

Result: Still outside the 6‑month window.

Sensitivity 2: Filing near the deadline (boundary effects)

Again, keep the start date as March 1, 2024.

  • Deadline: September 1, 2024
  • Compare two filing dates:
Filing dateRelative to deadlineExpected outcome (general/default)
2024-08-31Before deadlineWithin SOL
2024-09-01On deadlineAt deadline
2024-11-15After deadlineOutside SOL

Even small date changes can matter. If your actual filing date could plausibly be around the cutoff day, it’s worth re-running DocketMath using the exact dates from your docket/workflow (including any filing/receipt date your process uses).

Sensitivity 3: Start date shifts (common when “accrual” is disputed)

In real cases, the “event date” used as the start can shift by days or weeks. Here we keep the filing date the same (December 15, 2024) and move the start date.

Case C: Start date later

  • Start date: March 16, 2024
  • 6-month deadline: September 16, 2024
  • Filing date: December 15, 2024

Result: Still outside.

Case D: Start date earlier

  • Start date: February 15, 2024
  • 6-month deadline: August 15, 2024
  • Filing date: December 15, 2024

Result: Still outside, and the gap past the deadline is larger.

Quick checklist for using DocketMath effectively

Before trusting any SOL result, run through these practical checks:

Gentle warning: If a specific SOL applies based on the claim category or other facts, the general/default rule from Title 17‑A, § 8 may not control. Your DocketMath run should match the rule that governs that claim type in Maine for your specific situation.

Related reading