Worked example: Damages Allocation in Texas

Example inputs

This worked example shows how DocketMath can allocate damages in a Texas scenario using jurisdiction-aware rules and a general limitations-period default.

Because this example is set up for the US-TX jurisdiction you specified, we apply the general/default approach reflected in Texas Code of Criminal Procedure, Chapter 12 (as provided). This example is meant to demonstrate the calculation workflow and allocation mechanics; it does not attempt to cover every Texas claim category or every factual pattern that could affect a real limitations analysis.

Scenario (fictional but realistic numbers)

A plaintiff files a damages claim in Texas. The case involves:

• Past damages: costs/expenses incurred before filing
• Future damages: projected costs after filing
• Multiple components that must be allocated between time periods

Dates used

• Date of incident / accrual start: 2019-03-01
• Date suit is filed: 2022-08-15

Damages components (before allocation)

You can enter a breakdown so the calculator allocates amounts across eligible time windows.

Total baseline damages: $42,500 + $18,750 + $2,250 = $63,500

Texas limitations-period parameter used by DocketMath (default)

Per your provided jurisdiction data, DocketMath uses:

• General SOL Period: 0.0833333333 years
• General/default period basis: Texas Code of Criminal Procedure, Chapter 12
• Source: https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm

Important clarity point: No claim-type-specific sub-rule was found in the provided jurisdiction data, so this example uses the general/default period for the full allocation. If later you configure a claim-type-specific limitations rule, the allocation window—and results—can change substantially.

Gentle caution: If the underlying matter is not governed by Texas Code of Criminal Procedure, Chapter 12 (for example, many civil damages frameworks rely on different limitations statutes), the numeric window modeled here may not match the real-world rule for your claim.

DocketMath input checklist (what you’ll enter)

• Jurisdiction: US-TX
• Limitations period: 0.0833333333 years (general/default)
• Incident/accrual start date: 2019-03-01
• Suit filed date: 2022-08-15
• Damages components totals:

  • Past $42,500
  • Future $18,750
  • Other adjustments $2,250
• Allocation method: time-window allocation (split past vs. eligible window)

Example run

Below is the “shape” of the run you’d expect from DocketMath → damages-allocation in Texas (US-TX) using the general/default parameters above.

Step 1: Convert the general/default SOL period into days

DocketMath uses:

• 0.0833333333 years

Using 1 year ≈ 365 days:

• 0.0833333333 × 365 ≈ 30.4167 days

So, in this time-window model, the eligibility “lookback” is treated as roughly 30.4 days.

Step 2: Determine the time between incident start and filing

From 2019-03-01 to 2022-08-15 is about:

• 2019-03-01 → 2022-03-01: 3 years
• 2022-03-01 → 2022-08-15: ~5.5 months

Overall: roughly 3.46 years (about 1,264 days).

Step 3: Apply the eligible window to allocate past damages

Because the eligible window modeled here is only about 30.4 days, DocketMath allocates only a small fraction of past damages into the eligible band and treats the remainder as outside the window.

For proportional time-window allocation:

• Eligible fraction ≈ eligible days / total days
• Eligible fraction ≈ 30.4167 / 1,264 ≈ 0.0241 (about 2.41%)

Allocate the Past component ($42,500):

• Eligible past ≈ $42,500 × 0.0241 ≈ $1,024
• Ineligible past ≈ $42,500 − $1,024 ≈ $41,476

Step 4: Handle Future and Other adjustments

In this worked example, DocketMath keeps the non-past components in the model’s “not limited by the same lookback” bucket:

• Future damages ($18,750): not reduced by the same lookback window in this model (so it stays whole)
• Other adjustments ($2,250): carried through, then combined with eligible/ineligible totals as appropriate

Step 5: Produce the allocation output

The run output is a structured split into “eligible” and “ineligible” buckets.

Baseline total: $63,500
Eligible + ineligible: $22,024 + $41,476 = $63,500 ✅

Key takeaway: With a very short general/default limitations window (about ~30 days modeled here), filing timing dominates the eligible portion of past damages.

Step 6: Quick audit trail to verify the math

Sanity checks you can do:

• If the eligible window becomes longer, eligible past increases roughly in proportion to eligible days.
• If filing happens closer to accrual, the eligible fraction rises and the ineligible past drops.

Sensitivity check

This section stress-tests the allocation by changing the inputs that most affect a proportional time-window model: (1) filing date and (2) limitations period configuration.

Sensitivity #1: Filing date closer to accrual

Keep damages totals the same, but change suit filed date to 2019-03-25 (about 24 days after accrual start).

• Total days between 2019-03-01 and 2019-03-25: 24 days
• Eligible days modeled: ~30.4167 days
• Eligible fraction would effectively cap at ~100% (you can’t allocate more than all past damages)

Expected effect:

• Eligible past ≈ full $42,500
• Ineligible past ≈ $0
• Future + Other remain the same

Practical takeaway: With a very short limitations window, the allocation is highly sensitive to when the suit is filed relative to accrual.

Sensitivity #2: Different limitations window length (rule configuration)

If your jurisdiction dataset later provides a longer limitations period for the specific claim type, the eligible fraction increases.

Conceptual comparison (illustrative only):

• Total days stays ~1,264
• If eligible days were 365 days instead of ~30.4 days:

  • Eligible fraction ≈ 365 / 1,264 ≈ 0.289
  • Eligible past ≈ $42,500 × 0.289 ≈ $12,283 (vs. ~$1,024)

So even a change from ~30 days to ~365 days can be an order-of-magnitude effect on the eligible past amount.

Pitfall to watch: If the SOL logic is configured from the wrong legal framework (e.g., using a criminal-procedure chapter for a civil damages timetable), the allocation window can be dramatically off.

Where to plug this into your workflow

If you’re running DocketMath repeatedly:

• Keep the allocation method consistent (here: time-window allocation).
• Record the limitations-period source used (here: general/default based on Chapter 12 because no claim-type sub-rule was found).
• Run sensitivity checks at least for:

  • Filing date moved ±30 days
  • Limitations period swapped to any claim-type-specific rule you may later have

Related reading

• Browse the blog