How to run Settlement Allocator in DocketMath for Connecticut

Step-by-step

Run this scenario in DocketMath using the Settlement Allocator calculator.

Below is a practical walkthrough for running Settlement Allocator in DocketMath for Connecticut (US-CT), using jurisdiction-aware rules and Connecticut’s general statute of limitations framework.

1) Open the tool

1. Go to /tools/settlement-allocator.
2. Confirm you’re using the Connecticut jurisdiction option (jurisdiction code US-CT).

2) Enter the settlement math inputs

DocketMath’s Settlement Allocator is designed to take your settlement totals and allocate them across the categories you select within the tool (for example, amounts tied to different damage components or payment structures). Use inputs that match how your settlement agreement breaks out consideration.

Use this checklist as you fill in the form:

If you don’t have category amounts from the settlement terms, use the tool’s allocation approach that fits your intended scenario (for example, “allocate based on supplied weights” versus “use defaults”). DocketMath will show how changing your weights or category assumptions changes the output splits.

3) Confirm the statute of limitations basis used by the tool

For Connecticut, the tool uses the general/default statute of limitations period unless you provide claim-specific sub-rules in the UI (or unless the tool’s Connecticut ruleset identifies a more specific limitations period you’ve selected).

Connecticut’s general SOL period is:

• 3 years under Conn. Gen. Stat. § 52-577a (general statute of limitations for certain actions)

In this workflow, no claim-type-specific sub-rule was found, so DocketMath uses the general/default 3-year period tied to Conn. Gen. Stat. § 52-577a. Put simply: unless the tool offers a more specific option for your specific claim type, the calculator will default to the general 3-year window.

4) Provide timing details needed for allocation impact

Settlement allocation can change based on when alleged conduct occurred and when claims accrued or were filed. Enter any dates DocketMath requests that affect SOL timing, such as:

Once entered, DocketMath applies the 3-year general SOL window from Conn. Gen. Stat. § 52-577a as part of its jurisdiction-aware logic. The key output you’ll want to watch is whether the tool flags timing as potentially within versus outside the applicable limitations window under the general period.

5) Review the outputs and how they respond to your inputs

After running the calculator, review both the financial allocations and the timing/SOL effects:

1. Check the allocation breakdown (by category/component as configured).
2. Look for any timeliness/SOL-related impacts shown in the results (for example, how allocations adjust when parts of the settlement correspond to time periods the tool treats as within versus outside the general 3-year SOL window).
3. If the results seem off, change one input at a time—especially:

   • the event dates (start/end),
   • the filing date,
   • and any allocation weights you entered.

Practical tip: if the settlement categories remain the same but the SOL-related flags change, your date inputs are likely driving the adjustment behavior.

6) Export or copy the result for your workflow

Use the tool’s output controls (copy/export) to save:

• the settlement allocation totals,
• the category-level figures,
• and any SOL-related flags or summaries produced by DocketMath.

Keep a copy of your entered dates and assumptions for auditability—especially because SOL-based logic depends heavily on accurate event timing.

Common pitfalls

Avoid these frequent issues when running Settlement Allocator for Connecticut (US-CT):

• Using the wrong jurisdiction setting

  • If DocketMath isn’t actually set to US-CT, the calculator may apply a different limitations period and produce a misleading allocation effect.

• Assuming claim-type-specific SOL rules are embedded

  • For this workflow, no claim-type-specific sub-rule was found, so DocketMath uses the general/default 3-year period from Conn. Gen. Stat. § 52-577a.
  • If your matter involves a claim type with a different limitations period (or an exception that applies), the calculator may not reflect that nuance.

• Entering event dates without a defensible basis

  • SOL logic can flip allocations when a date crosses the boundary of a 3-year window.
  • Use dates that match the factual timeline you intend the allocation to model.

• Misreading results that display “within/outside”

  • Some tools show SOL flags while allocations remain informational; others adjust allocation amounts based on timeliness.
  • Confirm how DocketMath uses the SOL determination: whether it’s informational or a driver of the allocation totals.

• Providing incomplete dates

  • If you provide partial dates (for example, only year or only month) and DocketMath treats missing detail as a default, the SOL timing classification can shift.
  • Prefer full dates when the UI allows.

• Not aligning settlement categories with the inputs

  • If your settlement agreement breaks payment into specific components, your entered categories should match those components closely.
  • If you’re using weights/assumptions, document the basis so the allocation is explainable.

Try it

If you want a quick way to validate your setup, run a “sanity test” scenario:

• Set your jurisdiction to US-CT.
• Enter a reasonable settlement total.
• Provide a timing range for alleged events that places part of the timeline within a 3-year window and part outside it (using the 3-year general SOL period from Conn. Gen. Stat. § 52-577a).
• Keep allocation weights the same between runs.
• Then adjust only the event dates by about 1–3 months across the suspected boundary and rerun.

What to look for in DocketMath outputs:

• Do the SOL/timeliness flags change as expected after the date shift?
• Does the allocation breakdown move in the direction you expect based on the tool’s SOL-driven logic?
• Are the category totals consistent with the settlement total you entered?

If the outputs don’t react when you change timing inputs, revisit:

• the date fields you filled,
• whether the tool is actually using the Connecticut rule set,
• and whether your inputs are being interpreted as you intend.

You can access the calculator directly here: /tools/settlement-allocator.

Related reading

• Settlement Allocator Guide for Alabama
• Settlement Allocator Guide for Arizona
• Settlement Allocator Guide for Colorado