Worked example: Alimony Child Support in Texas

Example inputs

This worked example shows how DocketMath’s alimony-child-support calculator can be applied in Texas (US-TX) using jurisdiction-aware rules. I’ll use concrete numbers so you can see how the math flows end-to-end, and I’ll also flag where your real-world inputs would change the output.

You can try the same workflow here: Alimony & Child Support tool.

Household and income facts (example)

Assume the following facts for the example run:

Texas rule-timing input for this calculator run

Some Texas calculations include a time-window component tied to limitations/schedule concepts. The jurisdiction data provided for this worked example includes:

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

Important: The dataset note says:

• “No claim-type-specific sub-rule was found. The above is the general/default period. State this clearly in the content.”

So, for this worked example, treat 0.0833333333 years as the general/default period (not a claim-type-specific rule). In other words, we’re using the dataset’s default timing window rather than a narrower, claim-type-driven one.

Convert the provided general period into a usable number

0.0833333333 years × 12 months/year ≈ 1 month

So the timing component effectively behaves like a ~1-month default period for this run.

Example run

Here’s how the numbers would be fed into DocketMath’s alimony-child-support tool for Texas (US-TX). Field names can vary slightly in the UI, but these map to common input categories: incomes, number of children, time allocation, and monthly pass-through expenses.

Inputs used in this example

• Payor gross monthly income: $6,500
• Payee gross monthly income: $3,200
• Children: 2
• Time allocation: 40% for payor
• Health insurance: $160/month
• Childcare: $300/month
• Alimony: included (spousal support component enabled)
• Texas default timing period (from jurisdiction data): 0.0833333333 years (~1 month), using the provided general/default period

What DocketMath outputs (illustrative)

DocketMath will compute two categories in this configuration:

1. Child support amount (child-related obligation)
2. Alimony/spousal support amount (if enabled by the tool and supported by the selected inputs)

A common way to present the results (shown here as illustrative formatting) is:

How to interpret the “~1 month” timing component

Because the jurisdiction data provides only a general/default period—and explicitly notes no claim-type-specific sub-rule was found—this worked example applies that default value as the timing parameter.

Practical implications:

• If the tool exposes the timing parameter (or a “timing window” setting), changing it should change any output that depends on that window.
• If you cannot edit that timing parameter, the calculator should consistently apply the same default (~1 month) timing component for your run.

Quick intuition: how outputs respond to the inputs

Even without seeing every internal step, you can sanity-check the direction of change:

• Higher payor income → generally increases child support and can affect alimony.
• More children → generally increases child support.
• Time share (custody allocation): different calculators treat time-sharing differently, but changing your custody percentage often changes the net obligation.
• Pass-through expenses (like health insurance and childcare) → often increase totals because they add to the child-related cost base.

Sensitivity check

A sensitivity check helps you see which inputs most affect the outcome. Below are controlled tests based on the same baseline scenario above. The direction of changes is the key takeaway (exact dollar amounts depend on the tool’s model).

Test A: Increase payor income by $500/month

• Payor gross monthly income: $6,500 → $7,000
• Everything else stays the same.

Expected direction:

• Child support: up
• Alimony/spousal support: up or may increase, depending on how the tool evaluates relative income differences

Test B: Reduce payor time share from 40% to 30%

• Time allocation: 40% → 30%
• Everything else stays the same.

Expected direction:

• Child support: up (less time often increases the net obligation in many frameworks)
• Total combined monthly obligation: up

Test C: Increase childcare from $300/month to $600/month

• Childcare: $300 → $600
• Everything else stays the same.

Expected direction:

• Child support: up
• Total combined monthly obligation: up
• Alimony/spousal support: may or may not change substantially (it depends on whether the tool links childcare to the spousal-support basis)

Timing component sensitivity (default vs. changed period)

For this Texas run, the timing component comes from the jurisdiction data:

• Default timing component: 0.0833333333 years ≈ ~1 month
• Baseline rule used: general/default period
• Dataset note: no claim-type-specific sub-rule was found, so we do not apply a narrower claim-type window

If the tool allows changing the timing window, a simple directional expectation is:

• Longer timing window (if it affects schedule/retro duration) can increase duration-based totals.
• Shorter timing window can reduce those duration-based totals.

Related reading

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