Security2026-11-18·9 min read

What Is a Run Book, and What Goes in One for a Small Business?

A run book lets somebody who is not you keep the business trading. What belongs in it, where to keep it safely, and how to stop it going stale.

A run book is the short document that lets somebody who is not you keep the business trading. It names your suppliers and accounts, says how to get into them, lists who to ring, and sets out what to tell customers - without containing a single password. For a business of one to thirty people it is two or three pages, takes about an hour to write, and costs nothing.

What Is a Run Book, and What Goes in One for a Small Business?

A run book is the short document that lets somebody who is not you keep the business trading. It names your suppliers and accounts, says how to get into them, lists who to ring, and sets out what to tell customers - without containing a single password. For a business of one to thirty people it is two or three pages, takes about an hour to write, and costs nothing.

It is not a business continuity plan and not a password manager. The plan decides what you will do; the run book holds the facts you will need while doing it. The password manager holds the keys; the run book is the map that tells a stressed person the manager exists, whose account it sits under, and how a trusted second person gets in. Keep it somewhere that survives the thing that broke: a sealed printed copy away from the office, plus a digital copy reachable from a borrowed computer.

Adam's piece on writing the run book before you need it argues why you need one. This is the practical half: what goes in, where it can safely live, and how to keep it true. It sits under our guide to business continuity for small business.

What actually goes in a run book

Six blocks, in roughly the order a bad morning asks for them.

  • Your providers, one line each. Website host, domain registrar, internet, phones, payment terminal, accounting file, email. Each line takes this shape: what it is - who provides it - the account number - their support number - the email address the account is registered under. That last field is the one nobody records and the one that decides whether you can reset anything.
  • How to get in, without saying what the password is. Which password manager you use, whose account it lives under, and who is set up as an emergency contact on it. Where the printed recovery codes are. Which account resets which other account. See our note on account recovery codes if you have never printed a set.
  • Who holds admin on what. One line per system, naming the person or contractor who controls it. This is where the uncomfortable discoveries happen, and it doubles as your access review - Adam covers the pattern in who still has the keys.
  • Where the data is and how to reach it. Which backup service, which account, who can restore it, and roughly how long a restore takes. Not the backup itself, just the directions to it.
  • Who to ring. Bank, insurer, accountant, IT support, landlord, your two largest customers, with mobile numbers that work outside business hours. Then the official channels: ReportCyber for cybercrime, and IDCARE if identity information is caught up in it. Our note on writing an incident contact list covers the format.
  • What to say, in advance. Three or four sentences for the website, the voicemail and the socials if you were offline for a day. Write them calmly now. Nobody writes well at 6am with a dead server, and the wording you improvise under pressure is the wording that gets screenshotted.

What does not go in: passwords, MFA seeds, card numbers, or client data. A run book is a map, not a key. That is what makes it safe enough to print. There is a one-paragraph version too.

What it looks like at different sizes

Those six blocks stay the same at every size; the weight moves around.

  • Sole trader or two-person business. A page and a half, and the hardest block is "who to ring", because the honest answer is often nobody. Name a real person anyway - a partner, an adult family member, your accountant - and tell them the run book exists and where the sealed copy is. A document nobody knows about has already failed.
  • Five to fifteen staff. The admin block gets long and starts contradicting itself. This is the size where two people each think the other one renews the domain, and where a second administrator and a break-glass account stop being theoretical.
  • Trades and mobile businesses. Yours is mostly phones and field access, not servers: the fleet, the SIM plan, the job-management app. Keep a copy in the ute.
  • Anyone with a shopfront. Add the key holders, the alarm code holder, the landlord's after-hours number and the EFTPOS provider. Fire and flood are availability events too, and the insurer's first real question is what you lost, which is why the asset register belongs alongside it.

What a scan can and cannot see here

Nothing we scan will ever tell you your run book is missing, and that is worth saying plainly. Our ongoing scanning reads your public-facing posture - domains, DNS, certificates, email authentication, security headers - and the free Basic Scan checks seven of those public records once and emails the result back. Both look at the outside of the business. A run book is entirely on the inside.

