Why chasing clients by email quietly costs your firm money

You email a client on Monday and ask for five things: the year-end bank statements, the fixed-asset register, the lease agreement for the new office, the payroll summary, and confirmation of the intercompany balance. On Wednesday, three of them come back in a reply. The other two are never mentioned again. By the following week the whole thread has slid down the inbox, buried under a dozen unrelated messages, and you are left with a nagging feeling that something is still missing. You just cannot remember what.

That feeling is the cost. It is small each time, and it repeats hundreds of times a quarter across your portfolio.

Email has no memory of the request

The core problem is that email was never designed to track a list of obligations. When you send five asks in one message, email treats them as prose, not as five distinct items with five distinct states. There is no place that says “two of these are still open.” The reply comes back with three attachments and a friendly note, and now the accounting of what is left lives only in your head.

So you rebuild it. You scroll back up the thread, re-read your own message, tick off what arrived, and work out what did not. You do this every time you touch the client. A manager doing this across thirty clients is quietly re-deriving the same list, over and over, from a medium that refuses to keep score.

Three things email cannot give you:

• No shared view of what is outstanding. You and the client are looking at different fragments of the same conversation. Neither of you can point at a single, current picture of what is still needed.
• No status per item. A document has either arrived or it has not, but email cannot tell you whether the one that arrived is the right version, whether anyone reviewed it, or whether it was quietly superseded by a later reply.
• No memory of the ask. Once the message is sent, the request exists only as sentences in a thread. When the thread is buried, the request is effectively gone until someone reconstructs it by hand.

Because email holds none of this, the entire job of remembering falls on people. And the people who end up doing it are usually your most expensive ones.

The chase falls on your best people

Chasing is not junior work in practice, even though it should be. It is the manager who knows which client is reliable and which one needs a phone call. It is the senior who can tell, from a glance at the attachment, that the client sent the FY2024 register instead of FY2025. It is often the partner, on a Friday evening, forwarding a two-line reminder because fieldwork is blocked and the deadline is fixed.

Consider the shape of it without inventing numbers. A manager who spends, say, a few hours across a week chasing documents by email is not spending those hours on review, on judgement, on the work only they can do. Multiply that by the weeks in a busy period and a portfolio of clients, and the chase becomes a standing line in your cost base that never appears on any invoice.

The hidden multiplier is context-switching. Every time a reply lands, someone has to stop, open the thread, work out which of the five asks it answers, decide whether it is complete, and either file it or send a follow-up. None of those steps is hard. All of them break concentration. The cost is not the minutes on the clock; it is the review that took longer because it was interrupted six times to sort attachments.

There is a slower cost too. When the trail is an email thread, work compresses toward the deadline, fieldwork starts late, and the write-offs that follow a rushed close come out of realisation. The chase does not just consume hours. It moves the whole engagement later.

What changes when outstanding is a fact

The alternative is not “email harder.” It is to stop treating a document request as a message and start treating it as a tracked item.

In a per-item model, each of those five asks becomes a Request Item: one specific thing, with its own status, its own conversation, and its own versioned files. The item does not depend on anyone remembering it. Its state is stored. When the client sends the bank statements, that item moves to submitted. When you accept it, it moves to accepted. The two that were never mentioned again stay exactly where they were, visibly requested, because nothing moved them.

That is what makes “what is still outstanding” a fact instead of a guess. Outstanding is not something you re-derive by scrolling. It is read directly from the stored, audited status: an item is outstanding when it sits at requested or needs revision, and it is done when it has been accepted. Your worklist reads that number. The client’s portal reads that number. A reminder that goes out reads that number, so it only chases what is genuinely open and never asks for something already sent.

The relationship with the client improves for the same reason. Nobody enjoys being chased for a document they emailed last week, and nobody enjoys sending that chase. When the status is shared and accurate, the awkward “did you get my file?” exchange disappears. Both sides are looking at the same live list. For more on building that rhythm without burning out your team, see getting client documents on time.

The leak you can actually close

The reason this cost stays hidden is that it never arrives as a bill. It is absorbed, quietly, as senior hours that could have been billable, as reviews that ran long, as deadlines that slipped from comfortable to tight. Add it up across a quarter and it is one of the larger leaks in a professional-services firm, precisely because no one is looking at it.

You cannot fix it inside email, because the problem is email. What you can do is move the request out of the inbox and into a place that keeps score for you. Clivanta is built on that single idea: the Request Item, not the message, is the unit of work, and its status is stored, audited, and read by everything downstream.

Chasing clients will never be zero. But it should not be your best people’s second job.