Skip to main content
Documents and knowledge

Documents and knowledge

Answer new hire questions without asking a manager

A searchable knowledge base built from your existing documents cuts onboarding time and reduces interruptions.

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

Every business that runs on documents has the same problem on day one of a new hire's first week. The new person asks where the template is, what the standard terms are, how much you usually charge for add-ons, what the process is for approvals, or whether you've done work like this before. A manager answers from memory. Three weeks later, the next new hire asks the same question. The manager answers again.

A searchable knowledge base built from your own files solves this. Instead of interrupting someone, a new hire searches for "approval limits" or "client contract template" and gets an answer in seconds. The answer includes the page number and document name, so they can read the context themselves and verify it's current.

This works because you already have the knowledge. It lives in your contracts, policies, procedure documents, past proposals, email threads, and case files. You don't need to write a manual. You need to make what you've already written findable.

Who this helps most

A property manager in Surrey with 8 staff members spends 2 to 3 hours a week answering the same questions about strata bylaws, tenant dispute procedures, and how to handle maintenance requests. A new property manager takes a week to get up to speed. With a searchable knowledge base built from past cases and policies, that new manager finds answers on day one and asks fewer questions after day three.

An accounting firm in Burnaby has 15 years of client files, past tax strategies, and compliance notes. When a junior accountant takes on a client, they spend hours asking partners about that client's situation. A searchable archive means the junior can read past notes, understand the client's history, and ask smarter questions.

A dental clinic in Kelowna has procedure notes, insurance policies, and patient communication templates scattered across email, shared drives, and paper. New hygienists and front desk staff ask the dentist the same questions about insurance coverage, patient consent forms, and how to handle common complaints. A knowledge base built from those documents means new staff find answers without interrupting the dentist.

A plumber in Richmond has 12 years of job photos, past quotes, supplier lists, and warranty information. When a new apprentice joins, the owner spends time explaining which suppliers are reliable, what the standard markup is on parts, and how to quote a job. A searchable knowledge base means the apprentice can see past quotes and learn from them.

What it actually does

You upload the documents you already have: contracts, policies, past emails, case files, proposals, procedures, anything that contains the knowledge new staff need. The system reads them and builds an index. When someone searches for a question, the system finds relevant passages, shows them the answer, and cites the document and page number.

The answers are not perfect. The system sometimes misunderstands a question or pulls a passage that's close but not exact. That's why you keep a person in the loop. A manager or senior staff member reviews the answers before they go live, fixes any mistakes, and marks answers as approved. After a few weeks, most common questions have been reviewed and the system learns what good answers look like.

The cost is low. Most Canadian firms spend between 300 and 800 dollars a month to run a knowledge base this size, depending on how many documents and how many searches. Setup takes 4 to 8 weeks, including time to upload documents, test the system, and train staff on how to use it. It's not instant, but it's fast enough that you see value before the end of the first quarter.

When it's not worth doing

If your documents are a mess—scattered across three email accounts, three shared drives, and a filing cabinet—you'll spend weeks just organizing them before the knowledge base becomes useful. In that case, spend a month organizing first, then build the knowledge base. The effort pays off either way.

If your business is very new or you have only one or two staff members, a searchable knowledge base is overkill. A shared drive with good folder names and a one-page procedure document is enough.

If your documents are confidential and contain information you don't want new staff to see, you can build a knowledge base that only includes the documents they need. But that means more work to curate and maintain.

Where to start

  • Spend one hour this week listing the documents new hires always ask about: templates, past contracts, policies, procedures, pricing guides, or case files. Ask two or three staff members what they wish they could search for on day one. Write down 5 to 10 questions new hires always ask.
  • Gather those documents into one folder and count them. If you have between 50 and 500 documents, a knowledge base is a good fit. If you have fewer than 20, organize them on a shared drive first. If you have more than 1,000, you may need to choose which documents matter most.
  • Talk to your team about what would actually save them time. Ask a manager how many hours a week they spend answering the same questions. Ask new hires what they wish they could look up. If the answer is "a couple of hours a week", it's worth doing. If the answer is "maybe 15 minutes", wait until you have more staff.

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.