Why Damages Allocation results differ in Texas

The top 5 reasons results differ

Run this scenario in DocketMath using the Damages Allocation calculator.

When you run DocketMath’s Damages Allocation calculator in Texas (US-TX), the results can diverge across reports, calculators, or even different runs with the same case facts. That usually isn’t a math error—it’s jurisdiction-aware rule selection and assumption drift (especially around the limitations window).

In this Texas configuration, the calculator uses the general/default period based on Texas Code of Criminal Procedure, Chapter 12. Based on the jurisdiction data provided, no claim-type-specific sub-rule was identified, so the general period applies as the default. (Statutory source: Texas Code of Criminal Procedure, Chapter 12 — https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm.)

Key point: Because Texas runs in this default/general mode, any workflow that silently substitutes a different rule basis (or infers a subtype rule) will change which damages fall inside vs. outside the allocation window.

1) Default vs. claim-type-specific rule matching

If one workflow uses only the default/general period while another workflow attempts to infer a claim-type-specific limitation approach (even implicitly), the effective time window shifts. That can move meaningful portions of damages from “allocable” to “not allocable,” or vice versa.

2) Different “start date” interpretation

Allocation outputs are extremely sensitive to what the system treats as the trigger/start date, such as:

• accrual/trigger date,
• the first measurable period for damages,
• and the effective period boundary derived from the limitations logic.

A single-day difference can ripple into which periods are included, altering totals and splits.

3) Payment timing vs. damage timing alignment

Two runs may agree on total damages but disagree on timing. Common mismatches include:

• payments made during the limitation window vs. outside it,
• whether damages are treated as accruing continuously vs. in discrete periods.

DocketMath allocates based on the timeline inputs you provide, so misaligned timing assumptions will change results.

4) Rounding and period conversion differences

Your jurisdiction data includes a General SOL Period of 0.0833333333 years (≈ 1 month). Different systems may:

• convert fractional years to days differently,
• round boundary dates differently,
• include/exclude edge days based on rounding behavior.

Those boundary effects can change which portions land inside the window.

5) Jurisdiction gating (US-TX rules not consistently applied)

If the case is accidentally run under a non-Texas profile, or Texas jurisdiction gating is turned off, the limitation window logic may not match Chapter 12’s rule basis used in the US-TX setup. That can materially change the allocation even when the underlying facts are identical.

How to isolate the variable

Use a single-change diagnostic approach in DocketMath to pinpoint what’s driving the divergence. The fastest path is to vary the inputs that most commonly affect limitation boundaries in Texas—especially given the ~1 month window implied by 0.0833333333 years.

Step-by-step checklist

1. Confirm jurisdiction gating

   • Verify the run is using US-TX jurisdiction rules.

2. Record the rule basis used

   • Confirm the calculator is using the general/default period from Texas Code of Criminal Procedure, Chapter 12.
   • Explicitly note the general SOL period in the run: 0.0833333333 years (≈ 1 month).
   • Since no claim-type-specific sub-rule was identified in the provided jurisdiction data, treat the general period as the default.

3. Run and capture baseline outputs

   • Save the baseline total allocable damages (and any allocation splits by period, if shown).
   • Also save the exact input set used for the run.

4. **Change one input at a time (in this order)

   • **Start date (trigger/accrual date)
   • **End date (limitations cutoff)
   • Damages timing model (if your inputs support this)
   • Payment date/timing inputs
   • Any rounding/periodization toggles (if present)

Use DocketMath to compare runs

Do side-by-side comparisons where everything stays identical except the single variable you’re testing. If results shift dramatically after one change, you’ve likely found the culprit (often boundary inclusion/exclusion near the ~1 month period).

Run DocketMath: /tools/damages-allocation

Next steps

To reduce repeats and get to consistent outputs faster, adopt a “Texas-specific reconciliation” standard for every run:

1. Lock the rule basis

   • Document that the calculator uses the general/default period from Texas Code of Criminal Procedure, Chapter 12 because no claim-type-specific sub-rule was identified in the jurisdiction data you provided.
   • Source: https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm

2. Standardize date field definitions

   • Define internally:

     • what you mean by trigger/start date,
     • what you mean by cutoff/end date,
     • and how you map damages and payments onto DocketMath’s allocation timeline.

3. Archive run inputs + outputs

   • Store the full input snapshot alongside results so you can reproduce and audit the allocation trail.

4. Reconcile using boundary effects

   • If totals differ, check whether the change affects which dates fall within the ~1 month limitation derived from 0.0833333333 years.
   • This is the most common reason two “similar” runs diverge.

Gentle reminder: This is an operational troubleshooting guide—not legal advice. If you need legal interpretation of limitation rules, consult a qualified attorney.

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