Picture the week your best operations person is sick. Or on holiday. Or just in back to back calls and not looking at the inbox.
What stops? Not everything. Most work carries on. But a few small jobs quietly stop, and you only notice when a customer asks where their thing is.
This is a coverage problem, and it is the most common one in a small company.
How it shows up
A customer writes in and nobody is sure who answers. A supplier chases payment and the invoice is in someone's personal folder. A quote goes out and the follow up that usually happens on day three simply does not happen.
None of this is dramatic. That is the point. Nothing breaks loudly. A job that depended on one person's memory just does not get done.
Why a holiday rota does not fix it
Most owners answer this with "someone will cover." That works for the obvious tasks. It fails for the invisible ones, the jobs nobody wrote down because the person doing them never forgot.
A cover person cannot do a job they do not know exists.
A short list beats a long manual
You do not need a binder. Ask the person who knows to spend twenty minutes writing the answer to one question: what do I do in a normal week that nobody would notice if I stopped?
Write each item as one line:
The job in plain words. "Chase unpaid invoices over 10 days."
Where it lives. The inbox, the folder, the tool.
How you know it is done. A reply, a payment, a date in the sheet.
Who covers it and what they need to see.
Most people end up with eight to fifteen lines. That page is worth more than most software you could buy this quarter.
Test it before it matters
Pick one job from the list and ask someone else to do it using only the page. Do not help. Where they get stuck is the line that needs more detail.
Then fix it, and do the same with the next job. Doing this for two or three jobs a week gets you most of the way in a month.
Where automation fits
Once a job is written down with a clear finish line, it becomes a candidate for automation. A reminder that fires on day 10. A message that goes out when a form arrives. A flag when something has not moved in three days.
The order matters. Writing it down comes first, because you cannot automate what you cannot describe, and an automation that runs with no owner just fails quietly on a faster schedule.
A small test for this week
Ask each person on your team: if you were out for two weeks, what would stop? Write down the answers without comment. If two people give the same answer, you have found the first job to document.
If you have a job in your business that only one person really knows, tell us in the comments what it is. We build and run AI systems for ops teams, and some of our work is at octyn.co/casestudies.
Top comments (0)