How to run Damages Allocation in DocketMath for Delaware

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide walks you through running Damages Allocation in DocketMath for Delaware (US-DE). It uses jurisdiction-aware rules, including Delaware’s general statute of limitations (SOL), so your allocation timeline and any SOL-related warnings are consistent with the Delaware setup in the calculator.

1) Open the Delaware Damages Allocation calculator

Start at the primary CTA:

• /tools/damages-allocation

Once the calculator loads, confirm you’re in Delaware (US-DE) mode. DocketMath’s jurisdiction-aware rules determine which SOL period is used and how date-related warnings are evaluated.

2) Add the basic case timeline inputs

In Damages Allocation, you’ll typically define a timeline and the categories you want allocated. Before entering anything, gather the dates your workflow uses:

• Key event date(s) (e.g., accrual or occurrence date you’re modeling)
• Filing date (or the date the claim is treated as filed for your workflow)
• Any relevant decision date(s) if your workflow uses multiple stages

How inputs change outputs: after you enter dates, the calculator can determine whether the allocation portion falls inside or outside the configured SOL window. For Delaware, DocketMath will use the general/default SOL described next.

3) Enter amounts to allocate by category

Damages Allocation is designed to distribute totals across categories. Use the calculator’s category controls to input:

• Total damages (if your interface expects a single number), or
• Category amounts (if your interface expects you to split)

If your scenario uses multiple damage components, keep the amounts consistent with how you plan to report totals. After you run, DocketMath typically summarizes:

• Allocated totals per category
• Aggregate totals
• Timing/SOL-based flags tied to those allocations (when applicable)

4) Confirm the SOL rule Delaware will apply

This Delaware Damages Allocation run uses the general/default SOL period, because no claim-type-specific sub-rule was found in the provided jurisdiction data.

• General SOL Period: 2 years
• Delaware General Statute: **Title 11, §205(b)(3)
• Source: Delaware Code (Title 11, §205(b)(3)) https://delcode.delaware.gov/title11/c002/index.html?utm_source=openai

Important configuration detail:
DocketMath will apply the general/default period (2 years) as the SOL used for the Delaware setup, because no claim-type-specific sub-rule was found in the jurisdiction data provided.

5) Run the allocation

After dates and amounts are entered:

• Click the calculator’s Run / Calculate action (wording may vary by interface version).
• Review the results summary.

Outputs to expect to review:

• Allocation breakdown (by category)
• Timing impact (whether allocation portions are treated as within/outside the configured SOL window)
• Any warnings or flags tied to the 2-year general/default period

6) Adjust inputs and compare outputs

A practical workflow is iterative—change one thing at a time so you can see what drives changes in the output.

Try these controlled adjustments:

• Move the filing date by days/weeks to see if a SOL-related flag flips
• Adjust the event/accrual date to test which allocations remain inside the 2-year window
• If you entered multiple categories, change only one category amount to isolate how totals and summaries respond

This is especially useful when reconciling inconsistent records, because the tool should make the numeric effects visible in each run.

7) Export or capture the results

When the results match what you need for your workflow:

• Screenshot the results, or
• Export/copy results if DocketMath provides an export option

Also save the input dates and category amounts alongside your output so you can reproduce the allocation later.

Common pitfalls

Delaware is straightforward in this setup because the configuration uses a single general/default SOL period. Still, the most common mistakes are typically about date mechanics and category math, not “legal complexity.”

• missing a required input
• using a stale rate or rule
• ignoring calendar or holiday adjustments
• skipping documentation of assumptions

Pitfall checklist

• In this Delaware configuration, DocketMath uses the general/default SOL (2 years) under Title 11, §205(b)(3) because no claim-type-specific sub-rule was found.

Quick reference: Delaware SOL used in this tool run

Try it

1. Go to /tools/damages-allocation.
2. Select/confirm Delaware (US-DE) jurisdiction mode.
3. Enter:

   • Event/accrual date
   • Filing date
   • Damages category amounts (or total, depending on the input layout)
4. Click Calculate/Run.
5. Look for:

   • Allocation totals by category
   • SOL-related timing warnings/flags based on the 2-year general/default SOL under **Title 11, §205(b)(3)

To stress-test your inputs quickly:

• Keep category amounts constant.
• Change only the filing date by a small interval (e.g., 30 days) and re-run.
• Check whether the SOL-related timing status flips. If it does, downstream reporting and issue-spotting will be sensitive to filing-date accuracy.

You can also run two versions:

• Version A: earlier filing date
• Version B: later filing date
  Then compare results side-by-side to see how strongly the 2-year window affects the allocation output.

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