Somewhere along the way, the status update became a ritual. Every Friday, a document goes out. It has a RAG status, a list of completed tasks and a paragraph of carefully neutral language. And every Friday, fewer people open it.
Clients do not stop reading because they stop caring. They stop reading because the report stops telling them anything. When every week says on track in slightly different words, the document becomes wallpaper. The one week it matters, nobody is looking.
I learned this the hard way on a web build years ago. The report said green for six weeks. The client stopped reading by week three. In week seven we hit a real problem, and the first time they properly heard about it was in a meeting they had not expected to be difficult. The report had technically told them. It had not actually told them.
A status update has one job: to let the client make decisions. If it does not change what anyone does, it is administration dressed up as communication.
What to send instead
The format that works is short and slightly brave. Three things. What we need from you. What is at risk and why. What happens next, in plain order. If nothing is at risk, say so in one line and stop. A short honest update earns more trust than a long careful one.
And when something is genuinely wrong, pick up the phone first. The written update should never be the first place bad news appears. The report is the record. The relationship is the channel.
Need someone to get your project over the line?
Project delivery support for brand, digital, and creative teams that need clearer direction and smoother progress.