Spreadsheet checks before running attorney fee calculations in United States (Federal)

What the checker catches

Running attorney-fee calculations from a spreadsheet can go wrong long before you debate whether hours are “reasonable.” DocketMath’s spreadsheet-checker is designed to catch the mechanical issues that most often distort fee outputs—without telling you whether the underlying billing entries are legally compensable.

Here are the most common failure modes the checker looks for before you run the attorney-fee calculator:

• **Mismatched time units (hours vs. minutes)

  • Example: A cell that should be 1.5 hours is entered as 90 (minutes) but treated as hours.
  • Output symptom: Fee totals can inflate by roughly 60× for those rows.

• Rate column inconsistencies

  • Detects situations where some rows use a different attorney rate column than others (e.g., partner rows pulling associate rates).
  • Output symptom: Per-hour computations change unpredictably across tasks.

• Overlapping or duplicate time entries

  • Spots identical timestamps/descriptions (or repeated entries with the same duration) that would double-count.
  • Output symptom: Total hours exceed what your billing narrative or summary would suggest.

• Missing or blank required inputs

  • Flags rows where duration, rate, or category is blank—especially where the formula silently treats blanks as zero.
  • Output symptom: Totals are understated without any obvious error message.

• Formula drift

  • Catches when a “total” cell references the wrong range after you insert/remove rows or columns.
  • Output symptom: Totals don’t match the sum of the visible line items.

• Sign errors and negative durations

  • A subtraction column (adjustments/credits) accidentally fed into the “hours” field can produce negative hours.
  • Output symptom: Net fee amounts become unexpectedly low—or even negative.

• Mixed formatting of numbers

  • Detects values stored as text (e.g., "$350" or "350 "), which can break multiplication or cause silent coercion.
  • Output symptom: Calculations return zero or error strings.

• Category mapping gaps

  • If you bucket entries (e.g., “motion,” “hearing,” “research”) into categories used by the attorney-fee calculator, the checker can flag unmapped categories.
  • Output symptom: Some work never makes it into the fee base used by your calculation logic.

Note (non-legal): This checker focuses on spreadsheet correctness (data integrity, unit consistency, formula wiring). It does not validate whether any particular billing entry is legally compensable under federal law.

When to run it

Run the checker at the moments when spreadsheet mistakes are most likely to slip in—especially when you have multiple timekeepers, you’re iterating on the sheet, or you’re importing data.

Run the checker before importing a spreadsheet into the Attorney Fee workflow. It is especially helpful when you have multiple entries or when a teammate provided the inputs.

Recommended checkpoints

• After importing or pasting billing rows

  • Example: You copy from a PDF or export a CSV, then reorganize columns.
• After structural edits

  • Adding/removing columns, inserting rows, or changing column order can break cell references.
• Before running the attorney-fee calculator

  • Treat this like a pre-flight check: fix checker flags first, then rerun the calculation for final results.
• After applying adjustments

  • For example: reducing hours by a percentage, excluding tasks, or applying caps in your model logic.

Quick workflow

1. Export or assemble your billing table
2. Run the spreadsheet-checker logic in DocketMath
3. Fix flagged rows and formula references
4. Only then run /tools/attorney-fee for the final computation

What to look for in the results

Use the checker output to decide what kind of problem you’re dealing with:

• Data-entry problems: wrong units, blanks, duplicates
• Mapping problems: categories/rates not aligning with what your logic expects
• Calculation wiring problems: broken formulas or wrong ranges

If many flags cluster around one column, start there—rate/unit columns and category mapping are especially common root causes.

Try the checker

You can use DocketMath to sanity-check your spreadsheet before running the attorney-fee calculation. Start with the Primary CTA below, then come back to interpret what the checker flags.

Run DocketMath attorney-fee

Upload the spreadsheet, review the warnings, and then run the calculation once the inputs are clean: Try the checker.

Practical sanity tests you can do (even before using the checker)

These are lightweight checks that often catch the same issues:

• Total hours should roughly match your billing narrative

  • If your narrative says “about 12 hours” and the spreadsheet calculates “720,” that strongly suggests a unit mismatch.
• Rates should be consistent by timekeeper

  • A partner’s rows shouldn’t use an associate rate unless you’ve explicitly modeled blended rates.
• Totals should equal line-item sums

  • Spot-check 10–20 rows: confirm that (duration × rate) aligns with per-line totals and the grand total.

Checkbox checklist (fast)

How outputs change after fixing issues

When you correct a flagged problem, the output should shift in a predictable way:

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