Thirty seconds into a conversation with a practice principal, the same sentence arrives: our client data is confidential, so this isn't really for us.
It's a legitimate objection, correctly raised, and it's aimed at the wrong target. Nobody is suggesting you paste a client's financials into a chat window. The question worth asking is what proportion of the work that's actually costing your practice time involves client data in the first place — and in most practices, when you list it out, the answer is startling.
List the week and look at what's on it
Sit with a practice manager and inventory the jobs that run late, and the same items appear:
- Chasing records before a lodgement. The same email, dozens of times, with a name and a document list swapped. The chasing is the cost; the client's actual figures never enter it.
- Engagement letters and scope variations. Templated, repetitive, and drafted by someone senior because the wording matters.
- Explaining something technical to a client who doesn't want the technical version. Superannuation changes, a Div 7A position in plain English, why the refund is smaller this year. Pure writing, no figures required to draft the explanation.
- Internal process documentation. How the practice does a job, which exists in one person's head and nowhere else, and which is the actual bottleneck when someone leaves.
- Onboarding and induction material for a workforce that turns over, especially around the busy period.
- Proposal and pricing letters for advisory work the practice wants more of.
- Newsletters and client updates that get planned every year and written twice.
That's a significant share of the hours, and not one item on it requires a client's data. The confidential material sits in the work you're already careful with: the files, the ledgers, the returns, the advice. Those aren't the jobs making people work Saturdays.
Jobs a practice can start on this month
- The records-chase email, as a reusable setup rather than a copy-paste
- Engagement letters and scope variations
- The plain-English explanation of a technical change
- Process documentation for one job that lives in one person's head
- Induction material for the next busy-period hire
The part where the objection is right
There's a version of this that deserves to be taken seriously rather than argued out of.
If a staff member has been pasting client material into a personal free account for six months, you have a real problem, and it isn't a training problem — it's a visibility problem. The account type matters more than the brand here: a personal free account has no administrator, no record, and nothing happens to it when someone leaves. We set out why the same tool gives two different answers about your data in its own article.
So the sequence for a practice is usually: establish what's happening, write the rule, then train. Not because the training is risky, but because training people to use a tool the practice hasn't sanctioned puts the exposure on them and leaves the principal carrying it anyway. That's what the policy and audit engagement is for, and in many practices it's the whole first piece of work.
What changes once the line is drawn
Two things, and the second one is the one principals don't predict.
The obvious one: the work on the list above gets faster, and the practice stops losing evenings to typing.
The less obvious one: usage goes up among the careful people. The staff who were quietly avoiding these tools — often the most senior, most technically strong, most reputationally exposed — start using them on the sanctioned work, because they finally know where the line is. Before the rule exists, ambiguity reads as risk, and the people with the most to lose act accordingly.
If you can't currently answer "which accounts is my team using", that's the first thing to establish, and it's a conversation rather than a project.
Start an enquiryWhy a general course doesn't land here
Because the objection has to be answered before anything else is teachable, and a general AI course doesn't know it exists. The accounting and bookkeeping track opens with the client-data question rather than closing with a disclaimer, and the examples on the table are lodgement chases and engagement letters rather than blog posts and marketing copy.
The other thing a general course misses: in a practice, the person doing the work often also signs the cheque. That changes what's worth teaching. A partner doesn't need to become an enthusiast — they need the records-chase to stop eating Thursday, and they need to be sure that what the juniors are doing won't turn up in a professional complaint. Those are the two jobs, and they're both answerable.