Estate Property Radon Mitigation Agreement Review

**Published September 2, 2026**

A radon provision may require testing under a stated protocol, installation by a qualified contractor, payment up to a limit, and a post-mitigation result. Combining those steps into one status label makes it easy to miss a required retest or delivery.

Assemble the controlling file

Collect the signed agreement, every incorporated addendum, the estate authority record, relevant third-party reports, written notices, amendments, and the latest closing checklist. Preserve drafts separately from signed versions. Label each item with its source, received date, effective date when stated, and relationship to the transaction.

Before reviewing the clause, reconcile the property address, parcel or unit identifier, estate name, representative capacity, buyer name, and agreement date. A well-written provision attached to the wrong parcel or signed by an unverified person cannot close the evidence gap. Log conflicts rather than choosing the most convenient version.

Review the subject-specific evidence

Preserve the test device or laboratory report, sampling dates, property conditions stated in the report, measurement location, and chain-of-custody information when provided. Match the mitigation proposal to the contract scope and retain the installation record, warranty, permit, and post-work test.

For every field, cite the document and page or section. Preserve the original wording beside any normalized date, amount, or status. Definitions elsewhere in the agreement may control terms such as notice, approval, completion, business day, or receipt.

Map duties, deadlines, and dependencies

Turn each operative sentence into a dated task with a responsible party, trigger, required action, delivery method, and completion evidence. A deadline tied to receipt is different from one tied to execution or closing. Record the stated rule before calculating a calendar date, and keep extensions with the original provision.

Show prerequisites explicitly. An election may depend on delivery of a report; payment may depend on an invoice; release may depend on inspection or written approval. A status of “done” should point to evidence that satisfies the actual documented test, not merely to an email saying the work is underway.

Reconcile notices and the closing record

For a notice, retain the sender, recipient, permitted delivery method, address or account used, timestamp, attachments, and receipt evidence. Ordinary correspondence may be useful without meeting a formal notice requirement. Flag that difference for the authorized reviewer instead of reaching a legal conclusion.

Compare monetary or transfer terms with the current settlement statement, escrow instruction, invoice, ledger, or delivery receipt. Show the arithmetic and label estimates. When a later amendment changes a duty, preserve the earlier version and document exactly which term changed.

Maintain a neutral exception log

Write one exception per missing, conflicting, or unclear item. Include the controlling text, evidence present, evidence requested, operational effect, owner, and due date. Prefer reproducible language such as “signed approval not located in the indexed file as of September 2” over conclusions such as valid, waived, or compliant.

Health guidance and technical adequacy must come from qualified sources. The document reviewer should avoid interpreting measurements and instead confirm that required reports, work records, and notices are present.

Final handoff checklist

• Confirm the final signed agreement and all incorporated exhibits.
• Reconcile identity, property, authority, dates, and amounts.
• Link each duty to its trigger, deadline, notice, and completion evidence.
• Preserve superseded records and explain version changes.
• Assign every unresolved exception to a named reviewer.

This article provides general document-organization information, not legal, tax, safety, engineering, title, or investment advice. Requirements vary by contract and jurisdiction.