How to run Damages Allocation in DocketMath for Texas

Step-by-step

Run this scenario in DocketMath using the Damages Allocation calculator.

This guide walks you through running Damages Allocation in DocketMath for Texas (US-TX). The goal is to help you understand what to enter, how jurisdiction-aware rules affect the calculation, and how to interpret the output—without giving legal advice.

1) Open the correct calculator in DocketMath

1. Go to /tools/damages-allocation
2. Confirm the jurisdiction is set to Texas (US-TX).
3. Review the calculator name shown at the top to ensure you’re using Damages Allocation (not a different damages-related tool).

2) Collect the inputs you’ll need (and why)

Damages allocation typically requires you to break damages into components and allocate them across the parties/issues you’re modeling. In DocketMath, you’ll generally provide:

• Damage categories (the amounts you want to allocate)
• Allocation targets (who receives the allocation and/or which items are allocated)
• Effective dates (when relevant to timing windows used by the tool)
• Any caps, offsets, or weights the tool supports in its Texas rule set

Use this checklist to confirm you have what you need before you start entering values:

3) Ensure the Texas rule set is applied

When US-TX is selected, DocketMath applies Texas-specific jurisdiction logic.

For timing-related limitations, DocketMath uses the general/default limitations period because no claim-type-specific sub-rule was found in the provided jurisdiction data.

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

Important clarity for interpretation:

• DocketMath will treat this as the general/default period.
• The calculator will not apply a different limitations period based on a specific claim category unless the tool has claim-type-specific rules configured for Texas and those are actually available in the dataset you’re using.

4) Enter values category-by-category

Enter values in the way the interface prompts. A common workflow is:

• Add a damage category row (e.g., “Contract damages,” “Property loss,” “Other”)
• Enter the amount
• Assign the category to one or more allocation targets (depending on the tool’s options)
• Set any weights or allocation percentages if the UI provides them

As you enter amounts, watch for:

• Automatic totals (if shown)
• Warnings about negative values or inconsistent totals
• Any recalculation of remaining balance as you allocate

5) Confirm the time-window inputs (if prompted)

If the Damages Allocation UI asks for dates or a calculation window, enter them carefully:

• Use the same date convention across the tool (e.g., consistent formatting)
• Ensure dates correspond to the events you’re modeling
• If you’re unsure which date DocketMath expects (filing date vs. accrual date), use the UI’s field label text—the tool’s behavior depends on which field you populate

Because the Texas general/default period in this configuration is 0.0833333333 years, it helps to sanity-check that value:

• 0.0833333333 years ≈ 1 month (since 1/12 of a year)

This “about one month” relationship can help you confirm whether output timing effects look plausible, without needing to guess the internal math.

6) Run the calculation and review the outputs

After filling inputs, run the calculator. DocketMath typically returns:

• Allocated amounts by category and/or by target
• Totals to confirm sums match input totals
• Timing-related outputs if the tool incorporates the limitations window into the allocation logic

Use this quick output validation checklist:

7) Iterate with controlled changes

To understand how inputs change outputs:

• Change one input at a time (e.g., a single category amount)
• Re-run
• Compare deltas in the allocated totals

This helps you confirm whether the allocation behaves as proportional, weighted, capped, or subtractive in your setup.

A practical approach:

1. Record the output total allocation.
2. Adjust a single category amount by 10%.
3. Re-run.
4. If the total changes by roughly 10%, the allocation is likely proportional for that category in the current configuration.

Common pitfalls

These issues come up frequently when running Damages Allocation for Texas (US-TX) in DocketMath:

1. Mixing claim-type-specific expectations with a general/default SOL

   • The jurisdiction data here supports only the general/default period.
   • DocketMath won’t automatically swap in a different limitations period by claim type unless claim-type-specific rules are configured and available.

2. Assuming 0.0833333333 years means “one day” or “one week”

   • 0.0833333333 years corresponds to about 1 month (≈ 1/12 of a year).
   • If your timeline is much longer (or shorter), results may reflect a strict time-window assumption.

3. Leaving date fields blank when the UI expects them

   • Even if the calculator still produces an output, blank dates can trigger fallback logic you may not notice.
   • Prefer using explicit dates that match the labels on screen.

4. Allocating categories without ensuring totals reconcile

   • Watch for rounding behavior if the tool displays decimals.
   • Ensure the sum of allocated shares equals the category totals (or confirm any rounding rules the tool uses).

5. Treating “Texas rule set applied” as proof the right law section fits your scenario

   • DocketMath uses the jurisdiction data available to it.
   • Here, the referenced statute basis is Texas Code of Criminal Procedure, Chapter 12 (per the provided jurisdiction data).
   • Make sure that aligns with your modeling assumptions—especially if your underlying matter is not criminal.

Try it

Follow this quick “no-surprises” exercise to validate the workflow:

1. Open /tools/damages-allocation
2. Set jurisdiction to US-TX
3. Enter two damage categories with simple amounts (e.g., 100 and 50)
4. Allocate both categories to a single target (or split them evenly if the UI supports it)
5. If the tool requests dates:

   • Use dates within a short window that roughly matches the ~1-month general/default period (0.0833333333 years)
6. Run the calculation
7. Check:

   • Allocated totals match expected sums
   • The output breakdown includes timing-related adjustments (if shown)
   • No warnings indicate missing or inconsistent inputs

Then do one controlled iteration:

• Increase one category by 10%
• Re-run
• Confirm the allocated output for that category shifts in the same direction

If the results move predictably, you’re ready to run your real numbers.

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