Common attorney fee calculations mistakes in Maine

The top mistakes

Run this scenario in DocketMath using the Attorney Fee calculator.

Attorney fee calculations can look straightforward until one wrong assumption changes the entire number. In Maine, many “math failures” come from (1) mixing up timing rules, (2) misunderstanding what fee components your method should include, and (3) measuring inputs (hours, rates, costs, and dates) in a way that doesn’t match the calculation model.

Below are common mistakes people run into when estimating attorney fees in Maine using DocketMath—and how they show up in outputs.

1) Using the wrong statute of limitations period (SOL)

A frequent error is applying a claim-type-specific limitations period when you’re actually trying to model Maine’s general/default rule.

For Maine’s general/default limitations period, the applicable rule comes from:

• Title 17-A, § 8 (General SOL period: 0.5 years)
  Source: https://legislature.maine.gov/statutes/17-a/title17-asec8.html?utm_source=openai

Key point for calculations: Use this as the general/default period when no claim-type-specific rule is being used. Your brief data also indicates that no claim-type-specific sub-rule was found, so you should clearly treat this as the default for this kind of estimate.

How the error impacts the number:
If you accidentally extend the SOL beyond 0.5 years, your model may:

• include attorney time that would fall outside the default window, and/or
• overstate “recoverable” totals, which can then ripple into settlement ranges and credibility in review.

2) Including fee components the method didn’t intend to include

Another common trap is treating “attorney fees” as a single undifferentiated bucket even when your methodology expects separate inputs—for example:

• attorney hours vs. paralegal hours,
• motion-specific work vs. administrative/clerical tasks,
• billed attorney time vs. in-house time.

How it shows up in DocketMath outputs:
The total may look precise, but it can be conceptually wrong if the hours you entered don’t match the fee model you’re trying to evaluate. In practice, that often means the number is harder to defend during review.

3) Mixing up hourly rates, blended rates, and effective rates

People often enter:

• a single hourly rate when their data reflects different rates by attorney level, or
• a blended/effective rate and then apply a multiplier again (which can effectively double-count the “complexity” the blended rate was meant to represent).

Common symptom:
The output changes dramatically when you adjust one rate input, even though hours stayed the same—suggesting an inconsistent rate/multiplier setup.

4) Double-counting costs (or treating costs like fees)

Some calculations accidentally roll expenses into the attorney-fee line, even though the fee request being modeled separates:

• “fees” (labor) from
• “costs” (expenses).

How it impacts results:

• Your attorney fee estimate can become too high relative to how it would be itemized in a fee request.
• In negotiations, the “extra” amount becomes the first target for challenge.

5) Discounting or slicing time by the wrong window

Attorney-fee calculations are sensitive to what date range you’re evaluating. If the SOL window is off—or if invoices span multiple periods—how you allocate time can change the result.

Example of the failure mode:
You might include all fees from an invoice that partially falls outside the intended window, because you aggregated invoices instead of allocating based on work dates.

6) Applying “default” timing while your narrative implies claim-specific timing

Even if your spreadsheet is internally consistent, timing logic can still be inconsistent with your inputs. If you model using the default SOL window but your underlying scenario depends on a claim-type theory, you can end up blending assumptions.

Your brief data is explicit: use the general/default period when no claim-type-specific sub-rule is found. Don’t silently switch your timeline model midstream.

7) Rounding too early

Rounding is often the smallest input error—but it can still matter. Common issues include:

• rounding hourly rates first,
• rounding intermediate “hours × rate” subtotals,
• rounding before applying multipliers.

Result: small differences can compound into a visibly different settlement band.

How to avoid them

Here’s a practical checklist for cleaner, Maine-appropriate attorney fee estimates using DocketMath. Focus on inputs first—outputs are only as accurate as the assumptions behind 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.

1) Lock your timeline assumption up front

For this default scenario, use:

• General SOL period: 0.5 years
• Statute reference: 17-A, § 8
  Source: https://legislature.maine.gov/statutes/17-a/title17-asec8.html?utm_source=openai

Action steps in your workflow:

• Make sure your date range covers only the intended 0.5-year “default” window.
• Label the estimate clearly as “general/default modeling,” so you don’t reuse it for a different legal theory.

2) Use component-based inputs (not one big bucket)

If your fee method supports it, split your inputs into categories:

• attorney hours (by rate/level if needed),
• paralegal hours (if you include them),
• costs (enter separately if your method distinguishes them).

Checklist:

3) Normalize rate inputs and multiplier logic

Pick a rate approach and stick to it:

• Use hourly rates directly (different rates per attorney level), or
• Use a blended effective rate, but then avoid applying an additional multiplier that already accounts for that complexity.

Quick test for rate errors:
Change one rate by 10% while keeping hours constant. If the output moves far more than you expect, you may have double counting (such as applying a multiplier twice).

4) Slice by date—not just invoice totals

When time windows matter, allocate time to the relevant period.

Practical method:

• Use invoice/work dates to decide whether time falls inside the model window.
• If possible, apportion time when an invoice includes work outside the evaluation range.

5) Maintain an audit trail of rounding

To reduce rounding drift:

• keep full precision in intermediate steps,
• round only once for display (e.g., dollars to the nearest cent).

Checklist:

6) Run controlled “what-if” scenarios in DocketMath

Use DocketMath for repeatable scenario runs rather than manually editing formulas each time. For example:

• Scenario A: general/default SOL window (0.5 years)
• Scenario B: only if explicitly testing another theory, use an alternate window assumption
• Scenario C: costs separated vs. costs included (to see sensitivity)

Why this matters:
If the result swings wildly between scenarios, it usually indicates that timeline or cost treatment is driving the number—so that’s where your review should focus.

7) Document your assumptions before relying on the output

Before sharing results or treating them as settlement numbers, record:

• the SOL assumption (general/default 0.5 years under 17-A, § 8),
• whether costs were treated separately,
• the rate methodology (hourly vs. blended; and whether multipliers were applied).

If you want to run your own estimate, use DocketMath’s attorney fee calculator here: /tools/attorney-fee.

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