How to run Alimony Child Support in DocketMath for Kansas

6 min read

Published April 15, 2026 • By DocketMath Team

Step-by-step

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

This guide walks you through running an Alimony + Child Support scenario in DocketMath for Kansas (US-KS) using the Alimony Child Support calculator. You’ll see how jurisdiction-aware rules are applied, what inputs matter most, and how to interpret the outputs so you can refine assumptions quickly.

Note: This walkthrough is about using DocketMath to organize calculations. It’s not legal advice and doesn’t replace guidance from a qualified Kansas family-law professional.

1) Open the Kansas alimony/child support calculator

Start at the primary call to action:

  • /tools/alimony-child-support

When you open the tool, set the jurisdiction to Kansas (US-KS) if it isn’t already selected.

2) Confirm which categories you’re calculating

DocketMath’s Alimony Child Support calculator is designed to compute outcomes for both:

  • **Alimony (spousal support)
  • Child support

If your worksheet only needs one component (for example, child support only), you can still run the full tool and focus on the relevant output section. This can be faster than switching tools.

3) Enter parent/household details (the inputs that change the result)

The calculator will typically ask for items such as:

  • Number of children
  • Child-related ages or school/coverage flags (if included in the tool)
  • Income details for each parent
  • Estimated expenses or support-relevant adjustments (if the tool includes them)
  • Custody / parenting-time allocation (often a key driver of child support)

Use consistent timeframes across both parents (e.g., weekly vs. monthly). If the calculator asks for a “gross income” basis, avoid mixing gross and net figures.

Quick input sanity checks:

  • ✅ Same pay period basis for both parents
  • ✅ Include regular employment income if available
  • ✅ If you have variable income (commissions, bonuses), choose a reasonable monthly average and use it for both parties consistently

4) Enter alimony assumptions (the inputs that change the spousal amount)

Alimony outcomes are sensitive to inputs like:

  • Each party’s income
  • Any alimony duration/structure assumptions (if the tool asks)
  • Marriage-duration-related fields (if prompted)
  • Any qualifying adjustments captured by the calculator UI

If the tool presents multiple alimony “modes” (for example, different structure or modification assumptions), select the one that matches your scenario facts instead of toggling options just to compare numbers.

5) Review jurisdiction-aware rule application for Kansas

For Kansas, DocketMath uses Kansas jurisdiction settings tagged to US-KS.

One time-related item you may see referenced in planning workflows is Kansas’s general statute of limitations (SOL) for criminal actions:

  • K.S.A. § 21-6701 (Kansas general SOL period noted as 0.5 years in the jurisdiction data provided)

Important clarity: This content uses the jurisdiction data you provided and states the rule clearly as a general/default period. No claim-type-specific sub-rule was found in the provided jurisdiction data.

Warning: A general/default SOL period (like 0.5 years referenced from K.S.A. § 21-6701) is not the same thing as civil deadlines for family-law enforcement. In DocketMath, rely on the calculator’s own category-specific prompts for family matters rather than assuming one deadline applies to every context.

6) Run the calculation and interpret outputs

After entering the inputs, run the calculation.

You’ll typically see outputs separated into:

  • Child support totals (often monthly)
  • Alimony totals (often monthly)
  • Possible combined totals or recommended breakdowns (depending on the tool’s design)

Use the outputs like this:

  • If child support is unexpectedly high/low, revisit:
    • parenting-time allocation
    • income inputs
    • number of children and any coverage assumptions
  • If alimony swings significantly, revisit:
    • relative incomes
    • any alimony duration/assumption fields
    • marriage-duration related inputs (if asked)

7) Iterate responsibly: adjust one variable at a time

To learn what drives the result, change one assumption per run. A practical workflow:

  • Run #1: enter best-available facts
  • Run #2: adjust only income for Parent A (e.g., a sensitivity test like ±10%)
  • Run #3: adjust only parenting time (if allowed by the tool)
  • Run #4: adjust only alimony-related toggles/fields

This makes it easier to explain “what changed” later if you’re preparing a negotiation summary or sharing results with a professional.

8) Save/record your scenario notes

If the tool supports saving scenarios or exporting results, record:

  • The exact parenting-time allocation used
  • The monthly income amounts entered for each parent
  • Any toggles that affect deductions/coverage
  • The final outputs you want to compare

If exporting isn’t available, copy the key input values into your own notes so you can recreate the exact run.

Common pitfalls

Many Kansas alimony/child support computations go off track due to avoidable input issues. Here are the most common pitfalls when running the DocketMath Alimony Child Support calculator for US-KS.

  • Mixing pay periods
    • Example: one parent’s income entered as monthly while the other is entered as biweekly without converting.
  • Using inconsistent “income” definitions
    • Example: gross for one parent and net for the other.
  • Incorrect parenting-time allocation
    • If the tool requests a specific custody time split, entering a rough estimate can materially change the child support output.
  • Changing multiple variables at once
    • If you tweak income, custody, and alimony toggles in the same run, you won’t know what caused the output change.
  • Assuming the “general/default SOL period” applies to family-law deadlines
    • The jurisdiction data references K.S.A. § 21-6701 with a 0.5-year general SOL period.
    • That is a general/default period based on the provided jurisdiction data, and no claim-type-specific sub-rule was found.
    • Family matters typically involve category-specific rules and deadlines that aren’t interchangeable.
  • Over-reliance on a single output
    • Treat results as a calculation snapshot. Run sensitivity checks so you understand how robust the number is to your assumptions.

Pitfall: A single wrong number—like the wrong number of children or the wrong income basis—can make both the child support and alimony outputs look “reasonable” while being internally inconsistent with your scenario.

Try it

If you want a fast start, follow this mini-checklist before your first run in DocketMath for Kansas (US-KS):

Once you run it, compare your outputs to your expectations using these quick interpretations:

If this output looks off…Likely input driversWhat to check first
Child support too high/lowincome basis, parenting time, number of childrenincome definition + custody split
Alimony too high/lowalimony toggles, relative incomes, duration fieldsalimony assumptions + both incomes
Combined total swings a lotincome sensitivity + multiple fields changedensure only one input changed per run

Ready to run your Kansas scenario now? Use the tool here:

  • /tools/alimony-child-support

Related reading