Worked example: Closing Cost in West Virginia
7 min read
Published April 15, 2026 • By DocketMath Team
Example inputs
Run this scenario in DocketMath using the Closing Cost calculator.
Below is a worked example showing how DocketMath’s Closing Cost calculator can be used for a West Virginia matter. This example emphasizes jurisdiction-aware defaults—specifically the general statute-of-limitations (SOL) period the calculator logic can apply.
Jurisdiction and default SOL rule used
West Virginia’s calculator inputs depend on a general SOL period and the associated statute:
- General SOL period: 1 year
- General statute cited by the tool logic: W. Va. Code § 61-11-9
- No claim-type-specific sub-rule found: The content data provided did not identify a special SOL sub-rule for a specific claim category. Because of that, the example uses the general/default SOL rule.
Note / disclaimer: This example uses the general SOL period (1 year) from W. Va. Code § 61-11-9 as the default. If your claim type (or underlying theory) has a different limitation period, the timeline—and therefore the calculator’s output—could change. This is a practical illustration, not legal advice.
Example scenario (numbers used for the run)
To make the math concrete, assume:
- Event date (trigger date): January 15, 2026
- Filing date (when the action is initiated): January 10, 2027
- Total closing cost amount (principal): $4,800
- Funding/collection start lag (for cash-flow timing): 10 days
- State jurisdiction: West Virginia (US-WV)
Inputs to enter in DocketMath (closing-cost calculator)
Use these inputs in the Closing Cost tool (labels may vary slightly in the UI, but the concepts are the same):
- Jurisdiction:
US-WV - Trigger date:
2026-01-15 - Filing date:
2027-01-10 - Closing costs (principal):
4800 - Lag days (timing adjustment):
10
If your workflow separates “trigger” and “demand” or “notice” dates, use the date that corresponds to what the tool treats as the relevant start point for timing. In short: enter the timeline dates the tool expects, plus the cost amount, and set lag days to reflect your process.
Example run
This run illustrates how DocketMath applies a West Virginia default 1-year SOL period under W. Va. Code § 61-11-9.
Run the Closing Cost calculator using the example inputs above. Review the breakdown for intermediate steps (segments, adjustments, or rate changes) so you can see how each input moves the output. Save the result for reference and compare it to your actual scenario.
Step 1: Confirm the SOL window with the default rule
The calculator’s West Virginia default SOL is 1 year.
Under the assumptions above:
- Trigger date: Jan 15, 2026
- Filing date: Jan 10, 2027
- Result: the filing occurs just under the 1-year mark (roughly 360+ days, depending on how the tool counts days)
Result: The filing is within the 1-year general SOL window.
Reminder: The example uses the general/default SOL period only, because no claim-type-specific sub-rule was provided in the given inputs.
Step 2: Apply the lag days timing adjustment
The calculator also uses lag days to adjust timing assumptions tied to when costs are considered in the model.
- Lag days: 10
- Practical effect: the tool shifts the cost-related timing component by the lag amount before incorporating its closing-cost timing logic.
Even when the SOL outcome stays “inside” (timely), lag days can still change the numeric output because they affect the timing portion of the closing-cost calculation.
Step 3: Compute the closing cost output
Given:
- Closing costs (principal): $4,800
- Jurisdiction: US-WV
- Default SOL: 1 year (W. Va. Code § 61-11-9)
- Filing inside SOL: Yes
- Lag days: 10
DocketMath’s output reflects two interacting pieces:
- SOL-timing gating: whether the tool treats the matter as timely under the default 1-year rule
- Cost timing adjustment: changes driven by the lag days input and the tool’s closing-cost model
Example output (directional)
Because the filing date is inside the 1-year window in this scenario, the calculator should produce an output consistent with “timely under default SOL,” plus a timing adjustment related to lag days.
In practice, you can think of the output as:
- Computed closing cost based on the $4,800 principal
- Plus/minus a timing adjustment component influenced by lag days
To keep this example actionable, focus on directional behavior:
- If the filing date moves beyond the 1-year threshold, SOL gating can change the output materially (often reducing or recharacterizing amounts depending on tool logic).
- If lag days increase, the timing adjustment component typically shifts, changing the output even if the SOL status remains the same.
Warning (non-legal-advice): SOL rules can be nuanced. If your facts implicate a different limitation period than the general/default rule, you should use the correct sub-rule in the tool (or consult a qualified professional).
Sensitivity check
A sensitivity check shows how the result changes when you vary one input at a time. Below are practical variations that isolate the effect of SOL timing vs. process timing.
To test sensitivity, change one high-impact input (like the rate, start date, or cap) and rerun the calculation. Compare the outputs side by side so you can see how small input shifts affect the result.
Baseline (from the example run)
- Trigger date: 2026-01-15
- Filing date: 2027-01-10 (inside 1-year)
- Closing costs: $4,800
- Lag days: 10
- Jurisdiction: US-WV
- SOL logic used: 1 year under W. Va. Code § 61-11-9 (general/default)
1) Move the filing date across the 1-year threshold
Change only:
- Filing date: from 2027-01-10 to 2027-01-16
Expected behavior:
- The filing becomes outside the default 1-year window.
- The calculator’s SOL gating can flip, which may create a larger output change than adjusting lag days.
Checklist:
2) Increase lag days while keeping SOL status constant
Change only:
- Lag days: from 10 to 30
Expected behavior:
- Filing date remains inside SOL, so SOL gating should stay the same.
- The timing adjustment component should change because the tool model is sensitive to lag.
Checklist:
3) Vary the closing cost amount while keeping timing constant
Change only:
- Closing costs: try $2,400, then $9,600 (instead of $4,800)
Expected behavior:
- If the tool’s cost component scales roughly with the principal amount, outputs should scale directionally up/down.
- Timing adjustments may scale proportionally or may be partially additive—so you should observe the pattern.
Checklist:
Quick comparison table (what to look for)
| Change | Dates SOL outcome (default 1-year) | Lag days | Primary expectation in output |
|---|---|---|---|
| Baseline | Inside | 10 | Baseline closing cost + timing adjustment |
| Filing +6 days | Outside | 10 | Major change likely from SOL gating |
| Lag 30 days | Inside | 30 | Moderate change from timing adjustment |
| Costs $2,400 | Inside | 10 | Lower output directionally |
| Costs $9,600 | Inside | 10 | Higher output directionally |
Pitfall to avoid: If you change both filing date and lag days at once, you won’t be able to tell whether output changes are driven by SOL or by timing.
Related reading
- Average closing costs in Alabama — Rule summary with authoritative citations
- Average closing costs in Alaska — Rule summary with authoritative citations
- Average closing costs in Arizona — Rule summary with authoritative citations