Why Damages Allocation results differ in Delaware
5 min read
Published April 15, 2026 • By DocketMath Team
The top 5 reasons results differ
Run this scenario in DocketMath using the Damages Allocation calculator.
When you run DocketMath → damages-allocation for Delaware (US-DE), you may see allocation outcomes that differ from what you expected. In most cases, these differences aren’t caused by “math errors”—they come from rule triggers (especially time limits) and how date roles and buckets are applied.
Below are the top 5 causes that most often change Delaware outputs, even when the underlying damages numbers you entered look the same.
Whether amounts fall inside Delaware’s general 2-year SOL
- Delaware’s general SOL period is 2 years.
- The general rule you should keep in mind is Title 11, §205(b)(3).
- If any portion of the damages timeline you’re modeling falls outside that 2-year window, DocketMath may allocate it differently (for example, by effectively treating part of the damages as not recoverable under the limitations period—depending on how the tool maps “time” into allocation buckets).
**Date selection mismatch (event date vs. filing date vs. notice date)
- Delaware-aware results can change if one workflow uses a different “clock” date than another.
- Even a 30–90 day shift can move damages from “within” to “outside” the 2-year window.
- Practical example: if one run measures from the incident/event date, but your expectation measures from filing/notice, DocketMath will likely classify different slices of damages as time-barred or not.
How recoverable periods are segmented into buckets
- Damages allocation often depends on splitting damages into time buckets (e.g., before vs. after a cutoff date).
- If DocketMath’s segmentation aligns to a different cutoff or internal breakpoint than your prior spreadsheet logic, the proportions can shift noticeably—even if the total damages you entered are identical.
Overlapping conduct or multiple damage streams
- Allocation can vary when the record includes more than one relevant conduct date or multiple streams (e.g., different alleged periods that overlap).
- If you compress several event dates into a single “start date” (or combine time ranges too aggressively), you can accidentally expand or shrink the portion that lands inside the general 2-year framework used by the calculator.
Input normalization and rounding conventions
- Small differences from rounding (especially with decimals, “annualized” figures, or partial periods) can alter the final allocation totals.
- DocketMath may normalize or round in a way that differs from a spreadsheet, so two visually similar inputs can yield different allocations.
Common pitfall: If one run uses incident/event date as the anchor while the other uses demand/filing/notice date, Delaware outputs can diverge even though your damages amounts match.
How to isolate the variable
To determine what’s driving the difference, isolate one variable at a time. Here’s a fast, practical diagnostic workflow you can run with DocketMath:
Identify the exact start/end dates you’re feeding into the limitations logic (commonly: incident/event vs. filing date).
Goal: make sure you’re not comparing apples to oranges across runs.
Temporarily collapse multiple event dates into one start/end range.
If the outputs converge afterward, the discrepancy was likely driven by segmentation or overlapping time periods.
Change one thing: the cutoff alignment or the role of the same dates (for example, “event-to-filing” vs. another date relationship), while keeping damages amounts constant.
If results change sharply, your difference is likely time-window classification rather than the damages math.
For the Delaware jurisdiction data used here, there is a general/default limitations period of 2 years tied to Title 11, §205(b)(3).
Per your briefing, no claim-type-specific sub-rule was found, so you should not assume special carve-outs are being applied unless you explicitly map them beyond what’s in the provided data.
Source used for the statutory anchor: https://delcode.delaware.gov/title11/c002/index.html?utm_source=openai
If you used rounded annual figures, re-enter with full precision (or match your earlier spreadsheet precision exactly).
Re-run and compare—rounding/normalization can shift allocation outputs.
Quick statute anchor to keep in view: Delaware’s general rule in this dataset is Title 11, §205(b)(3) (general 2-year SOL).
Source: https://delcode.delaware.gov/title11/c002/index.html?utm_source=openai
Next steps
Once you’ve identified what’s different, move from diagnosis to a repeatable explanation:
Lock your date definitions
- Write down exactly which date you treat as the limitations “start” and which date you treat as the “end” in your workflow.
Run a baseline with a clean timeline
- Use a single, consistent timeline and verify the output matches your expectations under Delaware’s general 2-year approach (Title 11, §205(b)(3)).
Run sensitivity checks
- Shift the start date in 30-day increments (keeping damages amounts constant) and observe how the allocation changes.
- This quickly tells you whether the difference is primarily time-driven (SOL/bucket classification) or structure-driven (segmentation/multiple streams).
Save the exact input set
- When you find the combination that produces the result you’re trying to explain, save those inputs so you can reproduce the outcome and compare against the prior run that diverged.
Gentle disclaimer: This content is for workflow and calculator-understanding purposes. It’s not legal advice, and it can’t substitute for a review of the specific facts and Delaware law applicable to your situation.