Knowledge base
also known as internal wiki
A central, organised store of an agency's documented processes, templates and answers - so information is found, not re-asked.
For example, an agency keeps its SOPs, brand guidelines, client preferences and common answers in a searchable knowledge base. A new hire finds how things are done without interrupting a teammate, and quality stays consistent.
Why it matters to agencies: a knowledge base turns scattered, in-someone's-head information into a shared asset, which is the backbone of onboarding, delegation and consistent delivery. It reduces repeated questions and key-person risk, and it is often where SOPs and templates actually live.
What a useful knowledge base needs
- A clear structure and search
- An owner per area
- A review cadence
- Templates for common docs
- Easy access for the whole team
- A dumping ground no one can search.
- Letting it rot until no one trusts it.
- No owner, so nothing stays current.
What is a knowledge base?
A central, organised store of an agency's documented processes, templates and answers - so information is found, not re-asked.
What goes in an agency knowledge base?
SOPs, templates, brand and client guidelines, tool how-tos and FAQs - the documented answers a team reaches for repeatedly.
Why do agencies need a knowledge base?
It speeds onboarding, reduces repeated questions, keeps delivery consistent, and lowers the risk of knowledge walking out the door.
How is a knowledge base different from SOPs?
SOPs are the step-by-step procedures; the knowledge base is the organised place those procedures and other reference material live.