What does a late client report really cost a firm?

What does a late report actually look like?

It is almost never a report that never arrives. In most firms lateness is a matter of days, and it takes one of three shapes.

The first is the report that slips. It was due on the last working day of the month and it went out on the fourth of the next one, after two internal reminders and a holding email to the client. The second is the report that lands on time but only because someone worked late on it. The date was met; the cost was paid in someone's evening and in the checks that got skipped. The third is the quiet one: the report that arrives on the agreed date but describes a position that was true three weeks earlier, because the cut-off for information had to be early to leave room for production.

All three are treated as normal. None of them appears anywhere as a cost. That is the problem: the firm pays regularly, and in several currencies, for something that shows up in no report the firm produces about itself.

What does the client take from it?

A client rarely reacts to one late report. They form a view over several. The view is not that the firm is disorganised, which would at least be arguable. It is quieter and more damaging: this firm is busy with someone else.

That impression changes behaviour before it changes contracts. Someone who thinks they are second in the queue stops asking for the small extra piece of work, because they assume it will not come back quickly. They involve the firm later in decisions, once the options are already narrowed, which is when advice is worth least. And when a panel review or a fee negotiation comes round, they arrive with a general sense that service has drifted, without a single incident they can name.

Timing matters more than quality here. A report that arrives after the decision has been taken is not late. It is redundant, however good it is. For board reporting the value collapses the moment the meeting it was meant to inform has happened. We go into that production problem in board and management reporting.

What does lateness cost inside the firm?

The internal cost is bigger than the external one, and easier to see once you look for it.

Start with the chasing. Every late report generates its own small administration: the email asking where it is, the reply promising Thursday, the diary note to check on Thursday, the apology. None of it is billable and most of it involves senior people, because chasing needs authority and apologising needs the relationship owner.

Then there is compression. When production runs late, review gets squeezed. The reviewer reads in twenty minutes instead of an hour, or reads half, or signs off because the author is usually reliable. This is where risk enters. The firm has not decided to lower its review standard; it has run out of clock. Reports that go out under time pressure are the ones carrying last quarter's figures in a table nobody refreshed.

And there is the queue. A report that runs late does not only take its own time. It pushes the next thing back, and the next, until the week is spent recovering from Monday. That is the pattern we describe in the partner bottleneck: work only a few people can finish, piling up behind them.

How would you put a figure on it without guessing?

You do not need a study. You need one honest month.

Pick a reporting cycle the firm runs repeatedly: monthly client reports, quarterly reviews, whatever recurs. For that cycle note three things. How many hours went into assembling the report rather than thinking about it, meaning gathering figures, formatting, chasing colleagues for sections and fixing the template. How many hours went into chasing and apologising when it slipped. And who did those hours, by seniority.

Then apply the arithmetic: hours per week, multiplied by the number of fee earners doing them, multiplied by your own charge-out rate, multiplied by 46 working weeks. The guide to calculating unbillable hours sets out the method and the unbillable hours calculator does the sums. That figure is the visible part only. The work you were never asked to do cannot be counted, but you now know which direction it points.

Why does pushing people harder make it worse?

The usual response to late reporting is management attention: an earlier internal deadline, a tracker, a weekly stand-up on report status. These work for a while and then stop, because they add supervision to a process that was never short of effort.

Reports are late because of how they are produced. The data sits in three systems and has to be pulled by hand. The template has drifted, so each report starts by fixing the last one, a decay set out in why templates rot. Three people contribute sections in different styles and someone reconciles them. Every one of those steps is assembly, and assembly expands to fill whatever time is left. An earlier internal deadline moves the crunch. It removes no step.

What actually fixes it?

Separate assembly from judgement, then rebuild the assembly.

A recurring report has a fixed shape: the same sections, sources, tables and closing summary. That part can be produced automatically, in the firm's own format and language, as soon as the period closes. What cannot be automated is the interpretation: what the numbers mean for this client, what to recommend, what to warn about. That stays with the fee earner, and a named person still reviews and signs off anything that reaches a client.

The change is where senior time goes. Instead of assembling a document and having no time left to think about it, the reviewer opens a complete draft and spends the hour on the part clients pay for. Lateness stops being a scheduling problem because production is no longer the constraint. Client reporting covers how that is built, and technical reports covers the version with figures, site data and appendices attached.

Where should a firm start?

Take the reporting cycle that causes the most internal noise, not the most important client. Read the last three reports side by side and mark every element that was identical each time. That is your assembly layer, and it is where the hours are.

Then ask the relationship owner one uncomfortable question: when did we last send this early? If nobody can remember, the firm has been paying quietly for years. The audit will tell you what those hours are worth and whether reporting is the first thing to rebuild, or the second.