Inputs you need for Damages Allocation in New Hampshire

Inputs you will need

If you’re using DocketMath to support damages allocation work in New Hampshire (US-NH), start by collecting inputs that determine (1) what damages categories exist in your matter and (2) how long each claim could remain actionable under the state’s general statute of limitations.

New Hampshire’s default civil limitations period is 3 years under RSA 508:4. No claim-type-specific sub-rule was found for this workflow, so you should treat RSA 508:4 as the general/default period when running allocation assumptions.

Before you click Run it in DocketMath, gather these inputs:

• Jurisdiction code

  • Use: US-NH
• **Date of accrual (or best available proxy)

  • The date the damages-claim basis arose (often your “event date” accrual proxy).
• Filing date

  • Needed to compare against the 3-year window under RSA 508:4.
• Damages components you plan to allocate

  • Examples (tailor to your case): medical costs, lost earnings, property damage, out-of-pocket expenses, non-economic damages, interest, or other buckets you intend to allocate.
• Estimated amounts per component

  • Dollar figures (or ranges) you want allocated across the components.
• Allocation rules or weights you will apply

  • DocketMath may support different approaches depending on how you structure inputs (for example: direct assignment per component, proportional allocation, or category-weighted allocation).
• Any caps/exclusions you want the calculator to reflect

  • If you’re modeling an amount you believe should be reduced, capture the cap amount and/or the exclusion logic you want reflected in the allocation model.
• Currency / rounding preference

  • Decide whether to round at the component level or only at the end of the allocation.

Practical note: DocketMath only calculates with the data you enter. If your accrual date or component list is off, the output can still be mathematically consistent while not matching the underlying facts—so it’s worth validating your inputs before relying on results.

Where to find each input

Use documents in your case file (not just assumptions) to populate the DocketMath fields. Here’s a practical “where to look” checklist:

• **Jurisdiction code (US-NH)

  • Use your matter’s forum/jurisdiction setting in DocketMath.
  • If you’re modeling multiple jurisdictions, confirm you’re using the one tied to the claim theory you’re modeling.
• **Date of accrual (event date / accrual proxy)

  • Look in:

    • incident reports
    • demand letters
    • complaint allegations (often includes an event date)
    • medical records (useful if damages track treatment timelines)
• Filing date

  • Pull from:

    • the complaint filing stamp
    • e-filing confirmations
    • docket entry metadata (the “filed on” date)
• Damages components

  • Look in:

    • damages schedules
    • expert reports / declarations
    • invoices and receipts
    • payroll records / employment documents
    • repair estimates or appraisals
• Estimated amounts per component

  • Source each number from:

    • bills/invoices (medical, repair, travel)
    • employment records (lost wages)
    • accounting summaries (out-of-pocket totals)
• Allocation rules / weights

  • Source from your methodology notes or internal framework, such as:

    • proportional allocation percentages
    • category-based weights you intend to apply consistently across components
• Caps/exclusions

  • Identify the logic you want modeled from the case record:

    • settlement offsets or prior payments you want reflected
    • documented limitations you want to apply within the allocation model
• Rounding preference

  • Decide once and apply consistently (component-level rounding can slightly change totals).

Before you rely on results, sanity-check timing against RSA 508:4: if your filing date is more than 3 years after your accrual proxy, the modeled allocation may still help with arithmetic, but the underlying claim viability (limitations) becomes a separate, case-specific question.

For citation context: the general civil limitations period referenced here is RSA 508:4. Source summary: https://www.thelaw.com/law/new-hampshire-statute-of-limitations-civil-actions.391/?utm_source=openai

Disclaimer: This is workflow guidance, not legal advice. Limitations analysis can be affected by additional facts and any applicable exceptions.

Run it

Run DocketMath’s damages-allocation tool here: ** /tools/damages-allocation

Before running, confirm you’ve captured the core New Hampshire timing inputs:

• Accrual proxy date
• Filing date
• **General SOL period: 3 years (RSA 508:4)

Then, structure your damages components in DocketMath according to what the calculator expects. A reliable way to reduce mistakes is to follow this checklist:

How output changes when inputs change

Use these “what-if” patterns to interpret results:

• If the filing date moves later

  • The model’s SOL-related assumptions (where included in the workflow) can shift from “within 3 years” to “outside 3 years,” which may change how you treat components under the allocation assumptions tied to limitations timing.
• If the accrual proxy date moves earlier

  • The time gap increases, making it more likely the model indicates potential limitations exposure under the general 3-year period.
• If you add or remove damages components

  • Your allocation totals and per-component outputs change immediately, because the tool distributes and/or sums the inputs you provide.
• If you change allocation weights

  • Component-level outputs re-balance even when the overall total damages input stays constant.

When you finish the run, export the results (or copy outputs) and keep a record of the exact inputs used—especially dates—so you can rerun quickly if additional facts emerge.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules