Skip to main content
Documents and knowledge

Documents and knowledge

Answer new hire questions from your files, not your team

A knowledge base built from your documents lets new staff find answers instantly, without interrupting busy managers.

· 4 min read · Document AI · Onboarding · Knowledge management · Staff efficiency

When you hire someone new, they ask the same questions your last three hires asked. What's the lease template we use. How do we handle late payments. What's the policy on scope creep. Who approves change orders.

Your busy manager answers them again. And again. Each time, the answer takes 10 minutes to dig up, explain, and make sure the new person actually understood it.

There's a better way. You already have the answers. They're in your contracts, your policy documents, your past emails, your client files, your project records. They're just scattered across folders, drives, and inboxes. A new hire doesn't know where to look, so they ask a person instead.

A knowledge base solves this. It's a searchable collection of your documents, indexed so a new person can ask a question in plain English and get back the relevant sections with page citations. "What's our process for handling tenant disputes." The system finds your dispute resolution policy, your standard letters, the relevant clauses from your lease template, and tells the new hire which page each answer came from.

The new hire can read the source material themselves and feel confident they have the real answer, not a summary or someone's interpretation. Your manager gets back 5 to 10 hours a week that used to go to answering the same questions.

Who this works for

This approach works best for firms where knowledge lives in documents. A property manager in Surrey with 15 years of lease templates, dispute records, and maintenance checklists. An accounting firm in Burnaby with client files, tax strategies, and audit templates. A strata council with bylaws, meeting minutes, and vendor contracts. A dental clinic in Kelowna with patient intake forms, treatment protocols, and insurance templates.

It works less well if your knowledge is mostly in people's heads, or if you have only a handful of documents. If your business runs on three files and everyone knows them by heart, you don't need this yet.

What it actually takes

Building a knowledge base means:

  • Gathering your documents. This is the real work. You collect contracts, policies, past emails, project records, anything a new hire might need. Most firms spend 1 to 3 weeks on this, depending on how organized they already are.
  • Organizing them so the system can search them. You don't need to rewrite anything. The system reads what you have and indexes it. A person reviews the results to make sure the search actually works.
  • Testing it with a real question. You ask the knowledge base something a new hire would ask, read the answer, and check that it's right and cites the source.
  • Refining it. You might find that some documents are too old, or that the system is returning irrelevant results. You remove the old files or reorganize the good ones. This takes a few hours.

After that, new hires use it on day one. When they have a question, they search instead of asking. The knowledge base answers most questions. For the rest, they know who to ask and why.

The real trade-offs

A knowledge base is not a substitute for training. A new hire still needs to understand your culture, meet your team, and learn how you actually work. A knowledge base answers factual questions fast. It doesn't teach judgment.

It's also only as good as the documents you feed it. If your lease template is from 2015 and you've changed your terms since then, the knowledge base will give outdated answers. You need to keep it updated. This usually means reviewing it once a quarter and removing or updating documents that are no longer true.

And it requires a person to decide what goes in. You don't feed it everything. You choose the documents that matter for new hires, remove the ones that are outdated or confidential, and organize them in a way that makes sense. This takes thought, but it's not hard.

Where to start

  • Spend an hour listing the questions new hires actually ask. Ask your managers. Ask someone who started in the last six months. Write down 10 to 15 real questions. This tells you whether a knowledge base is worth building.
  • Gather one folder of documents that would answer those questions. Don't organize them yet. Just collect the contracts, policies, templates, and past records that contain the answers. This shows you how much material you have and whether it's findable.
  • Pick one question and test it. Ask your team to find the answer in your documents the way a new hire would. Time how long it takes. This is your baseline. A knowledge base should cut this to under a minute.

Drowning in documents?

We turn your documents and records into something you can ask questions of, with every answer cited to the page. It’s the same technology behind SearchStrata.