Tracking Earnest Money and Contingency Deadlines: A TC Workflow

A missed contingency deadline is rarely a dramatic event. It is a date that quietly passes while everyone assumes someone else is watching it — and then a seller sends a Notice to Buyer to Perform, or a buyer discovers their earnest money is no longer protected, and the file lands back on the transaction coordinator's desk as a problem instead of a checklist item. For a TC running a full pipeline, earnest money and contingency deadlines are the two things that turn a routine file into a liability file if they slip.

This is a practical workflow for tracking earnest money and contingency deadlines: confirming the deposit, watching the three contingencies that matter most, and keeping the documentation trail a brokerage needs if a deal falls apart. It pairs well with a one-pass disclosure checklist for the front end of the file — this piece picks up once the contract is ratified and the clock starts.

Confirm the deposit, don't assume it happened

Treat the deposit as unconfirmed until a dated receipt is in the file. The purchase agreement says the buyer will deliver earnest money within a set number of days of acceptance, but that line in the contract is not proof of anything — it is a promise. The TC's first job on a new file is converting that promise into a confirmed fact: a copy of the deposit receipt from escrow or the holding broker, dated and matched against the contractual deadline.

Earnest money typically runs 1% to 3% of the purchase price, which on a mid-market home is enough money that a late or missing deposit is a real default risk, not a technicality. Under California trust fund handling rules, a broker who receives trust funds directly must place them with the owner, into escrow, or into a trust account within three business days of receipt — and a buyer's deposit check may be held uncashed only until the offer is accepted, and only if the buyer gave written instructions not to deposit it (or the check is non-negotiable by the broker) and the seller was informed before or at the time the offer was presented that the check was being held. If your file involves the broker holding a check rather than a direct escrow deposit, that distinction is worth flagging to the supervising broker, not guessing at.

Track three dates for the deposit alone: the day it was contractually due, the day escrow or the broker actually confirms receipt, and the day you documented that confirmation in the file. If the first two don't match, that's a notice situation, not a note-to-self.

The three contingencies that actually end deals

Three contingencies — inspection, loan, and appraisal — are the ones that most often end a deal or land it in dispute. Every purchase agreement has more clauses than a TC can reasonably track with equal urgency, so these three get the calendar entries and the follow-up.

Inspection contingency

This gives the buyer a window to have the property professionally examined and to request repairs, a credit, or an exit if the findings are bad enough. Freddie Mac's guidance describes the inspection period as the buyer's chance to have the home "examined by a professional before you close," with the right to negotiate repairs or walk away if the contingency is still open. The date that matters is not when the inspection happens — it's when the contingency is due to be removed in writing.

Loan (financing) contingency

The financing contingency protects the buyer if they cannot secure a loan on the agreed terms within the agreed window, letting them walk away without penalty if it isn't removed. Loan approval timelines run on the lender's clock, not the transaction's, which is exactly why this is the contingency most likely to need an extension request rather than a silent miss.

Appraisal contingency

Once the loan process starts, the lender orders an appraisal to confirm the home supports the loan amount. If it comes in low, an appraisal contingency lets the buyer renegotiate or walk away instead of losing their deposit over a valuation gap. Closing itself typically follows 30 to 45 days after acceptance, which gives a rough sense of how much runway sits between contract date and the appraisal deadline in a normal file.

In California, general contingencies commonly run about 17 days from acceptance, with C.A.R.'s guidance referencing a 21-day period for the loan contingency — the printed default has changed across RPA revisions, so the number that governs is the one on the specific form in the file. Contingencies stay active — meaning the buyer retains cancellation rights — until they are removed in writing and signed. If a contingency period lapses without written removal, the seller's recourse is a formal Notice to Buyer to Perform, which under the same guidance gives the buyer roughly two days to remove the contingency or respond before the seller can move to cancel. That short a window is exactly why a TC needs the deadline on the calendar days in advance, not discovered the morning it expires.

The tracking grid

Keep this contingency grid open on every active file, alongside the contract. It is not a substitute for the contract language — it's the operational layer on top of it.

Every row needs two dates in the file: the deadline itself, and the date the removal (or notice) was actually documented. A contingency that was "probably fine" but was never removed in writing is still open as far as the contract is concerned.

The documentation trail that protects the brokerage

If a deal falls through, the file that matters isn't the one that shows the deal was handled well — it's the one that shows exactly when each notice, confirmation, and removal happened, in writing, with a delivery method attached. For every contingency, keep: the signed removal or the seller's notice, the date it was sent, how it was delivered, and who acknowledged it. For the deposit, keep the receipt and the date it was confirmed against the contractual due date. A verbal confirmation from an agent that "the buyer's fine on financing" is not documentation; a written loan status update or a signed contingency removal is.

This is also where a brokerage's exposure tends to concentrate. A dispute over a retained earnest money deposit almost always turns on whether contingencies were removed in writing before the buyer tried to cancel, or whether a notice was properly served before the seller tried to keep the deposit. A TC who keeps that trail current — rather than reconstructing it after a cancellation notice arrives — is doing the single highest-value thing on the file.

Where tracking tools fit without replacing judgment

Reminders and calendars help, but the volume of a busy pipeline is what actually breaks manual tracking, and it is the reason automation matters here — a TC juggling twenty files loses the thread on the file that's been quiet for two weeks, not the one that's noisy. This is where AI automation earns its place in a TC workflow. Charlie AI, the AI assistant inside Loqol (loqol.ai), an AI and automation platform built for licensed brokerages, automatically assembles contingency dates from the ratified contract into a tracked timeline, flags which files have an approaching deadline with no documented removal on file, and organizes the notice and confirmation documents as they come in — the kind of assembly and tracking work that AI does tirelessly and that keeps a TC's attention on the files that actually need a decision. For an independent brokerage, that is also a margin question: TC capacity is one of the first real cost lines a small firm adds as it grows, and an automated tracking layer that lets one coordinator carry more files cleanly is how a firm adds sides without adding that cost in step. The same system runs the rest of the file too — the vendor schedule, the escrow timeline, the follow-ups, the estimates for repair credits and closing dates — so the TC, the agent, and the broker are all looking at one live project plan, and the calls on extensions, notices, and cancellations get made with time to spare instead of after a deadline has already passed.

For brokerages standardizing this across a team, pairing deposit and contingency tracking with a consistent disclosure package workflow closes most of the gap between a file that looks organized and one that actually holds up if a deal goes sideways.