Worked example: Closing Cost in North Carolina

5 min read

Published April 15, 2026 • By DocketMath Team

Example inputs

Below is a worked example of calculating closing cost in North Carolina (US-NC) using DocketMath with jurisdiction-aware rules. This walkthrough is for understanding how a calculator can apply timing logic; it’s not legal advice.

Scenario (fictional numbers for illustration)

Assume a borrower is selling real property in North Carolina and wants to estimate closing costs for a typical transaction.

We’ll use a simple cost bundle:

  • Purchase price: $325,000
  • Loan amount: $260,000
  • Escrow deposit (estimate): $6,500
  • Title & settlement fees (estimate): $2,200
  • Recording / local fees (estimate): $1,050
  • Prepaids (estimate): $3,400
  • Other closing charges (estimate): $850

Where to enter these in DocketMath: open the closing-cost tool and enter these cost categories as the calculator’s inputs.

Jurisdiction-aware timing rule (North Carolina)

North Carolina’s default civil limitations period is 3 years for the general statute of limitations logic used by this calculator example.

Separately, North Carolina’s “SAFE Child Act” appears in the jurisdiction notes for this workflow as a reference point for child-protection related legal context. The key point for this example:

Note: No claim-type-specific sub-rule was found for this calculator workflow. The general/default period of 3 years is applied.

What you’re calculating

In this example, DocketMath’s closing-cost logic totals a closing cost estimate from itemized components. At the same time, the jurisdiction context (including the 3-year default limitations period) is included as part of the workflow metadata so it can be used by later steps that depend on time windows.

Inputs summary (what you would enter)

Use DocketMath closing-cost with inputs like:

InputValue
Purchase price$325,000
Loan amount$260,000
Escrow deposit$6,500
Title & settlement fees$2,200
Recording / local fees$1,050
Prepaids$3,400
Other charges$850

Optional jurisdiction context (for the workflow):

  • Jurisdiction: US-NC
  • General SOL period used (default): 3 years
  • Claim-type-specific adjustment: none found → default applies

Example run

Let’s run the numbers exactly as a calculator-style total.

Step 1: Add the closing cost components

Total closing costs = escrow + title/settlement + recording/local + prepaids + other charges

  • Escrow deposit: $6,500
  • Title & settlement fees: $2,200
  • Recording / local fees: $1,050
  • Prepaids: $3,400
  • Other closing charges: $850

Total = 6,500 + 2,200 + 1,050 + 3,400 + 850 = $14,900

Step 2: Capture jurisdiction timing context for the workflow

DocketMath associates jurisdiction-aware rules with the workflow. In this North Carolina example:

  • General SOL Period: 3 years
  • General Statute referenced: “SAFE Child Act” (as provided in jurisdiction data)
  • Claim-type-specific sub-rule: None found, so the default 3-year general period applies

This matters if your downstream workflow uses a “time window” for eligibility, reporting, or documentation timelines. In other words:

  • the closing cost number is driven by dollar inputs, and
  • the jurisdiction timing context is carried along as metadata.

Example output (what you’d expect to see)

A DocketMath closing-cost output would typically include:

  • Estimated closing cost: $14,900
  • Jurisdiction: North Carolina (US-NC)
  • General SOL period used: 3 years
  • Rule selection: default/general period (no claim-type-specific adjustment found)

Quick check against the price scale

Your purchase price is $325,000, so $14,900 is a reasonable order-of-magnitude estimate for many transaction cost breakdowns. To sanity-check it, you can compute:

  • $14,900 / $325,000 ≈ 4.58%

Warning: If you change even one category (for example, escrow or prepaids), your total can swing by thousands. Use the most recent lender/settlement estimates rather than mixing numbers from different quotes.

Sensitivity check

Now let’s see how the estimate changes when inputs move. Sensitivity checks are a fast way to identify which line items have the biggest effect.

Base total: $14,900

1) Escrow deposit changes ±$1,000

  • Base escrow: $6,500
  • Low escrow: $5,500
  • High escrow: $7,500

Revised totals

  • Low total: $14,900 − $1,000 = $13,900
  • High total: $14,900 + $1,000 = $15,900

Impact: a $1,000 escrow change moves the total by $1,000 (as expected in a direct-sum model).

2) Prepaids change ±$500

  • Base prepaids: $3,400
  • Low: $2,900
  • High: $3,900

Revised totals

  • Low total: $14,900 − $500 = $14,400
  • High total: $14,900 + $500 = $15,400

Impact: a $500 change moves the total by $500.

3) Title & settlement fees change ±$300

  • Base: $2,200
  • Low: $1,900
  • High: $2,500

Revised totals

  • Low total: $14,900 − $300 = $14,600
  • High total: $14,900 + $300 = $15,200

Sensitivity table (what moves the needle)

Line itemBaseChangeNew total (low)New total (high)
Escrow deposit6,500±1,00013,90015,900
Prepaids3,400±50014,40015,400
Title & settlement fees2,200±30014,60015,200

Jurisdiction timing sensitivity (what stays stable here)

This example’s jurisdiction notes specify:

  • General SOL period: 3 years
  • Claim-type-specific sub-rule: none found → default applies

So your jurisdiction timing context stays the same across these dollar-input changes. The closing cost responds to cost inputs; the 3-year default rule does not change unless a different claim-type-specific adjustment is identified and enabled in the workflow.

Practical input checklist (reduce avoidable variance)

When you re-run DocketMath for your own deal:

  • Update escrow deposit to match the latest lender estimate
  • Confirm prepaids include items like taxes/insurance as quoted
  • Replace title/settlement numbers with the most current quote
  • Keep recording/local fees aligned to the correct county/township
  • Include any known one-time other charges (notary, endorsements, etc.)

Related reading