Worked example: attorney fee calculations in New Hampshire

Example inputs

Run this scenario in DocketMath using the Attorney Fee calculator.

This worked example shows what an attorney fee calculation could look like in New Hampshire (US-NH) using DocketMath’s /tools/attorney-fee calculator. The goal is to demonstrate how the numbers flow—not to predict outcomes in any particular case.

Scenario (used for the math)

Assume a civil case in New Hampshire where the fee-shifting terms are handled through the applicable attorney-fee agreement/statute (the calculator focuses on the numerical mechanics). In this example:

• Claim filed date: January 10, 2025
• Assumed general statute of limitations (SOL) period: 3 years
• RSA 508:4 (general civil SOL): applies as the default period because no claim-type-specific sub-rule was identified in this example
• Fee-shifting starts (timing context): after a demand is made and the matter proceeds (for this example we’ll keep the focus on attorney hours and rates as the primary inputs to the fee calculation)
• Timekeepers:

  • Partner/lead attorney: 18 hours at $285/hour
  • Associate: 26 hours at $165/hour
• Paralegal/clerical: 6 hours at $95/hour
• Costs advanced by the attorney: $420 (filing fees, service, etc.)
• Billing basis for the arithmetic: hourly-fee model for the example (DocketMath can also model different fee structures depending on what you enter)

What you typically enter into DocketMath (/tools/attorney-fee)

When you use the calculator, you’re usually providing:

• Hours by role (partner, associate, paralegal)
• Hourly rates by role
• Optional costs (if your workflow includes reimbursable expenses)
• Optional timing inputs (such as filing/demand dates) if you want a sanity-check on how a 3-year SOL framework might fit into broader timing logic

Below is a compact input table for this worked example.

For the timing sanity-check, the example uses the general rule that the civil action SOL is 3 years under RSA 508:4. One source describing New Hampshire’s civil statute of limitations is:
https://www.thelaw.com/law/new-hampshire-statute-of-limitations-civil-actions.391/?utm_source=openai

Example run

Here’s the step-by-step fee math consistent with an “hourly times rate plus costs” structure.

Run the Attorney Fee calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.

1) Compute fees by timekeeper role

Partner (18 × $285)

• 18 × 285 = $5,130

Associate (26 × $165)

• 26 × 165 = $4,290

Paralegal (6 × $95)

• 6 × 95 = $570

Subtotal attorney fees

• $5,130 + $4,290 + $570 = $9,990

2) Add costs (if included in your workflow)

• Attorney-fee subtotal: $9,990
• Costs advanced: $420
• Total requested amount (fees + costs): $10,410

So, if you entered those numbers into DocketMath at /tools/attorney-fee, a typical output would resemble:

3) SOL timing sanity-check using RSA 508:4 (default rule)

If your workflow includes a timing check (e.g., whether a filing is within the SOL), this worked example uses only the general/default period:

• General SOL period: 3 years
• Statute: RSA 508:4
• No claim-type-specific sub-rule identified in this scenario, so the example uses the default general period.

With a claim filed date of January 10, 2025, the “last day” to file under a simple 3-year window is shown here only as a framework illustration:

• January 10, 2028 (3 years later)

4) What the calculator is effectively doing

In plain terms, /tools/attorney-fee is multiplying each role’s hours × hourly rate, then summing:

• Attorney fees subtotal = Σ(hours × rate)
• Optional total = attorney fees subtotal + costs

If you include timing inputs, it can also help you see how a 3-year RSA 508:4 model fits into your timeline logic.

Sensitivity check

Small input changes can meaningfully affect the total fee request. This section shows how the output shifts when you adjust key variables.

To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.

Sensitivity A: Rate change for the associate

Keep everything the same, but suppose the associate rate increases from $165/hour to $190/hour.

• Associate fees become: 26 × 190 = $4,940
• Partner fees remain: $5,130
• Paralegal fees remain: $570
• New attorney-fee subtotal: $5,130 + $4,940 + $570 = $10,640
• Add costs ($420): $11,060

Change from $10,410:

• $11,060 − $10,410 = +$650

Sensitivity B: Hours increase for the partner

Now assume partner time increases by 5 hours (from 18 to 23) at $285/hour.

• Additional partner fees: 5 × 285 = $1,425
• New attorney fees: $9,990 + $1,425 = $11,415
• Add costs ($420): $11,835

Change from $10,410:

• $11,835 − $10,410 = +$1,425

Sensitivity C: Excluding costs

If your workflow excludes costs from the “attorney fee” number and you only want fees:

• Attorney fees only: $9,990
• Versus fees + costs: $10,410
• Difference: $420

Sensitivity summary table

How this helps in practice

If you’re building a budget, stress-testing a demand amount, or sanity-checking invoices, this view helps you focus on the biggest levers:

• Hourly rates matter—especially for the timekeeper with the largest billed hours.
• Hours drive results linearly (and can swing totals quickly).
• Costs can be smaller than fee components, but they still move the total.

Gentle note: This example is for math mechanics only. Fee-shifting eligibility and recoverability depend on facts and legal standards, and you should consult a qualified attorney for legal advice.

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