Common Damages Allocation mistakes in Maryland

The top mistakes

Damages allocation errors can quietly undermine a Maryland case even when the liability story is strong. Using DocketMath’s damages-allocation calculator can help you sanity-check your numbers, but most mistakes come from inputs and assumptions—not from the math.

Below are the most common allocation pitfalls we see in Maryland (US-MD) litigation workflows.

1) Confusing “damages allocation” with “whether the claim is timely”

A common workflow error is treating the damages allocation step as a substitute for confirming the claim is timely. In Maryland, the general limitations period is 3 years, governed by:

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

Clear baseline: No claim-type-specific sub-rule was identified in the provided materials, so this guide treats § 5-106’s 3-year general period as the default for timing questions. Claim-specific rules may differ—verify them separately if your situation involves a specialized limitations framework.

Why it leads to allocation problems: teams sometimes allocate damages in detail and only later discover a timeliness issue. Once a claim is barred (or partially barred), the “best” allocation approach becomes less relevant to what can actually be recovered.

2) Picking a past-damages “time slice” that doesn’t match the SOL window

Another frequent issue is choosing a lookback window for past damages that doesn’t align with the limitations period. Even if your component amounts are accurate, the allocation can be distorted if the modeled date range includes amounts that should be excluded under § 5-106.

What DocketMath typically requires from you:

• a loss start date
• a loss end date
• any carve-outs or category structure you want reflected

If your loss period extends beyond the 3-year general period, the calculator may still return an internally consistent allocation—but it may conflict with Maryland timeliness constraints under § 5-106.

3) Entering inconsistent components (double-counting or omission)

Damages models often break down into components—commonly:

• economic losses (out-of-pocket costs, measurable losses)
• non-economic damages (if included in your model)
• future damages (if you model them)

A typical error is either:

• double-counting the same cost (e.g., including it in both a category and a “total” bucket), or
• omitting a component in one part of the structure, so the allocation no longer reconciles.

Quick integrity check in DocketMath:

• If you enter both category line items and a “total damages” figure, ensure the totals reconcile.
• If DocketMath asks for multiple inputs (amounts and percentages), confirm the structure isn’t counting the same dollars more than once.

4) Using allocation percentages that don’t match the scenario you’re modeling

Allocation percentages are only useful if they correspond to the same universe and the same mechanism you intend to model. Otherwise, you can produce a result that looks “reasonable” but answers the wrong question.

Examples of mismatches:

• You used percentages intended for one narrative (e.g., trial presentation) but are applying them as if they govern a different model (e.g., settlement allocation).
• You applied “partial-universe” percentages to totals that represent the “full universe,” or vice versa.

What to check before you calculate:

• confirm the allocation basis the calculator is using
• ensure the percentage totals align with the calculator’s expectation (commonly 100%, depending on design)
• don’t mix percentages built for one subset of claims/categories with totals built for another

5) Treating future damages as automatically covered by the same date logic as past damages

When future damages are modeled, teams sometimes reuse the past-damages slicing approach without thinking through how the timeline ties to the claim theory.

Under Md. Code, Cts. & Jud. Proc. § 5-106, the general limitations period governs whether claims are timely. Future-damages modeling can still be appropriate, but it must be consistent with the underlying timing and accrual framework for what is being claimed.

Common failure mode: future losses are entered starting from a date that assumes the entire claim is timely, without checking the timeline logic for your cause of action and limitations structure.

6) Failing to keep inputs auditable for later revisions

Damages allocation is rarely “one and done.” New discovery can change:

• the dates you believe are relevant
• category amounts
• the allocation percentages and structure

If your inputs aren’t traceable, you can’t reliably explain why results changed.

Where this shows up in DocketMath workflows:

• loss date fields get changed but the reason isn’t recorded
• components are renamed or re-grouped without noting it
• amounts are entered as “gross” vs. “net/adjusted” without tracking which is which

Even if the calculator is correct, untracked changes create confusion—and can lead to incorrect conclusions.

How to avoid them

You can reduce damages allocation errors quickly by using a disciplined checklist around your DocketMath damages-allocation run—especially for Maryland timing under Md. Code, Cts. & Jud. Proc. § 5-106.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

Step 1: Lock the limitations baseline up front (Maryland default)

Maryland’s general limitations period is 3 years under:

• Md. Code, Cts. & Jud. Proc. § 5-106

Given the provided materials, treat § 5-106’s 3-year general period as the default unless you confirm a claim-specific limitations rule applies.

Step 2: Enter a consistent date window in DocketMath

Use DocketMath to align your loss period inputs with your limitations framework.

Practical workflow:

• Identify the relevant loss start and loss end dates for claimed damages.
• Compare that window to the 3-year baseline from § 5-106.
• If your model is intended to reflect limitations-limited recovery, adjust the loss window accordingly.

If you change the date window, rerun the allocation—don’t estimate the difference.

Step 3: Reconcile totals before you allocate

Before calculating, reconcile inputs every time:

• add up component category amounts
• confirm the sum matches any “total damages” figure you enter (if applicable)
• ensure you’re not counting the same dollar amount twice across categories

If DocketMath output doesn’t “match” your reconciliation, stop and correct the input structure first.

Step 4: Validate allocation percentages against the modeled universe

Before you hit calculate:

• confirm the allocation method matches your scenario (who/what is included)
• ensure percentages add up to the calculator’s expected basis (often 100%)
• verify you’re not applying percentages built for a subset to totals built for a broader subset

Step 5: Separate past and future assumptions in your inputs

Treat future damages as a distinct modeling decision:

• enter future start and end dates explicitly
• keep future assumptions separated from past time-slice logic
• rerun allocations when future dates change

Step 6: Use DocketMath for “what changed” scenarios

DocketMath is especially valuable for sensitivity testing. Try three runs:

1. your current input set
2. shift the loss end date by a consistent amount (e.g., 30–90 days)
3. remove or adjust one component category to confirm it isn’t double-counted

If the output swings unexpectedly, it’s usually an input-structure problem, not a real-world valuation shift.

Step 7: Capture your input set for repeatability

For each DocketMath run, record:

• the date window(s)
• the category amounts and allocation percentages
• what you changed (and why), especially if limitations-driven date slicing is involved

This audit trail helps you review outcomes across drafts with less guesswork.

If you want to run your own model, start 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