How to run Alimony Child Support in DocketMath for Idaho

7 min read

Published April 15, 2026 • By DocketMath Team

Step-by-step

This guide shows how to run Alimony + Child Support in DocketMath for Idaho (US-ID) using the jurisdiction-aware setup. I’ll keep it practical and focus on what to enter, what to expect, and how Idaho-specific logic can affect the results. (This is not legal advice—think of it as a workflow for using the calculator.)

1) Start the correct tool

  1. Open DocketMath here: **/tools/alimony-child-support
  2. Confirm you’re in the Idaho jurisdiction context (US-ID).
  3. Choose the calculator inputs for your situation (the tool’s interface will guide you through categories).

Note: DocketMath’s “Idaho” configuration is the key step. Running the same inputs under another jurisdiction can change outputs because the calculator applies jurisdiction-specific assumptions and rule logic.

2) Enter timeline basics that affect calculations

In the alimony + child support workflow, your dates often influence whether the tool treats payments as current vs. future, and which time periods are being summarized.

Use the date fields (if shown) to represent:

  • Start date of the obligation (or the earliest effective date you want the calculation to cover)
  • End date (if the tool supports term-based scenarios)
  • Any interim period you want included in the output

If you don’t know exact dates, enter the closest known dates and rerun the calculation after you refine them. That helps you see how sensitive the results are to timing.

3) Provide child support inputs

For child-related calculations, enter the data DocketMath requests for the children and income context, such as:

  • Number of children covered
  • Any fields for parent income amounts (and whether amounts are pre-/post-tax, gross/net, or otherwise—use the option labels exactly as written)
  • If the tool provides toggles for shared parenting/placement factors, select the option that matches your scenario

What to watch:

  • Changing custody/placement settings can swing the output meaningfully, even if income inputs stay the same.
  • If you enter annual income but the tool expects monthly (or vice versa), the result will be off—double-check the unit labels near each field.

4) Provide alimony inputs

Next, fill in the alimony fields the tool requests. Common categories include:

  • The requesting vs. paying spouse (the tool may require selecting “who pays”)
  • Each spouse’s income (match the unit labels)
  • Any selection for alimony type (if the interface offers options)
  • Any fields for duration/term or amount basis

Because alimony structures can be sensitive to the tool’s scenario choices, keep your entries consistent:

  • If you model “short term” vs. “long term,” use the tool’s built-in selectors rather than trying to override by forcing numbers into the wrong fields.
  • When in doubt, use the scenario option that best matches how you want the output framed (monthly estimate vs. term total).

5) Confirm Idaho jurisdiction behavior (and SOL baseline)

DocketMath applies Idaho jurisdiction-aware logic when you select US-ID. For this workflow, you’ll still want to understand one Idaho timing rule that sometimes comes up alongside payment estimates: the general statute of limitations (SOL).

Idaho’s general SOL period is 2 years under:

  • Idaho Code § 19-403 (general statute of limitations)

In other words, the default SOL in Idaho is 2 years under Idaho Code § 19-403.

Warning: This 2-year period is the general/default period. The prompt indicates that no claim-type-specific sub-rule was found, so treat this as a baseline timing rule rather than a guarantee for any particular claim category.

6) Run the calculation and interpret the output

Once all required fields are entered:

  1. Click Calculate (or the tool’s equivalent action).
  2. Review outputs grouped by category—typically:
    • Child support (monthly and/or total depending on the tool)
    • Alimony (monthly and/or total depending on the tool)
    • Combined totals (if provided)

Use the output structure to sanity-check:

  • Do the monthly figures align with your expectations given the income levels you entered?
  • Does the combined number change when you toggle child-related inputs (like shared parenting/placement)?
  • Does the alimony amount track the alimony duration/term selections?

7) Do quick “what-if” sensitivity checks

To get practical value from the calculator, run small variations.

Checklist (fast reruns):

A good target is 2–4 reruns. This shows whether the tool’s outputs are stable or overly sensitive to one or two inputs.

8) Save or export (if your workflow supports it)

If DocketMath provides a way to save results or generate a report view:

  • Export or copy the summary
  • Keep a list of input changes you made between runs
  • Use versioning in your notes (e.g., “Run 1: baseline; Run 2: adjusted income; Run 3: updated placement”)

This makes it easier to compare results after you refine facts.

Common pitfalls

The most common issues with alimony + child support calculations in tools like DocketMath typically come from mismatched units, incorrect scenario selections, or misunderstanding default legal timing rules. Here are the pitfalls most likely to affect an Idaho workflow.

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

Unit and timing mismatches

  • Annual vs. monthly income entered incorrectly
    If DocketMath expects monthly figures and you paste annual totals, the result can be off dramatically (often by a factor of 12).
  • Start/end date assumptions
    If you unintentionally include or exclude a period, the tool’s monthly vs. total figures may not match your intent.

Scenario selection errors

  • Selecting the wrong custody/placement option (if the tool includes shared parenting factors)
    One wrong dropdown can materially change the child support output.
  • Picking an alimony scenario that doesn’t match the payment structure
    Some tools infer the structure based on your selections—avoid “fixing” the result by entering numbers into fields that don’t match the tool’s intended flow.

Misapplying Idaho SOL timing

Even if you’re calculating payment amounts, Idaho timing rules sometimes get referenced when you plan how far back matters can be pursued.

The guidance provided here is the general/default SOL baseline:

  • 2 years under Idaho Code § 19-403

Pitfall: Confusing the general SOL (2 years) with a claim-specific SOL can lead to incorrect assumptions. This section intentionally treats Idaho Code § 19-403 as a general/default rule because no claim-type-specific sub-rule was found in the materials provided.

Not running sensitivity checks

Skipping reruns can hide input problems:

  • You might not notice a unit error because the output still “looks plausible.”
  • Rerunning with only one changed input is a quick way to validate.

Try it

Ready to run your Idaho estimate in DocketMath?

  1. Open the calculator: **/tools/alimony-child-support
  2. Ensure jurisdiction is set to Idaho (US-ID).
  3. Enter inputs in this order:
    • Timeline (start/end)
    • Child inputs (children count, parent income, placement/custody settings if available)
    • Alimony inputs (paying spouse selection, income, alimony scenario/term options)
  4. Run the calculation and review category totals.
  5. Perform 2–4 quick reruns.

Use this minimal rerun checklist:

If you’re also documenting timing considerations, keep Idaho’s general SOL baseline in mind:

  • Idaho Code § 19-403 — 2-year general/default SOL
    This is a baseline reference from the materials provided, not a substitute for claim-specific legal analysis.

Related reading