Why Alimony Child Support results differ in New Hampshire

The top 5 reasons results differ

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

If you compare two “alimony + child support” numbers for New Hampshire using DocketMath (US-NH), you’ll often see different results even when the inputs look similar. In New Hampshire, those differences usually trace back to how DocketMath applies jurisdiction-aware rules—especially timing, income modeling, and what counts as enforceable exposure.

Before anything else (jurisdiction-aware timing context): New Hampshire’s general/default statute of limitations for civil actions is 3 years under RSA 508:4. The jurisdiction data here reflects the general SOL period; no claim-type-specific sub-rule was identified in the materials provided. That matters because how much of any retroactive amount is treated as reachable within the window can change the totals you see.

Here are the top 5 reasons your results differ:

1. Different “as-of” dates change arrears exposure

   • If one run effectively measures support up to an earlier date than another, totals can differ.
   • SOL concepts can affect what portion is treated as enforceable as a civil claim when timing falls outside the window described by RSA 508:4 (3 years general/default).

2. **Income inputs are interpreted differently (gross vs. net assumptions)

   • DocketMath models income based on the fields you provide.
   • If one scenario uses different employment income fields or different deduction assumptions (or leaves them blank vs. filled), outcomes can shift even when the “headline” numbers seem close.

3. Child support and alimony interact through the combined input bundle

   • Even if you’re focused on “alimony,” the calculator can still be influenced by child-support-related inputs because the run is a combined model.
   • Small changes—like number of children, parenting time assumptions, or income changes—can ripple into the combined output.

4. Timing of changes in income or custody

   • Updates to custody/parenting time and job/earnings start/end dates can swing the support picture.
   • Two scenarios with the “same annual income” can still diverge if the income occurs over different months (or if the date window differs).

5. Rounding and method differences between scenarios

   • Some differences come from how the same underlying numbers are distributed monthly and rounded.
   • Common pitfall: entering annual income in one run and monthly income in another without matching the same calendar/date assumptions.

Pitfall to avoid: Comparing two runs without matching the effective “through date” (or similar timing window) can make results look inconsistent when the difference is mostly timing-driven rather than input-driven.

How to isolate the variable

To figure out what caused the swing, use a controlled testing approach in DocketMath. The goal is to change one thing per run and observe what moves.

Quick isolation checklist

**Single-variable sequence (practical order)

1. Baseline run

   • Record: key monthly outputs (child support and alimony, if shown) and any timing/arrears-related figures the tool provides.

2. Change only the date window

   • Keep income and custody identical, but move the through date / window.
   • Expect the totals to change based on the measurement window and timing logic tied to the 3-year general/default SOL under RSA 508:4 (with the important caveat that this is the general period, and no claim-type-specific sub-rule was identified in the provided materials).

3. Change only income

   • Modify one parent’s income by a fixed increment (example: +$500/month) while keeping dates and custody variables constant.
   • Watch how both support components shift—because the combined model can re-balance.

4. Change only parenting/custody inputs

   • Adjust parenting time or child-related fields while keeping incomes and dates constant.
   • This often moves child support first; alimony can follow because overall assumptions can interact.

Interpretation rule of thumb

• If the difference disappears after you standardize the date window, timing is the driver.
• If it persists with dates standardized, focus on income-field interpretation and then on custody/parenting variables.

For direct access to the workflow you’ll be testing, start here: /tools/alimony-child-support.

Next steps

1. Run 3–5 scenarios

   • Baseline
   • Date-only change
   • Income-only change (Parent A)
   • Income-only change (Parent B)
   • Custody/children-only change

2. Create a simple comparison table

   • Track what you changed and what shifted in outputs.

1. Anchor expectations to timing rules

   • For timing-based questions about enforceability of civil claims, use the general/default 3-year SOL under RSA 508:4 as the jurisdiction-aware anchor.
   • Again, the provided jurisdiction data reflects the general SOL period; no claim-type-specific sub-rule was identified here.

2. Use DocketMath as a “what changed” diagnostic

   • The practical goal isn’t to treat any single run as a definitive legal conclusion.
   • Instead, treat it as a repeatable way to determine which inputs and date windows create the difference.

Gentle note: Calculator outputs are tools for understanding drivers. They’re not legal advice, and real cases can involve additional facts and court-specific considerations.

Related reading

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