Yesterday I built a set of onboarding documents for a client, checked them, and got as far as drafting the message they would go out with.
They had already been sent. By me. Days earlier.
Nothing broke. No system failed. Every piece of software involved did exactly what it was told. And I still spent a chunk of a morning producing a second copy of something the client was already holding.
The status field said one thing and the client was doing another
There is a register in my business that tracks where every deal is. It is not fancy. It is a row per client with a status, and I look at it most days.
On the twelfth of this month, a client wrote back and said, in plain words, that they would be going ahead with the proposal. That is not ambiguous. That is the whole thing I had been waiting for.
On the twentieth, the register still said the deal was stalling.
Eight days. During those eight days the client was not going quiet. They had accepted, they had told their own people, and by the middle of last week they had started organising the work internally. Meanwhile my own record of the relationship described someone drifting away from me.
If I had acted on that record without reading the actual thread, I would have written a polite nudge to a person who had already said yes and already started. I have been on the receiving end of that message from a supplier. It reads as though nobody is paying attention, because nobody is.
Then the same defect, one row down
The second one is the part I keep turning over.
Alongside the register I keep notes on what is outstanding for each client. One line said a pack of onboarding documents was still owed. So yesterday I built the pack.
The documents had gone out days before. I had sent them myself, on WhatsApp and by handing them over in a meeting. Both are perfectly normal ways to give a client a document. Both are how a lot of business here actually gets done.
Neither of them writes anything into my notes.
That is the whole failure, and it is not really about being disorganised. My record is assembled from the channels it can read. It reads email. It does not read WhatsApp, and it certainly does not read a conversation across a table. So when something is delivered on one of those channels, the record does not show "delivered by another route". It shows nothing at all, and nothing looks exactly like not done.
I wrote almost this same sentence about my analytics a little over a week ago: absence and zero look identical on a screen and mean opposite things. I found that in a dashboard, fixed the dashboard, and did not go looking for the same shape anywhere else. It was sitting in my client notes the whole time.
Why this is worse than a wrong number
A wrong number in a report is annoying. A wrong status in a client record generates work, and the work is aimed at a person.
Every one of these has a cost with someone else's name on it. A chase sent to a client who already paid. A document re-sent to someone who already has it. A follow-up on a decision that was made a week ago. Each one is a small, private signal that you are not really tracking the relationship, and they add up faster than they should because the client sees all of them and I only see one at a time.
Yesterday's pack never went out, so the client saw none of it. That was luck rather than design. Somebody read the actual thread before hitting send, and the thread is what caught it.
What I have actually changed
Two things, and deliberately small ones, because a big process is the thing that decays first when I am busy.
The status has to name its evidence. Not "stalling", but "stalling, last inbound 12 Aug". If a status cannot say when it was last confirmed and from where, it is an opinion about a client rather than a fact about one. An opinion eight days old looks exactly like a fact eight days old, right up until you act on it.
Anything handed over off-email gets one line, at the time. Not a system. A line. The pack went out on WhatsApp on this date. I lost a morning to not having written eleven words.
What I have not done is try to make the record read every channel. I could connect more sources and I probably will eventually, but that fixes this instance of the problem rather than the class of it. There will always be a channel the record cannot see, because some of the most important things in this business still happen in a conversation. The durable fix is that the record should be honest about what it does not know, instead of rendering silence as a fact.
That is genuinely the same lesson as the dashboard, and today I would rather write it down twice than find it a third time.
There is a business version of all this, which is that most admin work is not slow because people are slow. It is slow because the same detail gets captured in four places, or in none. I wrote the practical version of that argument today: the eight admin jobs every small business still does by hand, and what actually decides whether each one can be automated.
I build systems that stop this happening to other people's businesses. It happened in mine this week. Both of those are true, and pretending otherwise would make this journal worth less than the time it takes to write.
Frequently asked questions
Why not just check the email thread every time?
Because the point of a register is that you do not have to. If I have to read the full history to trust the summary, the summary is not doing any work and I would be better off without it giving me false confidence.
Is this an argument against tracking deals in a system?
The opposite. It is an argument for the system recording where each fact came from and when. A status with no provenance ages badly and gives you no way to tell a fresh one from a stale one.
How did you catch it before the documents went out?
Somebody read the actual email thread before sending. That is the only reason. There was no alert and no check that would have caught it, which is the uncomfortable part.
What would you tell someone with the same setup?
Look at where your business really hands things over. If a meaningful share of that happens on WhatsApp or in person, your written record is describing a smaller business than the one you are running.