Worked example: Closing Cost in Massachusetts

6 min read

Published April 15, 2026 • By DocketMath Team

Example inputs

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

Because this guide focuses on computation rather than advice, treat the numbers as a demonstration of how DocketMath behaves with jurisdiction settings—not as a determination of what you must pay.

Scenario (Massachusetts)

Assume the following purchase and loan facts for a Massachusetts residential real estate transaction:

  • Purchase price: $500,000
  • Loan amount: $400,000
  • Down payment: $100,000
  • Loan term used for the calculator: 30-year fixed (entered only to match typical inputs; your actual loan terms may differ)
  • Estimated closing costs paid by borrower (entered in the closing-cost calculator):
    • Government/recording fees estimate: $1,250
    • Title/settlement fees estimate: $2,100
    • Prepaids (taxes/insurance) estimate: $3,000
    • Lender-related fees estimate: $1,500
    • Other closing items estimate: $500

Jurisdiction setting used in DocketMath

In DocketMath, the jurisdiction-aware time rule referenced in this worked example is set as follows:

  • Jurisdiction: Massachusetts (US-MA)
  • Jurisdiction-aware time rule (used by the calculator’s default logic):
    • General SOL period: 6 years
    • General statute: Mass. Gen. Laws ch. 277, § 63

Note: No claim-type-specific sub-rule was found. The calculator uses the general/default 6-year period under Mass. Gen. Laws ch. 277, § 63 rather than a shorter or longer time window for a specialized claim type.

How these inputs relate to the output

In DocketMath, the closing-cost tool combines your entered fee categories into a total estimated closing cost, and—where the calculator includes jurisdiction-aware timing components—it uses Massachusetts’ general statute timing framework:

  • Fee subtotal: sum of the categories you enter
  • Jurisdiction timing component: based on the general/default 6-year SOL under Mass. Gen. Laws ch. 277, § 63 (because no claim-type-specific override is configured here)

Example run

You can run the same scenario in the closing cost tool here: /tools/closing-cost.

For this worked example, imagine you enter the fee category totals exactly as listed above.

Step 1: Sum the cost categories

Add the entered estimates:

CategoryAmount
Government/recording fees estimate$1,250
Title/settlement fees estimate$2,100
Prepaids (taxes/insurance) estimate$3,000
Lender-related fees estimate$1,500
Other closing items estimate$500
Total estimated closing costs$8,350

So, the closing-cost subtotal for this run is $8,350.

Step 2: Apply Massachusetts jurisdiction-aware default timing logic

If DocketMath’s Massachusetts-aware default logic is included in the output for this tool view, it is tied to:

  • Mass. Gen. Laws ch. 277, § 63
  • General SOL period: 6 years

In plain terms, the tool’s default logic assumes the general 6-year timeframe when it runs timing-related computations. Since no claim-type-specific Massachusetts sub-rule was identified for this calculator configuration, it does not switch to a different limitation period.

What you should expect to see in the output

Exact labels can vary by calculator view, but typically you’ll see:

  • Total closing costs (from your fee inputs): $8,350
  • Jurisdiction timing component: based on 6 years / Mass. Gen. Laws ch. 277, § 63

If the tool includes an “effective window,” “time horizon,” or similar field, the value should reflect the 6-year default described above.

Why the Massachusetts statute matters here (conceptually)

Even when the topic is “closing costs,” some workflows attach a time-based assumption for follow-up analyses (for example, how long certain disputes might be subject to general timing rules). Massachusetts’ general SOL rule is captured by Mass. Gen. Laws ch. 277, § 63 with a 6-year default period.

Warning: A statute of limitations analysis can change significantly based on claim type, accrual dates, and specific statutory exceptions. This worked example shows how DocketMath applies the general default (6 years; ch. 277, § 63) because no claim-type-specific sub-rule was found/configured for this example.

Sensitivity check

Now let’s test how the output responds when inputs change—so you can see which parts of the estimate drive the result most.

Sensitivity check A: Increase “Prepaids” by 20%

Keep everything the same, but adjust Prepaids:

  • Original Prepaids: $3,000
  • New Prepaids (20% increase): $3,600
  • Change: +$600

New total estimated closing costs:

  • $8,350 + $600 = $8,950

What stays the same in this example run:

  • The Massachusetts default timing component remains 6 years under Mass. Gen. Laws ch. 277, § 63, because we did not change jurisdiction and no claim-type-specific sub-rule was introduced.

Sensitivity check B: Reduce “Other closing items” to zero

Set the Other closing items estimate from $500 to $0.

  • New total: $8,350 − $500 = $7,850

Again, the 6-year default timing logic remains the same under Mass. Gen. Laws ch. 277, § 63.

Sensitivity check C: Change only the loan amount (does not change fee totals in this setup)

In this worked example, the fee inputs were entered directly as estimates. If you change loan amount but keep the fee category totals fixed (because you’re typing them in), the closing-cost subtotal you enter likely stays the same.

  • If you don’t re-calculate fees from loan size, then your entered category totals—and therefore the computed closing-cost subtotal—don’t change.
  • The jurisdiction timing assumption continues to use the general 6-year default under Mass. Gen. Laws ch. 277, § 63.

To see a different effect from loan size, you’d typically need a version/configuration where some fees are derived from loan amount.

Quick driver table (based on this example)

Input you changeExpected effect on total closing costsEffect on SOL/timing component
Prepaids estimateHigh (category is large)None (still general default)
Title/settlement estimateMediumNone
Government/recording estimateMedium/lowNone
Lender-related feesMediumNone
Other closing itemsLow/mediumNone
Jurisdiction settingN/A in these checksWould change if you switch states

Pitfall: Many borrowers assume changing the loan amount automatically changes all closing fees. In this worked example, fees were entered as category totals, so loan amount changes won’t move the subtotal unless the calculator is configured to derive those fees from loan size.

Related reading