The bill that never gets printed.

Every business has someone who knows how things actually work. Not the org chart version. The real one. How a refund gets done when the customer paid by bank transfer from abroad. Which supplier needs a phone call instead of an email. What to do when the intake form arrives half empty on a Friday.

Nobody hired her for that. It accumulated. And because it accumulated, it never shows up anywhere a business counts cost. There is no line for the dozens of interruptions a week, the messages that open with “quick question”, the work that sits still while she is on holiday.

The most expensive person in the business is the one everyone asks. Her bill never gets printed.

The cost is real, and it is hidden twice. Once in her week, which fills with other people's questions until the work she was hired for happens in the evenings. And once in the queue that forms behind her: the requests that wait, the customers who wait with them, and the new hire who learns that asking is a burden and starts guessing instead.

Then she takes two weeks off, and the business finds out what it was paying her for. The refunds pile up. Someone guesses at the supplier and gets it wrong. A customer waits nine days for an answer that takes her four minutes. Nobody does anything careless. They just do not know what she knows, and nobody ever wrote it down, because there was never a moment when writing it down was more urgent than doing it.

The usual fix is documentation, and everyone knows how that goes. A page written once, by the person with the least time to write it, accurate for a quarter and read by almost nobody. Documentation fails for a simple reason. It asks the busiest person in the building to do a second job, in a format nobody uses, about work she could do faster than she could describe it.

Documentation asks the busiest person in the building for a second job. That is why it never gets written.

Talking is different. Most people who cannot find an hour to write a process can explain it out loud in ten minutes, because explaining is what they do all day anyway, one interruption at a time.

The better starting point is a conversation. She describes the job to the assistant she already works with, in plain words, in a short interview: the steps, the systems, the exceptions, who signs off on what, and what done looks like. If she has an old checklist, she shares it first, and the interview only asks where real life differs from the page. What comes back is one draft procedure where every line says where it came from - something she said, or something her checklist said.

Then an admin approves it, and the agents they choose can run it. That split matters more than it looks. The person who knows the job is its author. The person accountable for the business decides whether agents may act on it. Nobody's knowledge goes live just because it was written down, and nobody has to write it in a form only engineers can read.

Knowledge comes from the person who does the job. Permission comes from the person who answers for it.

What changes is the queue. The routine version of the job no longer has to wait for her. She remains the person to ask about the strange cases - the transfer from a country nobody has seen before, the supplier who just changed hands - and those are the cases that deserve her attention. Her week starts to look like the job she was hired for, with the judgment calls on top, which is where her judgment was always worth the most.

The bill that never gets printed is paid in someone's week. Teach the job once, in her own words, and the week can come back.