Spreadsheet checks before running attorney fee calculations in California

What the checker catches

Run this scenario in DocketMath using the Attorney Fee calculator.

Before you run an attorney fee calculator in California, you want your spreadsheet to answer one fast question: “Does this model match the basic math and time assumptions behind fee calculations?” DocketMath’s spreadsheet checks are built to catch the kinds of issues that quietly change outcomes—especially when you copy data between formats or update assumptions without realizing it.

Common failure points the checker is designed to detect include:

• Date logic mistakes

  • Swapped start/end dates (fee period inversion).
  • Wrong day-count basis (calendar days vs. working days).
  • Off-by-one errors when converting between date formats.

• Rate/quantity mismatches

  • Hourly rate stored as the wrong scale (for example, 350 entered where 3.50 was expected).
  • Hours entered as minutes (for example, 90 minutes treated like 90 hours).
  • Totals calculated from the wrong column or row range.

• Weighted-rate and multiplier errors

  • Applying a multiplier to the wrong subtotal (for example, after costs/fees instead of before).
  • Using the correct multiplier factor, but for the wrong line items.

• Redundant or double-counted components

  • The same work category included twice under different labels.
  • Expenses (or “costs”) mixed into the labor subtotal (or vice versa).

• Unit normalization issues

  • Inconsistent time representation (decimal hours for one block, HH:MM for another).
  • Conversions applied in some rows but not others.

• Regression and rounding drift

  • Rounding too early (intermediate steps) instead of at the end.
  • Numbers formatted as text, causing totals to concatenate or behave unexpectedly.

• Category mapping problems

  • A row labeled “paralegal” accidentally routed into an “attorney” bucket (or the reverse).
  • Missing category labels that cause default rates to be used when they shouldn’t.

One more sanity check matters just as much as arithmetic: your modeled fee window and eligibility assumptions. A spreadsheet can calculate perfectly and still be “wrong” for your scenario if the time period you’re filtering doesn’t line up with the assumptions you intend to apply.

In this post, the jurisdiction framing uses California’s general statute of limitations period for civil claims as a 2-year general default under CCP §335.1. The 2-year period is the general default; this post does not apply any claim-type-specific sub-rule because none was provided. Source: https://www.alllaw.com/articles/nolo/personal-injury/laws-california.html

Gentle reminder: DocketMath’s checks focus on spreadsheet correctness (dates, units, totals, mapping). They are not legal advice. If your scenario requires a different limitations framework, ensure your inputs reflect that before interpreting results.

To keep calculations consistent, run the checker before using any attorney fee math outputs. Think of it like preflight checks for your model: catch structural problems (dates, units, mapping, totals) before you trust the attorney-fee totals.

When to run it

Use DocketMath’s spreadsheet checks at predictable checkpoints—especially when data changes or format conversions occur. If you wait until after you’ve computed fees, you’ll often find the problem only when totals “look off,” which makes debugging slower.

Recommended timing:

• After importing your timesheet or fee data

  • Particularly if hours, rates, or date ranges came from CSV exports or another spreadsheet with different date/time formats.

• After updating any fee inputs

  • Hourly rate changes, multiplier changes, category mappings, or flags for whether expenses are included.

• Before freezing a version for review

  • When your spreadsheet feeds into declarations, settlement worksheets, or internal summaries.

• Before applying the attorney-fee calculator

  • Run the spreadsheet checks first, then run the calculator only after the model passes the core validations.

A practical “no rework” workflow:

1. Clean and standardize date and unit formats in your spreadsheet.
2. Run DocketMath spreadsheet checks on the raw data.
3. Fix flagged issues, then rerun checks.
4. Only then run the attorney-fee calculation and interpret totals.

Quick checklist you can keep in mind every run:

Because California’s general limitations framing here is 2 years under CCP §335.1, your spreadsheet may include logic that filters which time entries are “eligible” based on a modeled window. If that filter uses the wrong boundaries or date parsing, your calculator can produce a precise-but-incorrect total. That’s exactly the kind of issue a checker-first workflow helps prevent.

Try the checker

DocketMath is the tool name you can use to sanity-check your spreadsheet before running attorney fee calculations. The goal isn’t to “guess” what your spreadsheet should do—it’s to confirm that it behaves as expected given your inputs.

Start with your current sheet and validate these three layers:

1) Inputs (the spreadsheet truth)

• Dates: confirm each entry date or fee period has valid start/end dates.
• Hours: ensure each time entry is numeric and in the intended format (e.g., decimal hours) or correctly converted.
• Rates/multipliers: verify you didn’t store rates as whole numbers when the calculator expects decimals (or the opposite).

2) Intermediate outputs (where errors hide)

• Row-level calculations: review a few representative rows.
• Subtotals by category: confirm sums match what you see in the sheet.
• Eligibility/window filtering: verify which rows are included/excluded matches the modeled window.

3) Final totals (where discrepancies surface)

After the calculations, totals should be consistent with:

• Sum of all line items
• Correct multiplier application (to the intended subtotal only)
• Correct separation of labor vs. expenses (if your model separates them)

If you want to go straight to the workflow, you can use the primary CTA for the attorney fee tool here:

• Primary CTA: /tools/attorney-fee

And in practice, you’ll typically run the spreadsheet checker first, then feed the validated dataset into the attorney-fee run. That “checker-first” sequence is one of the best ways to avoid long debugging sessions caused by hidden format or mapping issues.

Finally, keep the limitations framing clear in your model: this post uses California’s general default period—2 years under CCP §335.1—and does not rely on claim-type-specific rules because none were provided. If your scenario requires a different rule, update your spreadsheet inputs accordingly before interpreting outputs.

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