Treadstone Associates
Article · 7 min read

Documenting client instructions so they hold up

A client’s instructions rarely get disputed the day they are given. They get disputed months later, after a deal has gone sideways and the client’s memory of what they agreed to has quietly shifted. Whether your version holds up then depends on what you wrote down at the time — not on how confident you are that you remember it correctly. RECO’s own complaints process tells you, in effect, exactly what it will be looking for, which means it also tells you exactly what to be keeping.

Treadstone Associates · Updated 2026

Key takeaways

  • • RECO recommends its complaints process be supported by the representation agreement, offer documents, any consents or acknowledgements, listing information, and correspondence — that list is a working checklist of what to document contemporaneously.
  • • Every disclosure, consent, or acknowledgement required by TRESA must be written in plain language and identified by the prominent placement of the word “disclosure” — a model worth copying for any instruction you confirm in writing.
  • • A representation agreement’s duties list includes “keeping the client advised of all significant steps taken” — a running record, not a one-time signature.
  • • In Alberta, a broker must “review all real estate agreements in a timely manner,” and delegating a task to another licensee does not remove the delegating broker’s own accountability for it.

Work backward from what a complaint actually asks for

RECO does not leave you guessing about what matters later. When outlining how to submit a complaint, RECO recommends supporting it with the representation agreement (sometimes called a listing agreement or buyer representation agreement), offer documents or the agreement of purchase and sale, any consents or acknowledgements signed, listing information for the property, and any relevant correspondence. (RECO, Submitting a complaint) That is not just guidance for a consumer filing a complaint against you — read the other direction, it is the exact list of what your own file needs to contain to defend a decision you made months or years ago. RECO also states plainly that its investigation process has “no fixed time period” and explicitly “considers whether the real estate agent or brokerage involved has a history or pattern of misconduct” when deciding what action to take. (RECO, After a complaint is submitted) A single undocumented instruction rarely sinks a file on its own — a pattern of them, visible only once a regulator starts pulling every file you have, is what actually costs a licence.

The regulation gives this same discipline a name beyond the complaint checklist. O. Reg. 567/05, s. 22.1(2) requires a broker or salesperson to “make best efforts to obtain a written acknowledgement from the client indicating that the disclosure and advice” on material facts “has been received” — the same written-record habit this piece recommends for every significant instruction, already written into the regulations for this specific one.

Copy the plain-language, labelled-disclosure model for your own confirmations

TRESA’s own bar for disclosures, consents, and acknowledgements is instructive even outside the specific situations it governs. Every one of them must be “written in plain language that is clear and concise” and “Presented in a manner that draws the person’s attention to the required information,” and a disclosure specifically must be “identified by the prominent placement of the word ‘disclosure.’” (RECO Bulletin 3.1) That same discipline — plain language, clearly labelled, sent so the client’s attention is actually drawn to it — is exactly what turns a phone call into something defensible. A recap email that opens “Confirming what we discussed” and states the instruction in one clear sentence does more work than a vague voicemail note in your own file that only you can interpret.

The duty is a running record, not a signature at the start

Representation agreements are required to reflect specific duties owed to the client, and one of the named duties is “Keeping the client advised of all significant steps taken in the course of representing them.” (RECO Bulletin 2.3) That reframes documentation from a one-time event at signing into an ongoing practice through the file’s life — every price change, every strategy shift, every instruction to hold or accept an offer is itself a “significant step” the client is entitled to have been kept advised of, and a written trail is the only evidence that you actually did.

Alberta’s supervision angle: timely review, and accountability that does not delegate away

Alberta’s Rules build documentation discipline into brokerage supervision directly. A broker must “review all real estate agreements in a timely manner” (Rule 51(1)(i)), and while a broker may delegate duties to a qualified licensee, “the broker remains accountable for the conduct of the delegate” (Rule 52). (RECA Real Estate Act Rules 51, 52) The practical implication for an individual agent is the same regardless of province: a file that is easy for a supervising broker to review quickly — instructions dated, in writing, and consistent with the agreement on file — is not just good practice for your own protection, it is what your broker needs to actually discharge their own supervisory duty on your file.

Timing is part of the documentation, not separate from it

When an instruction has to be documented matters as much as whether it is documented at all. RECO’s multiple representation bulletin makes this explicit for one specific instruction — consent: “disclosure and consent at the time an offer is submitted is, in almost all circumstances, too late,” and the brokerage “can’t take any further steps on behalf of any of the clients until the disclosure is made and each of the clients involved provide their written consent.” (RECO Bulletin 3.2) The same logic applies to any significant instruction: a written confirmation sent after the fact, once a dispute has already started, reads very differently from one that was sent contemporaneously, before anyone had a reason to disagree. Build the habit of confirming an instruction the same day it is given, not when you first sense it might later be questioned.

A worked example

A seller calls to say they will accept $612,000 instead of holding out for $625,000, after weeks of no offers. If that instruction lives only in your memory of the call, a dispute six months later about whether you undersold their home comes down to your word against theirs. The five-minute fix is a same-day email: “Confirming our call today — you have instructed me to accept offers at or above $612,000, revised down from the $625,000 listed price, effective today’s date.” That single message, sent at the time, is worth more to your file than any amount of confident recollection produced afterward.

Related: see what documentation a clean termination needs, and why the same written-record discipline applies to conflicts disclosures.

Common questions

Does a text message count as documentation, or does it need to be a formal letter?

RECO’s own bar is plain language, clarity, and that the recipient’s attention is actually drawn to the content — a dated, clearly worded text or email satisfies that better than a vague voicemail, though it should be saved somewhere retrievable, not left to disappear from your phone.

Do I need the client to reply and confirm, or is my own written note enough?

A note you alone wrote is weaker than a written exchange the client actively engaged with, because RECO’s consent and acknowledgement model is built around confirming the other person actually received and understood the information — a client’s own reply, even a one-line one, is worth having.

How far back does documentation actually need to go?

RECO’s discipline process explicitly weighs a registrant’s history and pattern of conduct, not just the file in question, so there is no safe point at which older documentation stops mattering — keep it for as long as your retention practice under PIPEDA’s own limiting-retention principle reasonably allows.

Want a documentation habit that actually holds up later?

A short call can turn this into a simple template you can use on every file, not just the difficult ones.