What do we do when clients expect faster turnaround?

What are clients actually asking for when they say faster?

Three different requests hide inside the same sentence, and they need three different answers. The first is a hard external date: a funder's drawdown, a board meeting, a tender portal that closes at noon, a filing window. That date is real and nothing you do internally will move it. The second is a comparison: the client has had something similar back from somebody else in half the time, and now your timescale looks slow whether or not it is. The third, and the most common, is a request for certainty. The client does not actually need the report on Tuesday. They need to stop wondering whether it will arrive at all.

Firms tend to treat all three as the first kind. They hear a deadline, they say yes, and they absorb the difference out of evenings. Before changing anything, it is worth asking the client which of the three they mean. A surprising amount of pressure comes off when the answer is the third one.

Why does working faster burn out the senior people?

Because the only lever most firms pull is effort. When a deadline tightens, the work does not get redesigned. It gets moved into the hours that were not previously being used, and those hours belong to a small number of people. The same partners and senior associates review everything, sign everything and are the only ones who can finish the difficult parts, so every compressed deadline lands on the same desks.

That lever has a short travel. It works for a quarter, maybe two. Then the quality starts to drift, the notes get thinner, the second pair of eyes stops happening because there is no time for it, and people begin looking at job adverts. It is the pattern described in the partner bottleneck: a queue forms behind the people who cannot be duplicated, and shortening the promised date just makes the queue move faster into them.

There is a quieter cost too. Rushed work produces rework, and rework is invisible on any report because it is never recorded as a separate job. We cover where that lands in the cost of rework.

Where does the time between request and delivery actually go?

Take ten recent deliverables of the same type. For each one, write down three things: the date the client asked, the date it went out, and your honest estimate of the hours of real work inside it. Nearly every firm that does this gets the same shape of answer. A handful of hours of work, spread across a fortnight of elapsed time.

The gap is not laziness. It is structure. It is the days spent waiting for the client to send the missing documents. It is the draft sitting in a review folder until the reviewer has a clear morning. It is the author being pulled onto something more urgent and coming back cold. It is the formatting, the version that went out with last quarter's figures in it, the correction, the re-approval. None of that is work on the client's problem, and all of it is on the client's clock.

This matters because the two numbers behave differently. Effort time can only be squeezed by making people work harder. Elapsed time can be cut by changing the design of the process, and nobody has to stay late for it.

Which parts of the clock can be cut without touching quality?

The parts where no judgement is being applied. That is a longer list than most firms expect.

• The blank page. A first draft assembled from the firm's own templates, the file and the agreed structure removes the single longest pause in most deliverables, which is the wait for someone senior to have a clear stretch of time to start writing. Client reporting and technical reports are where this bites hardest.
• The gap after the event. An inspection, a site attendance or a client meeting produces a record days later, from memory. If the draft record exists the same day, the whole chain starts earlier. See meeting notes and follow-ups and inspection records.
• The chasing. Missing inputs are the most common reason a date slips, and chasing them is usually somebody's memory rather than a system.
• The assembly of known material. Standard sections, methodology, team credentials and prior-period comparisons do not need to be rewritten each time. This is most of the calendar in proposal and bid production, where the deadline is externally fixed and immovable.

Cut those and the deliverable does not become rushed. It becomes ready earlier, with the same amount of thinking in it.

How do you protect the review when the clock is shorter?

By deliberately not compressing it. Review is the part that carries the firm's name, and it is the first thing sacrificed when a date tightens. The point of taking the drafting out is to give the review back its time, not to cut the overall timetable to the bone and call it progress.

Two things keep this honest. A named person signs off anything that goes to a client, every time, with no exceptions for urgency. And reviewers are told what to check rather than left to read everything with equal attention: figures against source, scope against the engagement, anything that reads as advice. Reviewing AI output on client work sets out how to structure that so review does not simply become the new queue.

What do you say to the client in the meantime?

Commit to a date you can hold and tell them what you need from them to hold it, itemised, at the start rather than halfway through. Give them something visible while they wait: a short interim note, a confirmation that an input has landed, a flag the moment something is at risk. Most of the frustration behind "can you do it faster" is silence, and silence is cheap to fix. The firms that lose clients over turnaround are rarely the slowest. They are the ones that went quiet and then arrived late, which is the sequence set out in the cost of a late report.

Where should a firm start?

Pick the single deliverable clients ask about most often, and measure its elapsed time against its effort time for a month. If the gap is wide, you have found work that can be shortened without anyone doing more of it. How to calculate unbillable hours covers the counting, and the capacity calculator shows what those recovered hours are worth across the fee earners who currently absorb them.

Then rebuild that one job rather than the whole operating model. In an engineering consultancy it is usually the gap between attendance and issued report. In a law firm it is more often the client update that never gets written until it is chased. Different deliverables, the same diagnosis. If you want the diagnosis made for you, the audit takes about three minutes and names the process to tackle first.