The Document Chase: Where Your Firm's Hours Actually Go

Ask a CA firm where filing season goes and you'll hear about late nights over ledgers and portals that crash on the due date. Both are real. But sit inside a mid-sized firm through one GSTR cycle, one TDS quarter, one audit season, and a different picture emerges: the single biggest consumer of staff hours is getting documents out of clients, asking, re-asking, downloading, renaming, and figuring out what's still missing. This is the founding observation behind everything else in this series: the compliance work is rarely the bottleneck. The document chase in front of it is.

The chase is invisible because it's granular

No timesheet has a line called “chasing.” It hides in five-minute fragments: a WhatsApp nudge here, a phone call there, scrolling a thread to check whether the bank statement that arrived on the 4th covered April or May. Multiply those fragments across 100+ clients and every compliance cycle, and firms routinely lose the equivalent of one full-time person, often their sharpest article, to work that produces nothing billable.

Worse, the chase runs on personal channels. Documents land in a partner's own WhatsApp at 11:40 pm, as photos taken at an angle. Whoever maintains the intake Excel becomes a single point of failure. When she's on leave, the firm is flying blind three days before a deadline.

None of this shows up anywhere a partner would naturally look for it. Utilisation reports track chargeable hours against clients and matters, not against “sent client three reminders and is still waiting.” The chase eats time in a category nobody measures, so nobody budgets for it, nobody staffs for it, and nobody notices when it quietly doubles between one filing season and the next.

A week inside the chase: one article's timesheet

Numbers convince more than adjectives do. So follow one person, an article we'll call Priya, second year, through a single GSTR-3B week at a 90-client firm. Nothing about her week is unusual. That's the point.

Wednesday is worth sitting with. Priya's 10 am call to a client about missing e-way bills takes four minutes. The client promises to send them “in ten minutes.” They don't arrive by lunch, so she calls again at 2 pm, gets voicemail, and sends a WhatsApp instead. The bills land at 4:30 pm, as seven separate images with no client name in the filename. She spends another six minutes renaming and filing them correctly so the reconciliation makes sense to whoever reviews it. Total time spent on one client, one missing item: roughly twenty-five minutes, spread across four separate touches, none of which appears anywhere as “twenty-five minutes.” It appears as four small gaps in a day that otherwise looks unaccounted for.

Add it up and Priya spent 8.5 of her week's roughly 40 working hours, over a fifth of her time, chasing rather than reconciling. She is not unusually slow, and her firm is not unusually disorganised. This is what the chase looks like at ordinary scale, before anyone has tried to fix it.

Each event, a different list

The lists differ by event, by entity type, and by client. But they are knowable. Nothing about “which documents does this client owe us for this deadline” requires professional judgment. It's lookup work. Which means the tracking, and the chasing that follows from it, can be done by software rather than by a second-year article on a Wednesday afternoon.

Run the audit yourself, this week

You don't need a consultant or a new system to see the scale of this at your own firm. You need one week and a shared spreadsheet. Here's the method, in full, something you could start on Monday.

1. 1Pick one week during a live cycle, not a quiet one. A slow week hides exactly the problem you're trying to measure.
2. 2Give every team member, article to partner, one line to fill in per interaction: client name, channel (WhatsApp / call / email), what was asked or chased, and minutes spent, including the wait, not just the talking.
3. 3Log everything, even the interactions that feel too small to count. A two-line WhatsApp asking “any update?” counts. A call that went to voicemail counts.
4. 4At the end of the week, sum minutes by client and by staff member, not just as one grand total. The distribution across the book usually matters more than the average.
5. 5Compare total chase hours against hours actually billed or billable that same week. Most partners who run this for the first time are surprised by how close, or how lopsided, that ratio turns out to be.

Three lines don't prove anything. Two hundred lines, from one real week at your own firm, usually do. Firms that run this audit typically find the chase eating somewhere between 15% and 35% of total staff hours during an active filing week, concentrated in a predictable 10-15% of the client book. That second number matters as much as the first: most of the problem sits with a small, identifiable group of clients, not the whole book equally, which is exactly why a blanket fix works better than blanket effort.

What the fix looks like

1. 1One connected intake: clients keep sending to the firm email and WhatsApp they already use, and everything forwards into one system, never a portal they have to learn or a new number they have to save.
2. 2Automatic identification of whatever arrives: this file is a Form 16; this photo, taken at an angle with no filename, is April's bank statement, not May's.
3. 3A checklist per client per event, generated from the compliance calendar itself, not maintained by hand in an Excel sheet that only one person on the team fully understands.
4. 4Automatic, polite follow-ups that fire on a fixed schedule and stop the moment the document lands, so nobody has to remember who still owes what.
5. 5One firm-wide view of what's missing, sliced by deadline and by client, so a partner can see a shortfall on day three instead of discovering it the day before filing.

The hours don't disappear from the firm, they move. The same people who were spending a third of the week asking spend it reviewing, reconciling, and advising instead, work that's billable, and work that clients actually feel.

Isn't chasing clients just part of running a practice?

Some of it, yes, a firm will always need to ask clients for things. What's not inevitable is *how much* of that asking is repetitive, unstructured, and undocumented. Asking once, clearly, and tracking the answer is part of the job. Asking the same client for the same e-way bill four times across three channels, because nobody wrote down that the first two asks went unanswered, isn't professional judgment. It's a process gap wearing a busy schedule as a disguise. The goal isn't to strip out the relationship-building side of client contact; it's to stop spending that contact on things a checklist could have tracked without a person involved at all.

Why not just hire more support staff instead of automating the chase?

Because it doesn't fix the ratio, it just makes the ratio more expensive. A firm that hires a coordinator to chase documents by phone and WhatsApp has added a salary to solve a problem that scales with the client book: every new client still adds follow-up load, now split across more people instead of concentrated in fewer. Headcount is the right answer for judgment work, reviewing a reconciliation, advising a client, signing a return. It's an expensive way to remember that Kapoor & Co still hasn't sent April's e-way bills, and it caps out the same way the original problem did, just with a higher payroll attached.

Doesn't automating the chase feel impersonal to clients?

Less than the alternative, in practice. What clients experience as impersonal isn't a system sending a reminder, it's being asked for the same document four times because nobody kept track of what they'd already sent, or getting a vague broadcast that never says what's actually missing. A specific, well-timed reminder that stops the moment a document arrives reads as *organised*, not automated. The relationship-building still happens, just in the phone call reserved for the client who's genuinely struggling that month, instead of being spent re-explaining what a sales register is for the third time in a row.

The compounding payoff

Fixing intake isn't just a season-survival tactic. Chasing is the reason many firms cap their client book: every new client adds follow-up load to people already saturated. Move the chase to software and the marginal cost of a new client drops to the professional work alone. That's when a practice starts scaling like a business instead of like overtime.

Run the arithmetic on Priya's 8.5 hours a week. Recovered across a filing season, that's the difference between an article who burns out by March and one who has time to actually learn the technical side of the work, the side that makes them worth promoting. Multiply across a team of six, and a 90-client firm gets back roughly a person-year of capacity annually, without a single new hire, and without anyone working a single hour later at night to make up the difference.

The foundation the rest of this series builds on

Every other post in this series, the GSTR-1 week, the TDS quarter, the audit-season document list, the ITR rush, is really the same argument applied to a specific deadline: name the checklist, ask early and specifically, escalate the channel instead of the tone, and let software carry everything mechanical so a human only gets involved where judgment is actually needed. The document chase isn't a separate problem from each of those cycles. It's the problem underneath all of them, and it's the one worth fixing first, because fixing it once pays out on every deadline that follows.