How to run Settlement Allocator in DocketMath for Texas

Step-by-step

Run this scenario in DocketMath using the Settlement Allocator calculator.

Use DocketMath’s Settlement Allocator to model how a proposed settlement might be broken into categories for Texas matters. This walkthrough assumes you want the tool to apply jurisdiction-aware rules for US-TX.

1) Open the correct calculator

1. Go to DocketMath’s Settlement Allocator:

   • /tools/settlement-allocator
2. Confirm the jurisdiction is set to US-TX (Texas).
3. Choose the scenario inputs you plan to allocate—commonly the settlement amount, any known components, and the relevant dates that affect the tool’s timing logic.

Tip: If you’re not sure which date fields map to your workflow, start with your best estimate for the key trigger date you’re using (and keep notes so you can rerun later with alternatives).

2) Enter the settlement amount and components

In DocketMath, your allocator inputs determine how much money is available to distribute across output buckets.

Use this checklist:

• Total settlement amount: the gross figure you want allocated.
• Known amounts by category (if available): enter specific numbers you already have.
• Unknowns: if you leave certain categories blank, DocketMath will allocate the remaining value based on the jurisdiction-aware rules and your other inputs.

How outputs change based on your inputs

• When you increase the total settlement amount, the allocated totals generally scale up/down proportionally—unless you’ve entered category amounts that the tool treats as “known” or otherwise locked.
• When you enter more known category amounts, less remains for DocketMath to allocate across the remaining buckets.

Avoid input-format confusion If you have multiple payments (for example, lump sum plus structured components), enter the structure in the way DocketMath expects (typically by using the calculator’s fields to represent totals/timelines rather than combining different instrument types into a single number).

3) Set the Texas jurisdiction rule settings

Texas is driven here by Texas Code of Criminal Procedure, Chapter 12 as the general statutory context for timing (including general rules tied to limitations concepts). DocketMath’s jurisdiction-aware setup uses that general chapter reference for the default period when no claim-type-specific sub-rule is detected.

For Texas, DocketMath applies the following default timing rule:

• General SOL period: 0.0833333333 years
  (This equals 1 month, since 1 month / 12 months = 1/12 year = 0.0833333333.)

Key clarity for Texas (default behavior):

DocketMath also references the broader Texas framework in this jurisdiction configuration, using:

• Texas Code of Criminal Procedure, Chapter 12
  Source: https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm

4) Provide dates that affect allocation logic

Settlement allocators often adjust how amounts are treated based on time-related inputs. In Texas, that means the date fields you enter can influence the timing-based portions of the allocation.

Common date fields you may see in the calculator:

• Event date (e.g., date of incident or filing-related trigger your workflow uses)
• Assessment/start date (if your process distinguishes it)
• Settlement date (when the allocation is being valued)
• Other relevant timeline dates (if present in the UI)

Practical guidance

• Keep your timeline internally consistent. For example, if your event date should precede your settlement/valuation date, try not to enter an event date after the settlement date.
• Use the date format the UI expects (month/day/year vs. day/month/year). If you’re unsure, re-check the field placeholder text.

Why this matters Even if the total settlement amount stays the same, changing dates can shift the relative distribution across buckets because the tool applies timing logic (and may change results when a date span crosses a timing boundary).

5) Run the allocator and review outputs

After entering your values:

1. Click Calculate (or the equivalent action button).
2. Review the output table and any breakdown sections.

What to check in the results

• Which jurisdiction logic is active (it should reflect US-TX).
• Whether the output indicates it is using the default period (not a claim-type-specific override).
• Any “assumption” or “rule used” indicators in the UI.

Quick reference: likely effect of common input changes

For Texas, remember the anchor rule the tool is using in this default configuration:

• General SOL period used by DocketMath: 0.0833333333 years (1 month)
• Framework reference: Texas Code of Criminal Procedure, Chapter 12
  https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm

6) Iterate quickly with scenario comparisons

To sanity-check your model:

• Run a baseline allocation using your best estimates.
• Then change one variable at a time, such as:

  • shifting the settlement date by a few weeks
  • shifting the event date by a few days
  • adjusting one uncertain category amount

Then compare results.

Practical expectation: small date shifts can cause disproportionate changes when timing rules apply in a way that changes bucket treatment around boundaries (for example, when a time span moves from “within default period” to “outside default period,” depending on the tool’s internal computation).

Common pitfalls

Settlement allocation workflows fail more often due to input mismatches than due to “wrong law.” Here are the most common issues when running DocketMath Settlement Allocator for Texas:

1. Assuming a claim-type-specific limitations period is applied

   • DocketMath is using the general/default period because no claim-type-specific sub-rule was found in the provided jurisdiction data.
   • That default period is 0.0833333333 years (1 month) tied to the general framework from Texas Code of Criminal Procedure, Chapter 12.

2. Inconsistent date fields

   • Example: settlement/valuation date earlier than event date.
   • The tool may calculate, but the time-based logic won’t match your intended timeline.

3. Forgetting to lock known category values

   • If you enter a category amount but DocketMath treats it as editable (or you don’t use the calculator mode that represents “known” amounts), the allocator may re-balance categories.
   • Use the UI options as intended and confirm in the results that the known amounts remain stable.

4. Mixing totals and line items

   • Entering both a total settlement and separately entering category components that already sum to the total can lead to double-counting if the calculator doesn’t interpret those entries the way you expect.
   • Choose one approach:

     • provide one total and let DocketMath allocate, or
     • provide category amounts that sum to the total.

5. Relying on outputs without checking assumptions

   • Confirm the UI is set to US-TX and that the timing rule corresponds to the default general period.
   • Don’t assume “default” means what you expected for a specific claim type—here, the jurisdiction data did not identify a claim-type-specific sub-rule.

Pitfall to watch: treating the default Texas timing rule as if it were claim-type-specific can produce confidently wrong allocations—especially when your scenario spans more than the 1-month default period between the relevant trigger date and the settlement/valuation date.

Try it

Open DocketMath and run a quick baseline allocation:

• Go to /tools/settlement-allocator
• Set **jurisdiction to US-TX (Texas)
• Enter:

  • Total settlement amount
  • your best available timeline dates
  • any known category amounts (if you have them)
• Click Calculate

Then validate the sensitivity:

• Run a second calculation changing only one date (for example, shift by ~14 days).
• Compare the bucket distribution to see whether the default 1-month period materially affects results.

Texas anchor to remember during your test:

• General SOL period used by DocketMath here: 0.0833333333 years (1 month)
• Legal framework reference: Texas Code of Criminal Procedure, Chapter 12
  https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm

Gentle disclaimer: DocketMath outputs are best used as modeling support for internal review of settlement allocation assumptions. They are not a substitute for legal advice regarding any jurisdiction-specific dispute about limitations, applicability, or legal classification.

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado