Skip to main content

The chasing wears people down, not the work

Cody Halovich · 9 November 2026 · 4 minute read

Every spring the same complaint comes out of the back office of an accounting firm. It is rarely about the returns. It is about the third email to a client for a missing T4, the RRSP receipt that is still in the mail, the slip re-typed from a blurry phone photo, and the T183 authorization nobody has signed. Your people trained for years to prepare returns. The chasing is what wears them down.

The complaint is a list of the wrong work

When trained staff complain, it is tempting to hear a morale problem. Listen to the nouns instead. Nobody says the returns are too hard or the clients are too complicated. They name the reminder, the re-keying, the follow-up, the form that sits unsigned. Each of those is a task with a trigger, a known next step, and an obvious finish.

That pattern is worth noticing. The work people resent is the work that asks nothing of their training. Preparing a return with a rental property and a move between provinces takes judgment. Sending the same request for the same slip for the third time takes a calendar and patience. When the second kind crowds out the first, the job stops being the job they signed up for.

Nobody logs the chasing, so nobody counts it

From your chair the chasing barely exists. It never gets its own line on a timesheet. It happens in short pieces between real work, spread across the whole team, all season. A preparer opens a file, sees a gap, writes an email, moves to the next file, and comes back two days later to check. None of it feels big enough to mention, except in the complaint.

The cost lands somewhere else: in who stays. When the Canadian Medical Association asked physicians what would most improve recruitment and retention, reducing administrative burden came first, chosen by 77 percent (Canadian Medical Association, 2025). Physicians are not accountants, but the finding travels. Highly trained professionals rank the paperwork around their work, not the work itself, as the thing that decides whether they stay. Your senior preparer's complaint in March is the early version of that decision.

Chasing is a machine's job

Look at the chasing as a sequence. A client's file opens for the season. Last year's slips say which documents to expect. A request goes out. Documents come in by email, through the portal, or as a photo. Someone checks each one against the list. Whatever is missing gets asked for again, on a schedule. The return waits until the authorization is signed.

Every step in that sequence follows a rule the firm already knows. An agent can run it. It builds the request list from last year's file, reads what arrives, turns the phone photo into the fields the preparer needs, marks what is still outstanding, and sends the next reminder on the day it is due. It holds the file until the T183 comes back signed and tells the preparer when everything is in.

The preparer opens a complete file. The first time they hear about that client is when there is a return to prepare.

Keep the judgment with the person

This only works if the line is drawn in the right place. The agent takes the work with a trigger and a known finish. The person keeps everything that needs a professional: the slip that does not match what the client said, the client who has not answered after the third reminder and needs a phone call, the new situation this year that changes the return.

Do not automate past that line. The gain comes from taking the robotic parts off the role, not from squeezing the role down to nothing. A preparer who spends the season on returns and hard conversations has the job they trained for. A preparer whose whole day is checking what a system produced has a different version of the same complaint.

Start with the complaint itself

This week, ask each person on the team one question: which three tasks would you hand to someone else tomorrow? Have them write the tasks down in their own words. Do not discuss the lists yet.

Put the lists side by side and find the task that shows up most often. Then write down three things about it: what starts it, what it needs to finish, and what done looks like. If you can write those three lines without saying "it depends", the task runs on a rule, and a task that runs on a rule does not need one of your trained people to run it.

The next step

Have a question this didn't answer?

The discovery call is free. We'll talk about your operation and tell you honestly whether AI automation is the right move.