Escalation clauses: the form every agent uses wrong
The market is competitive again. Not 2021-competitive, but tight enough that in the last quarter we've watched half a dozen agents ask the same question in half a dozen different ways: how do I write an escalation clause for my buyer?
Almost every one of them started in the wrong place.
Between the two of us, we've drafted, reviewed, and cleaned up escalation-clause disputes at every stage, during the offer, at the counter, and (worst) three days before close of escrow when opposing counsel argued the language was unenforceable. The pattern is consistent. Agents reach for the Additional Clause Addendum. It's the wrong form. It has been the wrong form the entire time.
What an escalation clause actually is
An escalation clause is a contingent purchase-price provision. The buyer offers a base price with an agreement to increase the price, by a specific increment, up to a specific cap, if the seller receives a bona-fide competing offer at or above the base. The clause has three moving parts:
The base price: what the buyer is offering absent competition.
The escalation trigger: the threshold that activates the increase, defined by reference to a competing offer.
The cap: the maximum price the buyer is willing to pay under any circumstances.
Enforceable escalation clauses also address two secondary questions: proof of the competing offer (what does the seller have to show the buyer to validate the trigger?), and appraisal risk (what happens if the escalated price appraises low?). Skip either of those and the clause looks tidy until closing gets contested, and then it isn't.
Where the language belongs
The correct place, and the only place, for custom escalation language in the AAR Residential Resale Real Estate Purchase Contract is Section 8 "Additional Terms and Conditions," page 8 of the RRPC, lines 342-405. That's the free-form area of the Contract specifically reserved for custom deal terms the pre-printed language doesn't cover. It's part of the Contract itself. Signed by both parties at contract acceptance. Fully integrated with every other Contract provision, earnest money, inspection period, financing contingency, Cure Period Notice, without any of the interpretive gymnastics required when custom language lives on an addendum.
Why the Additional Clause Addendum is wrong for this
The Additional Clause Addendum (ACA) is what most agents reach for. It's the wrong form for three reasons.
First, the ACA is a pre-printed set of optional clauses. It exists to let agents add specific, pre-drafted provisions, non-refundable earnest money, backup offers, corporate relocation, to the base Contract. It is not a blank canvas for custom language. Writing an escalation clause into the ACA's margins or into an appended paragraph is a drafting choice that opposing counsel can argue was outside the form's intended use.
Second, an addendum modifies the Contract; Section 8 is part of the Contract. That distinction matters when the escalation-clause language interacts with other Contract sections. The RRPC's default remedies, its Cure Period mechanism, its earnest money forfeiture provisions, those all reference "this Contract." Custom language inside Section 8 is unambiguously part of "this Contract." Custom language on an addendum is one interpretive step removed, and that step is exactly where opposing counsel earns their fee.
Third, the ACA doesn't create the enforcement mechanics the escalation clause needs. Proof of the competing offer, timing of the escalation calculation, appraisal-risk allocation, none of those integrate cleanly with the addendum's structure. Section 8, drafted correctly, lets the escalation language sit alongside the Contract's own procedural machinery.
Three drafting mistakes that make escalation clauses fall apart
We've seen escalation clauses fall apart at closing for the same three reasons.
Vague proof-of-competing-offer language. "Buyer's price shall escalate if a higher offer is received" leaves every material term undefined. What counts as an offer, a signed contract, a term sheet, a text message? What price is being compared, the offered price or the net-to-seller after concessions? Who verifies? The correct clause defines proof explicitly: a fully executed competing purchase contract, delivered to buyer's agent, redacted to preserve competing buyer's privacy but preserving price and material terms.
No cap or a soft cap. An escalation clause without a hard numeric cap is a blank check. A cap that says "up to fair market value" is worse than no cap, because it introduces a valuation dispute at closing. State the cap in dollars. Full stop.
Silence on appraisal risk. If the escalated price appraises low, whose problem is it? If the clause is silent, the Contract's default appraisal contingency governs, which typically gives the buyer an out at the original appraised value. Sellers agreeing to escalation clauses often assume the buyer is committed to the escalated price regardless of appraisal, and they're often wrong. Drafting the appraisal question into the clause protects both sides from a surprise.
What a compliant workflow looks like
The mechanics an agent should follow, in order:
Confirm with the buyer that they want to escalate, that they understand the cap is a real number they'll be legally obligated to pay if a legitimate competing offer arrives.
Draft the escalation language directly into Section 8 "Additional Terms and Conditions" of the RRPC, lines 342-405. Do not put it on the ACA. Do not put it in an email. Do not attach it as a separate addendum.
Include all three moving parts, base price, escalation trigger, cap, plus explicit proof-of-competing-offer requirements and appraisal-risk allocation.
If the deal is high-stakes or the clause is complex, recommend the client consult an attorney. A.R.S. § 32-2153 limits the unlicensed practice of law by real estate licensees, and custom pricing language is one of the areas where that line is close.
Escalation clauses aren't inherently dangerous. Bad drafting on the wrong form is. The AAR RRPC gives agents exactly one right place for this language, and the whole industry has spent the last four competitive markets writing it somewhere else. That's a habit, not a rule. The correct answer has been sitting at line 342 of page 8 the entire time.
— Sarah Richardson (CEO) & Mike McGowan (CRO), reTEQ
