How to run Damages Allocation in DocketMath for Texas

Step-by-step

This guide walks you through running Damages Allocation in DocketMath for Texas (US-TX). You’ll enter case facts, run the calculator, and interpret the results using Texas proportionate responsibility rules under Tex. Civ. Prac. & Rem. Code ch. 33.

1) Open the correct tool

Start at the primary call-to-action:

• /tools/damages-allocation

In the tool interface, confirm the jurisdiction is set to Texas (US-TX). If DocketMath supports jurisdiction switching in your workspace, set it to US-TX before entering any values.

2) Identify the allocation universe (who is getting a share)

Damages allocation in Texas is tied to the actors the governing framework treats as “responsible.” In DocketMath terms, that means you should define the set of parties/entities the calculator will allocate among, typically:

• Plaintiff (if your workflow includes plaintiff responsibility inputs)
• Each defendant
• Any other responsible person/entities your case data supports

Tip: Use the same actor set consistently across runs. If your actor universe changes between scenarios, it becomes harder to compare results meaningfully.

3) Enter comparative responsibility factors as the calculator expects

Next, enter the relative responsibility information for each actor.

In general, the DocketMath Damages Allocation flow will ask for inputs like:

• Responsibility percentages (or values the tool converts into percentages)
• Total damages (or the damages number the tool needs in the configured format)
• Any other required fields the tool uses to compute per-actor shares

Practical approach:

• Use the best available allocation figures from the record (for example, jury findings, agreed responsibility allocations, or expert breakdowns).
• Keep the input basis consistent across all actors—avoid mixing different scales or concepts in a way the tool can’t distinguish.

4) Ensure the total responsibility inputs line up

Even if the tool accepts entry in multiple formats, the most reliable outcomes come from inputs that are internally consistent.

Before you hit Calculate, use this quick checklist:

• Each actor included in the allocation is intentional (no accidental duplicates)
• All actors’ responsibility entries use the same basis and are comparable
• You’re not double-counting any actor or combining overlapping categories
• You’re not mixing different meanings of “responsibility” across actors (unless the tool explicitly separates them)

5) Run the calculator

Click Calculate (or the tool’s equivalent).

DocketMath will compute outcomes such as:

• Each actor’s allocated share of damages
• The net allocation result based on your responsibility inputs and Texas allocation logic

6) Interpret the output in a Texas framing (ch. 33)

Texas proportionate responsibility principles under Tex. Civ. Prac. & Rem. Code ch. 33 determine how responsibility percentages reduce or allocate recoverable damages among parties. In practice, use the DocketMath output to answer:

• What percentage of the total damages is attributed to each actor?
• How does including plaintiff responsibility change the net recovery (if your inputs include it)?
• Do any actors have 0% responsibility, resulting in 0 allocated share?

For the statutory foundation referenced in this workflow, see:

• Tex. Civ. Prac. & Rem. Code ch. 33 (Proportionate Responsibility): https://statutes.capitol.texas.gov/Docs/CP/htm/CP.33.htm

7) If you need a scenario comparison, rerun with changed inputs

Damages allocation results are highly input-driven. If you’re preparing settlement ranges, sensitivity checks, or internal explanations:

• Run Scenario A with your current responsibility distribution
• Run Scenario B by adjusting one variable at a time (for example, moving Defendant A from 20% → 25%)
• Compare how the allocated dollar amounts shift per actor

This method makes it easier to explain why results changed, not just that they changed.

Common pitfalls

These issues commonly derail damages allocation runs in Texas models, especially when facts and percentages don’t match the tool’s expected structure.

1) Encoding claim-type-specific rules that aren’t confirmed in the tool

You might expect different periods or sub-rules depending on claim type. For this Texas workflow, no claim-type-specific sub-rule was found for the calculator’s general/default period.

• Result: If you try to apply a specialized deviation without confirmation the tool supports it, outputs may not reflect your intended model.
• Fix: Stick to the general/default allocation logic and clearly document any assumptions you’re making in your case notes.

2) Mixing responsibility concepts

A frequent mix-up is entering values that represent different concepts, such as:

• “Fault for negligence”
• “Fault for causation”
• Another “percentage” that reflects a different underlying basis

If DocketMath expects one responsibility metric per actor, mixing concepts can produce misleading results.

Checklist:

• Each actor’s responsibility value represents the same underlying concept
• You didn’t rescale or reinterpret one actor’s values using a different framework

3) Actor list mismatch across runs

If your actor list differs between calculations, the totals won’t be comparable.

Examples:

• Run 1 includes 3 defendants; Run 2 includes 4
• One run includes plaintiff responsibility; another omits it

Fix: Keep the actor universe stable when comparing scenarios; if you must change it, label the runs clearly.

4) Misunderstanding what “total damages” includes

If your case damages figure should include or exclude certain components (or if the tool expects a particular damages basis), you need to enter the correct number in the format DocketMath requires.

Otherwise, the allocation may be arithmetically consistent but the wrong total for your intended interpretation.

5) Skipping sanity checks

Even with automatic calculations, do quick checks:

• Do the allocated shares sum to the expected total (within rounding)?
• Do actors with 0% responsibility receive 0 allocated damages?
• When you adjust one input, do the outputs move in a direction that makes sense?

Try it

If you’re ready to run a Texas damages allocation scenario now:

1. Open /tools/damages-allocation
2. Confirm Texas (US-TX) is selected
3. Enter:

   • Responsibility percentages for each actor
   • Your total damages figure in the form the tool requests
4. Click Calculate
5. Review:

   • Per-actor allocated damages
   • How changes in responsibility move the results

Then run one additional sensitivity check:

• Scenario A: current responsibility assumptions
• Scenario B: adjust one actor’s responsibility by a realistic increment (example: +5%)
• Compare deltas in allocated dollar amounts

Practical note: Don’t stop at the first calculation. Under Tex. Civ. Prac. & Rem. Code ch. 33, allocations can be highly sensitive to the responsibility inputs—often the second run quickly identifies which actor dominates the payable shares.

For a useful contrast, you can also compare how other jurisdictions structure their workflow in DocketMath’s guides—see the Philippines materials in Related reading for examples of how input framing differs.

Related reading

• How to calculate Damages Allocation in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Damages Allocation in Philippines — Worked example with real statute citations
• Inputs you need for Damages Allocation in Philippines — Input checklist with sourcing guidance