Worked example: Damages Allocation in Maine

Example inputs

Run this scenario in DocketMath using the Damages Allocation calculator.

This worked example shows how DocketMath can allocate damages inputs in Maine (US-ME) using jurisdiction-aware rules for damages allocation timing. The goal is to demonstrate the mechanics—not to provide legal advice.

Case setup (fictional, for demonstration)

Assume a plaintiff alleges damages arising from an agreement breach plus related events. For allocation purposes, we need a damages measurement window tied to Maine’s general limitations period.

Because the jurisdiction data you provided indicates no claim-type-specific sub-rule was found, the tool uses Maine’s general/default statute of limitations.

Maine rule used

Maine’s general statute of limitations referenced in the jurisdiction data is Title 17-A, § 8. The jurisdiction data you provided lists the General SOL Period as 0.5 years and the applicable statute reference as:

• Maine Title 17-A, § 8 (general/default period used here)
• Source: https://legislature.maine.gov/statutes/17-a/title17-asec8.html?utm_source=openai

Important note: This example uses the general/default period because no claim-type-specific sub-rule was found in the provided jurisdiction data. That means the allocation window is driven by the same SOL rule regardless of asserted labels in this demonstration.

Inputs entered into DocketMath (/tools/damages-allocation)

Use these example inputs for the calculator damages-allocation:

If you want to run it yourself, use the primary CTA: /tools/damages-allocation.

Example run

Below is a worked-through run showing how the calculator typically behaves with the provided inputs.

Run the Damages Allocation 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-based coverage window

• General SOL Period (from jurisdiction data): 0.5 years
• General SOL Statute: Title 17-A, § 8
• Example dates:

  • Event start: 2025-01-10
  • Claim filed: 2025-08-01

From 2025-01-10 to 2025-08-01 is roughly 0.56 years (about 204 days / 365 days). With a 0.5-year period, not all of the measured timeline is covered by the limitations window.

Under a “covered vs. uncovered time” allocation approach:

• Covered portion: first 0.5 years of the measured timeline
• Uncovered portion: remaining tail beyond 0.5 years

Practically, the calculator converts that into a percentage covered.

Step 2: Convert time coverage to damages coverage

Given total claimed damages of $120,000, a proration method yields:

• Covered damages amount ≈ $120,000 × (covered fraction)
• Uncovered damages amount ≈ $120,000 × (uncovered fraction)

Using the approximate timeline:

• Covered fraction ≈ 0.5 / 0.56 ≈ 0.893
• Uncovered fraction ≈ 1 − 0.893 ≈ 0.107

Therefore:

• Covered damages ≈ $120,000 × 0.893 = $107,160
• Uncovered damages ≈ $120,000 × 0.107 = $12,840

Step 3: Apply the “front-loaded” distribution assumption

DocketMath’s allocation can incorporate a timing distribution rather than assuming damages accrue perfectly uniformly over time. Here we assume:

• 70% of the damages occur in the first half
• 30% occur in the second half

Because the covered window (0.5 years) captures most—but not all—of the overall span, a front-loaded pattern generally causes the covered amount to skew higher than a uniform distribution would.

A simple way to interpret what the tool is doing (conceptually) is:

• Determine which portions of the timeline overlap the covered window.
• Map those overlaps onto the “first half” vs. “second half” buckets.
• Apply the bucket percentages to compute allocated covered/uncovered damages.

For this demonstration, assume the distribution-aware computation lands at:

• Allocated covered damages: $108,900
• Allocated time-barred/uncovered damages: $11,100
• Total: $120,000

The exact dollar figures depend on the tool’s internal mapping of dates-to-fractions (e.g., day counts). The important point is directional: with a short default period, the exact overlap matters a lot.

Step 4: Output interpretation (what to do with the numbers)

You’ll typically see DocketMath present outputs as:

• Total claimed
• Covered (potentially recoverable) allocation
• Uncovered (potentially barred) allocation
• Optional breakdown by time bucket

Use these outputs to:

• sanity-check how sensitive damages are to a 0.5-year window
• test alternative event start and filing dates (those often move the coverage fraction significantly when the SOL is short)

Sensitivity check

Short SOL periods often create high sensitivity. Let’s vary one input at a time and observe how the allocation changes.

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 A: Filing date shifts later by 30 days

Keep everything else the same:

• Event start: 2025-01-10
• Claim filed: 2025-08-31 (instead of 2025-08-01)

Now the timeline is closer to 0.64 years.

• Covered fraction ≈ 0.5 / 0.64 ≈ 0.781
• Uncovered fraction ≈ 0.219

Under proration alone:

• Covered ≈ $120,000 × 0.781 = $93,720

With distribution-aware math, the covered figure may be somewhat higher or lower depending on how “front-loaded” buckets overlap the covered window; an illustrative range might be:

• Covered: ~$95,000 to ~$98,000
• Uncovered: ~$22,000 to ~$25,000

Sensitivity B: Event start moves forward by 20 days

Now assume:

• Event start: 2025-01-30
• Claim filed: 2025-08-01
• Total claimed damages: $120,000

Timeline from 2025-01-30 to 2025-08-01 is about 0.52 years—barely above the 0.5-year cutoff.

• Covered fraction ≈ 0.5 / 0.52 ≈ 0.962
• Uncovered fraction ≈ 0.038

Proration estimate:

• Covered ≈ $120,000 × 0.962 = $115,440
• Uncovered ≈ $4,560

A front-loaded timing pattern would likely keep the covered amount high here because most of the damaging timeline falls into the narrow covered portion.

Quick comparison table (illustrative)

Practical takeaway: run what-if tests before committing your damage model

If you’re using DocketMath for planning or evaluation, run at least:

• 1 baseline scenario
• 1 “later filing” scenario (e.g., +30 days)
• 1 “later event start” scenario (e.g., +20 days)

That gives you a range and helps explain why allocation results may look “tight” around the cutoff.

Also, to experiment quickly, go directly to: /tools/damages-allocation.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules