Documents and knowledge
Help new hires find answers in your own files
A searchable knowledge base built from your contracts, policies, and records cuts onboarding time and stops repeated questions.
· 4 min read · Document AI · Onboarding · Knowledge management · Process efficiency
The real cost of onboarding without a knowledge base
When a new property manager joins a firm in Surrey, they need to know the lease templates, the complaint process, the vendor contact list, and the rules for each building. Right now, those answers live in email, old spreadsheets, shared drives, and the heads of people who've been there five years. The new hire asks the same questions ten people asked before them. Each time, a senior person stops their work to explain.
A dental clinic in Kelowna has the same problem. A new hygienist needs to know the sterilization protocol, the insurance coding rules, the patient consent forms, and how to handle a complaint. Those answers are scattered across PDFs, old notebooks, and conversations. The practice manager ends up explaining the same thing to every new person.
This isn't a failure of training. It's a failure of organization. The knowledge exists. It's just not in a form that new people can search.
How a searchable knowledge base works
Instead of asking a colleague, a new hire types a question: "What's our lease renewal process?" or "How do we handle a noise complaint?" The system searches your actual files—contracts, policies, manuals, past records—and returns the relevant sections with page numbers and document names. The answer is cited, so the new person knows exactly where it came from.
This works because your documents already contain the answers. You're not creating new content. You're making the content you already have findable.
A plumber in Richmond has 15 years of job records, invoices, and past quotes. A new estimator can search "What did we charge for a water heater swap in 2022?" and get actual examples from the files. A distributor in Calgary has vendor contracts and pricing agreements. A new buyer can search "What's our payment term with Supplier X?" and see the contract.
The knowledge base learns from your documents, not from a generic internet source. It knows your specific rules, your specific history, your specific way of doing things.
What gets faster
Onboarding time. A new hire typically needs two to four weeks of questions answered by senior staff. With a searchable knowledge base, they answer 60 to 70 percent of those questions themselves in the first week. The remaining questions are ones that need judgment or a conversation—exactly the ones worth having.
Consistency. Right now, different people explain the same rule different ways depending on who's available and what they remember. A knowledge base gives everyone the same source of truth. A new accountant in Burnaby learns the expense policy the same way whether they ask in their first week or their tenth.
Interruptions. An accounting firm with 12 people in Gastown loses roughly 5 to 10 hours a week answering repeated questions from new staff, contractors, and people who forget. A knowledge base doesn't eliminate those conversations, but it cuts them by half or more.
What takes work
You need to gather your documents in one place first. If your contracts are in three different shared drives, your policies are in email, and your procedures are in someone's notebook, the knowledge base can't help. This is usually the first week of the project.
You also need to decide what goes in. Not every email or memo belongs in a knowledge base. A good one contains your actual rules, templates, contracts, and reference materials—the stuff people genuinely need to know. Your team should help decide what's in and what's not.
After it's built, someone needs to add new documents as they're created. This is usually 30 minutes a month for a firm with 10 to 20 people. It's part of your normal filing process, not extra work.
When this is worth doing
A knowledge base makes sense if you have:
- More than four or five people, so onboarding happens regularly.
- Documents that people actually need to reference—contracts, policies, procedures, templates, past records.
- A high cost to repeated questions. If your senior people spend 5 or more hours a week answering the same things, the payback is quick.
- Staff turnover or contractors who come and go.
If you're a solo practitioner or a two-person team, the overhead of building and maintaining a knowledge base probably outweighs the benefit. If your business runs on conversations and relationships rather than documented rules, a knowledge base is less useful.
Where to start
- Spend one afternoon listing the documents people actually ask about. Ask your team: "What do new hires ask about most? What do they search for in email?" Write down 20 to 30 documents that would answer those questions. This tells you whether a knowledge base is worth building.
- Pick one folder or category to start with. Don't try to organize everything at once. Start with your most-asked-about category—lease templates, expense policies, vendor contracts, whatever it is—and build a small knowledge base with just those documents. You'll learn what works before you commit to the whole thing.
- Talk to someone who's built one before. Ask a vendor or consultant to walk you through a 30-minute conversation about what the project actually takes: time, cost, and ongoing work. Get a real number, not a range.