How to run Settlement Allocator in DocketMath for Kentucky

Step-by-step

Use DocketMath’s Settlement Allocator to apportion a settlement across multiple parties and claims in a way that follows Kentucky’s civil procedure framework for class actions. This guide explains how to run the calculator for Kentucky (US-KY) and how to interpret the output.

1) Open the Settlement Allocator in DocketMath

1. Start at the primary tool link: /tools/settlement-allocator
2. In the calculator, set Jurisdiction: Kentucky (US-KY).
3. Confirm you’re using the Settlement Allocator calculator (not a different DocketMath tool).

2) Gather the inputs the allocator needs

Before you enter anything, collect the items that control how the total settlement is distributed. Exact labels can vary by UI version, but the core concepts are the same:

• Settlement total amount: the gross settlement figure you want to allocate.
• Allocation drivers: the factor(s) that map a settlement value to each party (commonly parties, categories/buckets, or other weighting inputs).
• Parties: who receives an allocation (e.g., individual plaintiffs/claimants, groups of class members, or other distribution groups).
• Any distribution constraints in the settlement agreement: for example, caps, exclusions, or limits on who can receive what.

If your settlement uses multiple “buckets” (such as Category A/B, or Claim Bucket 1/2), plan how each bucket maps to parties and what weight each party (or bucket) gets.

3) Enter party data and allocation weights

On the Settlement Allocator screen:

1. Add each party (or each party-bucket grouping) you want to allocate to.
2. Enter weights (or the equivalent allocation inputs) for each party/bucket.

How this changes outputs:

• A higher weight means a larger share of the settlement total.
• If you add parties or buckets without changing the total weights, each existing party’s share may shrink proportionally.

Quick sanity checks while entering data:

• Do the weights sum to what the tool expects (often 1.00 or 100%)?
• Are you including all parties the settlement agreement says are eligible for distribution?
• Are the categories/buckets aligned with the agreement’s distribution plan?

4) Apply Kentucky-specific structure (Rule 23 framework)

For Kentucky, the key procedural framework that the tool applies in this context is Ky. R. Civ. P. 23, which governs class actions.

In this Kentucky implementation:

• Ky. R. Civ. P. 23 is used as the governing/default procedural framework.
• No claim-type-specific sub-rule was found. That means the allocator should use the general/default Rule 23 period rather than changing behavior based on claim type.

Practical meaning for your run:

• If your situation involves a Rule 23 class posture (e.g., a certified class settlement), the tool should reflect that class-action framework in its handling/assumptions.
• If your situation is not a Rule 23 class action, you can still use the tool for allocation math, but you should not assume additional Rule 23-specific timing/notice elements apply unless your facts make them applicable.

5) Run the calculation

1. Click Calculate (or the equivalent button).
2. Review the outputs carefully:

   • Per-party allocated amount
   • Percentage shares (if shown)
   • Any intermediate breakdowns (such as bucket-level allocations, if the tool supports them)

6) Validate the results with a reconciliation checklist

Before you export, copy values, or use the numbers in a settlement workflow, reconcile the output against your inputs:

• Settlement total reconciliation: Do the allocated amounts add up to the settlement total (allowing for rounding)?
• Weight reconciliation: Do party shares reflect the relative weights you entered?
• Class action relevance: Does your case actually involve a Rule 23 class settlement posture?
• Agreement alignment: Do your entered parties/buckets match the settlement agreement’s distribution formula and eligible recipients?

Common mistake to avoid:

• Entering party weights that reflect negotiation priorities rather than the distribution formula in the settlement agreement. DocketMath can only allocate using the structure and weights you provide—if the agreement uses a different method, the output won’t match it.

7) Export or save for recordkeeping

If the tool supports export or reporting:

• Export the allocation as a report (PDF/CSV, depending on the UI).
• Save the key inputs so you can recreate the run later:

  • Settlement total
  • Party list
  • Weight/bucket structure
  • Jurisdiction selection (US-KY)
  • Any run settings visible in the tool

This helps maintain an audit trail if the parties later request clarification or if you need to rerun with revised numbers.

Common pitfalls

Kentucky (US-KY) runs with DocketMath Settlement Allocator typically fail or mislead in these areas:

1. Assuming claim-type-specific Rule 23 timing/periods exist

   • In this Kentucky guidance, no claim-type-specific sub-rule was found, so the allocator should use the general/default Rule 23 period.
   • If you see behavior that seems claim-type-dependent, double-check that you are not accidentally entering claim-type fields into the wrong bucket/category inputs.

2. Inconsistent party mapping

   • Example: You allocate to “Claimants Group A” in the tool, but the settlement distributes to “Named Plaintiffs” and “Class Members.”
   • Fix: Align the DocketMath party/bucket structure to the actual distribution recipients and groupings described in your settlement agreement.

3. Weights don’t match the tool’s expected format

   • Some tools require weights to sum to 1.00 or 100%.
   • Fix: Verify the sum and the numeric format the tool expects before calculating.

4. Ignoring rounding differences

   • Even when everything is correct, dollar amounts may differ by a small residual due to rounding.
   • Fix: Treat reconciliation as part of the workflow and document any tiny differences shown in export.

5. Running with the wrong jurisdiction

   • Jurisdiction selection can change how the tool applies jurisdiction-aware assumptions/framework logic.
   • Fix: Confirm Kentucky (US-KY) is selected before calculating.

6. Using the math tool without checking the procedural posture

   • If your matter truly involves a class settlement, there may be court approvals or additional procedural steps beyond allocation.
   • Fix: Use DocketMath for allocation mechanics, but verify compliance with any applicable court requirements separately.

Try it

Here’s a quick, low-risk test run you can do in DocketMath for Kentucky (US-KY).

Suggested test run

• Settlement total: $100,000
• Parties (3 buckets): Party A, Party B, Party C
• Weights:

  • Party A: 0.50
  • Party B: 0.30
  • Party C: 0.20

What to expect

After running with Jurisdiction = Kentucky (US-KY):

• Party A should receive $50,000
• Party B should receive $30,000
• Party C should receive $20,000

If the tool shows percentages, they should correspond to your weight inputs.

Change one input to see the effect

Update only one value:

• Change Party B’s weight from 0.30 to 0.40 (and keep the others the same if the tool accepts it, or re-normalize if it requires weights to sum)

What you should observe:

• Party B’s allocated amount increases
• Party A and/or Party C’s allocation decreases depending on whether the tool auto-normalizes weights

Kentucky Rule 23 context check

This Kentucky setup uses Ky. R. Civ. P. 23 as the class-action procedural framework. Because no claim-type-specific sub-rule was found, the calculator should rely on the general/default Rule 23 period rather than splitting behavior by claim category.

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