Inputs you need for Damages Allocation in Connecticut

Inputs you will need

Run this scenario in DocketMath using the Damages Allocation calculator.

To allocate damages in a Connecticut matter with DocketMath, you’ll need a focused set of inputs that lets the tool (1) determine what portion of damages falls inside Connecticut’s limitations period and (2) allocate the remaining amounts across your chosen buckets (time, parties, or other dimensions). Even when case facts vary, the workflow is consistent: you provide the dates that control the “lookback” and the totals/weights that control the split.

Before you run /tools/damages-allocation, gather the following.

1) Case timing dates (controls the lookback window)

Why this matters in Connecticut: the default general statute of limitations is 3 years under Conn. Gen. Stat. § 52-577a. DocketMath uses the dates you enter to determine the portion of damages that are within that period.

2) Damages categories (controls the allocation buckets)

You’ll typically model damages in one or more buckets (you can match your demand/schedule to how DocketMath is set up).

If your spreadsheet or demand already lists totals by category, you can usually transfer those totals directly into DocketMath.

3) Allocation dimensions (controls how the model splits amounts)

Choose the dimension that matches how your case team wants to allocate damages:

4) Attribution/weights (controls the math when splitting)

Depending on your allocation mode, you’ll need one of the following:

• If allocating by responsibility:
• If allocating by time or distribution methodology:

If your internal model uses caps or exclusions, add those cap-related inputs too—DocketMath will still show what’s impacted based on what you provide.

5) Evidence-based numbers (controls credibility and repeatability)

To keep the allocation auditable and easy to re-check:

Gentle reminder: DocketMath supports calculations and repeatable modeling, but it does not replace legal judgment, factual investigation, or compliance with your filing strategy.

Where to find each input

Use the mapping below to quickly locate the data you’ll need.

Most inputs live in the case file, contracts, or docket entries. Dates usually come from the triggering event notice; rates and caps come from governing documents or statute; and amounts come from the ledger or judgment. Record the source for each value so the run is reproducible.

Dates

• Incident/accrual date: allegations in the complaint, incident report, contract kickoff date, or the “harm start” date used in your earliest filings
• Filing date: the docket entry reflecting when the complaint was filed
• Period end dates: your damages schedule and accounting reports (e.g., month-by-month or quarter-by-quarter harm totals)

Damages totals and category splits

• Damages schedule / demand letter exhibits: often contain the clearest category totals
• Accounting and payroll documentation: commonly used for economic damages and time-sliced totals
• Medical or treatment summaries (if used in your model): may support non-economic or future-related modeling, if your approach uses them
• Settlement communications (if used): sometimes contain agreed buckets that you can mirror for modeling consistency

Allocation shares/weights

• Internal responsibility memo or apportionment draft: where responsibility percentages were computed
• Time-based harm methodology: how you distributed harm across months/quarters/events
• Prior drafts: if DocketMath is replacing an older model, reuse the same weights so your results remain comparable

Run it

After you’ve assembled the inputs above, run DocketMath at /tools/damages-allocation.

Enter the inputs in DocketMath and run the Damages Allocation calculation to generate a clean breakdown: Run the calculator.

When rules change, rerun the calculation with updated inputs and store the revision in the matter record.

Suggested run sequence (keeps results stable)

1. Enter key dates first: incident/accrual date and filing date.
2. Add your damages buckets: input category totals (economic, non-economic, or other buckets you’ve selected).
3. Select your allocation mode:

   • Time period (common when totals are monthly/quarterly), or
   • Party share, or
   • Claim line-item buckets (only if already consolidated)
4. Enter weights/shares so the model can distribute totals correctly.
5. Review the output and confirm reconciliation:

   • The portion of damages within the 3-year default window reflects what you intended under Conn. Gen. Stat. § 52-577a.
   • Your allocated totals reconcile with your starting category totals (or your model explicitly explains any adjustments).

What Connecticut’s default limitations rule changes

Because the general limitations period is 3 years under Conn. Gen. Stat. § 52-577a, your DocketMath output should reflect a lookback window running back 3 years from the filing date, based on how you define your accrual/incident date in the inputs.

Practical caution: If your accrual date is earlier (or later) than the harm timing you believe controls, DocketMath may exclude (or include) more damages than you intended. Align your accrual logic with how the record describes the harm you’re modeling.

Quick sanity checks (before you rely on the numbers)

For Connecticut, this is especially important because the limitations “included vs. excluded” portion is date-driven—small date mismatches can change the included damages.

Related reading

• Damages Allocation Guide for Alabama — Comparative Fault Rules
• Damages Allocation Guide for Alaska — Comparative Fault Rules
• Damages Allocation Guide for American Samoa — Comparative Fault Rules