Inputs you need for Damages Allocation in Texas

5 min read

Published April 15, 2026 • By DocketMath Team

Inputs you will need

To allocate damages in a Texas case using DocketMath (jurisdiction: US-TX), you’ll want a consistent set of numeric inputs. The goal is to make the calculation reproducible—especially when multiple claims, multiple damage types, or multiple parties are involved.

Because your Texas setup relies on jurisdiction-aware timing logic, DocketMath will use the Texas general/default limitations framework tied to:

Note: Your brief indicates that no claim-type-specific sub-rule was found for the period you’re using. DocketMath should therefore rely on the general/default period referenced above, rather than claim-specific limitations rules.

Use this checklist to gather inputs before you run the damages-allocation calculator:

DocketMath-ready format (recommended)

To reduce entry errors, keep formats consistent:

  • Percent fields: enter 0–100 or 0–1, but don’t mix formats within the same run.
  • Dollar fields: avoid commas and currency symbols if the calculator expects plain numbers.

Where to find each input

This section focuses on where you typically retrieve each input within your case materials and workflow—so you’re not “number hunting” during data entry.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

1) Claim/damage categories & totals

Look in:

  • Pleadings (complaint/petition; counterclaims; amended pleadings)
  • Demand letters and exhibits
  • Settlement correspondence with a clear damage breakdown
  • Trial exhibits or damages summaries

Extract:

  • Each category label your docket uses
  • The total amount claimed per category

2) Offsets, deductions, and prior payments

Common sources include:

  • Settlement/payment records
  • Insurance correspondence and explanations of benefits
  • Releases (often specify netting terms)
  • Accounting schedules prepared for mediation or discovery

Practical tip: If your “claimed total” already reflects netting (gross minus offsets), don’t subtract again. Clearly track whether the value you enter is gross or net in your notes.

3) Apportionment basis inputs

These usually come from:

  • Contract provisions (if you allocate by performance period)
  • Expert reports (if you have weights or component drivers)
  • Damage spreadsheets used during negotiation
  • Verdict form mappings (if you translate verdict items into allocation components)

Key step: Identify whether your basis is:

  • Percentage-based (you enter percentages), or
  • Factor-based (you enter weights/factors and DocketMath computes shares)

4) Allocation groups and identifiers

Use:

  • Case management sheets
  • Discovery indexing tables
  • Your internal allocation matrix (who pays / who receives; and for which period/incident)

5) Relevant dates (timing logic)

For the Texas context, your tool setup uses the general/default period tied to:

  • Texas Code of Criminal Procedure, Chapter 12

Source to use for the general default timing framework:

Warning: Don’t assume a claim-type-specific limitations rule applies. Your brief states that no claim-type-specific sub-rule was found, so general/default governs the timing logic in this configuration.

Run it

Once you have the inputs, run DocketMath’s damages-allocation tool here:

Then enter values in a careful order (this reduces entry mismatches):

  1. **Set jurisdiction to Texas (US-TX)
  2. Enter damage categories and totals
  3. Apply offsets/deductions (only where your netting approach requires them)
  4. Add allocation basis inputs
    • If using percentages: confirm each allocation group totals correctly (typically 100%)
    • If using weights/factors: confirm the components reflect your methodology
  5. Enter relevant dates for the timing horizon that DocketMath uses under the general/default framework from Texas Code of Criminal Procedure, Chapter 12

How outputs change when you change inputs

Use this quick input → effect check to sanity-test results:

Input you adjustTypical effect on DocketMath output
Increase total claimed damages in a categoryRaises that category’s allocated share (before offsets, depending on your setup)
Change or add offsets/deductionsUsually lowers allocated amounts (often proportionally, depending on your basis)
Modify allocation percentagesRebalances who receives what within the allocation group
Change allocation groupsSplits/redirects totals across different parties/periods (outputs will show separate group calculations)
Adjust relevant dates/horizon inputsCan change which timing-dependent component is used under the Texas general/default logic

Pitfall to avoid: If allocation percentages don’t sum correctly inside each group, the output can look plausible while being inconsistent with your documented apportionment method.

Export and audit

When the run completes, validate the output with quick internal checks:

  • Reconciling totals: Do category totals match what you entered (gross vs. net)?
  • Reconciling groups: Do group totals reconcile across allocation shares?
  • Reconciling timing assumptions: Are the dates you entered consistent with the general/default Texas reference?

If anything doesn’t reconcile, update the inputs and rerun.

Related reading