Spreadsheet checks before running attorney fee calculations in Connecticut

What the checker catches

Before you run an attorney-fee calculation in a Connecticut case, use a spreadsheet sanity-check to catch the errors that most often survive “formula looks right” reviews. DocketMath’s attorney-fee calculator can handle the math, but the spreadsheet around it still needs guardrails—especially because the most common fee mistakes are structural, not arithmetic.

Here’s what the spreadsheet checker is designed to catch:

• **Wrong time basis (hours vs. days vs. increments)

  • Example: your spreadsheet converts minutes to hours, but the fee table assumes the hours are already converted.
  • Symptom: totals are off by a factor of 60, 6, or 1/8, depending on the conversion path.

• **Rate mismatch (blended vs. per-step rates)

  • Example: you calculate a blended rate per month but also apply a rate tier multiplier again.
  • Symptom: attorney fees jump when you change a single case date—even though the underlying time entries didn’t change.

• Date math drift

  • Example: you compute “days since filing” using calendar days, while another part of the spreadsheet expects business days (or vice versa).
  • Symptom: weekend/holiday rows change the outcome even though the substantive work performed should be unchanged.

• Omitted lines and broken ranges

  • Example: a filter is left on, or a SUM/SUMIFS range excludes the last row of time entries.
  • Symptom: the total hours shown in your output doesn’t equal the sum of the line items you think are included.

• **Double-counting (carryover columns)

  • Example: you add both “time entry amount” and “subtotal amount” into the final total.
  • Symptom: totals increase too quickly when you add a single additional time entry, because the same component is effectively counted twice.

• Blank or text values in numeric fields

  • Example: “1,250” is stored as text due to comma formatting or copy/paste from a PDF.
  • Symptom: spreadsheet totals silently ignore or inconsistently handle those values.

• Unit inconsistencies

  • Example: one worksheet stores hours in decimal form (e.g., 1.5), while another stores hours in HH:MM format.
  • Symptom: fee computations may still run, but rate multiplication won’t reflect the actual time represented by the spreadsheet.

Finally, don’t ignore the timeline logic. In Connecticut, the general statute of limitations period is 3 years under Conn. Gen. Stat. § 52-577a. This is the general/default period; no claim-type-specific sub-rule was found for the purposes of this checklist. In fee spreadsheets, timeline cutoffs often decide which time entries are included—so the checker should verify cutoff dates and inclusion flags.

For quick reference, the general SOL anchor is:

• 3 years (general/default)
• Conn. Gen. Stat. § 52-577a
  Source: https://law.justia.com/codes/connecticut/title-52/chapter-926/section-52-577a/?utm_source=openai

When to run it

Run the checker at three points: before you calculate fees, after you incorporate cutoff logic, and before you share results.

A practical schedule:

• Step 1: Before calculating attorney fees

  • Confirm your spreadsheet’s units:

    • Are hours converted to decimal hours?
    • Are rates stored consistently (e.g., $ / hour)?
  • Confirm that totals reconcile with line-item sums:

    • If the spreadsheet can’t explain why the totals equal the included detail lines, it’s a red flag.

• Step 2: After you apply Connecticut timeline filters

  • If your spreadsheet excludes entries older than the 3-year general/default SOL period under Conn. Gen. Stat. § 52-577a, verify the inclusion test:

    • Are you comparing the correct date fields (entry date vs. event date)?
    • Is the cutoff date computed once and reused consistently across sheets?
    • Does your “include” column handle blank dates predictably (e.g., blank date should not accidentally pass the cutoff test)?

• Step 3: Right before you export results

  • Look for filter leftovers:

    • Sorting/filtering can change what you see without changing underlying formulas.
  • Validate that your SUMIFS/SUMPRODUCT ranges cover the exact same rows as the detail view you’re exporting.

Checklist you can run in under 10 minutes:

Because fee spreadsheets often evolve during drafting and revision, re-run the checker whenever you:

• change the cutoff date,
• update a rate tier table,
• add or remove time entries,
• or copy/paste data from another system.

Try the checker

Use DocketMath’s attorney-fee workflow as a “math backstop,” but treat the spreadsheet checker as your first line of defense for correctness. (This is not legal advice—just a practical QC approach to reduce avoidable spreadsheet errors.)

A simple way to test spreadsheet logic without disrupting your process:

1. Pick 3 representative time entries

   • One clearly included (recent)
   • One near the cutoff boundary (needs careful evaluation)
   • One clearly excluded (older than the cutoff)

2. Run the checker

   • Verify that the included/excluded flags align with the general 3-year period under Conn. Gen. Stat. § 52-577a.

3. Trace how output changes when you tweak one thing

   • Change only one input at a time:

     • Adjust hours by +0.5
     • Swap a rate tier
     • Move a date by 1 day
   • Your fee total should change in a predictable way:

     • If hours change by +0.5 and the rate is unchanged, the fee should shift by +0.5 × rate.

4. Reconcile line-item math

   • Confirm the internal relationships:

     • hours × rate = line amount
     • sum(line amounts) = subtotal
     • subtotal = final total

If you want to do this interactively, start with the tool here:

• Primary CTA: attorney-fee

And if you keep a separate spreadsheet calculator, you can validate outputs against DocketMath after the checker passes by comparing the same inputs through both systems.

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