Today's business post is about leave requests: the ones that arrive in a WhatsApp chat, get approved with a thumbs-up, and never reach the place where the balance is kept. Writing it reminded me of the same mistake, made in my own business, three weeks ago.
The draft that was ready
On 1 October I asked for a reply to be drafted to a client. A while later I was told the draft was ready.
I opened my email to send it. There was nothing on the thread. The reply had been written, carefully, in a separate chat window, and "ready" meant it existed somewhere. It did not mean it was where I would send it from.
I had to ask twice before it went where it belonged. Nothing was lost in the end. But for a few minutes I was the person scrolling through one tool to find work that should have been waiting in another.
Why "it exists somewhere" is not the same as "it is done"
The words were accurate in a narrow way. The text existed. The trouble is that the status pointed at the wrong place. When someone says a thing is ready, the person hearing it goes to the place where they act on it. If the thing is not there, the status is false, even when the work is real.
That is the leave problem exactly. The request is real. The approval is real. But they live in a chat, and the balance lives in a spreadsheet, and payroll lives somewhere else again. Every step happened. None of it is where the next person looks.
What I changed
It became a rule. A draft is only a draft when it sits on the thread it replies to, ready to open and send. If it cannot be put there, the status has to say so plainly: "in chat only". No more "ready" for work that is somewhere else.
It is a small rule. What it really says is that the record of work is the place where the work gets done, not wherever it happened to be typed. That is the whole idea behind the Business Operating System we build for businesses: one source of truth, so a request, its approval and its outcome are all in the place people actually open.
What I took from it
The cost was not the few minutes. It was the moment of not trusting the status. Once "ready" can mean "somewhere", every "ready" after it gets checked by hand, and that is the admin a system is supposed to remove.
If your team's requests, approvals and replies are scattered between chats and files, the free Business Autopsy maps where they go and what to join up first. Today's post on leave management software shows the same fix applied to leave.
Frequently Asked Questions
What went wrong with the draft?
The reply was written in a separate chat window instead of on the email thread it answered. It was reported as ready, but it was not in the place I would send it from.
What rule came out of it?
A draft is only a draft when it sits on the thread it replies to. If it cannot be put there, the status has to say "in chat only", never "ready".
How does this connect to the Business OS?
A Business Operating System keeps requests, approvals and outcomes on one record, in the place people act on them. Work that happens somewhere else stops being reported as done.