Team Systems
A small team runs on what is written down. Without documentation, every question routes to the founder and nothing survives a holiday. This hub covers the minimum viable operating system for a team of two to ten.
Reviewed by a qualified professional
James Whitfield — FCCA, Chartered Certified Accountant — 18 years advising UK SMEs on employment costs, payroll and business finance. Reviewed 5 August 2026.
Last updated 2 August 2026
Where are you stuck?
Overview
Why documentation matters at this size
A team of two to ten runs on whatever is written down, because there is no layer of middle management to hold undocumented knowledge safely. When everything lives in the founder's head, every absence, illness or busy day becomes a single point of failure for the whole business.
This is not about building corporate process for its own sake. It is about removing yourself as the only route to an answer, so the business can function on a day you are unreachable, and so a new starter can become useful in weeks rather than months.
The test of good documentation at this size is simple: could someone competent but new answer a common question correctly using only what is written down? If not, the knowledge is still trapped.
The order to work through it
Start with the questions you answer most often, not with an ambitious plan to document everything. Ten short answers to your ten most frequent questions will do more good in a week than an unfinished attempt at a full operations manual.
Once the frequent questions are covered, move to the processes that would cause real damage if done wrong while you were away — payments, customer-facing commitments, anything safety- or compliance-related. Frequency first, consequence second.
Only after those two categories are reasonably covered does it make sense to build out a fuller knowledge base structure, meeting rhythms and access registers. Structure imposed too early tends to sit empty because there is not yet enough content to organise.
Common failure modes
In Kayley's experience, the most common failure is writing a document once and never assigning an owner or a review date, so it quietly goes stale and the team stops trusting it — at which point everyone reverts to asking the founder anyway.
A second failure is writing procedures for a filing cabinet rather than for the person doing the job: too long, too formal, and disconnected from how the work actually happens day to day. Nobody opens a twelve-page document under time pressure.
A third is leaving access and permissions undocumented until a leaver forces the issue. An access register built only in a crisis is far weaker than one maintained as routine housekeeping.
What to write down
For each recurring process, capture the trigger (when this applies), the numbered steps, the tools needed, the definition of done, and who to ask if it goes wrong. Keep it to a single screen wherever possible.
For access, keep a simple register: system, who has access, at what level, who granted it, and the review date. Include financial access explicitly — bank logins, cards and approval permissions are often the least documented and highest-risk area.
For meetings, write down the smallest set of recurring rhythms that keeps work visible without adding overhead: who attends, what is reviewed, and how long it runs. Most small teams need far fewer meetings than they eventually accumulate.
What "done" looks like
You are in reasonable shape when a new starter can find written answers to your ten most common questions without interrupting you, and when a genuine week away does not require you to be contactable for routine matters.
Every important document should have a named owner and a review date, and should be updated at the point a process changes rather than in an annual clean-up that never quite happens.
Access and leaver controls should be routine, not reactive: when someone joins or leaves, there is a checklist for what gets granted or removed, rather than a scramble to remember what they could see.
The five-minute action
Subtopic map
What this hub covers
Operations manuals
One place that answers how this business does the things it does repeatedly.
How to Create a Small Business Operations Manual (12 min read)SOPs
Short, testable procedures written for the person doing the job, not for a filing cabinet.
How to Write SOPs Your Team Will Actually Use (10 min read)Knowledge bases
Structure, ownership and review dates so documentation does not rot.
How to Build a Knowledge Base That Doesn't Rot (10 min read)Access management
Who can log into what, at what level, and who reviews it.
How to Set Up Team Access Management Without an IT Team (11 min read)Meeting and reporting rhythms
The smallest set of recurring meetings that keeps work visible.
Meeting and Reporting Rhythms for Small Teams (10 min read)Founder absence
Making a week away boring, on purpose.
How to Plan for Founder Absence Without the Business Stalling (11 min read)Starter and leaver controls
Consistent onboarding and offboarding of accounts, cards and data.
How to Manage Starter and Leaver Controls Properly (10 min read)Subtopic map
Guides in this hub
Each guide answers one question in full and ends with something you can write down today.
How to Create a Small Business Operations Manual
Start by writing down the small number of processes that would cause real damage if you were unexpectedly away for a week, using a single-screen format of purpose, trigger, steps, …
Read (12 min read)How to Stop Being the Bottleneck in Your Business
You stop being the bottleneck by finding the specific point where work queues behind you — decisions, money, knowledge, customer relationships, systems or your own availability — a…
Read (11 min read)How to Write SOPs Your Team Will Actually Use
Write each SOP as a single screen: purpose, the trigger that starts it, numbered steps in the order they're actually done, the tools or logins needed, a one-line definition of done…
Read (10 min read)How to Build a Knowledge Base That Doesn't Rot
A knowledge base is a structured, searchable collection of documented processes and answers that lets a team operate without routing every question through the founder. A knowledge…
Read (10 min read)How to Set Up Team Access Management Without an IT Team
Team access management is the practice of controlling who can log into each business system, at what permission level, and ensuring that access is removed promptly when someone lea…
Read (11 min read)Meeting and Reporting Rhythms for Small Teams
Meeting and reporting rhythms are the minimum set of recurring conversations and written updates that keep a small team's work visible without creating unnecessary overhead. Most t…
Read (10 min read)How to Plan for Founder Absence Without the Business Stalling
Founder absence planning is the process of identifying every decision, payment and customer relationship that currently routes through the founder and assigning a named cover for e…
Read (11 min read)How to Manage Starter and Leaver Controls Properly
Starter and leaver controls are the written checklists that ensure every new employee is granted the right access and every departing employee has all access removed, consistently …
Read (10 min read)Featured tool
Founder Bottleneck Assessment
Finds where the business queues behind you across decisions, money, knowledge, customer relationships, systems and absence — and what to move first.
Use the Founder Bottleneck AssessmentTemplate
Team Access Register template
A simple register of systems, access levels, owners, review dates and leaver actions — including bank and card access.
Use the template online or print a copy for your team. No email address is required.
Founder stories
If you have built an operations manual for a team under ten people, we would like to hear what you kept and what you deleted.
Contribute your storyTools for team access and employee spending
Policy first, product second. These are partner products and we may be paid if you use them. Read the risks and the alternatives before the offer.
Tide
Access control includes financial access. Once you have an access register, role-based banking access is the practical way to give a bookkeeper or an administrator what they need without sharing your login.
Tide is relevant once you need someone other than you to see, spend or reconcile business money: role-based Team Access for a bookkeeper, debit Expense Cards for employees, receipt capture and transaction organisation.
This page describes a Tide referral campaign. If you open an account through a tracked link on this site we may receive a referral payment, and you may receive a reward if you meet the campaign conditions. This does not change what we recommend or what we tell you about the product.
Read the full offer record, risks and eligibilityFrequently asked questions
Which processes should I document first?
The ones that are frequent, currently interrupt you, or would cause real damage if done wrong while you were away. Frequency first, risk second.
How long should an SOP be?
Short enough that someone will actually open it. A single screen with numbered steps, the tools needed, the definition of done and who to ask beats a twelve-page document nobody reads.
How do I stop documentation going stale?
Give every document an owner and a review date, and update it at the moment the process changes rather than in an annual clean-up.