Inputs you need for attorney fee calculations in Connecticut

Inputs you will need

If you’re running an attorney fee calculation in Connecticut using DocketMath (Calculator: attorney-fee), collecting the right inputs up front helps you produce outputs you can reconcile to your billing records.

For timeliness context in Connecticut, it’s often important to understand the governing limitations period you’re modeling. Connecticut generally provides a 3-year period for certain attorney-related claims under Conn. Gen. Stat. § 52-577a. Important: this is the general/default period—no claim-type-specific sub-rule was found in the brief you provided—so only treat it as a baseline unless your specific scenario identifies a different rule.

Here’s a practical checklist of the inputs you typically need for attorney-fee calculations in DocketMath. Use it to confirm you have enough facts to model fees cleanly.

• Example categories: fee petition, post-judgment fee request, or contractual/fee-shifting context.

• Why it matters: it affects how you structure and explain the fee story (what you’re asking for and what you’re including).

• Format: Month Day, Year (or exact date).

• Why it matters: helps you align billing records and define the timing window you want DocketMath to analyze.

• Example: “through March 15, 2026.”

• Why it matters: determines the end point for your calculation assumptions and any timing/timeliness context you model.

• Why it matters: DocketMath can’t compute what you don’t separate—especially when time entries and fixed amounts are mixed.

• Provide at least one rate; multiple rates are common (partner vs. associate vs. paralegal).

• Why it matters: outputs change with rate inputs. If rates vary by timekeeper role (or time period), you’ll generally want to model them consistently.

• Usually you’ll enter totals or line-item quantities (depending on how you collect your records).

• Why it matters: this is typically the core driver of the fee calculation.

• Example: attorney, partner, associate, paralegal.

• Why it matters: roles are how you keep rate-by-role calculations auditable.

• Why it matters: some models separate “fees” from “costs.” Decide which buckets you want included in your output.

• If you have them, capture both amount and date.

• Why it matters: supports tighter documentation and better alignment with any “through” date you’re using.

• If you’re calculating “net amount due” instead of “total incurred,” you’ll need payments.

• Why it matters: outputs can change from gross to net depending on what you subtract.

Disclaimer / not legal advice: This checklist is for planning and workflow. It’s not legal advice, and it may not cover every fact pattern. For timeliness, Conn. Gen. Stat. § 52-577a is a 3-year general/default baseline (as provided), but your specific case could require a different analysis.

Where to find each input

Collecting inputs is easiest when you know which document usually contains each field. Use this mapping as you gather materials for DocketMath.

• Start date

  • Source: engagement letter, substitution of counsel, or first billing invoice header.

• Relevant “as of” date

  • Source: the date you intend the calculation to cover (e.g., filing date for a fee motion, judgment date, or a defined cutoff in your spreadsheet).

• Billing period structure + time entries

  • Source: itemized invoices, billing summaries, or timekeeping exports.
  • Tip: look for columns like “Date,” “Task/Description,” “Hours,” “Rate,” and “Timekeeper.”

• Hourly rates + timekeeper roles

  • Source: engagement letter or invoice line items.
  • Tip: if your invoices show a blended rate, capture the exact “rate used” number so your DocketMath entry matches.

• **Hours billed (or subset to include)

  • Source: invoice totals you plan to claim, or line items you’ll include/exclude.
  • Tip: if you’re excluding certain entries, keep the excluded totals in a separate list so your audit trail stays intact.

• Expenses and amounts

  • Source: expense line items on invoices (often labeled: “costs,” “expenses,” “out-of-pocket,” or similar).

• Payments already made

  • Source: client ledger, trust account statements, or invoice “paid” status summaries.

• **Timeliness tracking (if you choose to model it)

  • Connecticut baseline reference: Conn. Gen. Stat. § 52-577a provides a 3-year general/default limitations period for relevant claims (per the brief’s data).
  • Practical use: model your time windows using your start date and “as of” date, but avoid assuming this statute perfectly matches every scenario without a case-specific check.

Run it

Once you have the inputs, run your Connecticut attorney-fee calculation in DocketMath using /tools/attorney-fee.

1. Open /tools/attorney-fee.
2. Enter the matter timing inputs:

   • representation start date
   • your “as of” cutoff (or filing/analysis date)
3. Add billing inputs:

   • timekeeper roles and hourly rates
   • hours billed (or totals per timekeeper, depending on how your data is prepared)
4. Add expense inputs (if included):

   • expense amounts (and dates, if you track them)
5. Choose your calculation perspective:

   • gross fees (total incurred) vs. net amount due
   • include payments already made if you want an outstanding balance
6. Review outputs for:

   • total fees (and total expenses, if applicable)
   • any computed time spans you selected (helpful for documentation and consistency checks)

To keep results defensible and easier to reconcile, align your DocketMath run with how your invoices are structured. For example, if your invoices separate partner vs. associate time, enter those separately rather than blending them into one rate—your output will typically be easier to explain later.

Pitfall to avoid: If you enter a single “total hours” number but your records reflect multiple rates/timekeepers, the result may look reasonable but be difficult to reconcile. Keep rate-by-role inputs consistent with your underlying billing.

For timeliness context during your workflow, use the 3-year general default from Conn. Gen. Stat. § 52-577a as your baseline assumption. This is a general/default period, not a claim-type-specific rule (based on the provided brief note). If your scenario indicates a different rule, you may need to adjust your date inputs and assumptions accordingly.

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