Inputs you need for Damages Allocation in Delaware
4 min read
Published April 15, 2026 • By DocketMath Team
Inputs you will need
Damages allocation in Delaware usually turns on what damages you’re allocating and when the claim accrued—because Delaware generally limits how far back you can recover based on the statute of limitations. Using DocketMath (jurisdiction-aware for Delaware / US-DE), you’ll want a tight set of inputs so the calculator can allocate damages consistently.
Here’s the practical checklist of inputs to gather before you run /tools/damages-allocation:
Important Delaware rule used here (default): Delaware’s general/default statute of limitations period for many civil claims is 2 years, referenced here as Title 11, §205(b)(3). No claim-type-specific sub-rule was identified for this workflow, so the 2-year default is treated as the governing limitation period for purposes of this calculator run. (Source: https://delcode.delaware.gov/title11/c002/index.html?utm_source=openai)
How these inputs affect the output
- Accrual date + the 2-year window can reduce recoverable time frames, shifting money from “recoverable” to “time-barred” (depending on how your allocation is structured in your workflow).
- Damages start/end dates determine which portions of your damages fall inside vs. outside the limitation window.
- Category amounts determine how DocketMath allocates totals across your chosen buckets (past/future, economic/non-economic, or other splits you set up).
- Offset/mitigation amounts reduce the net amounts attributed to specific periods or categories, which changes totals and downstream allocations.
Where to find each input
Use the checklist below to locate the information you’ll plug into DocketMath. The goal is to capture dates and sums you can defend in a case narrative or damages summary.
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.
1) Jurisdiction (US-DE)
- In DocketMath, set Jurisdiction = Delaware (US-DE) so the tool applies Title 11, §205(b)(3)’s 2-year default limitation period.
2) Accrual date
Common places to locate it:
3) Damages start date and end date
Look for:
4) Damages categories and category amounts
You typically already have these in:
If you’re allocating by period, organize amounts so each category can be mapped to dates.
5) Mitigation/offset amounts
Track:
6) Allocation method selection (in DocketMath)
Inside DocketMath, choose the allocation structure that matches your damages framing. If your team separates “recoverable time window” from “outside window,” make sure the method you select supports that workflow.
If your goal is to align your inputs to a consistent timeline/model, you may also find it helpful to review:
Run it
Ready to run Damages Allocation in Delaware?
- Go to /tools/damages-allocation (your primary CTA).
- Confirm the calculator is set to:
- **Jurisdiction: Delaware (US-DE)
- Enter the inputs from the checklist:
- Accrual date
- Damages start and end dates
- Category amounts (and any offsets)
- Select the allocation method that matches how your damages should be bucketed.
- Run the calculation and review outputs:
- Allocated amounts by category
- Any separation between recoverable and non-recoverable time ranges based on the 2-year limitation window from **Title 11, §205(b)(3)
Warning / planning note: The tool run uses the Delaware 2-year default because no claim-type-specific limitations sub-rule was identified for this workflow. If your case involves a statutory cause of action with a different limitations scheme, the governing period may not be Title 11, §205(b)(3)—that difference can materially change what portions of your damages are allocated as recoverable.
What to sanity-check after you run
Use this quick audit list:
If totals look off, adjust the inputs rather than forcing an interpretation—allocation outputs are only as accurate as the dates and amounts you feed into DocketMath.