Worked example: Closing Cost in New York

6 min read

Published April 15, 2026 • By DocketMath Team

Example inputs

Below is a worked example for New York (US-NY) closing cost calculation using DocketMath’s closing-cost calculator and jurisdiction-aware rules for the relevant timeline assumptions.

Here is a simple illustration for New York. These values are for demonstration only and should be replaced with your actual inputs.

  • Principal or amount: $100,000
  • Rate or cap: 10%
  • Start date: 2025-01-15
  • End/as-of date: 2025-09-30

Assumed scenario (for demonstration)

You’re estimating closing costs as part of a broader “how long does this stay actionable” workflow. The calculator’s goal is to convert your inputs into a consistent output while applying a New York general limitation period rule.

Key jurisdiction rule used in this example (New York)

For New York, the relevant default timeline in this example is the general statute period of 5 years, referenced through:

  • N.Y. Crim. Proc. Law § 30.10(2)(c) (general/default period used here)

Source: https://www.nysenate.gov/legislation/laws/CPL/30.10

Note: No claim-type-specific sub-rule was found for this worked example. That means this example uses the general/default period (5 years) as the jurisdiction-aware rule, rather than tailoring to any specific claim type.

Inputs you provide to DocketMath (closing-cost)

For clarity, this example uses a common pattern of inputs a homeowner, lender, or transaction team might enter when estimating total closing costs.

Check the items you’ll set in the /tools/closing-cost calculator:

  • Purchase price: $450,000
  • Closing cost percentage estimate (transactional assumptions): 1.8%
  • Fixed closing fees (paperwork/services): $1,250
  • Title/escrow-related estimates: $2,400
  • Other closing expenses: $600
  • Jurisdiction: **New York (US-NY)

Timeline context (used to show “jurisdiction-aware” behavior)

DocketMath uses New York’s default timeline assumption to align outputs with a consistent 5-year general period. The calculation section focuses on dollars, but the example also shows how the jurisdiction rule gets attached to the “timing window” context in the output you’ll see.

Gentle note: This is a worked example for illustration, not legal advice. Closing costs and timeline assumptions can vary based on the facts and how a specific matter is classified.

Example run

Now let’s run the numbers 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: Percentage-based closing costs

  • Purchase price: $450,000
  • Closing cost %: 1.8%
  • Percentage-based costs:
    • $450,000 × 0.018 = $8,100

Step 2: Add fixed and itemized components

DocketMath then adds your itemized estimates:

  • Fixed closing fees: $1,250
  • Title/escrow-related: $2,400
  • Other closing expenses: $600

Itemized total:

  • $1,250 + $2,400 + $600 = $4,250

Step 3: Total estimated closing costs

  • Total = percentage-based costs + itemized total
  • Total = $8,100 + $4,250 = $12,350

Step 4: Attach New York jurisdiction-aware timing context

Because the example uses New York’s general/default period (no claim-type-specific sub-rule was identified here), the output also associates this with the 5-year general period.

  • New York general period: 5 years
  • Statutory reference: **N.Y. Crim. Proc. Law § 30.10(2)(c)
  • Practical interpretation in this workflow: the tool treats 5 years as the baseline timeline you’d want reflected in a transaction-related “how long does risk/eligibility persist” context.

Example output summary (what you’d see conceptually)

Output componentValue
Percentage-based closing costs$8,100
Itemized closing fees$4,250
Total estimated closing costs$12,350
Jurisdiction timing context used5 years (general/default)
Statutory citation in contextN.Y. Crim. Proc. Law § 30.10(2)(c)

Action: try it in DocketMath

Primary CTA:

Sensitivity check

Even with a solid baseline, closing-cost estimates can swing quickly when you adjust a single input. Here are three targeted sensitivity checks using the same $450,000 purchase price and the New York general-period (5-year) context.

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.

Sensitivity check A: Change the percentage estimate (1.8% → 2.1%)

Recalculate percentage-based costs:

  • New % = 2.1%
  • Percentage-based costs = $450,000 × 0.021 = $9,450
  • Itemized costs remain $4,250
  • New total = $9,450 + $4,250 = $13,700

Impact: $13,700 − $12,350 = +$1,350 (about +10.9%)

Sensitivity check B: Keep 1.8%, increase itemized fees (Fixed fees $1,250 → $1,900)

Percentage-based costs stay at $8,100.

  • New itemized fixed fees = $1,900
  • Itemized total = $1,900 + $2,400 + $600 = $4,900
  • New total = $8,100 + $4,900 = $13,000

Impact: $13,000 − $12,350 = +$650 (about +5.3%)

Sensitivity check C: Keep all dollars fixed, adjust purchase price ($450,000 → $500,000)

Percentage-based costs change; itemized costs remain constant:

  • Percentage-based costs = $500,000 × 1.8% = $9,000
  • Total = $9,000 + $4,250 = $13,250

Impact: $13,250 − $12,350 = +$900 (about +7.3%)

Pitfall: Closing costs are often estimated using a mix of a percentage and specific line items. If you increase only the percentage but ignore that title/escrow and “other expenses” may also change with the transaction, you can end up overstating or understating the total in either direction.

What doesn’t change in this example (jurisdiction timing context)

In all three sensitivity scenarios, the New York timeline assumption remains the same because this worked example uses the general/default period of 5 years tied to N.Y. Crim. Proc. Law § 30.10(2)(c).

  • Baseline timeline: 5 years
  • No claim-type-specific sub-rule applied in this worked example (per the note)

If your workflow eventually needs claim-type specificity, you’d want to re-run the tool with a ruleset that matches the relevant classification—this example intentionally does not do that.

Reminder: This is not legal advice; the correct limitation period can depend on specific facts and how a matter is categorized.

Related reading