One of the quietest competitive advantages a small agency can build is a well-maintained knowledge base. At Choco Media, our agency documentation system is not the most glamorous part of what we do — but it is probably the thing that saves us the most time each month. When a new project kicks off, when a team member is out sick, when a client asks a question we have answered before, or when we need to onboard someone in the middle of a busy sprint, everything we need is in one place. This post explains why we made that investment, how the system is structured, and the habits that keep it alive.
This is aimed at small agencies, freelancers, and in-house teams who are building or scaling their operations. You do not need a complex tool or a dedicated ops person. You need a clear structure, a consistent habit, and the discipline to write things down even when you are busy — especially then.
The payoff is real. Onboarding new people becomes faster. Clients get more consistent communication. Decisions get made faster because the reasoning behind past choices is already written down. And when something breaks, the fix is already documented.
Why Most Agency Knowledge Gets Lost
The default state for most small agencies is that knowledge lives in people’s heads. The senior person knows how the client likes their reports formatted. The account manager remembers why a particular approach was chosen six months ago. The contractor who built the tracking setup knows where all the tags are. This works fine until one of those people is unavailable — on holiday, sick, or gone.
What we typically see in client work is that the knowledge loss happens gradually and then all at once. A team works well for a year. Then someone leaves, or the agency grows and brings in new people, and suddenly no one can find the information that used to live in someone’s inbox or memory. The cost is not just time — it is client confidence and internal morale.
- Tribal knowledge makes you dependent on specific people being available
- Repeated onboarding conversations for every new team member or contractor
- Inconsistent client deliverables because no one agreed on the standard
- Time lost re-explaining context that should already be written down
- Decisions re-litigated because no one recorded why the original choice was made
The knowledge base is the fix. Not a perfect fix — documentation requires maintenance — but a structural one.
What Belongs in an Agency Knowledge Base
The most common mistake is trying to document everything before you document anything. That produces a knowledge base that is 80% aspirational and 20% useful. We took the opposite approach: start with the things that cause the most pain when they are not written down.
Client context
Every active client should have a page that covers: what they do, who the main contacts are, what their goals are for the engagement, what tone they expect in communication, any non-obvious preferences, and the history of major decisions made together. This is not a contract — it is a living document you update as you learn more about the client.
Process documentation
The recurring things you do — onboarding a new client, producing a monthly report, running a campaign audit, offboarding — should be documented as checklists or step-by-step guides. This is the category that pays off fastest because these processes repeat constantly.
Decision records
When you make a significant decision — to use one tool over another, to structure pricing a certain way, to adopt a particular methodology — write a brief note that records what you decided and why. This single habit eliminates a surprising number of repeated debates.
Templates and standards
Document the formats you use: report templates, email structures, brief formats, proposal layouts. These belong in the knowledge base alongside instructions for how to use them.
- Standard operating procedures for recurring deliverables
- Client-specific preferences and history
- Tool documentation and access information
- Brand and voice guidelines for internal and client content
- Decision logs for major strategic or operational choices
The Structure We Use
We run our knowledge base in Notion. The tool matters less than the structure, but Notion works well for us because it supports linked databases, nested pages, and good search. The top-level structure is simple:
Agency HQ
This is the home page. It links to every major section and includes a short summary of what each section contains. When someone joins the team, this is the first page they see. It needs to be clean, accurate, and navigable in under two minutes.
Clients
One database entry per client. Each entry is a page with sub-pages for context, active projects, meeting notes, and a decision log. The database has fields for engagement status, tier, renewal date, and primary contact so we can filter and sort without digging.
Processes
A library of SOPs — standard operating procedures. Each is written as a numbered checklist with a brief explanation of why each step matters. We tag each SOP by function (content, paid media, reporting, operations) and by frequency (weekly, monthly, project-based).
Templates
Every reusable format in one place. Report templates, brief structures, email scripts, proposal sections. Each template has a short note on when to use it and what to customise.
Tools and access
A record of every tool we use: what it does, who has access, where credentials are stored (we use a password manager and link to the relevant vault, not the credentials themselves), and any non-obvious quirks.
The knowledge base does not need to be perfect. It needs to be good enough that someone can pick up where another person left off without a handover call. That is the only benchmark that matters.
The Documentation Habit That Actually Sticks
Documentation habits fail for one reason: writing things down feels like extra work when you are already doing the work. The fix is to make documentation part of the work, not a separate step after it.
The simplest version of this is what we call “document on exit.” When you finish a task — setting up a campaign, writing a client report, onboarding a new tool — you spend five minutes updating the relevant page in the knowledge base. Not writing a dissertation. Just updating the checklist, adding the decision you made, noting the thing that was non-obvious.
A second useful habit is the post-project review. At the end of each engagement or major project, we spend thirty minutes as a team asking: what was not documented that should have been? What did we figure out during this project that we will need to know again? Those answers go into the knowledge base before the project is closed.
- Document on exit: update the relevant page immediately after completing a task
- Post-project review: capture learnings before closing out an engagement
- Monthly audit: scan for outdated pages and flag or update them
- New hire test: ask new team members to find information using only the knowledge base and note where they get stuck
How AI Has Changed Our Documentation Workflow
In the past year, AI has made maintaining our knowledge base noticeably faster. The main change is that we use AI to draft the first version of any new process document. We describe the process in a voice note or a rough bullet list, feed it to our AI tool of choice, and get a structured SOP draft back in minutes. We then review and edit — which is much faster than writing from scratch.
We also use AI to summarise meeting notes into decision records. After a client call, the notes go in, a prompt produces a structured summary, and we review and file it. The human step is the judgement call — what was actually decided, what context matters for the future — but the drafting is handled.
Our AI automation services for clients follow the same logic: find the repetitive drafting tasks and automate them, so the human time goes toward the things that require judgement. Internal documentation is exactly the kind of task where this principle applies.
One thing we have learned: AI-generated documentation needs a human review before it goes into the knowledge base. Models are good at structure and language, but they do not know what you actually decided or why. That context always has to come from the person who was in the room.
What to Do When the Knowledge Base Gets Stale
Every knowledge base gets stale. Tools change, processes evolve, clients leave, new patterns emerge. A stale knowledge base is almost worse than none because it creates false confidence — someone follows an outdated SOP and makes an avoidable mistake.
The fix is a monthly audit, not a quarterly one. Monthly is often enough to catch drift before it causes problems, and short enough that you can do it in an hour. The audit checklist is simple:
- Review all pages updated more than 60 days ago and check if they are still accurate
- Check tool and access documentation — have any tools changed or been replaced?
- Review active client pages — are contact details, project status, and preferences current?
- Check SOPs against what the team is actually doing — has the process drifted?
- Remove pages that are no longer relevant rather than leaving them to create confusion
The person who runs the audit rotates each month. This distributes the maintenance burden and means everyone on the team has a current picture of what is in the knowledge base.
Using the Knowledge Base for Client Handovers
One of the clearest return-on-investment moments for an agency knowledge base is the client handover. When an engagement ends, we produce a handover document from the client page in our knowledge base — a structured summary of what was done, what decisions were made, how everything is set up, and what the client should do next.
Because the client page has been maintained throughout the engagement, this document takes us about an hour to produce rather than half a day. The client receives something comprehensive. The relationship ends on a strong note. And we have often found that well-offboarded clients come back or refer others, because the handover signals professionalism.
We wrote a detailed post on the client handover document we use at end of engagement if you want the specific template. The knowledge base is the source material that makes that document possible.
Onboarding New Team Members with the Knowledge Base
The onboarding test is the clearest signal of whether your knowledge base is working. When a new person joins — whether a full-time hire, a contractor, or a long-term collaborator — can they get up to speed using the knowledge base alone? Can they find the tools, understand the processes, and pick up an active client without a multi-hour briefing from the most senior person on the team?
If the answer is yes, the knowledge base is doing its job. If the answer is no, the gaps they encounter are your documentation backlog.
We run a structured first week for new team members that includes two full days of knowledge base exploration before any client-facing work. They flag every page that is confusing, outdated, or missing. Those flags become the agenda for a short review session at the end of the week. It is the most efficient way we have found to keep the knowledge base accurate and to give new people genuine context rather than a surface-level briefing.
This connects to our broader approach to onboarding clients in 14 days — the same principle applies internally: structured process, clear documentation, explicit checkpoints.
The Ongoing Investment
A knowledge base is not a project with an end date. It is an ongoing practice. The agencies we see struggle with this tend to treat it as a setup task — something to build once and then leave. That produces a knowledge base that is accurate for three months and useless after six.
The agencies that make it work treat documentation as a professional standard, the same way they treat client communication or financial reporting. It is not optional, it is not extra — it is part of how the work gets done.
For a small agency, the investment is modest: a few hours to set up the initial structure, five minutes per task to maintain it, and an hour a month for the audit. The return — faster onboarding, more consistent delivery, less time lost to repeated questions — pays for itself within the first quarter.
If you are building or rebuilding your agency operations and want to think through how documentation fits into the broader picture, we are happy to talk through it. The knowledge base is one piece of a well-run agency — and it is one of the cheaper pieces to get right.