Worked example: Closing Cost in South Dakota

6 min read

Published April 15, 2026 • By DocketMath Team

This article is for informational purposes only and does not constitute legal advice. Laws change frequently — verify all citations with current official sources.

Example inputs

Below is a worked example of a closing cost calculation in South Dakota using DocketMath with jurisdiction-aware rules.

Because your brief specifies no claim-type-specific sub-rule, this example uses South Dakota’s general default statute of limitations (SOL) period for the relevant timing rule:

General SOL period: 3 years
General statute: SDCL 22-14-1

Note: This example applies the general/default SOL period. If a case involves a specialized SOL rule for a specific claim type (not provided in the brief), the timing logic could change.

Scenario (what you’re solving)

You want to estimate a closing cost figure that depends on:

a base closing cost amount
a date-based timing component tied to the 3-year SOL framework (general/default under SDCL 22-14-1)

Assumptions for the example

Use these inputs in DocketMath (calculator: closing-cost) for US-SD:

Input	Value	Why it matters
Jurisdiction	US-SD	Enables South Dakota rules
Base closing cost	$3,250	Starting figure before timing adjustments
Event date	2026-01-15	The anchor date for elapsed time
Filing date	2023-01-20	Used to compute whether timing falls within the SOL window
SOL length used	3 years	Default SOL period per SDCL 22-14-1
Daily accrual rate (timing adjustment)	$2.50/day	Converts “days elapsed” into a cost delta

Timing interpretation (how the example models it)

We’ll treat the timing component as follows:

Compute days elapsed between the filing date and event date.
Compare elapsed time to the 3-year SOL period.
Apply a timing adjustment:
- If elapsed time is within 3 years, adjustment is $0 (no SOL-driven bump)
- If elapsed time exceeds 3 years, add an incremental amount using the daily rate

This is a computational model for demonstration—not legal advice.

Checkbox checklist for sanity before running the example:

Confirm you’re using **South Dakota (US-SD)
Confirm you have dates in YYYY-MM-DD
Confirm the calculator is set to use the general/default 3-year SOL (SDCL 22-14-1) because no special sub-rule was provided
Confirm your daily accrual rate aligns with your underwriting or internal costing model

Example run

Now run the example in DocketMath → /tools/closing-cost using the inputs above.

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: Calculate elapsed time

Filing date: 2023-01-20
Event date: 2026-01-15

From 2023-01-20 to 2026-01-15 is (approximately) 1,096 days (non-leap-year and leap-year effects around 2024 are captured by the day-count method).

Step 2: Translate 3 years into days

A strict “3 years” window isn’t always exactly 1,095 days because of leap days. For a practical tool run, DocketMath’s jurisdiction-aware logic should treat the SOL framework as a date-based comparison rather than a constant day count.

For purposes of this worked example, we’ll use the equivalent window:

3 years from the filing date → up to roughly 2026-01-20

Under that comparison:

Event date 2026-01-15 is within the 3-year window ending around 2026-01-20.
Therefore, no SOL-driven timing bump is triggered.

Step 3: Apply closing cost formula

Base closing cost: $3,250
Timing adjustment: $0 (because the event date falls inside the 3-year SOL period window)

Estimated closing cost output:

$3,250 + $0 = $3,250

What the tool would display (conceptually)

You should expect output sections similar to:

Computed elapsed time (days)
SOL window status (within/exceeded)
Adjustment computed (and why it’s $0 in this run)
Final closing cost figure

If you want to reproduce the calculation quickly: open DocketMath closing cost tool and plug in the dates and amounts.

Warning: If your filing date and event date are swapped (a common data entry issue), elapsed time can flip from “within SOL” to “outside SOL,” changing the adjustment by days × $2.50/day in this example model.

Sensitivity check

Sensitivity checks answer a practical question: How sensitive is the closing cost to date choices? Below are two variations that keep everything constant except the event date.

Base assumptions reused:

Jurisdiction: US-SD
Base closing cost: $3,250
Filing date: 2023-01-20
Daily rate: $2.50/day
SOL rule: **3 years under SDCL 22-14-1 (general/default period)

Variation A: Move event date forward by 10 days (still within the window)

Event date: 2026-01-25
Compare to ~3-year end around 2026-01-20

In this variation, the event date is likely outside the window by about 5 days (depending on the exact day-count convention).

Timing adjustment:

If exceeded by 5 days: 5 × $2.50/day = $12.50

Estimated closing cost:

$3,250 + $12.50 = $3,262.50

Variation B: Move event date forward by 60 days (meaningfully outside)

Event date: 2026-03-21

Now the event date is clearly beyond the 3-year window. If we estimate the exceedance at roughly 60 days beyond the window: