What a Contingent Sale Is and How to Track One

A contingent sale still has conditions outstanding. The seller accepted an offer and the contract binds both parties, but named conditions must be satisfied or waived before closing. Here is which contingencies exist, what each one requires, and how to track them to release. Every condition carries a deadline and a specific release document, and a file missing either one is incomplete no matter what the status field says.

A contingent sale is a transaction where the seller has accepted an offer but named conditions must still be satisfied before closing. Each contingency carries a deadline, and each resolution must be recorded in writing.

The contract is binding from acceptance. That is the part consumers most often get wrong, and it matters operationally because a contingent file is a live transaction with obligations on both sides, not a reservation. What the contingencies add is a set of documented exit rights held by whichever party the clause protects, usually the buyer.

Each right has three moving parts: the condition itself, the date by which it must be resolved, and the document that resolves it. Miss the date and the right may lapse by its own terms. Skip the document and the file cannot prove the right was ever cleared. Both failures show up in the same place, at audit or in a dispute, months after anyone remembers what happened.

Four conditions carry most residential files: inspection, financing, appraisal and sale of the buyer's existing home. Four more appear regularly depending on the property and the state: title review, association document review, survey and insurance.

• Inspection. The buyer inspects and may terminate, request repairs, or proceed. The shortest window in the file and the one that produces the most terminations.
• Financing. The buyer must secure a loan commitment by a stated date. The contingency most often extended, and the extension needs an amendment rather than a phone call.
• Appraisal. If value comes in below contract price, the buyer may renegotiate or terminate depending on the addendum. Resolution is frequently a price amendment rather than a straight removal.
• Sale of buyer's home. The buyer must close another property first. Long-running, dependent on a transaction the brokerage may not control, and usually paired with a kick-out clause.
• Title review. The buyer reviews the commitment and objects to exceptions. Runs from delivery of the commitment, which is a different anchor from all of the above.
• Association documents. Statutory in several states, and the clock starts when the documents are delivered rather than when the contract was signed.
• Survey and insurance. Property-specific, and both can surface issues that reopen negotiation late in the file.

Track each contingency as a dated task anchored to the acceptance date: the deadline, the counting convention, the responsible party, and the release document that closes it.

The anchor date is the detail that causes the most avoidable errors. Most contingencies count from acceptance, meaning full execution and delivery, which is often a day or two after the date printed at the top of the offer. Title and association reviews count from delivery of a document, so those clocks cannot be set on the day the contract is signed. They get set when the delivery is confirmed, and the confirmation goes in the file.

Counting conventions differ too. Most forms count calendar days with the day after acceptance as day one. Some state forms count business days, and a few exclude legal holidays. Where the deadline lands on a weekend, some forms roll it forward and others do not. Read the definitions section of the contract once per form type, write the rule down, and apply it the same way every time.

Contingency periods do not run one after another. They overlap, which means a coordinator is managing four to six deadlines at once on a single file, and twenty to forty across a normal caseload.

A workable method has four rules. Derive every date from the contract on the day it is executed, never later. Set a reminder ahead of each deadline rather than on it, commonly three days out, so there is room to negotiate an extension. Assign each contingency to a named person, since a deadline owned by everyone is owned by nobody. And close each one with its document rather than with a status change.

This is the point where the tooling either helps or does not. Deadlines derived automatically from the executed contract and tied to a required document produce a file that closes itself out correctly. Brokerages running contingency deadline tracking off the contract dates rather than off manual calendar entries stop losing days to re-derivation every time a closing date moves.

A kick-out clause lets the seller keep marketing during a contingency, typically the buyer's home sale, and forces the buyer to waive or walk within a notice window, commonly 72 hours, if another offer arrives.

The sequence is fixed and every step generates a record.

• The seller accepts a secondary offer that meets the standard the clause describes, usually an acceptable bona fide offer.
• The seller delivers written notice to the first buyer, by the delivery method the contract names. Method matters, since email is sufficient under some forms and not others.
• The notice window opens on delivery, not on sending. Record the delivery timestamp and the proof.
• Inside the window the buyer either removes the home-sale contingency in writing and often increases earnest money, or the contract terminates.
• If the buyer removes, the file continues with the remaining contingencies intact. If not, the release goes in the file, earnest money is disbursed per the contract, and the secondary offer moves to primary.

The two documents that decide any later dispute are the delivery proof for the notice and the buyer's written response. Neither is optional, and a 72 hour window means both have to be captured the same week they happen.

Before a file moves from contingent to pending, run one test: count the contingencies named in the contract and its addenda, then count the releases. The numbers match or the file is not ready.

• Every named contingency has a signed removal, a superseding amendment, or a dated record that the period expired without a termination notice.
• Each release names the contingency it clears. A general document saying the buyer is satisfied does not clear four separate conditions.
• Each release is dated on or before the deadline it closes, or is accompanied by an amendment extending that deadline.
• Money terms changed by a release, such as an earnest money increase on a kick-out waiver, are reflected in the ledger.
• The transaction calendar is re-derived, since several remaining dates count backward from closing.

Where a contingency lapsed rather than being released, the file needs a dated note establishing that the period ran and no termination notice arrived. Silence is only evidence when the calendar backs it up.

Three outcomes, and each one produces a different document set. Waiver, where the buyer gives up the right without the condition being met. Release, where the condition was satisfied and the right is closed out normally. Termination, where the condition failed and a party exercised the exit.

Termination is the one with the most downstream work. It requires the termination notice, the earnest money release instructions signed by both parties, proof of disbursement, an MLS status change back to active inside the board's window, and a reason code on the file so the brokerage can see where its deals die.

The National Association of Realtors Realtors Confidence Index reported that in the twelve months ending June 2025, 6 percent of contracts were terminated and 20 percent were delayed. Delay is the larger operational cost, because a delayed file is re-worked rather than closed, and every extension is another amendment and another set of re-derived dates.

• Open contingencies by due date. One list across the whole office, sorted by date rather than by file.
• Contingencies past due without a release. The single highest-value exception report in a transaction pipeline.
• Days in contingent status. A file contingent for 45 days is telling you something a file contingent for 6 days is not.
• Termination reason codes. Inspection, appraisal, financing, home sale, other. Without codes, fall-through analysis is anecdote.
• Extension count per file. Repeated extensions on financing are an early warning that the closing date is fiction.