Step-by-step

This guide walks you through running Damages Allocation in DocketMath for Connecticut (US-CT). The calculator uses jurisdiction-aware rules based on Conn. Gen. Stat. § 52-572h, which provides the default/general period used for allocation in Connecticut.

Note: A jurisdiction rule for Connecticut was found as a general/default period. No claim-type-specific sub-rule was found, so this guide treats the statute’s general period as the controlling rule for the calculator run.

1) Open the calculator

Go to the primary action link: /tools/damages-allocation
Select Connecticut as the jurisdiction (US-CT) if DocketMath prompts you.

If the interface asks for jurisdiction first, choose US-CT before entering any financial values—this helps ensure the correct period logic is applied.

2) Confirm the statute basis (Connecticut)

DocketMath’s jurisdiction-aware configuration for Connecticut is driven by Conn. Gen. Stat. § 52-572h (default/general period). For context, you can review the statute here:
https://www.cga.ct.gov/current/pub/chap_925.htm#sec_52-572h

In practice, that means your allocation calculation will incorporate the Connecticut default/general period described by the statute. Because no claim-type-specific override was identified for this tool run, the calculator should apply the same general period logic across the scenario (even if your UI includes a claim category setting).

3) Gather the inputs DocketMath needs

Before you type anything, collect the details you’ll use across the form. Depending on the calculator screen, you’ll typically provide:

The damages amount(s) you want to allocate
The time range relevant to the damages (often start/end dates, or equivalent)
Any allocation drivers the tool uses (for example, how damages are segmented if the form supports segmentation)

To reduce rework, keep your dates in the same format throughout your record (for example, YYYY-MM-DD if the tool accepts it).

4) Enter your facts into DocketMath

Work through the calculator left-to-right:

Enter the damages amount (or amounts, if the form supports multiple components).
Enter the relevant dates (start and end) that define the allocation window.
Choose any options the tool provides that affect timing-based allocation (for example, an option like “use statutory period,” if available).

Once you select Connecticut (US-CT), DocketMath applies Conn. Gen. Stat. § 52-572h logic to map your time window to the statute’s general/default period. Because no claim-type-specific sub-rule was found, you should expect the same period logic rather than a different period per claim category.

Gentle reminder: This is guidance for using the tool—not legal advice. If your case involves unusual timing issues, consider getting legal guidance.

5) Review the allocation output and timing breakdown

After you run the calculation, DocketMath will produce allocation results, commonly including:

Allocated totals by segment/period
The effective period span used by the rules (i.e., how your dates map to the statutory period framework)
A summary of how much of the overall damages falls inside vs. outside the period logic

Check these two items carefully:

Does the effective period window reflect your intended start/end dates?
Do the segmented outputs match the structure shown in the UI?

If the tool displays an indicator such as “statutory period used”, confirm that it reflects the Connecticut general/default period associated with § 52-572h.

6) Save your run (and capture key details)

Once the inputs and outputs look right:

Save the calculation result in DocketMath (if your workflow supports saving).
Capture the key inputs and the period summary so you can reproduce the run later—especially if you plan to adjust dates or run scenarios.

This helps you compare versions consistently and avoid accidental drift in assumptions.

Common pitfalls

Damages Allocation runs often go wrong due to date mismatches, incomplete segmentation, or incorrect assumptions about which Connecticut period logic applies.

Assuming a claim-type-specific Connecticut sub-rule exists in the tool
For this Connecticut setup, DocketMath applies Conn. Gen. Stat. § 52-572h as a general/default period. No claim-type-specific sub-rule was found, so the calculator uses the general logic rather than a different period for each claim category.
Using inconsistent date formats
If one date is entered differently (or you paste dates from multiple sources), you can shift where the statutory period mapping “lands.” Convert dates first and then enter them consistently.
Entering a total damages figure when the tool expects segmentation
If DocketMath expects multiple damages components (for example, different phases or event dates), inputting a single combined number may reduce accuracy. Use the tool’s supported structure when possible.
Misreading what the “period used” means
When the output shows an effective or statutory period span, treat it as the tool’s computed mapping of your provided date range to the Connecticut rule. Allocation weights depend on that mapping.
Changing jurisdiction or options after entering inputs
If your UI lets you switch between jurisdictions or toggle timing options, confirm the selection before entering values. Switching afterward can alter how the period logic is applied.

Warning: Don’t rely only on the allocation totals. Always verify the computed time mapping—an incorrect period window can systematically misallocate amounts across every segment.

Try it

Use this quick sanity-check approach to validate your Connecticut run in DocketMath:

Open /tools/damages-allocation
Set jurisdiction = Connecticut (US-CT)
Enter your damages and date range
Confirm the tool indicates the Connecticut mapping tied to Conn. Gen. Stat. § 52-572h
Quickly check whether the output’s allocated totals “feel” consistent with time (even at a rough level)

Then do a controlled variation:

Keep the damages amount the same.
Shift only the start date by a small increment (if your facts allow).
Re-run and observe:
- whether segment boundaries change
- whether allocated totals inside the period move accordingly

If a tiny start-date tweak causes a large allocation swing, revisit your date inputs and ensure the calculator is interpreting the intended time window.

Finally, document what you entered:

the exact start/end dates used
whether damages were treated as a single component or multiple components
the scenario/settings you selected in the DocketMath UI

This makes your run reproducible and easier to explain when comparing scenarios.

How to run Damages Allocation in DocketMath for Connecticut