Common attorney fee calculations mistakes in New Hampshire

Run this scenario in DocketMath using the Attorney Fee calculator.

Running attorney fee calculations in New Hampshire gets tricky fast—not because the math is hard, but because common “assumptions” are. Whether you’re preparing a demand, supporting a fee request, or stress-testing exposure for a settlement conversation, small errors in inputs or structure can swing the final number.

DocketMath’s attorney-fee tool is designed to keep the workflow consistent. Still, if your inputs are off (or you apply the wrong rule), you’ll get a confidently wrong output.

The top mistakes

• using gross recovery when net applies
• mixing recoverable and non-recoverable time
• skipping statutory prerequisites
• forgetting fee caps or schedules

Capture the source for each input so another team member can verify the same result quickly.

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

1) Using the wrong time baseline (and mixing “billable” with “recoverable”)

A frequent error is taking total billed hours and treating them as recoverable hours automatically. In most attorney-fee disputes, recoverable time is tied to what’s compensable under the applicable authority (contract, statute, or other basis) and what the court will treat as reasonable.

What goes wrong in calculations

• You enter billable hours for everything, including work that may be excluded (e.g., unrelated tasks, clerical time, or duplicated work).
• You fail to separate:

  • drafting that supports the claims at issue, vs.
  • ancillary work that may not be compensable.

Math impact

• If you overstate recoverable hours by even 10–20%, the total fee often scales linearly (hours × rate), producing a large difference before you even consider multipliers or reductions.

2) Ignoring the “reasonableness” layer when applying hourly rates

Even if the hourly rate looks “reasonable” to you, fee calculations often rely on reasonableness concepts rather than pure arithmetic.

Common input mistakes

• Using a blended rate without documenting why it matches the work type.
• Applying a single rate to tasks that should be segmented (e.g., partner-rate drafting vs. associate research vs. paralegal support).

Math impact

• A rate error is multiplicative. For example, if recoverable hours are 30 and the rate is overstated by $50/hour, the calculation is off by $1,500.

3) Double-counting time entries across revisions or parallel tasks

Drafting cycles and case management create overlapping time. Many fee submissions require clean traceability—especially where multiple lawyers worked on the same phase.

Typical double-count pattern

• Two timekeepers log work on the same document version “from start to finish.”
• The fee input reflects both sets of hours without adjustment.

Math impact

• Double counting can inflate the fee by multiples, not percentages, once you apply any across-the-board adjustments.

4) Forgetting reductions for tasks that don’t connect to the outcome

Another common error is calculating fees based on effort rather than outcome alignment. Fee calculations can require pruning:

• unsuccessful claims,
• discrete work tied to those claims, or
• work not reasonably necessary to achieve the result.

Math impact

• This is where “hours” needs structured reductions (not after-the-fact guesses).
• If you apply a blanket reduction incorrectly (e.g., subtracting the wrong number of hours), you may under- or over-correct.

5) Misapplying the statute of limitations timeline

Fee disputes often ride alongside other claims. People sometimes assume there’s a special limitations period for fee claims.

In New Hampshire, the general/default civil SOL period is 3 years, set by RSA 508:4. No claim-type-specific sub-rule was found in the provided jurisdiction data, so treat RSA 508:4 as the default SOL for general civil actions unless another specific rule applies.

Statute to use

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

Math impact

• Even though SOL doesn’t directly change “hours × rate,” it changes whether fees are recoverable at all for the relevant time window and whether certain work can be tied to enforceable claims.

6) Producing totals without reconciling assumptions

A final, practical error: presenting a single number without an audit trail.

Common breakdowns

• No list of assumptions (e.g., which entries were excluded, which tasks were segmented by timekeeper).
• Not showing how inputs change outputs when revised.

Math impact

• Even if the number is right today, it won’t survive a later review if you can’t explain why those hours and rates are being used.

How to avoid them

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.

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

Use a structured input checklist in DocketMath

When you run DocketMath’s attorney-fee calculator at /tools/attorney-fee, treat each input like a decision you can defend later. For example:

This checklist helps ensure you’re not relying on “one number” assumptions.

Separate “rate logic” from “time logic”

A clean workflow reduces mistakes:

1. Confirm the hourly rates you entered reflect the timekeeper and work type.
2. Confirm the hours you entered are recoverable (after exclusions/reductions).
3. Only then reconcile the total.

In practice, you’ll often catch errors faster by asking:

• “If I changed hours by 5, did the total move exactly by rate × 5?”
• “If I changed rate by $25/hour, did the total move exactly by hours × $25?”

That kind of sensitivity check detects double counting or incorrect input wiring.

Maintain an “audit-ready” adjustment log

Before finalizing the calculator output, capture a short narrative for each adjustment:

• What hours were excluded (by description)?
• Why were they excluded (unrelated task, duplicate, or outcome mismatch)?
• What reduction method did you use (specific hour subtraction vs. percentage)?

DocketMath outputs are easiest to validate when your adjustments are transparent.

Anchor the timeline early using RSA 508:4’s default SOL

Because RSA 508:4 provides a 3-year general/default SOL period, make it part of your workflow before you finalize fee scope:

You’re not changing the calculation mechanics—you're ensuring the calculation targets fees that can realistically be pursued.

Run “what-if” scenarios to avoid hidden assumption lock-in

A practical way to catch mistakes is to model ranges:

If Scenario B and Scenario C produce totals that don’t behave as expected, you likely have an input error (or an overlap issue).

Related reading

• Worked example: attorney fee calculations in Vermont — Worked example with real statute citations
• Attorney Fees Guide for Alaska
• Attorney Fees Guide for American Samoa