Common Damages Allocation mistakes in Connecticut

The top mistakes

Damages allocation errors can derail a Connecticut civil claim even when liability facts are solid. Using DocketMath (the damages-allocation calculator), you can catch many mistakes early—especially those that create inconsistent totals, misapplied time periods, or category mix-ups that later become hard to explain in filings.

Below are the most common mistakes we see in Connecticut (US-CT) when people allocate and total damages.

1) Using the wrong Connecticut statute of limitations window

Many allocation workflows accidentally attach an incorrect time horizon to “damages” calculations (e.g., using a 6-year assumption from another state, or using a claim-specific period that doesn’t apply).

In Connecticut, the default general limitations period is 3 years under Conn. Gen. Stat. § 52-577a. DocketMath’s allocation step may ask for dates (or implicitly rely on them), so if you feed an incorrect starting date, your damages window—and therefore the result—will be wrong.

2) Mixing damages categories that belong in separate columns

A frequent allocation failure is treating different kinds of damages as if they roll up the same way. For example:

• Some inputs should be handled as recurring losses over a time window.
• Others should be handled as one-time amounts.
• Some workflows accidentally double-count by adding both “principal loss” and an amount that is already included in the principal.

In DocketMath, keep categories aligned with how the calculator expects them. If the tool is set up to compute totals based on (a) a time-windowed component and (b) a fixed component, but your spreadsheet feeds everything as fixed, the output can look plausible while still being internally inconsistent.

3) Double-counting attorney’s fees or interest

Another common issue is copying values from pleadings or settlement summaries and then re-adding them during allocation. Depending on the structure of your damages-allocation run, it’s easy to:

• Include fees in the “damages” bucket and then also add fees again in a separate “costs” bucket.
• Add interest twice—once as part of a received settlement number and again as an interest calculation input.

DocketMath users should verify whether an input already includes the amount you plan to separately compute.

4) Allocating totals that don’t reconcile to underlying inputs

Even when each input is “about right,” the final totals often fail a basic reconciliation test:

• Sum of allocations ≠ total damages
• Total damages window ≠ computed time period length
• Category subtotals don’t match what the narrative description would support

A simple check in your workflow is to re-sum the categories you entered into DocketMath and confirm they equal the calculator’s reported total (within any rounding rules you apply).

5) Feeding incorrect dates (especially for start/end boundaries)

Date errors are one of the fastest ways to produce wrong allocations:

• Using filing date instead of event date
• Using an end date that includes one extra month of losses
• Reversing start/end dates

Because the Connecticut default limitations period is 3 years (Conn. Gen. Stat. § 52-577a), date boundaries are not just formatting—they determine whether a portion of damages is included in the calculation at all.

6) Treating settlement amounts as automatically “broken into” categories

Settlement figures provided as a single lump sum often hide the allocation terms. If you feed a lump sum into DocketMath as though it represents only one component (e.g., only lost wages, only property loss), you may produce an output that is mathematically consistent but logically misleading relative to how the settlement was structured.

How to avoid them

DocketMath is strongest when you treat damages allocation like a reproducible calculation: define inputs clearly, validate totals, and align timing rules to Connecticut’s general limitations baseline.

Use a written checklist for inputs, document each source, and run a quick sensitivity check before finalizing the result. When two runs differ, compare inputs line by line and re-run with one variable changed at a time.

Step-by-step quality checklist (Connecticut-aware)

Use DocketMath to run your allocation, then validate the following before you rely on the output:

Inputs that commonly change outputs (and how)

When using DocketMath (damages-allocation), the biggest output swings usually come from:

• Time-window boundaries (start/end dates): Changes how much of a recurring damages series you include.
• Category type (recurring vs fixed): Determines whether DocketMath spreads losses across the window or treats them as a single item.
• Whether a figure includes fees/interest: Converts what should be one component into two separate components, inflating totals.

If your DocketMath output is higher or lower than your expectation by a noticeable margin, start by reviewing these three inputs before you adjust anything else.

Practical workflow tip: keep an “allocation memo” alongside the numbers

Before filing or negotiating, attach a one-page internal memo to your worksheet showing:

• the dates used,
• the 3-year baseline reference (Conn. Gen. Stat. § 52-577a),
• and a line-by-line description of what each input represents.

This doesn’t replace legal analysis, but it helps prevent common allocation disputes caused by unclear categorization.

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