Worked example: Damages Allocation in Maryland

Example inputs

Run this scenario in DocketMath using the Damages Allocation calculator.

This worked example shows how DocketMath calculates a damages allocation in Maryland using the tool’s jurisdiction-aware rules and a general SOL baseline.

Because you requested a worked example (not legal advice), treat this as an illustration of how the calculator can be used to structure numbers—not a prediction of outcomes in any particular case.

Jurisdiction rule applied (Maryland)

Maryland’s default/general limitations period for most civil actions is 3 years, under:

• Md. Code, Cts. & Jud. Proc. § 5-106 (general/default period)

Example scenario (numbers used for the calculation)

Assume a plaintiff alleges a damages mix that must be allocated across time-based buckets to help determine what portion may fall within the limitations “lookback” window implied by the general 3-year SOL.

Use these example inputs:

If your case uses different allocation logic (for example, discrete invoices or discrete work milestones), you’d adjust the allocation basis inputs accordingly—but the Maryland SOL baseline remains 3 years under § 5-106 for this general example.

What DocketMath uses behind the scenes (high-level)

The damages-allocation calculator uses the jurisdiction code US-MD and the general SOL period (3 years) to identify the lookback window from the filing date. Then it applies your allocation basis to assign each damages category to the portion that falls inside the allowed time window.

For a direct run, start at: /tools/damages-allocation

Example run

Here’s how the run plays out step-by-step in a typical “pro rata by months” workflow.

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: Determine the Maryland SOL lookback window

• SOL period (general/default): 3 years
• Filing date: 2025-03-15
• Lookback start date: 2022-03-15 (3 years prior)

Because the example’s trigger/occurrence date is 2022-01-10, part of the claimed period falls before the lookback start date.

• Claimed timeline begins: 2022-01-10
• Lookback window begins: 2022-03-15
• Therefore, some early portion is outside the 3-year baseline window.

Step 2: Convert the timeline into month buckets

With a pro rata by months approach, the calculator measures:

• Total months in the claimed period (from 2022-01-10 to 2025-03-15)
• Allowed months inside the SOL window (from 2022-03-15 to 2025-03-15)

For this example, a month-based approximation yields:

• Total claimed months: 38 months
• Allowed months (within SOL window): 36 months

So the allowed fraction is:

• 36 / 38 ≈ 0.9474 (about 94.74% of claimed damages fall within the SOL window)

Step 3: Allocate each damages category

The tool then applies the allowed fraction to each damages component:

Rounding can cause the total to be off by a small amount (here, essentially $90,000).

Step 4: Output interpretation (what “allocated” means)

In this setup, DocketMath’s damages-allocation output effectively answers:

• “What portion of the claimed damages sits inside the 3-year window implied by Md. Code, Cts. & Jud. Proc. § 5-106?”

It does not decide liability. It also does not replace pleading-specific legal analysis. Instead, it provides a structured numerical allocation that can help quantify exposure tied to the lookback window.

Sensitivity check

Even with a fixed 3-year baseline under § 5-106, small date changes can shift the allocated result—especially when the alleged start date is close to the lookback boundary.

Below are three sensitivity variations using the same total claimed damages ($95,000) and the same simplified pro rata approach.

Variation 1: Filing date shifts by 30 days later

• Filing date becomes 2025-04-14
• Lookback start becomes 2022-04-14
• The allowed fraction decreases slightly because more early months fall outside the window.

Illustrative effect: if allowed fraction drops from 0.9474 to 0.9211, then:

• $95,000 × 0.9211 ≈ $87,500

Variation 2: Occurrence date starts later

Keep the filing date fixed (2025-03-15) but change trigger/occurrence date from 2022-01-10 to 2022-02-15.

That reduces the “pre-lookback” portion, so the allowed fraction increases.

Illustrative effect: if allowed fraction rises to 0.9737, then:

• $95,000 × 0.9737 ≈ $92,500

Variation 3: Switch allocation basis away from pro rata by months

If you change allocation logic (for example, modeling that dollars are weighted toward later months), the allocated totals can move without changing the SOL lookback dates.

For intuition:

• Category C may be mostly earned near the end of the period
• Category A may be mostly earned near the beginning

Even with the same SOL window, re-mapping “when money was earned” changes what portion lands inside the allowed time.

Quick checklist for what to test in DocketMath

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