Common attorney fee calculations mistakes in Massachusetts

The top mistakes

Running attorney fee calculations in Massachusetts is simpler when your inputs are clean—but the same avoidable errors show up repeatedly when using DocketMath’s attorney-fee calculator for matters tied to Mass. Gen. Laws ch. 277, § 63.

1) Using the wrong statute of limitations baseline

A common error is assuming Massachusetts has a special, claim-type-specific limitations period for fee recovery. For this guide, use the general/default period: 6 years under Mass. Gen. Laws ch. 277, § 63.

• What goes wrong: You apply the wrong lookback window and accidentally include (or exclude) time entries that fall outside what your model assumes.
• How it changes DocketMath outputs: If you filter time entries by “within X years,” using the wrong X can skew the totals before you even address rates or reductions.

Clear rule for this guide:
No claim-type-specific sub-rule was identified here, so the default 6-year period is used (per Mass. Gen. Laws ch. 277, § 63).

2) Mixing billed time with “recoverable” time

Another frequent issue is treating raw invoice hours as if they are automatically recoverable.

• What goes wrong:

  • You use total billed hours without reflecting that some entries may require adjustment (e.g., duplicative drafting or excessive block-billed research).
  • You double-count overlapping work (for example, partner + associate time on the same substantive revision) without tracking why both were necessary.
• How it changes DocketMath outputs: If you input hours that are too broad, the calculator will multiply those hours by rates—producing a higher result than a model that uses reduced/filtered recoverable hours.

3) Applying an attorney rate to the wrong role

Rate mismatches happen when you don’t align who did the work with the rate you enter.

• What goes wrong:

  • Using a partner rate for associate hours.
  • Forgetting a separate rate for paralegals.
  • Averaging rates across multiple roles without mapping which hours correspond to which role.
• How it changes DocketMath outputs: DocketMath fee results are driven by rate × hours. Even correct hours can yield incorrect totals if rates are assigned to the wrong role.

4) Not normalizing time entries (minutes vs. decimals)

Time unit errors are among the easiest to prevent.

• What goes wrong:

  • Entering “30 minutes” as 30 instead of 0.5 hours.
  • Over-rounding (for instance, always rounding up to the nearest 0.25).
• How it changes DocketMath outputs: A small conversion slip can multiply dramatically. For example, treating 18 entries of 30 minutes as “30 hours each” inflates the modeled hours massively.

5) Ignoring rate timing (mixing old and new rate periods)

Hourly rates often change over time, so “one rate for everything” can distort the result.

• What goes wrong:

  • Applying today’s rate to earlier years’ time entries.
  • Blending rates even though your data supports different rates by year and/or role.
• How it changes DocketMath outputs: Even when hours are correct, inconsistent “rate date” handling can shift totals substantially.

6) Overlooking duplicate work across revisions

Many matters involve multiple drafts and revisions. The error is counting all revision hours as fully recoverable without structure.

• What goes wrong:

  • Including full hours for every draft/edit without tagging which revisions were substantive versus minor.
  • Counting multiple attorneys’ time on the same substantive revision without distinguishing first-pass work from review/rework.
• How it changes DocketMath outputs: If your modeling goal is “clean” recoverable time, duplicates should be reviewed and, if appropriate, reduced or flagged before running totals.

7) Treating overhead or non-hourly items as billable attorney time

Not every expense belongs in the “hours” bucket.

• What goes wrong:

  • Entering overhead or non-hourly costs as if they were compensable time.
  • Rolling flat-fee items into the hourly rate field.
• How it changes DocketMath outputs: DocketMath will treat whatever you enter into the hours/time fields as time—so keep costs in their own category instead of converting them into “hours.”

How to avoid them

Use DocketMath to make your calculations reproducible. The key is ensuring your inputs clearly map to the outputs you want—especially around the lookback window, time units, and recoverability assumptions.

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.

Step 1: Lock the timeline (use the 6-year default)

For this guide, the default lookback is 6 years under Mass. Gen. Laws ch. 277, § 63.

• Action checklist:

Step 2: Separate time by role and normalize units

Before running any totals, structure the dataset so each entry answers: who did the work, when, and how long?

• Action checklist:

Step 3: Model recoverability before you compute fees

Don’t rely on hope that “the calculator handles reductions.” If reductions matter to your methodology, represent them in your inputs.

• Action checklist:

  • Scenario A: raw hours
  • Scenario B: reduced/filtered recoverable hours

Step 4: Apply rate changes by period

Treat rates as period-specific.

• Action checklist:

Step 5: Keep costs out of the “hours” fields

Expenses and overhead should be separate so they don’t inflate fee/time totals.

• Action checklist:

Step 6: Run DocketMath for traceable, repeatable results

When your inputs are consistent, run DocketMath using the attorney-fee tool to generate fee totals you can audit.

Try the calculator here: /tools/attorney-fee

• Mini workflow:

  1. Normalize time entries (decimals; 0.5 for 30 minutes).
  2. Assign rates by role and by date period.
  3. Filter entries using the 6-year default based on Mass. Gen. Laws ch. 277, § 63.
  4. Compare outputs using raw vs. modeled recoverable hours.

Step 7: Sanity-check outputs with quick crosschecks

Before relying on numbers, do basic consistency checks.

• Quick checks:

Gentle reminder: This is general information for planning and modeling, not 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