How to run Alimony Child Support in DocketMath for Texas

7 min read

Published April 15, 2026 • By DocketMath Team

Step-by-step

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

This walkthrough shows how to run an Alimony + Child Support calculation in DocketMath for Texas (US‑TX) using the alimony-child-support calculator. The goal is to help you set up jurisdiction-aware inputs correctly so the tool produces a consistent, auditable calculation worksheet you can use in your workflow.

Note: DocketMath provides calculation support—not legal advice. Use the output as a starting point for reviewing your numbers against the controlling court order and Texas law.

1) Open the correct tool and set the jurisdiction

  1. Open the calculator here: /tools/alimony-child-support
  2. Confirm the jurisdiction is set to Texas (US‑TX).
  3. Verify the calculator mode matches your intent (the tool is designed to address “alimony + child support” workflows under a single calculation page).

If your interface separates “jurisdiction” from “calculator,” set US‑TX explicitly before you enter amounts.

2) Enter the parties’ and order context (the “who/when” inputs)

In Texas-related calculations, date and order context can affect how payments are treated over time. Enter:

  • Start date for payments (e.g., the date support is ordered to begin)
  • End date (if known)
  • Payment frequency (monthly is common)

Then add identifiers that help the output stay readable:

  • Parent A / Parent B (or obligor / obligee labels used in your workflow)
  • Names may be optional, but labeling reduces transcription mistakes later.

3) Add child support inputs

Child support typically depends on details such as:

  • Number of children covered by the order
  • Any child-specific coverage categories your scenario uses (for example, if ages or coverage periods are modeled separately)

In DocketMath, fill fields exactly as shown on the calculator screen. Pay close attention to units, such as:

  • Annual vs. monthly income
  • Gross vs. net income (use the tool’s expected definitions)

A practical tip: if you have income information in one format (like yearly wages), confirm whether the calculator expects yearly or monthly before entering it.

4) Add alimony/spousal support inputs

For the spousal portion:

  • Enter the agreed/ordered spousal payment amount, or the parameters the calculator requests (depending on the calculator’s input design)
  • If the tool supports duration handling, input the intended duration (or use the relevant duration field if it appears)

Because spousal outcomes are highly fact-specific, keep your inputs aligned with your actual order (or your draft order template) rather than attempting to “re-litigate” disputed facts inside a calculator.

5) Check how DocketMath applies the timeline

After you fill inputs, review the tool’s timeline/output section. You should see results broken down into:

  • Payment periods (often by month)
  • Totals for child support and totals for alimony/spousal support
  • Possibly a combined total (if the calculator provides one)

Use the output to confirm expectations:

  • Does the calculator stop at your end date?
  • Are payment amounts constant, or do they change across periods?
  • Does the tool prorate partial periods (for example, if the start date is mid-month)?

6) Review outputs and export or save your worksheet

Before you move on:

  • Confirm the units (monthly totals, yearly totals, total-by-period, and overall total)
  • Compare the combined total against your rough “sanity check” expectation
  • Save/export your worksheet so your record includes both inputs and computed totals

This is where DocketMath is particularly useful: you can reuse the same worksheet and re-run it after changing one input (like the start date or payment frequency).

Jurisdiction-aware timeline note: Texas limitations and periods

Texas datasets used in tools may include baseline timing assumptions. In this case, your jurisdiction data provides a general/default period of 0.0833333333 years.

  • 0.0833333333 years ≈ 1 month (because 0.0833333333 × 12 = ~1)

Texas also has statutory material relevant to procedural timelines. One cited reference for Texas procedural rules is:

Warning: The 0.0833333333-year value is a general/default period from your dataset, not a claim-type-specific rule. Your scenario’s real-world time rules may depend on the specific procedural posture and the exact kind of obligation being enforced.

Common pitfalls

Below are the issues that most often cause wrong numbers or confusing worksheets when running Alimony + Child Support in DocketMath for Texas (US‑TX).

  • missing a required input
  • using a stale rate or rule
  • ignoring calendar or holiday adjustments
  • skipping documentation of assumptions

Pitfalls to avoid

  • Mixing income units
    • Example: entering annual income in a field that expects monthly income (or vice versa).
  • Using the wrong payment frequency
    • Example: selecting “weekly” while your figures are based on “monthly” (or entering amounts that were calculated for a different schedule).
  • Incorrect timeline boundaries
    • An off-by-a-few-days start date can change proration and period totals.
  • Stopping too early or running too long
    • Setting an end date incorrectly—or leaving it blank when the order has an end date—can cause totals not to match the order.
  • Failing to align outputs with the order
    • If you already have a court order, enter what the order says (amounts and durations). Avoid using the calculator to “rebuild” disputed facts not captured in your inputs.
  • Assuming “Texas default” applies to every issue
    • The 0.0833333333-year default (~1 month) is a general/default dataset value and is not a guarantee it matches your specific enforcement/procedural timeline.

Quick input checklist (use before you trust the totals)

Pitfall: Relying on the combined total without checking the child support subtotal and the alimony/spousal subtotal. When something is mis-entered, the split often reveals which section drove the discrepancy.

Try it

Use DocketMath to run a test calculation and validate your worksheet logic. The fastest way to build confidence is to run a baseline case, then modify one variable at a time.

Open the Alimony Child Support calculator and follow the steps above: Run the calculator.

Suggested “sanity test” workflow

  1. Run a baseline scenario:
    • Set jurisdiction: US‑TX
    • Choose a simple timeline (for example, 12 monthly payments)
    • Enter a small, clean spousal payment amount and a simple child support setup
  2. Change one variable:
    • Update the start date by ~1 month
    • Re-run and confirm totals change roughly in proportion to the number of months affected
  3. Change payment frequency:
    • Switch from monthly to weekly (or the tool’s available alternatives)
    • Confirm the tool rescales timing/amounts as expected
  4. Change the number of children:
    • Increase from 1 to 2 children
    • Confirm child support totals move while the spousal subtotal stays stable unless the calculator explicitly couples them

What “good output” should look like

  • Totals align with the number of payment periods
  • No unexpected negative values
  • Split subtotals (child support vs. alimony/spousal support) change only when related inputs change
  • Timeline behavior (proration, stop-date handling) matches your dates

Texas timeline reminder for worksheet interpretation

If your workflow uses dataset timing assumptions:

  • 0.0833333333 years ≈ ~1 month
  • This is a general/default period and not claim-type-specific

So the worksheet is best used for payment math and scenario planning, while procedural timing tied to enforcement should be checked against the correct Texas authority for the specific issue.

Related reading