Ask a delivery team where their week goes and they will tell you about the work. Ask them to track it for five days and something else shows up.
The same piece of status gets handled four or five times before it reaches the person who asked for it.
Follow one update through a week
A developer finishes a task on Tuesday. Here is what typically happens to that single fact:
- They move the ticket. That is the system of record, and it is the only step anyone would call “reporting”.
- They mention it in standup, because nobody trusts the board to be current.
- The PM types it into a running notes doc, because the board does not explain why it took longer than expected.
- On Thursday the PM copies it into the client’s status template, reworded, because that client wants outcomes rather than tickets.
- On Friday it gets summarised again for an internal delivery review, this time next to four other projects.
Five handlings. One fact. And every handling is a chance for it to drift out of sync with the other four.
Why it never shows up in a plan
Because no single instance of it is expensive. Moving a ticket takes seconds. Typing a line into a doc takes a minute. Nobody has ever put “reformat Tuesday’s update for the client” on a sprint board, and nobody ever will.
It is spread thin enough across the week that it feels like the texture of the job rather than a task. That is exactly what makes it durable. Costs that are visible get argued about and eventually fixed. Costs that are invisible just get absorbed, and they get absorbed by whoever has the most context — which is your most experienced person.
The duplication is the problem, not the reporting
This is where most attempts to fix it go wrong. A team decides reporting is the problem, so they add a template, or a new board view, or a weekly form. Now there are six handlings instead of five.
The thing worth attacking is not that status gets reported. Clients need status. It is that the same information is entered by hand in more than one place, in a different shape each time, by someone senior enough to make the judgement calls about wording.
Once you see it that way the question changes. Not “how do we report better” but “where is the single place this gets captured, and what can generate the other four from it”.
A way to see it in your own team
You do not need a tool for this. Take one project and one week, and write down every place a piece of status was typed, pasted or reworded by a person. Do not estimate it from memory — memory is what has been hiding it.
Two things usually come out of that exercise. The count is higher than anyone guessed, and at least one of the destinations turns out to be something nobody actually reads.
That second one is free time. You can stop doing it this week, before you automate anything at all.
Turn repetitive project work into repeatable AI workflows.
Download the free AI Project Delivery Starter Kit — practical templates to improve reporting, meetings, and project communication.