Damages Allocation rule lens: Maryland

The rule in plain language

Maryland’s baseline statute of limitations (SOL) for many civil claims is 3 years under Md. Code, Courts & Judicial Proceedings § 5-106. This is the default “catch-all” SOL when a claim-specific limitations period does not apply.

In DocketMath’s Damages Allocation lens for Maryland (US-MD), § 5-106 is used as the jurisdiction-aware starting point for timing questions that can affect what damages periods you include in a damages allocation workflow.

What § 5-106 is (in practical terms)

Under Md. Code, Cts. & Jud. Proc. § 5-106, the general limitations period is 3 years. The operational consequence is that damages are often “gated” by time—meaning you may only allocate damages for the portion of the timeline that falls within the allowed filing window.

How the time window typically drives allocation

In a damages allocation exercise, the question is often less about whether damages exist and more about which portion of the damages timeline belongs in the damages math.

When the 3-year SOL applies (via § 5-106), the includable damages timeframe is commonly anchored to date concepts such as:

• the incident / accrual point (depending on the claim’s accrual mechanics)
• the date the action is filed
• a resulting lookback period (often described as “within the prior 3 years,” subject to how the accrual date is determined for the claim)

Because DocketMath’s allocation workflow is date-driven, applying the correct SOL lens helps keep your included-vs-excluded damages periods consistent with Maryland’s default timing rule.

Concrete inputs that feed the allocation

In practice, a damages allocation run typically requires you to enter or align inputs like:

• Filing date (the lawsuit filing date)
• Timeline start (earliest damages accrual date you want to model)
• Timeline end (latest accrual date / cutoff date)
• Damage stream method (one-time vs. recurring vs. event-based)
• Amounts by period (e.g., monthly/quarterly amounts, or category totals tied to dates)

Once those dates are set, the 3-year rule under Md. Code, Cts. & Jud. Proc. § 5-106 determines whether portions of the timeline fall within or outside the SOL window for allocation purposes.

Watch-outs when building an allocation model

When you apply the general/default SOL timeline, a few common modeling issues come up:

• Partial periods / non-aligned dates: If your damages data is monthly but the SOL “gate” cuts mid-month, you may need a proportional (partial-period) approach so included amounts reflect the actual boundary.
• Category overlap: If different categories begin accruing at different times, a single SOL window won’t automatically mean every category is fully included.
• Default rule assumption: Because no claim-type-specific sub-rule was found for this lens, your workflow should reflect that § 5-106 is being used as the general/default limitations period.

Caution (not legal advice): If a claim-specific SOL applies to your particular cause of action, relying solely on the 3-year default rule in § 5-106 could misstate the included damages period and distort allocation totals.

Maryland citation anchored in the lens

• Md. Code, Cts. & Jud. Proc. § 5-106 — 3-year general/default SOL used as the baseline when no claim-type-specific SOL sub-rule applies.
  Primary source: https://codes.findlaw.com/md/courts-and-judicial-proceedings/md-code-cts-and-jud-pro-sect-5-106/?utm_source=openai

Why it matters for calculations

A damages allocation lens is usually about allocation boundaries—which means SOL timing can change the shape of the damages result even when the overall damages concept is the same.

Small differences in the rule text can change the output materially. Using the correct jurisdiction and effective date ensures the calculation aligns with the authority that applies to your matter.

The SOL-lens effect: shrinking or shifting the damages period

When the 3-year SOL applies under § 5-106, the included damages timeframe is generally tied to the filing date and the relevant accrual/date framework used in the model. Practically, that can produce two common effects:

• Shrinking the included period: Earlier damages fall outside the 3-year window and must be excluded from the includable allocation total.
• Shifting which periods are included: If your filing date or your assumed accrual timeline changes, the lookback window shifts, and different segments of your damages schedule may move from excluded to included (or vice versa).

In DocketMath, this means your output is sensitive to the timeline boundaries you enter.

What to expect in your allocation math

When DocketMath applies the SOL lens, your results typically reflect:

• Included period totals: the portion of damages occurring within the SOL window
• Excluded period totals: the portion outside the window
• Category-by-category allocation: if you break damages into components that attach to different dates
• Sensitivity to inputs: an audit trail showing how changes in the dates alter totals

Concrete “input → output” examples to try

Because the SOL gating is date-driven, small input changes often move numbers quickly. For instance:

• Moving the filing date later: can shift the lookback window forward, changing which earlier periods are included/excluded.
• Moving the accrual start date later: can drop earlier months/quarters even if the filing date is unchanged.
• Cutting off damages earlier: can reduce totals because fewer periods exist to be evaluated against the SOL gate.

Use the calculator

You can run this through DocketMath using the Damages Allocation calculator configured for Maryland (US-MD).

Run the Damages Allocation calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Step-by-step: inputs that change the output

To align your data with the SOL-lens logic in this Maryland lens:

Once those dates are provided, the calculator applies the 3-year default SOL under Md. Code, Cts. & Jud. Proc. § 5-106 to determine which portions of the timeline are includable.

Get started directly

Open the Maryland damages allocation tool here: **/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