Spreadsheet checks before running attorney fee calculations in Florida

What the checker catches

Run this scenario in DocketMath using the Attorney Fee calculator.

Before you run an attorney fee calculation in a Florida matter, you can reduce spreadsheet errors with a quick sanity-check pass. DocketMath’s spreadsheet-checker is built for that moment—when the model “mostly works,” but you want confidence before fee-related totals, multipliers, or in-scope time windows flow into outputs.

Below are the common problem patterns the checker is designed to catch in the specific context of attorney-fee spreadsheets (including timing rules that can determine which invoices or time entries are included).

• Wrong rows / periods included

  • Fee sheets often calculate totals by date range (e.g., “work performed within” a window).
  • A spreadsheet can accidentally pull in entries just outside the range—especially when filters are driven by formula logic rather than simple manual selection.
  • The checker flags date fields and comparisons that don’t match the cutoff logic you selected (including cases where formats are mixed).

• Silent sign errors

  • Spreadsheet logic sometimes treats credits, discounts, or adjustments as positive values, or subtracts them twice.
  • A reliable model should make charges vs. adjustments distinguishable in how they roll up.
  • The checker looks for patterns where totals decrease (or increase) in ways that conflict with your sign conventions—e.g., a “credit” line behaving like an additional charge.

• Unit and rate mismatches

  • A classic spreadsheet bug: hours entered as minutes (or vice versa), or rates applied per minute instead of per hour.
  • The checker helps you verify that:

    • total = hours * rate is computed with consistent units
    • numeric fields didn’t get coerced into text (which can break multiplication or lead to unexpected blanks)

• Date math and time zone / coercion issues

  • Excel/Google Sheets can coerce dates into serial numbers.
  • If a date is stored as text, date comparisons can fail or exclude rows unexpectedly.
  • The checker checks whether date comparisons are behaving consistently across the sheet.

• Category leakage

  • Some spreadsheets separate totals by category (e.g., research, drafting, hearing prep).
  • If a category column is misspelled, or a formula references the wrong column, totals can be wrong even when subtotals appear “reasonable.”
  • The checker verifies that category subtotals roll up cleanly into the expected grand total.

• **Statute-driven “in-scope” assumptions (Florida)

  • Many fee spreadsheets use a time window driven by the general/default SOL.
  • In Florida, the general/default statute of limitations period for claims is 4 years.
  • Statutory reference: Florida Statute § 775.15(2)(d) (general rule). Source: https://www.flsenate.gov/Laws/Statutes/2004/775.15?utm_source=openai
  • Important: No claim-type-specific sub-rule was found here, so treat 4 years as the default period for timing sanity checks—unless your fee claim logic uses a more specific rule.

Gentle reminder: the checker isn’t determining the merits of any fee request. It’s guarding against spreadsheet errors that can create incorrect totals or incorrect “in-scope” time windows before you use the numbers in any filing or negotiation.

A practical “red flag” checklist

Use this checklist before running your attorney-fee calculation in DocketMath:

When to run it

Run the spreadsheet-checker at three specific points. This helps you avoid discovering errors only after fees are already calculated and exported.

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.

1) After importing or pasting data

This is the earliest moment to catch structural issues, such as:

• copied data arriving as text instead of dates/numbers
• shifted columns or changed column order
• missing headers
• inconsistent date formats across rows

If you wait until after formula setup, you may end up diagnosing the wrong layer of the problem (formatting vs. calculations vs. rollups).

2) After you define the date window / “in-scope” logic

Because the Florida general/default SOL is 4 years under § 775.15(2)(d), spreadsheets commonly use it to determine whether time entries fall within a relevant window.

Run the checker after you set:

• window start and end dates
• inclusion/exclusion rules around boundaries
• the logic that converts raw dates into “in-scope” flags

This step helps ensure:

• the date comparisons behave as expected
• the rows included match your intended window

3) Immediately before running attorney-fee calculations

Even a well-built sheet can drift—especially after manual edits. Run it one more time right before invoking attorney-fee to confirm:

• updated totals match refreshed inputs
• last-minute re-categorization didn’t break rollups
• sign conventions still align with how your model calculates fees

Pitfall to avoid: if you only run checks once (right after building the sheet), you can miss later changes—like recategorizing invoices or updating cutoff dates. A final pass reduces that risk.

Try the checker

You can use DocketMath as a two-step pipeline: sanity-check the spreadsheet first, then run the fee calculation.

1. Open DocketMath spreadsheet-checker for your worksheet.
2. Provide the sheet inputs, such as:

   • date of work performed (or invoice date, depending on your model basis)
   • hours/units
   • rate
   • category (if your sheet breaks totals out)
   • any adjustments/credits
3. Review the checker output for:

   • date coercion warnings
   • subtotal-to-total rollup mismatches
   • unit/rate arithmetic inconsistencies
   • negative/abnormal value flags
4. Only after the checker looks clean, run DocketMath attorney-fee using the same inputs.

Input behaviors to watch

Small input-format issues can cause large output changes. Common patterns include:

Florida timing sanity check (default rule)

For spreadsheet “in-scope” windows, use this grounding point:

• General/default SOL period: 4 years
• Statutory reference: Florida Statute § 775.15(2)(d)
• Source: https://www.flsenate.gov/Laws/Statutes/2004/775.15?utm_source=openai

Because no claim-type-specific sub-rule was found in the provided material, treat 4 years as the default period for the spreadsheet’s baseline timing sanity checks unless your specific situation uses a different, more specific rule.

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