How to calculate Alimony Child Support in New Hampshire

Quick takeaways

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

• New Hampshire uses a court-driven framework for ordering child support and alimony, and the amounts depend on case-specific facts like income, parenting time/custody split, and marriage duration.
• DocketMath’s “alimony-child-support” calculator (US-NH) helps you model those inputs consistently so you can see how changes affect estimated results.
• This guide is about how the calculation workflow works and what inputs matter—it’s not legal strategy and it can’t guarantee what a court will order.
• Don’t confuse payment timing with the size of the order: the tool estimates amounts, while real cases also involve separate rules around enforcement, modifications, and claim timing.
• Statute of limitations note (general rule): New Hampshire’s general civil statute of limitations is 3 years under RSA 508:4. Based on the jurisdiction data provided, this is a default/general period, and no claim-type-specific sub-rule was identified.

Inputs you need

Before you run DocketMath → /tools/alimony-child-support, collect the inputs below. If you don’t have every exact number, reasonable estimates are fine for scenario planning—as long as you keep them consistent across scenarios.

Use this intake checklist as your baseline for Alimony Child Support work in New Hampshire.

• jurisdiction selection
• key dates and triggering events
• amounts or rates
• any caps or overrides

If any of these inputs are uncertain, document the assumption before you run the tool.

A. Household and parenting inputs (for child support modeling)

• Children involved: number of eligible children
• Parent time / custody split (if applicable): e.g., percentage of overnights/days per parent (enter it the way the calculator prompts)
• Any shared expenses or special situations your DocketMath workflow requests

B. Income inputs (for both alimony and child support)

For each parent (or party as applicable), you’ll generally need:

• Gross earned income (salary, wages)
• Self-employment income (if applicable)
• Other income sources (commissions, bonuses, rental income, etc.)
• Overtime / irregular income treatment (if your situation includes it)
• Reliable totals by the timeframe you’ll use (most calculators work best with monthly figures)

C. Alimony-specific inputs (for alimony modeling)

• Length of marriage (years/months)
• Relative earning ability, reflected through the income inputs you provide
• Duration/purpose indicators the tool asks for (some calculators request a target timeframe)
• Health-related or need/ability factors only if prompted by the calculator interface

D. Practical data checks

• Use the same time period for all income inputs (monthly or yearly—pick one and stick with it).
• Convert amounts into one consistent unit (commonly monthly, if the tool expects it).
• Keep basic documentation so you can update the model quickly (pay stubs, tax returns, benefit letters, etc.).

Checklist

How the calculation works

DocketMath’s alimony-child-support calculator models how income and caregiving/parenting-time factors combine to produce (1) child support and (2) alimony outputs. Because it’s jurisdiction-aware, the tool’s logic and data structure are aligned to New Hampshire (US-NH).

1) Step-by-step model flow (what the tool is doing)

At a high level, the calculator typically follows this pattern:

1. Normalizes income inputs

   • It brings both parties’ income into comparable forms based on the entries you provide.
2. Applies parenting-time inputs to child support

   • The tool uses the custody/overnights (or similar time share) inputs to adjust the child support computation.
3. Calculates an estimated child support amount

   • It produces an amount (often monthly), based on the internal logic and parameters you entered.
4. Calculates an estimated alimony amount

   • It uses income disparity, marriage duration, and other tool-solicited need/ability indicators (if applicable).
5. Displays scenario results

   • The UI may show estimated monthly figures and sometimes intermediate values; you can also rerun scenarios after changing inputs.

2) What changes the numbers most

When people rerun the calculator, results usually shift most due to:

• Income changes (either parent):

  • If one parent’s income decreases (or increases), the child support estimate and potential alimony balance can move.
• Custody/time split:

  • Even small differences in the parenting-time inputs can change child support outputs because the framework uses those inputs to allocate responsibility.
• Marriage length:

  • Alimony outputs often track marriage duration closely.
• Consistency of income reporting:

  • If you enter conservative numbers for one side and aggressive numbers for the other, outputs can swing more than they would under aligned assumptions.

3) Statute of limitations context (general civil rule)

The DocketMath calculation itself focuses on support amounts, but timing can matter in real procedural contexts. The provided jurisdiction data indicates:

• General SOL period: 3 years
• General statute: RSA 508:4
• Source: https://www.thelaw.com/law/new-hampshire-statute-of-limitations-civil-actions.391/?utm_source=openai

Because no claim-type-specific sub-rule was found in the provided jurisdiction data, this should be treated as the default/general period, not a tailored deadline for every possible support-related claim.

4) How to use DocketMath results responsibly

Use the output as a planning estimate:

• Start with your best-known inputs.
• Replace estimates with verified income totals when you have them.
• Run multiple scenarios (for example, 50/50 vs. 60/40 custody, or income with/without overtime).
• Keep a short record of what you changed so you can interpret why results moved.

Common pitfalls

Avoid these common mistakes when modeling alimony and child support in New Hampshire (US-NH) with DocketMath.

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

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

1) Mixing income timeframes

• Entering weekly income as if it were monthly
• Including bonuses/irregular pay without converting them into a consistent average

Fix: Choose one timeframe (monthly is often easiest) and convert everything before entering it.

2) Assuming custody time doesn’t affect output

Because the framework uses parenting time inputs, child support estimates can change when custody/time split changes.

3) Treating the tool output as a guaranteed court order

DocketMath can estimate amounts, but courts consider evidence, credibility, and legal standards that aren’t fully captured by every input.

Fix: Treat results as a range and run a quick sensitivity check (change custody split and income assumptions slightly and observe the impact).

4) Forgetting the SOL context (general rule only)

If you’re also planning around timing, remember the provided general rule:

• Default/general SOL: 3 years
• Cited statute: RSA 508:4 (general civil SOL per the jurisdiction data provided)

5) Entering estimates without tracking assumptions

If you approximate income, it’s easy to forget what you assumed and compare scenarios incorrectly later.

Fix: Maintain quick notes:

• What income sources were included/excluded
• How you treated overtime/bonuses
• Your assumptions about the parenting-time schedule

Sources and references

• RSA 508:4 — New Hampshire general statute of limitations (general/default civil SOL period referenced in provided jurisdiction data)
  https://www.thelaw.com/law/new-hampshire-statute-of-limitations-civil-actions.391/?utm_source=openai

Start with the primary authority for New Hampshire and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

• Primary authority reference

Next steps

1. Go to DocketMath → /tools/alimony-child-support and enter your current best estimates for income and custody/time.
2. Run at least two scenarios:

   • Scenario A: your current numbers
   • Scenario B: a realistic adjustment (for example, different custody split or updated income from the most recent pay period)
3. Identify the biggest drivers of the output:

   • If income drives the estimate, update verified income first.
   • If parenting time drives the estimate, verify your time split matches the pattern you can document.
4. Record:

   • The inputs you used
   • The timeframe covered (month/year)
   • Any assumptions about irregular income or schedule patterns
5. If timing is part of your planning, keep in mind the RSA 508:4 / 3-year general SOL as a general guardrail (not a claim-specific timeline) while you gather more detail.

Related reading

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