Alimony Child Support reference snapshot for New Hampshire
5 min read
Published April 15, 2026 • By DocketMath Team
Rule or statute summary
In New Hampshire, alimony and child support obligations are enforced through a mix of family-law orders and standard enforcement tools. This reference snapshot focuses on one timing concept that often matters when unpaid support is being collected or pursued: the general civil statute of limitations (SOL).
The default (no claim-type-specific sub-rule identified)
For this snapshot, no claim-type-specific sub-rule was found in the provided jurisdiction data. That means the timing guidance below uses the general/default SOL period for civil actions—not a specialized limit tied to a particular arrears category or enforcement procedure.
- General SOL period: 3 years
- General statute: RSA 508:4
Practical note: If a court treats a specific enforcement mechanism or claim posture differently (for example, enforcement tied directly to a judgment or other specialized procedure), a different timing rule may apply. This snapshot intentionally uses the general/default period listed in the brief.
What a 3-year SOL affects (practically)
When someone is owed money under an alimony or child support order, timing questions can come up in a few common workflow moments—especially when you are deciding how far back you can pursue amounts through a civil action framing versus relying on ongoing enforcement pathways that remain available because the obligation is anchored in the underlying order.
In practical terms, you may be working with these inputs:
- Unpaid amounts (arrears) for specific months/periods.
- A decision about whether the timing still supports a particular civil-action recovery theory.
- A need to build a consistent timeline that can be shared with counsel or used for self-checking.
Use this 3-year SOL as a planning lens
Use the 3-year SOL as a planning lens for your arrears timeline:
Gather due dates and payment dates
- For each unpaid period, record the date the installment was due.
- Record the date(s) payments were actually made and the amounts.
Create a “within 3 years / outside 3 years” map
- Compare the dates of missed installments to the relevant enforcement action timeline you’re planning for.
- Mark installments that fall inside the 3-year window versus those outside it.
Preserve your records
- Court order and any modifications
- Payment ledger (what was paid, when it was paid)
- A summary table of missed vs. paid amounts
If you want a quick estimate first, use DocketMath
- The calculator can help you produce modeled support amounts to align against your arrears ledger and the 3-year planning window.
(Gentle disclaimer: This is a timing snapshot for planning and organization, not legal advice. If your case involves a particular enforcement posture, ask a qualified NH family-law attorney or legal aid for confirmation of how timing applies in your situation.)
Citations
- RSA 508:4 — General statute of limitations for civil actions: 3 years
Source (reference link provided): https://www.thelaw.com/law/new-hampshire-statute-of-limitations-civil-actions.391/?utm_source=openai
Scope reminder: This snapshot applies the general/default 3-year SOL from the brief. If there is a claim-type-specific rule or a specialized procedural path tied to a judgment/enforcement mechanism, the applicable period may differ.
What to keep consistent in your worksheet
To apply the SOL approach consistently, have these items ready:
- Your reference date (the date you’re considering filing or otherwise initiating the action you’re modeling)
- Missed installment due dates (for alimony and child support)
- Missed amounts per period
- Payment dates and amounts actually received (so you can separate fully/partially paid vs. unpaid periods)
Use the calculator
For a New Hampshire alimony + child support reference workflow, use DocketMath’s alimony-child-support calculator to turn common “order-style” inputs into estimated outputs you can compare to your arrears timeline.
Primary CTA: **/tools/alimony-child-support
What to enter (and why)
While the exact fields can vary by calculator configuration, the practical structure usually includes:
- Income inputs
- Each party’s income figures used for support modeling.
- Support inputs
- Child-related parameters (e.g., number of children), plus any tool-specific variables.
- Timeframe
- The month/year (or period) you want to model, so the results correspond to the same period you’re tracking in your arrears records.
- **Order-related assumptions (if applicable)
- Inputs that reflect the structure of an existing order scenario (as opposed to purely retroactive assumptions).
How outputs should change as inputs change
You can sanity-check results by watching how changes map to typical support logic:
- Higher payor income → often increases estimated support totals.
- More children (if included) → often increases child-support-related amounts.
- Changing the modeled timeframe / period selection → changes the totals you’re comparing against arrears for that specific window.
- Changing assumptions that affect how the calculator allocates amounts → can shift which periods appear larger/smaller in your comparison table.
Connect calculator outputs to the 3-year SOL planning lens
Once you have modeled amounts (or help preparing totals), connect them to your timing map:
Build a simple arrears timeline (spreadsheet-style)
- List each unpaid installment period with:
- due date
- modeled/claimed amount
- paid amount (if any)
- remaining unpaid balance for that period
Mark each installment against the 3-year window
- Installments that fall within 3 years under RSA 508:4 (general/default) stay in your “likely within the civil SOL planning window” bucket.
- Installments outside the window are candidates for time-bar planning under the general/default assumption—subject to any different claim-specific timing rules that may apply.
Use this to structure (not replace) legal review
- The output helps you organize dates and amounts so counsel can quickly confirm which timing rules govern your exact posture.
