Worked example: Closing Cost in Delaware

Example inputs

Run this scenario in DocketMath using the Closing Cost calculator.

This worked example shows how DocketMath can estimate a closing cost figure in Delaware (US-DE) using jurisdiction-aware rules. It’s a calculation walkthrough—not legal advice—meant to help you understand what the tool does and how the result can change.

Before we run numbers, here are the Delaware jurisdiction anchors the example uses for timing assumptions:

• General SOL (statute of limitations) period: 2 years
• Delaware general statute cited: Title 11, § 205(b)(3)
  Source: https://delcode.delaware.gov/title11/c002/index.html?utm_source=openai
• No claim-type-specific sub-rule found in the provided jurisdiction data: we apply the general/default 2-year period for the scenario below.

Scenario assumptions (inputs to the closing-cost calculator)

In DocketMath’s Closing Cost workflow, the calculator typically needs a few core items. For this example, assume:

• Purchase price: $250,000
• Down payment: $50,000
• Loan amount: $200,000
• Loan type (for illustration only): Fixed-rate
• Property tax estimate (annual): $3,200
• Owner’s insurance estimate (annual): $1,200
• Title/settlement fees (one-time): $3,900
• Recording/municipal fees (one-time): $750
• Prepaids/escrows (one-time): $4,800
• Interest rate (for escrow/interest-related timing only): 6.25%
• Close date timing factor: 2-year SOL anchor included for the workflow’s jurisdiction-aware period logic (general/default)

Because timing rules are part of DocketMath’s jurisdiction-aware logic, the example ties the analysis to:

• Delaware General SOL Period: 2 years
• Title 11, § 205(b)(3) (general/default limitations period)
  Source: Delaware Code (Title 11) https://delcode.delaware.gov/title11/c002/index.html?utm_source=openai

Checkbox input checklist

Use the list below to mirror what you’d enter in DocketMath:

• Purchase price = $250,000
• Down payment = $50,000
• Loan amount = $200,000
• One-time settlement/title fees = $3,900
• One-time recording fees = $750
• One-time prepaids/escrows = $4,800
• Annual property tax estimate = $3,200
• Annual owner’s insurance estimate = $1,200
• Delaware timing anchor uses 2 years under 11 Del. C. § 205(b)(3) (general/default)

Example run

Now let’s run the example in a clear, step-by-step way.

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.

1) Compute the loan-based baseline

• Purchase price: $250,000
• Down payment: $50,000
• Loan amount: $250,000 − $50,000 = $200,000

DocketMath uses the loan amount to contextualize any financing-linked parts of the workflow (for example, how escrow-related assumptions relate to the loan structure).

2) Add one-time closing items

Using the one-time items provided:

So far, this subtotal is driven by the explicit fee inputs you supplied. The Delaware SOL rule shows up in DocketMath’s jurisdiction-aware logic related to timing windows (not as a direct multiplier of your one-time fee line items).

3) Apply jurisdiction-aware timing logic (Delaware general/default SOL)

For Delaware, the provided jurisdiction data indicates:

• General SOL Period: 2 years
• General Statute: **Title 11, § 205(b)(3)
• No claim-type-specific sub-rule found: use the general/default 2-year period.

In this worked example, the “closing cost” output may incorporate a timing-related component inside DocketMath’s workflow (for example, logic that aligns certain prorations or escrow timing assumptions to a jurisdiction’s limitations anchor). The important takeaway is:

• DocketMath is jurisdiction-aware
• The Delaware anchor applied is the general/default 2-year period under **11 Del. C. § 205(b)(3)
• There is no claim-type-specific override available from the provided ruleset

4) Produce the final estimated closing cost output

Using the explicit line items above, the visible one-time portion begins at:

• $9,450 (one-time items subtotal)

Depending on how DocketMath applies its internal timing-linked steps, your final number could reflect additional logic-driven timing effects. However, with the information provided in this example, the most directly reproducible result is:

• Your major visible line items total: $9,450
• Delaware-specific rule usage: general/default 2-year SOL (11 Del. C. § 205(b)(3))
• No claim-type-specific adjustment: default period only

Result summary (what you can map to the tool output)

• Estimated closing costs (baseline one-time items): $9,450
• Delaware SOL anchor applied: 2 years using **11 Del. C. § 205(b)(3)
• No claim-type-specific override: default period only

To reproduce the workflow yourself, use the primary call to action: /tools/closing-cost.

Sensitivity check

Small changes to inputs can move closing costs through two main pathways:

1. Direct impact: changes to explicit fee inputs and prepaids/escrows.
2. Indirect impact: changes to timing-linked assumptions that depend on jurisdiction logic (here, the general/default 2-year Delaware period under 11 Del. C. § 205(b)(3)).

Below are practical sensitivity runs you can use to see which inputs matter most.

A) Direct fee sensitivity (most visible)

Because title/settlement, recording, and prepaids are one-time inputs, changing them often produces a near dollar-for-dollar movement in the one-time subtotal.

Takeaway: One-time fee changes are usually the fastest way to see movement in the output.

B) Prepaids/escrows sensitivity (can be large)

Prepaids/escrows are frequently one of the largest upfront items in closing totals.

• Base prepaids/escrows: $4,800
• If prepaids rise by $1,000, your one-time subtotal rises by about $1,000.

Example sensitivity run:

• New prepaids: $5,800
• New subtotal: $10,450
• Delta: +$1,000

C) Jurisdiction-aware timing sensitivity (Delaware default SOL)

With the provided Delaware dataset, the only timing anchor available is the general/default rule:

• 2-year period via **11 Del. C. § 205(b)(3)
• No claim-type-specific sub-rule found

So, if you keep the scenario consistent with the general/default assumptions, the Delaware timing anchor should remain stable. In practical terms:

• If you don’t change the jurisdiction timing rule (stay on general/default), the 2-year SOL anchor remains 2 years.
• Your output should generally be more sensitive to direct fee and prepaid inputs than to timing anchor selection—because fee inputs directly change the subtotal shown above.

Pitfall to avoid: Don’t assume a different limitations rule applies automatically just because the facts “feel like” a particular dispute type. With the provided ruleset, DocketMath uses the general/default 2-year period under Title 11, § 205(b)(3)—and no claim-type-specific override was identified.

Quick checklist for sensitivity runs

If results change dramatically when you adjust only timing-linked factors, that’s a signal to validate which part of the workflow is driving the change (often useful for understanding the tool’s internal assumptions).

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