How to run Settlement Allocator in DocketMath for Connecticut

Step-by-step

This guide walks you through running Settlement Allocator in DocketMath for Connecticut (US-CT) using jurisdiction-aware rules.

In Connecticut, class actions are governed primarily by Connecticut Practice Book §§ 9-7 to 9-9, which substantially mirror Federal Rule of Civil Procedure 23. Separately, Conn. Gen. Stat. § 52-105 is a short, one-line statute authorizing representative actions where the parties are numerous.

1) Start the tool from DocketMath

• Open the tool at: /tools/settlement-allocator
• Select Connecticut (US-CT) if your interface prompts you for jurisdiction.
• Choose the allocator mode that matches your workflow—typically the Settlement Allocator calculator itself (not a separate reporting/export tool).

2) Confirm the allocator’s timeline rule set (Connecticut)

When you run in Connecticut (US-CT) mode, DocketMath applies logic aligned with:

• Conn. Practice Book §§ 9-7 to 9-9 (class action procedures), and
• Conn. Gen. Stat. § 52-105 (representative action authorization).

Because the Connecticut provisions mirror the structure of FRCP 23, your inputs generally need to align with the underlying allocation concepts—especially:

• who is included/eligible,
• the weight/measure used to distribute the settlement, and
• the relevant period used by the default/general period rule set.

3) Enter the required inputs

Field names can vary slightly depending on the DocketMath UI version, but the Settlement Allocator inputs typically fall into these categories. Enter them carefully and consistently with your settlement terms.

A) Settlement terms basics

• Total settlement amount (the fund you want to allocate)
• Any fees/costs set aside (if the tool asks whether your amount is net to class vs gross)

B) Class weighting inputs (who receives)

• Class member identifiers (or simply the number of claimants, depending on the UI)
• Each member’s weighting factor (commonly based on claim size, loss amount, or another configured weighting data type)

Tip: Weighting is where results tend to diverge most often—ensure your member weights match the settlement’s described method.

C) Eligibility / lookback period inputs (when it matters)

Connecticut’s allocator logic follows the general/default period in Conn. Practice Book §§ 9-7 to 9-9, not claim-type-specific timing rules.

Provide:

• Start date for the relevant/default period
• End date for the relevant/default period

If the UI asks for a single “relevant period” rather than separate dates, enter it in the exact format the tool requests.

D) Allocation method settings

DocketMath may offer toggles such as:

• proportional allocation by weight
• capped weighting (only if your settlement uses a per-member cap)
• rounding rules (e.g., nearest dollar vs truncation)

Set these according to how your settlement administrator (or agreement) expects the allocation to be modeled.

4) Run the calculation

• Click Calculate (or the equivalent button).
• Review key outputs:

  • Total allocated amount
  • Per-class-member allocation
  • Any unallocated remainder due to rounding, caps, or excluded members

5) Validate outputs against your expectations

Before exporting or sharing:

1. Sum check: confirm the allocations total equals (or closely matches) your total settlement amount minus any set-asides the tool is configured to apply.
2. Eligibility check: confirm excluded or ineligible entries appear as $0 allocations or are removed entirely (the behavior depends on the tool configuration).
3. Period check: verify that members with dates outside the relevant default/general period are treated consistently with the Connecticut mode’s approach under Conn. Practice Book §§ 9-7 to 9-9.

Common “validation clues”:

6) Export or share results

If your workflow requires it:

• Export to CSV/PDF if available in the UI.
• Record internally:

  • jurisdiction = US-CT
  • the start/end dates you entered for the relevant period
  • allocation method settings (caps, rounding, and net/gross convention)

This documentation helps reconcile differences if counsel, the administrator, or the court later questions allocation shifts.

Common pitfalls

These are the most frequent causes of unexpected Settlement Allocator results when running Connecticut (US-CT).

1) Mixing up “default/general period” with claim-type-specific timing

Connecticut mode is built around Conn. Practice Book §§ 9-7 to 9-9 and uses a default/general period approach. Based on the available information, there is no claim-type-specific sub-rule to apply.

Checklist:

• I did not try to apply different eligibility periods by claim type in the tool
• I entered one relevant/default period consistent with the settlement’s terms

2) Mis-entering settlement amount (gross vs net)

Even if the allocator is correct, inconsistent inputs can break reconciliation.

Checklist:

• I entered the settlement amount in the format the tool expects
• I matched the fees/costs configuration to my settlement documents

3) Date boundary errors

When eligibility depends on dates, small date mistakes can have outsized effects.

Checklist:

• Start/end dates match the same calendar interpretation used in the eligibility records
• End date is not accidentally set before some member’s qualifying event date
• I avoided “off-by-one” mistakes on the boundary dates

4) Caps and rounding not aligned with the settlement

If your settlement uses caps, rounding, or special remainder rules, you must mirror them in DocketMath settings.

Checklist:

• Per-member caps are enabled only if the settlement has them
• Rounding direction matches the settlement (e.g., nearest dollar vs truncation)

Pitfall: Caps can cause “total allocated” to stop matching the fund you expected because the tool may either (a) leave a remainder, (b) redistribute it, or (c) report it as unallocated depending on settings.

5) Using weight values in incompatible units

If weighting depends on dollar loss vs percentage share vs other measures, the allocator needs consistent units across all class members.

Checklist:

• All weighting inputs use the same basis across members
• I didn’t mix raw losses with already-normalized weights

Try it

To run a Connecticut allocation quickly:

1. Open /tools/settlement-allocator
2. Select Connecticut (US-CT)
3. Enter:

   • total settlement amount (and the tool’s required net/gross convention)
   • relevant period start date and end date (single default/general period)
   • each class member’s weighting input(s)
   • allocation settings (caps/rounding if used)
4. Click Calculate
5. Review:

   • total allocated vs expected net
   • any $0 allocations and whether they align with the relevant period/eligibility logic

Immediate sanity checks:

• Change the end date by 1 day—allocations for members near the boundary should shift accordingly.
• Expand the relevant period to cover all member dates—if eligibility is purely period-based, fewer members should drop to $0.
• If the tool allows it, temporarily disable caps to see whether allocations increase for previously capped members (use this only as a diagnostic).

When validating against an administrator report, reconcile:

• totals (net vs gross),
• excluded counts,
• and remainder/rounding handling.

Related reading

• How to calculate Settlement Allocator in Ohio — Full how-to guide with jurisdiction-specific rules
• How to calculate Settlement Allocator in Philippines — Full how-to guide with jurisdiction-specific rules
• Worked example: Settlement Allocator in Philippines — Worked example with real statute citations