How Settlement Allocator rules vary in Kentucky

What varies by jurisdiction

Settlement allocation rules aren’t one-size-fits-all. Even when you use the same DocketMath Settlement Allocator workflow, the jurisdiction-aware rules you apply in Kentucky (US-KY) can change how the class is framed and, as a result, which people are treated as eligible for a settlement share.

For Kentucky, the key starting point is Ky. R. Civ. P. 23, which sets the framework for class actions. Based on the jurisdiction data you provided, no claim-type-specific sub-rule was found for the allocation logic described here. That means this calculator should rely on the general/default period logic in the Rule 23 class-action framework, rather than a special time window carved out for particular claim types.

In practical terms, the most common Kentucky-specific variations show up in:

• Rule 23 class-action framing
  Your Ky. R. Civ. P. 23 process impacts the settlement’s class structure and approval pathway—both of which affect how you translate “class membership” into allocator eligibility.
• Time-period boundaries for “who is in the class”
  If your class definition uses dates or events, those boundaries determine the eligible population count. Change the date/event filter and you change who is eligible, which changes each person’s proportional share.
• Consistency between the numeric allocator and the distribution narrative
  Even if your allocator is purely mathematical, your final distribution approach should be understandable as consistent with what the court approves under Ky. R. Civ. P. 23 and what the certified class covers.

What to verify

Before you click /tools/settlement-allocator, verify inputs and mapping choices so your output aligns with Kentucky’s Ky. R. Civ. P. 23 class-action structure (not generic assumptions).

1) Confirm the settlement is in a Rule 23 class-action setting

DocketMath works best when the settlement you’re allocating is tied to a certified or certifiable class approach. In Kentucky, that expectation connects to Ky. R. Civ. P. 23.

Checklist:

• The matter is being administered as a Ky. R. Civ. P. 23 class action (not an unrelated procedural posture)
• You have a class definition you can translate into allocator eligibility filters

2) Confirm you’re using the general/default eligibility period (no claim-type split)

Because the jurisdiction data indicates no claim-type-specific sub-rule was found, your eligibility time logic should be the general/default Rule 23 period framework.

What to do:

• If you’re considering different eligibility windows for different claim types, pause and verify whether Kentucky’s applicable Rule 23 framework supports that split. If you can’t support it from your source documents, use the general/default period.

3) Validate eligibility criteria against the actual class definition

Settlement allocations depend on “who is in the class.” That means your DocketMath eligibility filters should mirror the class membership criteria used in the settlement record.

Practical mapping questions:

• What date range (or event range) defines class membership for eligibility?
• Do the class criteria include thresholds (e.g., participation thresholds) that you must reflect as filters?
• Are there opt-in/opt-out mechanics or notice-driven features that change who is eligible?

4) Check outputs against the intended distribution logic

Don’t treat the calculator as a black box. Use quick “sanity checks” so the math outcome matches the story you intend to support under Ky. R. Civ. P. 23.

Checks to run:

• If you adjust your eligibility count by a small amount (for example, tightening/loosening the date filter slightly), does the allocation behavior change in a way that still fits your class-definition basis?
• Are you comfortable explaining why the eligible population set drives the per-person proportional shares?

Common pitfall: class-definition mismatch. If the date/event filters don’t align with the class membership criteria, proportional allocations can shift materially—even when the settlement fund and claim totals are correct.

5) Document assumptions for defensibility

Record what you assumed and how you translated the class framework into DocketMath inputs.

Assumption log (simple):

• Settlement type: Ky. R. Civ. P. 23 class action
• Eligibility window used: general/default period logic; no claim-type-specific split
• Class definition source: [internal workpapers / settlement agreement / order cite]
• DocketMath parameter mapping: [which date field/event field became your eligibility filter]

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

Sources and references

• Ky. R. Civ. P. 23, Kentucky Court Rules (browse): https://govt.westlaw.com/kyrules/Browse/Home/Kentucky/KentuckyCourtRules
• TODO: If you are relying on a specific Kentucky settlement approval order or class-definition language, add the exact docket/order citation(s) here to support how you translated eligibility-period boundaries into DocketMath.