Damages Allocation rule lens: Delaware

The rule in plain language

Run this scenario in DocketMath using the Damages Allocation calculator.

In Delaware, the general Statute of Limitations (SOL) period for many damages claims is 2 years, and the clock starts when the claim “accrues.” For a Damages Allocation rule lens (the way you’d model time-eligible versus time-ineligible damages), the key takeaway is that you may be working with a default limitations clock—especially when you do not have a claim-type-specific limitations rule identified.

Delaware’s general SOL provision for certain actions is in Title 11, § 205(b)(3). Delaware’s code collection for Title 11 is here:
https://delcode.delaware.gov/title11/c002/index.html?utm_source=openai

Important: No claim-type-specific sub-rule was found for this lens. That means this 2-year period should be treated as the general/default baseline, not as a tailored rule for a specific contract or tort category. In practice, you should verify whether the underlying facts and theory point to a different, claim-type-specific limitations period.

What “2 years” means for your allocation timeline

In an allocation workflow, you typically (1) set an accrual date, (2) compute the SOL deadline (2 years later), and then (3) sort damages by whether they fall within the eligible window.

For example:

• If your claim accrues on January 1, 2024, the default 2-year SOL window runs through January 1, 2026 (subject to accrual mechanics and any tolling issues—those are not covered here).
• Damages tied to events that fall outside the eligible accrual-to-deadline window may be treated as time-barred and could be excluded from the eligible bucket in your allocation model, depending on how your input dates map to damages timing.

Because this is a damages allocation lens, the practical question is rarely just “is the claim timely?” Instead, it’s usually: which time slices of damages are eligible versus excluded based on the default limitations window.

Why it matters for calculations

Damages allocation commonly breaks a total figure into components by time (months/quarters), activity (phases), or event category. The SOL affects that breakdown because eligibility can vary by when damages occurred or when they’re considered to have accrued for your theory.

Concretely, the 2-year default SOL changes at least three model steps:

1. Which periods qualify:
   If you model damages monthly or quarterly, you need to determine which months/quarters fall inside the SOL window.

2. How to prorate time-spread losses:
   If you enter damages as a lump sum but it is really attributable to a span of time, your allocation may require proration across the portion of that span that lands inside the eligible period.

3. What the output “eligible bucket” means:
   Your allocation output is often presented as:

   • Eligible damages (inside the SOL window)
   • Potentially excluded damages (outside the SOL window)
   • Net eligible total based on your modeling assumptions

Delaware default SOL inputs that drive the math

Use this checklist to connect the statute to the allocation model in a consistent way:

How outputs change when you adjust dates

Even small date changes can noticeably alter the eligible portion of a time-sliced damages timeline. A simple sensitivity view looks like this:

Delaware citation lens (what you should plug into your model)

For this Delaware Damages Allocation rule lens, treat these as your modeling anchors:

• Delaware general SOL period: 2 years
• General statute cited for this lens: **Title 11, § 205(b)(3)
• Source: https://delcode.delaware.gov/title11/c002/index.html?utm_source=openai

Use the calculator

DocketMath’s damages-allocation calculator helps you apply time-based eligibility to your damages timeline using the Delaware default 2-year SOL as the baseline.

Run the Damages Allocation calculation in DocketMath, then save the output so it can be audited later: Open the calculator.

Step-by-step: set up inputs in DocketMath

1. Open the tool: go to /tools/damages-allocation
2. Select jurisdiction: choose **Delaware (US-DE)
3. Enter the accrual date: the date your claim is treated as accruing for SOL purposes in your model
4. Enter your damages timeline inputs:

   • If you have time-sliced amounts (e.g., monthly totals), enter those by period.
   • If you have a single total incurred over a span, enter:

     • the total damages amount, and
     • the start/end dates of when those damages accrued/incurred so the tool can allocate by time.
5. Run the allocation: the calculator separates damages into “within SOL window” vs. “outside SOL window” buckets using the 2-year default.

If you’re also building broader case inputs, you can keep your workflow consistent by starting with /tools/damages-allocation.

What to expect from the output

A typical damages allocation output conceptually includes:

• Total damages input
• **Eligible damages (within default SOL window)
• **Potentially excluded damages (outside default SOL window)
• Net eligible total based on your time-eligibility mapping

Because you’re using a default general SOL rule, the output should be treated as a modeling allocation of damages eligibility, not a definitive legal determination.

Quick example (illustrative)

• Accrual date entered: May 1, 2023
• Default SOL length: 2 years → SOL deadline: May 1, 2025
• You have monthly damages from Jan 2023 through Dec 2025

In a time-based allocation model, the tool typically classifies months as:

• outside the eligible lookback (before the deadline threshold, depending on your mapping),
• eligible within the SOL window,
• and outside the default SOL window after the deadline.

The exact month-by-month classification depends on how you input period dates and how the tool prorates or filters totals.

Practical tips to get more reliable allocation math

• Prefer period-based damages (monthly/quarterly) over lump sums when available.
• If using a lump sum, include start/end dates that are supportable as the span when the losses occurred.
• Keep your date convention consistent: if your damages are “incurred” monthly, align your mapping to the same monthly convention.

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