Worked example: Damages Allocation in Delaware
5 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Below is a worked example for allocating damages in Delaware (US-DE) using DocketMath’s damages-allocation calculator.
Scenario (fictional numbers for demonstration)
Assume a plaintiff’s civil claim involves:
- a written agreement breach (monetary loss), and
- separate categories of damages shown here for illustration: compensatory damages and interest.
To make the allocation and SOL “time-pruning” visible, we’ll use:
- a claim filing date in Delaware, and
- several damage components each tied to its own event date.
Dates and assumptions used in this example
| Item | Value |
|---|---|
| Claim filing date | March 1, 2026 |
| Damage event A (contract loss) | Jan 15, 2024 |
| Damage event B (ongoing loss) | Jul 10, 2024 |
| Damage event C (interest accrual start) | Nov 1, 2024 |
| Damage amounts (raw) | A: $40,000; B: $25,000; C: $6,500 |
Delaware time rule used (general/default)
In this example, DocketMath needs a statute-of-limitations (SOL) window to determine which damage components are potentially recoverable based on their event dates.
For Delaware, this worked example uses the general/default limitations period provided in the jurisdiction data:
- General SOL Period: 2 years
- General Statute: Title 11, §205(b)(3)
Source: https://delcode.delaware.gov/title11/c002/index.html?utm_source=openai
Important (as provided): No claim-type-specific sub-rule was found in the jurisdiction data. So DocketMath treats Title 11, §205(b)(3) as the default/general period in this example, rather than applying a different deadline based on a specific cause of action.
Note: This is a general/default demonstration. Real cases can involve additional nuances, and this example is not legal advice.
What we enter into DocketMath
On the /tools/damages-allocation workflow, you would typically provide:
- Jurisdiction: US-DE
- Filing date: March 1, 2026
- Damage components: for each component (A, B, C), an event date and a raw amount
- SOL rule: Delaware default/general (2 years under 11 Del. C. §205(b)(3))
Labeling each component (A, B, C) helps you track how the cutoff affects each line item.
Example run
Let’s walk through one DocketMath run step-by-step using the inputs above.
Step 1: Compute the “lookback” cutoff date
- General SOL period: 2 years
- Filing date: March 1, 2026
- Cutoff (earliest date potentially within the period): March 1, 2024
Under the default/general approach used here, damage event components before March 1, 2024 are treated as falling outside the limitations window for purposes of this allocation logic.
Step 2: Classify each damage component by event date
| Component | Event date | Raw amount | Within 2-year window? | Treatment in this allocation example |
|---|---|---|---|---|
| A (contract loss) | Jan 15, 2024 | $40,000 | No (before Mar 1, 2024) | Pruned from recoverable total |
| B (ongoing loss) | Jul 10, 2024 | $25,000 | Yes | Included |
| C (interest accrual start) | Nov 1, 2024 | $6,500 | Yes | Included |
Step 3: Produce the allocated damages totals (illustrative)
DocketMath’s output (illustrative) would be summarized like this:
Recoverable damages (within window):
- Component B: $25,000
- Component C: $6,500
- Total included: $31,500
Time-barred / pruned damages (outside window):
- Component A: $40,000
- Total pruned: $40,000
Step 4: Show the allocation breakdown
| Category | Included components | Amount |
|---|---|---|
| Included in allocation | B + C | $31,500 |
| Excluded due to SOL cutoff | A | $40,000 |
| Gross illustrative total | A + B + C | $71,500 |
Pitfall: If you enter an incorrect event date for a component (for example, using a “notice date” rather than the date tied to when the loss occurred or began), the cutoff decision can change—moving dollars from “pruned” to “included,” or vice versa.
Where the Delaware rule comes in
This default/general SOL gate is based on the provided Delaware jurisdiction data:
- 11 Del. C. §205(b)(3) (general/default)
- 2-year window applied in this example
Source: https://delcode.delaware.gov/title11/c002/index.html?utm_source=openai
Sensitivity check
Now test how sensitive the allocation is to date choices, because SOL-driven allocation often turns on boundary dates.
Sensitivity test A: Filing date moved by 30 days
Change only the filing date, keep component event dates the same.
- Original filing date: March 1, 2026
- New filing date: March 31, 2026
- New cutoff becomes: March 31, 2024
Re-check inclusion:
- Component A: Jan 15, 2024 → still outside
- Component B: Jul 10, 2024 → inside
- Component C: Nov 1, 2024 → inside
Result: No change in included/pruned amounts.
Included total: still $31,500
Sensitivity test B: Component A moved closer to the cutoff
Now move Component A’s event date toward the cutoff.
- Component A event date updated: Jan 15, 2024 → Mar 10, 2024
- Filing date remains: March 1, 2026
- Cutoff remains: Mar 1, 2024
Re-check inclusion:
- Component A: Mar 10, 2024 → now inside
- Component B: Jul 10, 2024 → inside
- Component C: Nov 1, 2024 → inside
New included total:
A ($40,000) + B ($25,000) + C ($6,500) = $71,500
That is an increase of $40,000, driven entirely by moving one component’s event date past the cutoff.
Quick sensitivity summary (what matters most)
- The allocation is most sensitive to:
- the filing date, and
- each damage component’s event date
- In this worked example, Delaware’s default/general gatekeeper is:
- 2 years under 11 Del. C. §205(b)(3) (because no claim-type-specific sub-rule was provided)
Warning (practical): Try to use event dates that reflect when the damages category is meaningfully tied to the underlying facts—not accounting dates that merely record when paperwork was generated.