Estate Agency Sale Progression: An Accepted Offer Is Not Exchange or Completion
An estate agency portal should help staff explain where a particular property sale stands without turning a seller's accepted offer into a completed transaction. Before commissioning it, separate the buyer's offer, the seller's response, confirmed exchange of contracts and actual completion. A single green “sold” label cannot safely explain all four.
This guide uses the ordinary home-selling process described by GOV.UK for England and Wales. It is not a conveyancing service, a contract-formation decision engine or guidance for Scotland, Northern Ireland or another country. Have a qualified legal professional approve the transaction definitions and customer wording for your actual practice.
Record which buyer's offer was accepted
An offer belongs to a proposed transaction, not just to the property listing. A property can receive several offers, and the selected buyer can change. Keep the buyer reference, offered amount, relevant stated conditions, seller response and dated history together. Do not overwrite an earlier buyer's accepted offer when a replacement buyer appears.
GOV.UK explains that offers may be verbal or written and that an estate agent must inform the seller of offers received. For the proposed software, let staff record the communication channel and when the seller was informed. An attachment may support the record, but the presence of an uploaded email should not automatically mean the seller accepted its contents.
Agree who can record the seller's decision and what evidence the agency needs. “Offer received,” “presented to seller” and “seller accepted” answer different operational questions. A customer-facing update should use the one that actually occurred.
Keep acceptance separate from binding exchange
The official offers guidance states that an offer is not legally binding in England and Wales until contracts are exchanged. It also describes title review and searches after an offer has been accepted. A successful offer negotiation therefore does not establish that the later legal work is complete.
Ask the developer for separate progression evidence rather than a checklist that promotes the sale automatically when every visible box is ticked. Identify who supplied the exchange confirmation, which transaction it concerns and when exchange actually occurred. A proposed exchange date, a signed document uploaded by a participant and an authorised confirmation of exchange must remain distinguishable.
These are recommended record controls, not a claim that software can decide the legal sufficiency of a document. If confirmation is uncertain, show that uncertainty to the responsible staff member. Do not publish a binding-contract message simply because a target date has passed.
Treat completion as its own confirmed event
GOV.UK's conveyancing guidance distinguishes exchange, which makes the agreement legally binding, from completion, which includes the transfer of money and documents needed to transfer ownership. Preserve that distinction in the portal. Do not derive “completed” solely from “contracts exchanged.”
Keep the intended completion date separate from the confirmed completion event. If the plan changes, staff should be able to see the revised expectation without losing the original communication history. Decide whose confirmation is required before the agency records completion and releases any related operational task.
A key-collection appointment can be useful planning information. It should not, by itself, certify completion or authorise release of keys. Have the agency and its legal advisers define the actual release instruction and the person permitted to act on it. The public guidance cited here does not establish your agency's key-release procedure.
Separate the listing from the transaction
A portal may also control public advertising labels. Decide how “offer accepted,” “under offer,” “sold subject to contract” or another reviewed phrase maps to your agency's records. Do not invent a universal legal meaning for a marketing label or assume every property platform uses the same vocabulary.
Keep the public listing decision separate from the legal progression record. If a transaction falls through and the seller wants to market the property again, retain the unsuccessful transaction and create a clearly related next one. Reopening the listing must not erase the earlier offer, exchange evidence or professional review.
Similarly, a transaction participant should not gain access to another buyer's correspondence merely because both records concern the same address. Design the client view around the authorised transaction and its permitted information, not an unrestricted property history.
Ask for an end-to-end demonstration
Use fictional records in the acceptance test. Present two buyers' offers, accept one, change the expected exchange date and upload a document that is not yet exchange confirmation. The portal should preserve the distinctions without promoting the sale to a later milestone.
Then record authorised exchange evidence while completion is still outstanding. Change the planned completion day and demonstrate the separately confirmed outcome. Finally, rehearse a failed transaction followed by a new buyer: the listing may change, but the old transaction remains intelligible and its private documents stay private.
Bring a blank progression sheet and examples of the agency's approved client messages to a custom application discussion. The useful first release is a shared, explainable account of the sale, not an automated promise that every accepted offer will complete.
Sources and scope
GOV.UK: offers and negotiations supports the offer channels, estate-agent communication and England-and-Wales exchange distinction. GOV.UK: transferring ownership distinguishes exchange from completion. The proposed record structure, access boundaries and demonstration cases are implementation advice, not additional legal rules.