Mutual Rescission Agreement

A mutual rescission agreement unwinds an existing contract by consent, addressing return of payments and property, accrued performance, third-party rights, and surviving claims.

A useful document turns the parties' actual arrangement into measurable duties, approvals, timing, remedies, and a reliable execution record. Its terms should be reconciled to the transaction rather than copied from an unrelated form.

• Parties cancel an undelivered goods sale and return a deposit
• A service project is unwound before material performance
• A mistaken transaction is reversed by mutual consent

The document name alone does not determine the right structure. Consider a different instrument or qualified legal review when any of these conditions applies:

• Not a unilateral termination under an existing termination right
• Not enough to release third-party liens, taxes, or obligations

Record exact facts before clauses are written. Names, authority, dates, amounts, defined terms, dependencies, and incorporated materials should be verifiable and consistent.

• Original contract and performance to date
• Money, goods, data, and property to return
• Third-party commitments and accrued liabilities
• Release scope, survival, and effective date

These decisions shape the allocation of responsibility and should not be left for boilerplate to decide:

• Whether rescission is retroactive or prospective
• How used or damaged property is valued
• Which claims survive or are released
• What third-party consent is needed

• Identification and rescission effective time
• Mutual restitution and transfer steps
• Treatment of accrued claims and third parties
• Limited or full releases and survival
• Tax, records, and dispute resolution

Every provision should use the same parties, dates, standards, defined terms, and document hierarchy. A clause that is reasonable by itself can still create a conflict when it is not reconciled with payment, default, termination, or another exhibit.

1. 01Describe the intended result and the relationship in plain language.
2. 02Confirm parties, authority, governing jurisdiction, dates, money, property, services, and approvals.
3. 03Resolve the key decisions and identify every schedule, exhibit, disclosure, consent, or filing.
4. 04Draft the provisions as one consistent system, then review the complete execution set before signature.

Simply saying a contract is 'void' does not reverse title transfers, taxes, payments, or third-party rights. Rescission and release have different effects and should be reconciled.

The main agreement may establish the framework while schedules, exhibits, disclosures, consents, or operational records supply transaction-specific details.

• Original agreement and amendments
• Payment and delivery reconciliation
• Return and release receipts

Each incorporated document should be identified precisely, use the same names and effective date, and follow a stated order of precedence if terms conflict.

Inventory actual performance, agree simultaneous returns or escrow, obtain third-party approvals, and preserve a final reconciliation and release record.

• Confirm legal names, roles, capacity, addresses, and signing authority
• Reconcile dates, amounts, definitions, cross-references, schedules, and exhibits
• Confirm that duties, deadlines, approvals, acceptance standards, and payment triggers are measurable
• Check that default, termination, remedies, and surviving obligations work together
• Complete jurisdiction-specific forms, notices, witnesses, notarization, filings, or professional review when applicable
• Deliver and preserve the complete signed package with its incorporated documents

These sources provide federal, state-resource, regulatory, or institutional context. They do not replace checking the law and required forms applicable to the parties, transaction, and governing jurisdiction.

1. Source 1

   D.C. Code § 28:2-209 — Modification, rescission, and waiver

   D.C. Council. Enacted rules for changing and rescinding sales contracts.

2. Source 2

   D.C. Code § 28:2-401 — Passing of title

   D.C. Council. Enacted rule distinguishing title transfer and security interests.

3. Source 3

   D.C. Code § 28:1-304 — Obligation of good faith

   D.C. Council. Enacted good-faith obligation in commercial-code performance and enforcement.