“It’s fine, I know where everything is.”
You say it on a Tuesday night, scrolling to a tab you built a year and a half ago. The rows are color-coded. One of them is yellow, and it means something specific. You need a second to remember what.
The file works, and it always has, which is the whole problem.
If you have ever thought everything depends on me, you read your business correctly.
The work moves when you open the file or answer the message.
You built the tracker in a quarter when three clients needed you at once, and it kept you afloat. The business grew, and the file grew with it. No calm week ever arrived to teach anyone else how to read it.
So the calm days now feel borrowed. You enjoy them with one eye on your phone.
That file is also proof. Only someone who knows the work cold could have built it. Every column holds a judgment call you got right, over and over. It is a record of your expertise, and one person can read it.
It holds decisions, too. Which client gets the exception. What the yellow row flags. Why one tab hides until the first of the month. None of that is written anywhere except in how the file looks to you.
You have pictured handing it over. You can see the first question coming before they open it, and the second one right behind it. So the file stays with you, and so do the late nights spent updating it.
That is a Hostage File.
A beautifully organized tracker with one reader carries the same risk as a messy one. Color-coding is a private language. Tidying it makes the secret better kept.
Maybe you run a solo practice and nobody else will ever need to open it. It works today. It keeps working until a flu, a family emergency, or a client who needs an answer while you are on a plane.
The file gets expensive the day you bring someone on.
Their first question is where things live. The answer is a file only you can read, so you pay a new person to wait for you to explain it. A contractor works out that it is quicker not to touch it, and stops asking. Clients wait while you hunt for an answer inside it.
The file now has one reader and a growing line of people working around it.
It was built for survival, and nobody updated it once survival ended.
In my experience, a tracker like this outlives the busy quarter that created it by years. It never fails loudly enough to get replaced. It keeps producing, which is exactly why it stays. Its cousin is the process you never wrote down, and what an AI tool does when it meets one: Why Your AI Agent Can’t Fix a Process You Never Wrote Down.
When your attention is the only thing connecting the file to the work, cash flow and client trust both depend on you being reachable. Every day. Including the sick ones.
You leave on Friday. By Monday, a message arrives asking where something stands. The answer lives in the file, so you answer from wherever you are. The week off becomes a week on call with a nicer view.
You prepare for days beforehand and leave notes nobody asked for. You come back to find nothing broke, which should feel like relief and feels like luck.
Luck is a poor foundation for something you spent years building.
The file can stay exactly where it is once it stops needing you.
Picture a Thursday afternoon. Someone on your side opens the tracker, finds what they need, and moves the work forward. You hear about it on Friday, in passing, as something that already happened. The yellow row means the same thing to them that it means to you.
That is a Thursday back. That is a week off where the phone stays in the hotel room.
The yellow row has been waiting for a second reader longer than you have been waiting for a week off.
If you are unsure how much of your business rests on files and memory only you hold, stop and think abut where the business still runs on you instead of through you.

It’s Handled™ | Operational architecture for founders who built the business, and are ready to stop being the infrastructure.
October 13, 2026
Be the first to comment