Common Damages Allocation mistakes in New Hampshire

The top mistakes

Damages allocation errors in New Hampshire often happen before anyone calculates totals. DocketMath’s damages-allocation tool helps you model allocations, but the quality of the output depends on how you frame the underlying damage items (and how you time them). Below are the most common mistakes we see for US-NH workflows.

1. Mixing up damages categories and then “netting” them

• A frequent error is collapsing different damage types into one combined number and then distributing that combined total across parties or time periods.
• In practice, that can create internally inconsistent results (for example, treating medical expenses as if they were lost wages when the allocation method is supposed to distinguish categories).
• In DocketMath, prefer a structured input approach: enter damages in the same categories you intend to allocate, then let the calculator apportion based on those inputs rather than re-aggregating prematurely.

1. Allocating based on liability assumptions that aren’t carried into the damages step

• Another common workflow error is baking liability reasoning into the “total damages” before allocation—such as reducing a category total because you think one party is 30% responsible.
• That may be workable in some contexts, but it becomes a error when the tool is meant to allocate damages items based on allocation facts you provide.
• A practical rule: keep your allocation method consistent and transparent. If your intent is proportionate responsibility, reflect that proportion in the allocation inputs, rather than changing the effective totals midstream.

1. Forgetting New Hampshire’s 3-year general civil statute of limitations

• Many filings struggle not because the math is wrong, but because the time window is wrong.
• New Hampshire’s general statute of limitations for civil actions is 3 years under RSA 508:4.
• Important: No claim-type-specific sub-rule was found in the provided materials, so this content uses the general/default period as the starting point—not a shorter or longer specialized timeline.

Gentle reminder: DocketMath can help you model allocation outcomes, but it can’t replace a limitations analysis. If part of a damages stream falls outside a 3-year window under RSA 508:4, your allocation structure should reflect that modeling choice (for example, by separating in-window vs. out-of-window components).

1. Using the wrong “start date” for time-limited damages

• A frequent cause of mismatch is applying the limitations concept to the filing date only, instead of separating:

  • when damages accrued (or when loss periods occurred), and
  • the date you measure backward from (the relevant cut-off under RSA 508:4).
• Even a small date shift can change which wage-loss months, weekly losses, or expense events are included in the allocable portion.

1. **Overlooking partial-period effects (monthly, weekly, or event-based damages)

• If you enter damages as if they occurred all at once, you may accidentally allocate amounts to periods that should be excluded.
• Conversely, if your damages are event-based (e.g., discrete invoices) but you allocate as if they were continuous (e.g., wages), your outputs may look precise while being conceptually mismatched.
• The fix is to reflect the nature of each item in how you input it: event dates for discrete expenses, and period labels for ongoing or recurring losses.

1. Rounding too early

• Rounding damages or allocations before DocketMath calculates totals can create “drift.”
• That drift often shows up as:

  • allocated totals that don’t reconcile with the sum of line items, or
  • a need for manual “plug” adjustments later.
• A better workflow: enter full-precision amounts, run DocketMath, then round only for final presentation.

1. Leaving out “small” line items that change allocation math

• Even seemingly minor categories can affect allocation results—especially where the method relies on relative proportions, weights, or category totals.
• Omitting a small category can distort the distribution and create reconciliation problems when opposing parties (or the court) expect a complete line-item breakdown.

How to avoid them

Use a consistent, tool-friendly workflow. The goal is not just accurate math; it’s accurate structure—especially around time windows and category alignment.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

1) Confirm your allocation basis before entering numbers

Before using DocketMath (damages-allocation), decide what the allocation represents, such as:

• Proportion by item type (different category treatment, if that’s your model), or
• Proportion by party impact (percentages you provide), or
• Proportion by time window (only include the portion that falls within the applicable period).

Then keep that basis consistent across every line item. If you change your allocation logic midstream, DocketMath may still produce internally consistent outputs—but they may not match your intended theory.

2) Apply the New Hampshire general SOL window to time-based components

For general civil damages modeling, the default limitations period is:

• 3 years under RSA 508:4

Because no claim-type-specific sub-rule was provided, treat this as the general/default starting point.

Practical checklist for SOL cut-off modeling (US-NH):

• continuous (e.g., ongoing wage loss),
• periodic (e.g., weekly losses),
• event-based (e.g., discrete invoices or discrete loss events).

3) Use DocketMath inputs that match the nature of the damages

DocketMath is most reliable when each entered line item corresponds to what it actually represents.

Input-to-output alignment tips:

• Use event dates for invoice-like expenses.
• Use period labels (month/week) for ongoing or recurring losses.
• Keep the category label consistent with how you plan to report results (e.g., medical, property, wages).

If your damages are mixed, split them into multiple line items rather than combining them into one bucket.

4) Enter full precision; round only at the end

To reduce reconciliation problems:

5) Validate totals and reconciliation every time

After running damages-allocation, run quick sanity checks:

• Sum of allocations: should match the total you intend to allocate (within your rounding rules).
• Category reconciliation: each category’s allocated amount ties back to its category total.
• Time-window separation: any SOL-excluded portion is clearly separated or omitted.

If any check fails, revise the inputs—don’t just adjust formatting.

6) Document your date assumptions so changes are explainable

When results change (often due to time cut-off adjustments), you’ll want to know which dates drove the change.

Maintain a brief internal record:

If you need a structured starting point for your model, use DocketMath here: damages-allocation.

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