The one tool that does part of this job is the password manager you already have. Bitwarden's emergency access hands your vault to a nominated contact after a waiting period you set, unless you decline first. 1Password's Emergency Kit is a printable PDF of your account details and secret key, meant to be filled in by hand and kept with your passport rather than on the machine. Both are third-party features, and either one turns "the keys are locked inside the thing that broke" into a solvable problem.

Government guidance exists too, with a caveat. ASD's Australian Cyber Security Centre publishes Business Continuity in a Box, built with the United States CISA, covering how to stand up interim email and applications mid-incident. It targets organisations of roughly 10 to 300 people, its applications half assumes intermediate cloud knowledge, and the ACSC says it cannot replace a continuity plan in its entirety. For a five-person business, take the shape of the thinking and leave the tenant provisioning.

Where it lives, and why not a shared document

A run book is exactly the inventory an attacker would like to find: every provider, every account, every admin, every recovery path, in one tidy file. Storage is a security question, not a filing one.

Do not put it in a shared Google Doc or a network folder everyone can read. Do not email it to yourself, and do not pin it in a team chat. Each of those means one compromised mailbox hands over the map of the whole business, and ASD reports cybercriminals running an aggressive campaign of credential theft, buying stolen usernames and passwords from the dark web to reach personal email, social media or financial accounts (ASD, 2025). A mailbox is never just a mailbox; it is the reset path for everything else.

Three places, deliberately chosen:

  • A secure note in your password manager. Same vault as the keys, same protection, and your nominated emergency contact inherits it automatically.
  • A sealed printed copy off the premises. Home, the accountant, a safe deposit box, signed across the seal so you can tell whether it has been opened. Paper keeps working during exactly the events that take your systems down.
  • One printed copy on the premises, if you have somewhere lockable. Convenient, and the first copy lost in a break-in or a fire, which is why it is never the only one.

Print the date on page one, in large type. It is the most useful thing on the document.

Building one this week, and keeping it honest

Set aside an hour. Write the six headings and fill in what you know from memory. Spend the rest of the hour on the gaps, because the gaps are the finding: the hosting company you cannot name, the domain nobody is sure who registered, the accounting login pointing at a former bookkeeper's address. Each blank is a real fault you just found for free.

Then protect it from the failure mode that ruins most run books. They are written once, filed, and never opened again. Two years later the emergency contact is a staff member who left in 2024, the "urgent" mobile number rings a dentist in another state, and the hosting company has been bought twice. That document is worse than no document, because whoever is holding it will spend their first hour believing it.

Two habits keep it true:

  • Half an hour in the calendar, twice a year. Read it top to bottom and correct what has drifted. If page one is more than twelve months old, treat every phone number as unverified until someone rings it. Ring three at random; that is the whole test.
  • Edit it at the moment things change. New provider, staff departure, changed accountant: the run book edit belongs in the same sitting as the change itself, not on a list for later.

The cheapest way to find out whether it works is to read it aloud with someone else against an invented scenario, which is what a tabletop exercise is. Every place the reader stops to ask you a question is a line the run book was missing. It also settles whether the backups block is accurate, a different question from whether the backups run: see how often to test your backups.

When a run book is not enough

A run book answers "who do I call and how do I get in". It does not answer "what are we going to do", and it does not get anything back on its own. Those are jobs for the wider plan - the scenarios, the priorities, the recovery targets - which belong in a business continuity plan, with the run book as its reference section.

It also does not help if the underlying resilience is not there. A perfect map to a backup nobody has ever restored is a perfect map to a disappointment. And if the business genuinely cannot run without one person, documentation reduces the damage without removing the risk; Adam's piece on the bus factor of a five-person business is honest about where paper stops helping.

Be realistic about scale, too. The average self-reported cost of cybercrime to an Australian small business was $56,571 in FY2024-25 (ASD, 2025). An hour with a blank page does not cover that. What it removes is the part of a bad week that is pure friction, so the time and money go to the actual problem.

Start it this week. And if you would rather begin with something a tool can measure, the free Basic Scan checks seven public records on one domain and emails you the result. It will tell you nothing at all about your run book, which is rather the point.


Sources

#security#australian-business#small-business