How to run Alimony Child Support in DocketMath for New Hampshire

Step-by-step

This guide walks you through running alimony and child support in DocketMath for New Hampshire (US-NH). The goal is to help you get jurisdiction-aware calculations and understand what changes when you adjust inputs—without treating the output as legal advice.

1) Start with the right tool in DocketMath

1. Go to the primary calculator: **/tools/alimony-child-support
2. Confirm the jurisdiction is set to New Hampshire (US-NH).

   • If DocketMath prompts for jurisdiction, select US-NH before entering any numbers.

2) Enter case facts using the calculator’s input fields

DocketMath’s alimony-child-support calculator is designed for quick “what if” runs. Enter values that match the scenario you’re modeling (for example: income, payment frequency, duration, and support start date—depending on the fields shown in the tool).

Use this checklist while entering data:

How outputs change (input sensitivity):

• Increasing the payor income typically increases the calculated support amounts (assuming all else is held constant).
• Changing payment frequency can change the displayed periodic amount (even if the overall total period is conceptually aligned).
• Adjusting dates affects how many payment periods the tool models.

3) Run the calculation

Click Calculate (or the equivalent button shown in the tool). DocketMath will return figures based on the inputs you entered and the selected US-NH jurisdiction.

4) Review the results panel like a checklist

When results load, scan for at least these items (exact labels depend on the interface):

• Alimony estimate (if included in your input set)
• Child support estimate (if included in your input set)
• Total periodic payment (if displayed)
• Payment schedule or summary (sometimes shown as totals or a timeline)

If the tool outputs multiple components (for example, separate lines for alimony vs. child support), treat each line item as a distinct component you can test by changing only one input at a time.

5) Run “scenario tests” to understand sensitivity

Instead of trying to get it perfect in one pass, use controlled revisions:

This helps you identify what drives the numbers inside DocketMath—especially if you’re reconciling estimates against a worksheet or order you already have.

6) Understand New Hampshire’s general limitation period (timing context)

When thinking about enforcement or related timing questions, New Hampshire’s general civil statute of limitations can be a useful background point.

• 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

Important clarity: No claim-type-specific sub-rule was found in the provided information. So the 3-year period is the general/default period described by RSA 508:4. Different legal theories (and different causes of action) can have different limitation rules, so treat this as a general timing reference rather than a guarantee about any specific claim.

7) How this timing context affects your DocketMath workflow

Even though the alimony-child-support calculator focuses on payment modeling, the 3-year general SOL can matter when you’re deciding what timeframe to model or what timeframe to review in your records.

A practical workflow:

• Use DocketMath to estimate support for the timeframe covered by your chosen inputs.
• Separately, use the RSA 508:4 general 3-year context to decide whether you should constrain the historical window you’re analyzing (for example, for record review or comparison).
• Document the dates you used, so your model aligns with the timeframe you’re evaluating.

This helps keep your “calculation story” consistent: your modeling window matches the timeframe you’re assessing, rather than mixing assumptions.

Common pitfalls

Below are the most frequent issues people run into when using DocketMath for US-NH alimony/child support runs.

• 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.

Input and configuration pitfalls

Timing pitfalls related to RSA 508:4

Pitfall to avoid: People sometimes treat “general SOL” as an automatic enforcement cutoff. Instead, treat RSA 508:4’s 3-year as a general timing reference and align your analysis window with what you’re actually evaluating.

Try it

Ready to run a New Hampshire calculation in DocketMath?

1. Open the calculator: **/tools/alimony-child-support
2. Set jurisdiction to US-NH
3. Enter your income, frequency, and dates as prompted
4. Click Calculate
5. Perform at least 2 scenario checks:
6. Save or note what changed between runs so you can explain your assumptions later.

If you’re also tracking timing questions, keep a quick note that the general 3-year SOL under RSA 508:4 is a default timing reference, and also keep your modeled timeframe consistent with your record review.

Related reading

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