Worked example: Alimony Child Support in Idaho

Example inputs

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

This worked example shows how DocketMath can calculate an alimony + child support combined outcome using jurisdiction-aware rules for Idaho (US-ID). The goal is to demonstrate the mechanics—not to predict a specific court result for any particular family.

Gentle note: This is an educational illustration of a calculator workflow. It’s not legal advice and isn’t a substitute for reviewing Idaho law and any court-specific requirements.

Scenario (facts used for the example)

We’ll model a simplified case with stable assumptions:

• Jurisdiction: Idaho (US-ID)
• Filing/decision date used for the calculation: not modeled
  DocketMath focuses on the payment numbers in this example; we’re not computing any legal deadlines.
• Parties’ incomes (monthly, gross):

  • Parent A (paying): $6,500
  • Parent B (receiving): $4,200
• Number of children: 2
• Shared parenting time: Standard split assumed
  The calculator will use its custody/visitation inputs/rules based on how you enter them.
• Child-related inputs:

  • Daycare/childcare: $450/month
  • Health insurance premium attributable to children: $125/month
• Alimony (spousal support):

  • Monthly guideline amount (entered as an input the tool uses): $600/month
  • Duration assumptions: Not computed in this example
    This worked example focuses on the monthly combined amount. We are not applying a spousal-support termination-length model here.

State law timing note (the “SOL” piece)

Some tools/workflows include a “deadline” component (for example, whether a claim is timely). For Idaho, the provided jurisdiction data supplies the general limitations period:

• General SOL period: 2 years
• General statute: Idaho Code § 19-403
• Source (code text reference): https://law.justia.com/codes/idaho/title-36/chapter-14/section-36-1406/?utm_source=openai

Important clarification: The brief note you provided says no claim-type-specific sub-rule was found, so this worked example treats the 2-year SOL as a general/default period only. We’re stating the default period plainly and not attempting to apply a different SOL based on claim type.

Inputs checklist (what you would enter in DocketMath)

Start from the calculator via the Primary CTA: /tools/alimony-child-support

Use these inputs:

• Monthly gross income (Parent A): $6,500
• Monthly gross income (Parent B): $4,200
• Number of children: 2
• Childcare expense: $450
• Child health insurance premium (attributable to children): $125
• Monthly alimony amount (spousal support input): $600
• Custody/parenting time variables (if prompted by the tool): use the standard split assumption or your actual entered values
• Idaho jurisdiction selected (US-ID): yes

Example run

Below is a representative run consistent with the structure DocketMath uses: calculate child support first, then add alimony to produce a combined monthly total.

Because this is a worked example (not a live court calculation), treat the numbers as illustrative of how a tool workflow behaves given the inputs above.

Step 1: Calculate child support (tool-driven)

Inputs driving this component:

• Income gap: Parent A ($6,500) vs Parent B ($4,200)
• 2 children
• Add-ons:

  • childcare: $450
  • health insurance premium attributable to children: $125

DocketMath applies Idaho-aware logic (US-ID) to estimate the monthly child support baseline and then adjusts for the expense inputs you provide.

Example output for child support: $1,250/month (illustrative tool result)

Step 2: Add alimony (spousal support)

In this example, you supply the monthly alimony amount directly as an input (rather than modeling alimony duration/termination).

• Alimony input: $600/month

Example output for alimony: $600/month

Step 3: Combine monthly amounts

Combined monthly support (alimony + child support):

What DocketMath is doing under the hood (practical explanation)

In plain terms, this workflow:

1. Uses Idaho (US-ID) rules to turn income + children + shared-time inputs (as entered) and child-related add-ons into a monthly child support figure.
2. Treats your spousal support number as an additional monthly component.
3. Produces a combined monthly total so you can change inputs and immediately see what moves arithmetically.

Sensitivity check

People usually run “what if” scenarios rather than changing every fact at once. Below are three targeted sensitivity checks that keep the base case the same except for one variable.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

1) Increase Parent A income by +$500/month

• New Parent A income: $7,000 (was $6,500)
• Child count, childcare, insurance, custody split, and alimony input unchanged

Expected effect: child support rises as the paying parent’s income increases, which increases the combined total as well.

Illustrative result:

• Child support: $1,380/month
• Alimony: $600/month
• Combined: $1,980/month

2) Remove childcare expense ($450/month → $0)

• New childcare input: $0
• Everything else unchanged

Expected effect: child support decreases because childcare is an add-on included through the expense input.

Illustrative result:

• Child support: $1,050/month
• Alimony: $600/month
• Combined: $1,650/month

3) Increase alimony input by +$200/month

• New alimony input: $800/month (was $600/month)
• Child support-related inputs unchanged

Expected effect: child support stays the same in this workflow; the combined total increases linearly because alimony is directly additive.

Illustrative result:

• Child support: $1,250/month
• Alimony: $800/month
• Combined: $2,050/month

Idaho timing note reminder (SOL stays the same in this example)

If your process includes a deadline component, the provided jurisdiction data indicates:

• General SOL: 2 years
• Idaho Code § 19-403
• Default/general period only (no claim-type-specific alternative provided)

If you’re applying SOL logic to a real situation, you should confirm the correct SOL based on the specific type of action or claim—because the calculator/worked example here is not a claim-type classifier.

Related reading

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