Delegation in a CA Firm: From Verbal Handoff to Work You Can See

Work in a practice is assigned in conversation and tracked in someone's head. That holds until filing week. How to make delegation visible without adding process nobody follows.

How Work Is Actually Assigned

In most practices delegation is a sentence: you take the GST for these four clients this month. It works because everybody remembers, and for a small team it is genuinely efficient — no ceremony, no tool, no overhead. The problem is that it degrades silently as the team grows, and it degrades fastest exactly when load is highest. Filing week is when memory is most stretched and when the cost of a dropped item is greatest.

The Two Failures

Informal delegation fails in two directions. Work gets done twice, because two people each believed it was theirs — wasteful but visible and recoverable. Or work gets done by nobody, because each assumed the other had it — invisible until a deadline passes. The second is the expensive one, and it is structurally more likely, because a handoff that was never explicitly accepted leaves no trace to contradict either person's assumption.

Assignment Means a Named Person

The minimum viable fix is not a tool. It is that every piece of work has one named owner, written down somewhere both parties can see, before the period starts. Not a team, not a colour, not an initial in a cell — a person who has seen that it is theirs. Most of the value of a task system is just this, enforced. The system matters more when the team is large enough that the written record needs to be queryable rather than read.

Model the States Work Actually Passes Through

A filing is rarely one action. Data is requested, chased, received, checked, prepared, reviewed, filed, and the acknowledgement is saved. Recording that as a single done-or-not flag discards every intermediate state, which is precisely where work gets stuck. In particular, waiting on the client needs to be its own state rather than a note, because it is the single most common reason something slips and it needs different action from work that is simply not started.

Delegated Work Needs a View

Whoever handed work out needs to see where it went without asking. Without that, follow-up becomes a standing meeting or a series of interruptions, both of which cost more than the tracking would have. The symmetric view matters too: each person needs one list of everything assigned to them across all clients, rather than having to check each client's file to assemble their own workload.

Capacity Is Invisible Until It Fails

Nobody in a practice knows who is overloaded until someone misses something or burns out. Because every task carries an owner and a state, the distribution of open work across the team becomes a fact rather than an impression. That number is only useful before the filing week — checking it afterwards tells you what you already learned the hard way. The point of tracking capacity is rebalancing while rebalancing is still cheap.

Constrain Assignment to the Team

A small but genuinely useful rule: work can only be assigned to someone who has access to the client it belongs to. It prevents the specific failure where something is handed to a person who cannot actually see the file, discovers this later, and hands it back — by which point several days have passed and everybody believes it is being handled.

Keep the Record After the Fact

The questions that arrive months later are about the past: who prepared this, who reviewed it, when was it filed. A practice that can answer those from a record rather than from recollection is in a materially better position, and the cost of having that record is close to zero if the work was tracked while it was being done. Retrospective reconstruction, by contrast, is expensive and never quite complete.