How to interpret Alimony Child Support results in New Hampshire

6 min read

Published April 15, 2026 • By DocketMath Team

What each output means

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

DocketMath’s Alimony Child Support calculator for New Hampshire (US-NH) is meant to translate your inputs into estimates you can use to compare scenarios. Think of it as a math-based interpretation aid, not a court order. So use the numbers for direction and magnitude—and for identifying what drives the outcome—rather than treating them as a guaranteed result.

In New Hampshire, child support and alimony are governed by different parts of state law (commonly referenced as RSA 461-A for child support and RSA 458 for alimony). Separately, if your goal is also to understand timing risk (for example, whether something must be filed within a certain window), New Hampshire’s general civil statute of limitations is referenced in RSA 508:4.

Typical outputs you should expect

Depending on how DocketMath structures the run, your results typically include:

  • Estimated monthly child support
    A calculated monthly figure based on inputs such as the income you enter and the custody/time-sharing parameters that DocketMath uses.

  • Estimated monthly alimony
    A calculated monthly figure based on the alimony-related inputs DocketMath collects.

  • Estimated combined monthly support
    A combined roll-up so you can compare scenarios side-by-side (child support + alimony).

  • A scenario comparison view (if enabled)
    A view showing what changes when you adjust specific inputs (for example, income or time-sharing) and how the combined number responds.

If you see additional lines in the calculator (for example, intermediate totals or step outputs), treat those as building blocks that help explain how the final monthly amounts were assembled.

Timing matters (and uses a separate analysis)

If you’re interpreting the results because you’re also concerned about whether a delayed action could be brought later, note that support math and statute of limitations analysis are different.

New Hampshire’s general civil statute of limitations is 3 years under RSA 508:4:

Important: No claim-type-specific sub-rule was identified in the brief for this post. Treat RSA 508:4’s general/default 3-year period as a baseline, not a guarantee that every situation uses the same timeframe.

If you want to revisit your numbers quickly, start here: /tools/alimony-child-support.

What changes the result most

In practice, DocketMath results tend to move most when you change inputs that affect:

  1. the income base, and
  2. the allocation factors, especially the time-sharing/custody parameters that drive the child support portion.

These inputs have the biggest impact on the final number. Adjust them one at a time if you need a sensitivity check.

  • date range
  • rate changes
  • assumption changes

High-impact input areas (most common drivers)

  • Income numbers (gross and/or verified net, depending on how DocketMath structures inputs)
    Higher income generally increases support calculations. Because formulas scale off income, small changes can create noticeable monthly differences.

  • Whether inputs reflect current vs. historical periods
    If you enter past or temporary income, your estimate may not reflect the period you’re trying to model. Consider updating inputs to match the relevant timeframe.

  • Custody / time-sharing inputs (child support driver)
    Changing time-share assumptions can substantially shift the child support estimate. If DocketMath asks for percentages or related parameters, test sensitivity by changing one input slightly (e.g., 60/40 vs. 65/35) to see how the estimate reacts.

  • Any support-related adjustments DocketMath requests
    Optional toggles or adjustment fields (if your version includes them) can materially change outputs. If an optional field is available, run with it both ways so you understand its effect.

Do a simple “sensitivity test” (fast, practical, and evidence-friendly)

Instead of guessing what “should happen,” compare controlled scenarios:

  1. Choose a baseline scenario (your best estimate of the facts).
  2. Change one input at a time (for example, adjust income by a realistic amount).
  3. Record the updated monthly child support, monthly alimony, and combined result.
  4. Repeat for custody/time-sharing inputs and any adjustment toggles.

A simple tracking table can look like this:

Input changedBaseline resultNew resultMonthly changeWhat it suggests
Income (Parent A)$____$____+/− $____Income base is a major driver
Income (Parent B)$____$____+/− $____Relative income shifts matter
Custody/time-share$____$____+/− $____Child support is sensitive to time allocation

Tie timing concerns to RSA 508:4 (baseline only)

If your “interpretation” includes timing questions due to delays, use the RSA 508:4 general 3-year baseline:

  • General civil SOL period: 3 years
  • Statute: RSA 508:4

Caution: Don’t automatically assume RSA 508:4 controls every support-adjacent dispute. This post uses RSA 508:4 as a general/default baseline because no claim-type-specific sub-rule was identified here.

Next steps

To interpret your DocketMath output in a way that’s useful for real conversations (or decision-making), convert the numbers into a factual checklist you can verify.

Run the Alimony Child Support calculator now and save the inputs alongside the result so the workflow is repeatable. You can start directly in DocketMath: Open the calculator.

1) Validate your inputs against documents

Gather and compare what you entered to available records such as:

  • pay stubs or payroll summaries
  • tax returns
  • benefit statements
  • custody orders or agreements
  • any prior support agreements

Focus especially on:

  • income figures
  • custody/time-sharing assumptions
  • any toggles/optional adjustments you selected

If something is uncertain, consider two runs:

  • Conservative scenario (lower income / more favorable time-share for the party you’re trying to protect risk-wise)
  • Alternative scenario (higher income / different time-share)

2) Compare component results (not just the combined number)

If your output shows child support and alimony separately:

  • Does child support account for most of the combined amount?
  • Does alimony drive most of the variation when you change income?
  • Do custody/time-sharing changes mainly move the child support line?

This tells you where you should do the most work verifying the facts.

3) If timing is part of your decision, anchor to RSA 508:4

For timing risk, use RSA 508:4’s general 3-year baseline to frame questions like “Is this likely too late?” But keep in mind—again—that this is a baseline, not a one-size-fits-all rule for every claim type.

4) Bring “scenario notes” when you discuss results

When sharing results with someone else (a family member, mediator, or attorney), the most persuasive format is:

  • “Baseline uses X income and Y time-share.”
  • “Changing income by $___ changes combined support by about $___.”
  • “Changing time-share by ___ changes child support by about $___.”

That reduces confusion caused by focusing on a single number.

If you want to rerun and compare multiple scenarios, go back to: /tools/alimony-child-support.

Related reading