Why Alimony Child Support results differ in Texas

The top 5 reasons results differ

Run this scenario in DocketMath using the Alimony Child Support calculator.

When you run DocketMath’s alimony-child-support calculator for Texas (US-TX), it’s common to see materially different outputs even when you believe the facts are “similar.” In practice, differences usually come from how the calculator applies Texas jurisdiction-aware rules and which inputs you provided—especially because outcomes are sensitive to the structure of what you enter (income breakdowns, expense fields, and timeline assumptions).

Here are the top 5 reasons the results differ:

1. **Input coverage differs (income types and timing)

   • Texas calculations are highly sensitive to which income streams are included and how recent they are.
   • For example, one run may include base salary only, while another also includes recurring bonus/commission. Even if two users report the same “monthly pay,” the composition of that monthly amount can change how other fields are computed.

2. **Order structure assumptions (combined vs. separate obligations)

   • Users often expect one combined figure, while other workflows or selections produce separate components (e.g., alimony vs. child support).
   • If your selections effectively ask the calculator to compute different components—or bundle them differently—the output can shift significantly.

3. **Different treatment of support-related inputs (expense fields)

   • Health coverage, childcare costs, and other recurring expenses can be entered in different ways (for example: monthly total vs. monthly by category).
   • Small input differences here can “move” specific line items and then change totals.

4. County/judicial workflow differences show up through your inputs

   • Even within Texas (US-TX), courts can process evidence and interpret documentation differently.
   • That doesn’t change statutory law, but it can change what numbers are realistically supported, which in turn affects what you enter into DocketMath for the calculator run.

5. **Time-modeling differences (how long obligations are assumed to last)

   • If you enter a different start date, compare runs with different duration assumptions, or change timeline-related options, totals can diverge.
   • Jurisdiction-aware default timing model: DocketMath’s Texas jurisdiction data shows General SOL Period: 0.0833333333 years and General Statute: Texas Code of Criminal Procedure, Chapter 12.
   • No claim-type-specific sub-rule was found, so the calculator uses that general/default period as the baseline.
   • Link used by the jurisdiction default: https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm

If you want a starting point, use the tool here: /tools/alimony-child-support.

How to isolate the variable

To identify what changed the outcome, use a controlled “diff” approach in DocketMath.

• Freeze the jurisdiction and tool settings so both runs use the same rule set.
• Compare one input at a time (dates, rates, amounts) and re-run after each change.
• Review the breakdown to see which segment or assumption drives the difference.

Step-by-step isolation checklist

• Total support estimate

  • Any line items that move
  • Any timeline/duration-based figure

Variables to test (highest impact first)

1. Gross monthly income inputs
2. Net vs. gross handling choices (if the interface offers them)
3. Child-related expense entries (childcare fields)
4. Health coverage cost entries
5. Start date / duration / timeline assumptions

Quick “signal” table (what it usually means)

Gentle reminder: This is a troubleshooting workflow—not legal advice. Use it to understand calculator sensitivity before relying on any output.

Next steps

Once you isolate the driver, improve your inputs so the result is stable across re-runs.

1. Lock down the numeric inputs

   • Keep the same pay period and income method across runs (same cadence and same assumption basis).
   • Use one consistent monthly convention for expenses.

2. Document exactly what you changed

   • Example log: “Run #2 changed gross monthly income from ___ to ___.”
   • This makes it easier to explain why results differ when you compare scenarios.

3. Re-run after the correction

   • Your goal is convergence: if you fix the specific field that caused divergence, totals should stabilize.

4. Be mindful of default timing behavior

   • Because no claim-type-specific sub-rule was found, the calculator may rely on the general/default SOL period rather than a more specialized period.
   • The jurisdiction default is supported by Texas Code of Criminal Procedure, Chapter 12 (see: https://statutes.capitol.texas.gov/Docs/CR/htm/CR.12.htm).

Related reading

• Alimony & Child Support Estimator Guide for Alabama
• Alimony & Child Support Estimator Guide for Arizona
• Alimony & Child Support Estimator Guide for Colorado