Inputs you need for Damages Allocation in Maryland

Inputs you will need

To allocate damages in Maryland with DocketMath—using the damages-allocation calculator—you’ll typically need a clear set of case “building blocks.” These inputs determine (1) which components are counted toward damages, (2) how they’re allocated across parties or categories, and (3) whether time limits (like the general statute of limitations) might affect which claims are included.

Use this checklist to gather the minimum inputs before you start.

Core damages inputs

Allocation logic inputs

Maryland timing input (default SOL framing)

Maryland’s general statute of limitations is typically the starting point when you don’t have a claim-type-specific rule:

Note (important): This guide uses Maryland’s general/default SOL of 3 years under Md. Code, Cts. & Jud. Proc. § 5-106. It does not apply a claim-type-specific sub-rule because none was identified here. That means your analysis will use the general period as the default SOL assumption.

Source: https://codes.findlaw.com/md/courts-and-judicial-proceedings/md-code-cts-and-jud-pro-sect-5-106/?utm_source=openai

Where to find each input

Here’s a practical “source map” for where to pull each input from common case materials. If you’re organizing your file for a consistent workflow, you’ll save time during repeat runs in DocketMath.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

Damages categories and dollar amounts

Dates tied to damages

Payments already made and offsets

Allocation basis (shares/weights)

Maryland SOL timing inputs (general rule)

For timing, you’re primarily relying on:

• Md. Code, Cts. & Jud. Proc. § 5-106 for the general SOL period of 3 years
  Source: https://codes.findlaw.com/md/courts-and-judicial-proceedings/md-code-cts-and-jud-pro-sect-5-106/?utm_source=openai

Then you map those dates:

Run it

Once your inputs are ready, run the DocketMath tool here: /tools/damages-allocation.

In a typical workflow, you’ll see outputs that help you allocate dollars and (if enabled in the tool) evaluate SOL timing assumptions using Maryland’s general rule.

What to expect from the calculator

1. Allocation results

   • DocketMath applies your allocation basis (shares/weights or a distribution rule) to the category totals.
   • Output changes when you update any of the following:

     • damages category amounts
     • weights/shares
     • offsets/payments made
     • category-to-party mapping

2. **SOL timing filter (default/general)

   • If the tool includes SOL logic, it uses the 3-year general period under Md. Code, Cts. & Jud. Proc. § 5-106 as the default.
   • Because no claim-type-specific sub-rule is used here, the output reflects that general/default assumption.

Practical “input sensitivity” checks

Before relying on an output, test that the model is behaving as you expect:

Gentle reminder: This is an analytical workflow tool, not legal advice. If your case involves unusual facts or a potentially different limitations rule, consider validating assumptions with a qualified professional.

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