Most complaints about professional service are not about the outcome. They are about the eleven weeks nobody said anything, which is the part of the job that scales worst and automates best.
Key takeaways
Build the update from the file rather than from memory, on a fixed cadence, and send it even when there is nothing to report. That last part is the whole of the problem. Firms are reliably good at reporting a development and reliably bad at reporting the absence of one, and the absence is where the client’s anxiety lives.
Commentary [6] to rule 3.2-1 of the Law Society of Ontario’s Rules of Professional Conduct says it exactly: a lawyer should be prompt in handling a matter, responding to communications and reporting developments to the client, and — in the absence of developments — contact with the client should be maintained to the extent the client reasonably expects. The rule itself sets the standard as service that is competent, timely, conscientious, diligent, efficient and civil. None of those words is about the outcome.
A file already emits an event stream, it is just scattered. Matter management holds the tasks and the limitation dates. The calendar holds what happened and what is next. The document folder holds what was produced. The mailbox holds what was sent and received. A model can read all four and produce a five-line draft that names what happened since the last update, what is scheduled, what the firm is waiting on, and what it needs from the client.
What it must not do is decide what is material. Materiality is a professional judgment about the client’s matter, and a draft that quietly omits an adverse development because it looked like an ordinary docket entry is worse than no update. Present the draft with the underlying events visible so the reviewer is checking against the file rather than against the summary.
A status update sent to a client for the purpose of a commercial relationship is a commercial electronic message. Under section 6 of Canada’s anti-spam legislation, sending one is prohibited unless the recipient has consented, expressly or impliedly, and the message complies with subsection 6(2) — which requires prescribed identification of the sender and any person on whose behalf it is sent, information enabling the recipient to readily contact one of them, and an unsubscribe mechanism in accordance with subsection 11(1). Subsection 6(3) requires that contact information to remain valid for a minimum of 60 days after the message is sent.
Subsection 6(6) then disapplies paragraph 6(1)(a) only — the consent requirement — for a message that solely does one of seven listed things. Two of them cover ordinary file updates: paragraph (b), a message that facilitates, completes or confirms a commercial transaction the recipient previously agreed to enter into; and paragraph (d), a message providing notification of factual information about the recipient’s ongoing use or purchase of a service offered under a subscription, membership, account, loan or similar relationship, or about that ongoing relationship itself.
Two consequences follow, and both are commonly missed. First, the exemption is from consent, not from the content requirements in subsection 6(2). Second, the word is solely. Append a line about a new service the firm now offers and the message is no longer solely a notification, so you are back to needing consent for it. Keep status updates and marketing in separate messages — which is also better practice, because a client reading about a delay does not want a pitch.
What counts as a development the client reasonably expects to hear about depends on what you were engaged to do. Under rule 3.2-1A.1 a lawyer providing services under a limited scope retainer must confirm the services in writing and give the client a copy when practicable, and the commentary notes that reducing the agreement to writing helps both sides understand the limitations and risks. Treadstone Law’s article on limited scope retainers in Ontario litigation explains how narrow those engagements can be.
An automated cadence built on a full-service assumption will over-report on a limited retainer and, worse, imply the firm is watching things it is not. Configure the cadence per matter type, not per firm.
The update is client information, so rule 3.3-1 applies to it in full: a lawyer shall at all times hold in strict confidence all information concerning the business and affairs of the client acquired in the course of the professional relationship. In practice that means the drafting tool sits inside the systems you already control, the send goes through the channel the client agreed to, and a shared family mailbox is a decision somebody makes deliberately rather than a default. The Law Society of Ontario’s practice supports and resources are the starting point for the firm-level version of this.
The supervision rule applies to the sending too. Under rule 6.1-1 a lawyer assumes complete professional responsibility for their practice and must directly supervise non-lawyers to whom tasks are assigned. An update that leaves the firm unread by anyone is a communication nobody supervised.
A litigation practice sets a four-week cadence on every active file. The draft is assembled on a Monday, a lawyer clears the queue in a single sitting, and the updates go out Tuesday. Roughly half say some version of "nothing has moved; the next date is X; we need nothing from you".
The change the firm notices is not gratitude. It is that inbound "any news?" emails fall away, and that the ones that remain are about something specific. That is the real return: the firm stops spending unbilled time reconstructing file history to answer a question it could have pre-empted in ninety seconds.
Count what you can count: the interval between updates on each open matter, the number of inbound status enquiries per matter per month, and the proportion of matters with no client contact for more than the cadence you set. All three are already in your systems.
This is about keeping a client informed on work in progress. Intake, appointment scheduling, reminders and front-desk handling belong on the professional practice owners page. Chasing your own receivables is a different job again.
And it is worth being clear about what a failure here is. Poor communication is usually a service complaint rather than a negligence claim, but the two can arise from the same facts — Treadstone Law sets out the difference between suing a professional in negligence and in contract.
How often is often enough?
The rule is the client’s reasonable expectation, which is set by what you told them at the outset. Say the cadence in the engagement letter and then keep it; a stated monthly rhythm that is honoured beats an unstated weekly one that lapses.
Should the client be able to see the file directly?
A portal helps and does not replace the update, because a portal shows activity and an update explains it. Firms that ship a portal and stop writing usually see enquiries rise, not fall.
Can AI answer the client’s reply?
It can draft the reply. Sending it unread is the line, because the reply is where a client’s question turns into instructions, and instructions need a person.
Does this apply outside law?
The wording differs by profession but the expectation does not. An accountant, engineer or broker with a live engagement and a silent quarter has the same problem and the same fix.
A 30-minute call is enough to tell you whether AI pays for itself here.
