Operations Documentation: What to Write Down First
By the SystemaFlow team · Updated November 2026 · Share this
The person who knows how the supplier payments work is on holiday. Someone finds a spreadsheet called "FINAL v3", a note in an old email and a message that begins "don't forget to". By lunchtime you've decided the business needs better operations documentation, and you've no idea where to begin.
Start your operations documentation with who owns what. Then write up the recurring jobs that stop when one person is away, then where things are kept, then who decides when something goes wrong. You can stop there for quite a while. That's enough to get a business through a bad week.
If a regulator, insurer or major client requires particular documents, those go at the front of the queue, in the format they ask for.
Operations documentation: what counts?
It helps to know you're dealing with four different kinds of document, because they need different handling.
| Type | What it answers | Typical form | How often it changes |
|---|---|---|---|
| Ownership | Who's responsible for this? | One list of jobs with one name beside each | When people or roles change |
| Procedures | How is this job done? | A one-page SOP or checklist | When the job or a tool changes |
| Reference | Where is it, and who do I ask? | An index, contact list or supplier list | Often, in small ways |
| Records | What happened, and what did we decide? | Logs, minutes, trackers | Every time the work happens |
People tend to start with procedures, because that's what "documentation" sounds like. We'd start with ownership. A procedure with nobody's name on it goes out of date quietly, and it's usually the first thing people stop trusting.
What should you document first?
1. Who owns what. List the ten or so jobs that keep the business running, with one named owner and one backup for each. Expect a surprise. When the team at Tamberly Studio, the small design studio we made up for our free pack, went through theirs, nobody's name fitted timesheets. Priya thought Tom collected them. That gap was behind their late invoices.
2. The jobs that stop when one person is away. Go down your list and ask what would sit undone for two weeks if the owner was off. Write those up first, on one page each. What to systemise first has a scoring tool if several are competing.
3. Where things are kept. Files, logins, supplier accounts, templates, the current price list. Say where each one is. This page is quick to write and saves a surprising number of interruptions.
4. Who decides, and who steps in. Which decisions can people make themselves, and who gets the call when something's urgent? Without this, every awkward question comes back to the same desk. If the same emergencies keep coming round, give each one a page using an operations playbook template.
5. The rhythm. When the team plans, checks and reviews. A weekly operating rhythm is also where your documents get checked, so it's what keeps the first four alive.
What belongs in the documents?
Documentation goes wrong in both directions. Some things are missing altogether, and other things get written up that never needed to be. Try sorting these.
Write it, link it or leave it out?
Eight typical items from a small business. Pick a home for each one, then compare your answer with ours.
The steps for paying supplier bills
It recurs, money depends on it and it stops when the usual person is away.
Who covers the shared inbox when the usual person is off
It's one line, and it prevents a very common gap.
What to do if the website goes down
It's rare, but nobody wants to work it out in the moment. Half a page is plenty.
Your accounting software's instructions for raising a credit note
The vendor keeps its help pages up to date. If you copy them, you've taken on that job yourself.
Your staff handbook and policies
They're controlled documents with their own home. Link to them so there's only one version.
Your main client contract terms
Point to the signed version. A summary can drift from what was agreed.
The admin password for the accounts system
Never write passwords in a procedure. Say where the logins are kept.
How you ran a one-off office move last year
It won't repeat in that form. Keep a few lessons learned at most.
0 of 8 answered.
How to write it without a project
You don't need a documentation sprint. Those tend to produce a lot of pages in a fortnight and very little afterwards.
Attach the writing to the work. The next time a job on your list comes round, the person doing it talks it through and writes each step as it happens. A short screen recording is fine as a first capture for anything fiddly, as long as the steps get written beneath it, because nobody wants to watch six minutes to find step four.
Aim for one page each, and keep to one job per page. The one-page SOP template gives you a layout to copy. If a set of pages is becoming a proper reference, how to write an operations manual covers pulling it together, and the operations manual template gives you the structure.
Keep it findable with one index
As soon as you've got more than a handful of documents, make one page that lists them. It only needs four columns.
| Topic | Where it lives | Owner | Next check |
|---|---|---|---|
| Pay supplier bills | Finance folder › Task cards | Named person | A real date |
| Who to call if the website's down | Operations folder › Contacts | Named person | A real date |
| Current price list | Sales folder | Named person | A real date |
A typical layout. Swap in your own topics and names.
Pin that page wherever your team already works. Then give the check dates a home in your monthly review, and go through whichever ones have come due.
Money and client processes deserve more frequent checks than the rest. Beyond that, the honest test is whether someone followed the page recently and it was right. If nobody's opened a document in a year, either the job's gone or the page has. Find out which, and delete it if you can. There's more on the hidden knowledge these pages are meant to catch in invisible workflows.
SystemaFlow™ systems can save you the blank pages. They're done-for-you templates in Word and PDF, not software, so they'll sit in whichever shared folder or tool you already use.
Want the full version?
To keep your documentation findable and current, there's the Operational Clarity pack in the Business Foundations Core Vault. The Shared Team Wiki Map indexes where everything lives, who owns it and when it's due for review. It sits alongside the Team Operating Guide and the Roles and Responsibilities Matrix.
See what's in the Business Foundations Vault →Or get all 352 systems, and every one we add later, with Masterworks: $999, paid once.
Was this helpful?
Frequently asked questions
- What is operations documentation?
- The written record of how a business runs from day to day: who owns each job, how recurring work is done, where things are kept and what happens when something goes wrong.
- What should I document first?
- Start with who owns what. Then write up the recurring jobs that stop when one person is away, followed by where things are kept and who decides or steps in when something goes wrong.
- Where should operations documentation live?
- In the place your team already opens every day, with one index page linking to everything. Word files in a shared folder, Notion and SharePoint can all work.
- How is operations documentation different from an operations manual?
- Documentation is everything you've written down about how the business runs. A manual is that material organised into one structured reference.
- Who should write it?
- The person who does the job, or someone sitting beside them while they do it. Give every document one named owner, who keeps it right after that.
- Should passwords go in operations documents?
- No. Say where logins are kept, such as the company password manager, and keep the passwords themselves out of the document.
