How to run Settlement Allocator in DocketMath for West Virginia

Step-by-step

This guide shows how to run Settlement Allocator in DocketMath for West Virginia (US-WV) using jurisdiction-aware rules. The focus is on getting the right inputs and understanding how the outputs change based on those inputs—not on providing legal advice.

1) Start at the Settlement Allocator tool

1. Open DocketMath → Settlement Allocator here: **/tools/settlement-allocator
2. Confirm the jurisdiction is set to West Virginia (US-WV).
3. Make sure you’re using the correct calculator configuration:

   • calculator: settlement-allocator
   • platform template: platform-howto

2) Enter the settlement and case timing inputs

DocketMath’s Settlement Allocator uses timing to drive allocation results. Add the key dates and amounts you have available:

• Settlement amount (total dollars to be allocated)
• Relevant event date (the date the tool uses as the anchor for time-based rules)
• Filing or claim date (when the claim was brought, if your workflow captures that)

If your workflow tracks multiple dates (for example, demand date vs. filing date), choose the date that corresponds to the tool’s “relevant event” prompt. Consistency matters: changing the anchor date can change the time-based logic and therefore the output allocation.

3) Verify which statute-of-limitations (SOL) period DocketMath will apply (West Virginia)

For West Virginia, DocketMath uses the general/default statute of limitations when no claim-type-specific sub-rule is found.

• General SOL period: 1 year
• Statute reference: W. Va. Code § 61-11-9
  Source: https://codes.findlaw.com/wv/chapter-61-crimes-and-their-punishment/wv-code-sect-61-11-9/

Important: No claim-type-specific sub-rule was found for this setup. So, DocketMath will apply the general 1-year period as the governing timeframe under W. Va. Code § 61-11-9, rather than switching to a different duration for a specific claim type.

4) Run the allocator and review the results

Click Calculate / Run (wording may vary). Then review the result sections to see how your inputs affected the output:

• Allocation breakdown: what portion the tool assigns based on the entered timing and amounts
• Timing impact indicators: whether the entered dates place the matter within or outside the 1-year window
• Any flags or warnings: if DocketMath surfaces warnings when inputs make the calculation ambiguous

If something looks off, the first place to check is usually:

1. the anchor date (the tool’s relevant event date), and
2. the other timing date used for comparison.

A one-year boundary can meaningfully change how the tool categorizes timing and therefore the allocation.

5) Adjust inputs to see how outputs change (iterative workflow)

Use a controlled “what-if” approach:

• Keep settlement amount constant.
• Change only one date at a time.
• Re-run the calculator after each single change.

This makes it clear whether the allocation shift is being driven by:

• moving into/out of the 1-year window under W. Va. Code § 61-11-9, or
• changing which date the tool treats as controlling.

Sanity-check idea:

• If you move the relevant event date forward by a few months but remain within the same year window, the output may shift modestly.
• If you cross the 1-year threshold, expect a clearer shift.

6) Export or capture results for your workflow

Once the allocation looks right for your recordkeeping needs:

• Save/export the results if DocketMath provides that option.
• Record the exact inputs that produced your run—especially the two dates—so you can reproduce the same results later.

For teams, capturing these parameters prevents “mystery differences” between versions of the same case run.

Common pitfalls

Settlement Allocator output depends heavily on timing and on how DocketMath matches jurisdiction rules to the inputs. Watch for these recurring issues:

• Using the wrong “anchor” date

  • If the tool expects a specific date as the relevant event, entering a different but related date can move the case into or out of the 1-year window under W. Va. Code § 61-11-9.
• Assuming a claim-type-specific SOL applies

  • In this West Virginia setup, no claim-type-specific sub-rule was found. DocketMath will use the general/default 1-year SOL under W. Va. Code § 61-11-9, not a specialized duration.
• Changing multiple variables between runs

  • If you adjust settlement amount and dates at the same time, you won’t know which change caused the output shift.
• Ignoring boundary effects

  • Moving dates near the 1-year threshold can change timing classification outcomes abruptly.
• Not documenting the run parameters

  • If you only save the output without the underlying inputs (especially the dates), reconciling differences later is much harder.

Try it

1. Open DocketMath’s Settlement Allocator: **/tools/settlement-allocator
2. Set Jurisdiction = US-WV.
3. Enter:

   • a settlement amount
   • the relevant event date
   • the filing/claim date (or the second date the tool requests)
4. Run the allocator.
5. Make a single adjustment:

   • shift the relevant event date by, for example, 30 days, and re-run
6. Compare the allocation sections before and after.

You should see output changes driven by how the entered dates relate to West Virginia’s general 1-year SOL under W. Va. Code § 61-11-9.

Related reading

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