How to run Settlement Allocator in DocketMath for West Virginia
7 min read
Published June 4, 2026 • By DocketMath Team
Step-by-step
This guide walks you through running Settlement Allocator in DocketMath for West Virginia (US-WV) using jurisdiction-aware rules aligned to W. Va. R. Civ. P. 23. You’ll set up the inputs, run the allocation calculation, and sanity-check the output against the Rule 23 default period guidance.
Note: This walkthrough explains how to use the tool and apply the West Virginia Rule 23 period rule inside the allocator logic. It’s not legal advice and doesn’t replace review by your counsel or your court’s instructions.
1) Start the tool from the primary CTA
Open DocketMath’s calculator here: /tools/settlement-allocator
If you’re using a dashboard, you may also find it under calculators; the key is that you’re inside the Settlement Allocator flow (calculator: settlement-allocator).
2) Set the jurisdiction to West Virginia (US-WV)
In the jurisdiction selector:
- Select West Virginia
- Verify the jurisdiction code shows US-WV
DocketMath uses jurisdiction-aware rules for the selected court system. For West Virginia, the rule set is grounded in W. Va. R. Civ. P. 23 (court-supervised class action settlement mechanisms).
3) Understand the West Virginia “default period” used by Rule 23
DocketMath’s West Virginia configuration uses the general/default period because no claim-type-specific sub-rule was found for the period guidance.
What this means in practice:
- The tool relies on W. Va. R. Civ. P. 23 as the governing baseline for the period used in the allocator logic.
- No claim-type-specific period override is applied in this configuration.
Why it matters: the allocator may use the Rule 23 period to determine whether a claim falls inside the eligible allocation window (for example, based on notice/cutoff/submission dates). If you expected different claim categories to use different time windows, the tool won’t apply that—by design.
4) Enter your allocation inputs
Settlement Allocator typically needs inputs that describe (a) the settlement amount and (b) the claim population you’re allocating across. The exact field names can vary slightly by UI version, but the concepts are consistent.
Use these checkable targets while filling the form:
- Settlement fund / total settlement amount
Enter the gross settlement amount you want allocated. - Individual claim data (claim rows / buckets)
For each claimant or claim bucket, enter the amount (or metric) used as the basis for allocation—e.g., claim value, weighting score, or another schema-specific metric. - Eligibility inputs relevant to the Rule 23 period window
If the UI includes dates (e.g., notice date, cutoff date, submission date), fill them consistently with the timeline your case is using. - Any weighting or normalization factors
If your case groups claims into categories, ensure the categories and factors are applied consistently across all entries.
Practical tip for consistency:
Use the same date basis across all claim rows. If you mix date formats (or accidentally switch between date types), the Rule 23 period logic can incorrectly exclude rows you intended to include.
5) Run the calculation
Click Calculate / Run Settlement Allocator.
DocketMath will apply:
- West Virginia (US-WV) jurisdiction rules tied to W. Va. R. Civ. P. 23,
- the general/default period logic (because no claim-type-specific override was found),
- and the allocation method embedded in the calculator for your input schema.
6) Review outputs: what to validate first
After the run finishes, review the sections below (names may differ, but the checks are the same):
| What to check in results | Why it matters | What “good” looks like |
|---|---|---|
| Total allocated vs. settlement amount | Confirms no missing eligible claims or rounding drift | Allocated totals match within expected rounding |
| Eligible vs. ineligible claim counts | Rule 23 period logic affects eligibility | Claims you expect to be eligible are included |
| Per-claim allocation amounts | Core deliverable of the allocator | Amounts align with your entered claim values/weights |
| Date-window effects | The Rule 23 default period drives inclusion | Boundary cases fall where your timeline intends |
7) Iterate safely with scenario testing
If the output looks off, rerun after changing only one variable at a time, such as:
- the relevant timeline date(s),
- the settlement amount,
- or the eligibility indicator per claim.
This makes it easier to identify whether the change affected eligibility (Rule 23 period window) versus the allocation math.
Warning: The most common cause of “wrong-looking” allocations is date-window eligibility errors and inconsistent date formats. Even a small date shift can move claims across the Rule 23 eligibility boundary.
8) Capture your run details for reuse
When you’re satisfied with the numbers:
- save/export results if the UI supports it,
- record that the jurisdiction setting is US-WV,
- note the run configuration (especially the dates and the settlement fund input).
If you later update claim entries, rerun with the same configuration to compare changes.
Common pitfalls
Settlement allocations usually fail in predictable ways. Here are common issues when running Settlement Allocator for West Virginia (US-WV) under W. Va. R. Civ. P. 23.
1) Assuming a claim-type-specific period override exists
DocketMath’s West Virginia configuration uses the general/default period from W. Va. R. Civ. P. 23 because no claim-type-specific sub-rule was found for period handling.
- Pitfall: You enter data assuming different claim categories should use different time windows.
- Result: Claims may be marked ineligible when you expected them to qualify under a different period rule.
2) Date inconsistencies across claim rows
If claim rows have different date formats (or mixed time zone assumptions after import), the Rule 23 window can be computed incorrectly.
- Fix: Standardize dates to the same format and verify they refer to the same date type (e.g., submission vs. cutoff) before rerunning.
3) Rounding surprises in totals
UI rounding can cause small differences between:
sum of per-claim allocations, and
the displayed settlement total.
Fix: Check whether the tool rounds at the row level, subtotal level, or final output level.
4) Entering the settlement figure incorrectly (gross vs. net)
Allocation scales directly from the settlement amount you enter.
- Pitfall: Using a net number after deductions when the calculation expects the full settlement fund.
- Result: Output allocations are lower than expected.
5) Mixing weights/values from different methodologies
If your case uses one metric for allocation (e.g., claim value), but you input a different metric (e.g., estimate vs. requested relief), results can diverge substantially.
- Fix: Confirm which field/column maps to the calculator’s allocation basis and keep that mapping consistent.
Try it
You can run a West Virginia allocation immediately in DocketMath:
- Go to /tools/settlement-allocator
- Select West Virginia (US-WV)
- Enter:
- the settlement amount
- claim rows (and any eligibility inputs if prompted)
- relevant dates to align with W. Va. R. Civ. P. 23’s general/default period
- Click Calculate
- Verify:
- totals (allocated sum vs. settlement amount),
- eligibility counts (especially around boundary dates),
- per-claim distribution
If the first run doesn’t match expectations, rerun with one change at a time—typically a date correction or eligibility flag update.
Note: If your timeline changes (notice date, cutoff date, or claim submission date), rerun so the Rule 23 window eligibility recalculates.
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
