Common attorney fee calculations mistakes in Connecticut

5 min read

Published April 15, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

The top mistakes

Run this scenario in DocketMath using the Attorney Fee calculator.

Running attorney fee calculations in Connecticut is usually less about math and more about choosing the right legal inputs. The DocketMath attorney-fee calculator can help you systematize those inputs, but common mistakes still slip into spreadsheets and fee models.

Here are the biggest pitfalls we see when teams calculate attorney fees and related amounts in Connecticut (US-CT):

Using the wrong statute of limitations period
- Connecticut’s default general statute of limitations is 3 years, governed by Conn. Gen. Stat. § 52-577a.
- Many fee models accidentally assume a longer period (or import another jurisdiction’s time limit), which can affect what work is included or how claims are staged in the calculation.
- Key point: No claim-type-specific sub-rule was found for this default period in the materials used here. Treat § 52-577a’s 3-year rule as the general/default period unless you have a separate, clearly identified basis for a different limitations period.
Double-counting costs vs. fees
- A frequent modeling error is treating “expenses” as if they were “attorney fees,” or adding costs twice—once in an “itemized costs” line and again inside a blended rate.
- This can inflate totals and create reconciliation mismatches when you later compare to invoices, time entries, or a fee agreement.
Using the wrong billing rate assumptions
- Teams sometimes mix:
  
  an hourly rate from engagement letters,
  
  an effective blended rate after staffing changes,
  
  and an opposing party’s claimed rate from a different case stage.
- The output changes dramatically if you calculate fees as:
  
  hours × rate vs.
  
  hours × blended rate vs.
  
  hours × rate subject to partial reduction rules (even when you don’t apply reductions, rate selection alone matters).
Failing to normalize time entries
- If some entries are stored in “minutes” and others in “decimal hours,” your totals can drift.
- Another version: lumping all “trial time” into “prep time,” which can make later reasonableness checks harder because your categories no longer match how the work was performed.
Incorrect sequencing of work vs. limitations cutoffs
- If you’re limiting which hours you include based on timing, your date logic needs to be consistent:
  
  work start date vs. invoice date vs. billing date.
- When the cutoff is tied to a 3-year limitations framework under § 52-577a, inconsistent date choice changes the included hour count.
Forgetting task-level exclusions
- Many teams compute totals without tagging work type (drafting, research, court appearances, administrative coordination).
- Even if you don’t apply exclusions in the DocketMath model today, missing tags can prevent you from running accurate “what-if” scenarios later.

Pitfall to watch: If you set DocketMath to calculate fees using an all-in “hourly rate” that already includes overhead, and then you also add overhead as a separate percentage, you can unintentionally double-count. Decide whether overhead is inside the rate or added on top—then keep that choice consistent across every line item.

How to avoid them

You can reduce calculation errors quickly by tightening your inputs, documenting assumptions, and using the calculator outputs as a reconciliation tool—not just a final number. If you’re modeling fees, start with DocketMath’s attorney-fee tool here: /tools/attorney-fee.

1. Lock the timing rule up front (Connecticut default)

Start your model by writing down the date logic and the legal basis that drives it.

Connecticut default general limitations period: 3 years
Authority: Conn. Gen. Stat. § 52-577a
https://law.justia.com/codes/connecticut/title-52/chapter-926/section-52-577a/?utm_source=openai

Because no claim-type-specific sub-rule was identified in the materials provided, you should treat § 52-577a as the general/default period. Then implement a single cutoff rule in your spreadsheet—and mirror it in your DocketMath inputs.

Checklist (timing):

2. Separate “fees” from “costs” in the model

Use a structure that matches how records are organized so your totals can be traced back to source data.

A practical setup:

Time entries → attorney hours → attorney fees
Expenses → filing fees, service fees, travel, etc. → costs (if applicable)

Then in your final review, confirm that your totals are the sum of the correct components.

Checklist (categories):

3. Choose exactly one rate strategy

In DocketMath, consistency matters. Decide whether your model uses:

Standard hourly rate (one rate per timekeeper),
Blended rate (one averaged rate across multiple roles), or
Rate per period (different rates for different date ranges)

Then keep that approach uniform across the dataset.

Rate sanity checks:

Compare total calculated fees against an invoice total for one representative week.
Confirm that rate changes reflect actual staffing transitions rather than spreadsheet edits.

Checklist (rates):

4. Normalize time entries before calculating

Before you run DocketMath:

Convert all entries into the same unit (e.g., decimal hours).
Store a consistent “work date” field if you’ll apply the 3-year window.

Quick conversion rule of thumb:

30 minutes = 0.5 hours
15 minutes = 0.25 hours
45 minutes = 0.75 hours

Even small unit inconsistencies can compound across dozens (or hundreds) of entries.

5. Reconcile with “what-if” scenarios

Use DocketMath to run quick comparisons that reveal hidden modeling issues.

Examples:

What happens if you include only entries within the 3-year window?
What happens if you switch from blended rate to role-specific rates?
What happens if you exclude a category of non-legal administrative time?

If a small input tweak produces a massive output swing, that’s a signal to review the underlying unit/rate/category settings.

Note (general guidance, not legal advice): Modeling defaults and cutoff decisions can vary based on case facts. Use this as a calculation aid, and confirm assumptions with qualified counsel or your organization’s policies where appropriate.