Somewhere in your life or your business there is a job that only one person really knows how to do. It might be the monthly invoice run, the way the shop gets opened on a Saturday, or the odd sequence of clicks that gets the website updated without breaking the contact form. As long as that person is around, nobody worries. The first time they catch a cold, take a holiday or move on, everyone discovers how much was stored in one head. A runbook is the friendly fix, and here are the questions people ask most often when they decide to write one.
What exactly is a runbook?
It is a short, written, step-by-step routine for a task you do again and again. Think of it as a recipe card for work. It says what the task is for, what you need before you start, what to do in order, and what to try if something goes sideways. The word comes from IT teams, who write them for keeping systems running, but the idea works for a market stall, a family budget, a small agency or a volunteer group.
The point is not paperwork for its own sake. The point is that anyone reasonably capable can pick it up and get the same result, even on a bad day.
Which tasks deserve a runbook first?
Start with anything you do more than twice. Then add anything that would hurt if it were done wrong, and anything where the person who knows how is the only one who knows how. A quick filter that works well in practice:
- Is it repeated weekly, monthly or seasonally?
- Would a mistake cost money, trust or a whole afternoon?
- Could a stand-in realistically handle it if you vanished for two weeks?
If the third answer is “no”, that task goes to the top of the list. For a small online business that often means things like publishing a new product page, refunding an order, or restoring a page after a bad edit. For a wider look at how the technology side of a business hangs together, there is a good read on finding your way around the technology a business actually needs that pairs well with this exercise.
How long should a runbook be?
Shorter than you think. One page is a good ceiling for most routines. If it runs to three pages, it is probably two tasks wearing one coat, and splitting it will make both easier to follow. A person under mild stress reads fast and skips, so every step should be one action, written in plain words, with no clever shorthand that only you understand.
Who should write it: the expert or a beginner?
Ideally both, in sequence. The expert talks through the task while a newcomer types. The expert forgets that half of what they do is automatic, and the newcomer keeps asking “wait, how did you know to do that?” Those questions are where the missing steps hide. If you are a one-person operation, do it the other way round: do the task slowly, narrate out loud, and record yourself, then turn the recording into steps.
What should every runbook contain?
A consistent shape helps people find things quickly. Here is a layout that holds up well:
- Name and purpose. One sentence on what it does and when you use it.
- Before you start. Passwords or access, tools, who needs to be told.
- The steps. Numbered, one action each, with what you should see afterwards.
- When it goes wrong. The usual suspects and a first thing to try.
- Who to ask. A role and a backup, not just a name.
- Last checked. A date and who tested it.
Keep the same headings everywhere. People learn the layout once and then read every runbook faster.
Can a runbook cover money tasks too?
Yes, and these are some of the best candidates, because they are routine and because errors are expensive. A monthly routine for checking subscriptions, reviewing what went out of the account and confirming what came in is a classic example. Write it so the person doing it knows exactly which statements to open, what counts as unusual, and where to record what they found. For ideas on what to look for in the first place, take a look at this practical piece on catching small spending leaks before they drain a runway. Your runbook turns that kind of advice into a repeatable habit instead of a once-a-year panic. This is general information about organizing routines, not financial advice.
Where does a data or tech blog fit in?
Data teams have written runbooks for years, since a broken overnight job is far easier to fix with the steps on paper. If that world is new to you, TheDataOps.org is a DataOps blog that data engineers browse for reliable pipeline practice, and it shows the same idea at larger scale. You can borrow the mindset without the jargon.
How do I get people to actually use it?
This is the question that separates a useful runbook from a forgotten file. A few things make the difference:
- Put it where the work happens. Pin it in the team chat, print it and tape it next to the till, or link it from the calendar reminder.
- Make it the first thing you hand a newcomer. If the document is how people learn, it will stay correct, because they will complain when it is wrong.
- Reward corrections. The person who says “step four is out of date” is doing you a favour. Say so.
- Use it yourself. If the author still works from memory, everyone else will too.
How do I keep it up to date?
Give each runbook a review date and an owner, and put the review in the calendar. Also treat every surprise as an edit. If the routine failed on Tuesday because a login screen changed, fix the page on Tuesday while the details are fresh. Over a year, a handful of small edits keeps the document honest far better than a big rewrite you never get around to.
What if the task changes all the time?
Then write down the stable part. Even a chaotic job has a skeleton: who to tell, where the files live, what to check at the end. Capture that, and add a line that says “this part varies, ask whoever ran it last”. A half-useful runbook still beats an empty folder, and you can tighten it as the task settles.
Is it worth the time for a tiny team?
Probably more than for a big one. Large organisations have slack and spare people. With three people, almost every task hangs on one person. An hour spent writing down your most important routine pays for itself the first time somebody is ill or on holiday, and it is the cheapest form of insurance a small business can buy. It also makes handovers painless if you ever hire, sell or step back.
What does a finished example look like?
Here is a deliberately plain one for a shop that sells online, so you can see the tone.
- Open the order list and filter to “paid, not shipped”.
- Print the packing slips and set them out in order.
- Pick each item, check the name and size against the slip, and tick it.
- If anything is out of stock, stop and message the customer using the saved template.
- Pack, label, and scan the parcel into the courier system.
- Mark the order as shipped so the customer gets their email.
- Note any problems in the shared sheet, then tidy the packing table.
Seven lines, no jargon. Someone who has never packed an order could follow it, and that is the test.
What is the first step I can take today?
Pick one task you did this week that you would hate to explain over the phone from a hospital bed. Open a blank page and write the steps as you do it next time. Do not polish. Hand it to someone and watch where they pause, then fix those spots. In a month you will have three or four short runbooks, and the feeling of relief when someone else handles a task without calling you is hard to overstate. That is all this is: good work made repeatable, by anyone, whether you are there or not.
