Knowledge base builds
Our SharePoint knowledge management consulting turns the procedures, policies and hard-won shortcuts scattered across inboxes, shared drives, an old wiki and two long-serving employees into one searchable knowledge base: an SOP library, a policy hub, how-to pages and an expert directory. Written for the operations lead at a 20–100 person firm who answers the same questions every week. Your experts keep owning the content; we build the place it lives. One written scope, one fixed price agreed before work starts, typical delivery in 2–4 weeks with 30 days of hypercare.
Representative dashboard — sample data
What you get
Each part replaces something that already exists in a worse form — a folder of Word procedures, a policy PDF attached to an old email, a “just ask the office manager” habit. The build gives every one of them a page, an owner and a review date.
Standard operating procedures as SharePoint pages built from one template: purpose, who does it, the steps, the exceptions and the forms involved. Tagged by department and process, so the right procedure turns up whether someone browses or searches.
One home for the policies staff are expected to follow, each with an effective date, an approver and a version history. Superseded versions are retained but kept out of the way, so nobody follows last year’s rule by accident.
Short pages that answer one question each — how to raise a credit note, where the client templates are, what to do when the scanner jams. The questions come from the capture workshop and from the ones your team is tired of answering.
A list of who knows what, linked to people’s Microsoft 365 profiles: the systems, clients, processes and specialisms each person can be asked about. It covers the knowledge that will never be written down, and shows who to ask instead.
A managed-metadata term set in your own vocabulary, filters on the knowledge base home page, and promoted results for the questions asked most, so typing “expense policy” returns the policy rather than every email attachment that mentions it.
Every page carries an owner, a next-review date and a status. Power Automate reminds owners before a review falls due, and a review view shows the person running the knowledge base what is overdue — the part that keeps it from going stale.
How it works
A senior engineer talks through where your know-how lives today and which questions cost the most time. You then receive a written scope — knowledge areas, templates, content waves, search setup — with one fixed price to approve before anything is built.
The first working session maps the knowledge itself: the procedures people follow, the policies they reference, the questions they ask each other, and who the go-to person is for each. That map becomes the knowledge base’s navigation and term set.
We build the site, templates, directory and review flows, convert your existing documents into pages in agreed waves, train page owners, and stay on for 30 days of included hypercare while the habit of looking it up first takes hold.
In a firm of 20 to 100 people, most operating knowledge was never written down on purpose. Procedures live in a Word file someone wrote for a new hire three years ago, in a long email thread, in a wiki that stopped being updated when its champion left, or only in the head of the person who has done the job longest. Nobody decided it should work that way; it simply grew. The cost shows up as interruptions — the same handful of people answering the same questions — as inconsistent work when two people follow two versions of a procedure, and as real risk when someone with unrecorded knowledge goes on leave or resigns. More storage does not fix it. A file share full of documents is not a knowledge base, because a document that cannot be found, has no owner and might be out of date does not answer anyone’s question.
Our general SharePoint intranet and document management consulting organizes files: sites, libraries, permissions and the migration off a file server. That is often the right first project. Knowledge management solves a narrower problem — getting a reliable answer to an operational question in under a minute — and the deliverable is shaped differently:
| Aspect | Plain document management | Knowledge base build |
|---|---|---|
| Unit of content | Files in libraries, opened and downloaded | Pages that answer one question or describe one procedure, read in the browser |
| Structure | Folders or libraries by department or client | Navigation by task and question, with a term set in your own vocabulary |
| Ownership | Whoever uploaded the file | A named owner, a next-review date and a status on every page |
| Freshness | Version history, but nothing prompts a review | Scheduled review reminders and an overdue view for the knowledge lead |
| Finding things | Full-text search across everything stored | Search tuned with metadata filters and promoted answers for common questions |
| Tacit knowledge | Not addressed | An expert directory that says who to ask when the answer is not written down |
| Typical buyer | A firm leaving a file server or cleaning up shared drives | A firm whose people keep asking each other the same questions |
The knowledge base is a SharePoint communication site with the Microsoft 365 licenses you already hold — no add-on product. Pages are built from templates for each content type (SOP, policy, how-to), with required page properties for owner, review date, department, process and status, so every page is filterable and nothing gets published without an owner. The policy hub keeps an approval step and version history; the expert directory is a SharePoint list linked to people’s profiles, browsable by skill, system or client. Where your tenant structure itself is the problem — overlapping sites, no hub, no shared metadata — that is a wider design job, and our SharePoint information architecture consulting designs the hubs, navigation and term store across the whole tenant; the knowledge base is one solution that sits on top of it. For the platform’s own capabilities, Microsoft’s SharePoint documentation (opens in new tab) is the reference.
It does not. Microsoft retired Viva Topics on February 22, 2025. According to Microsoft’s notice on the changes to Topics (opens in new tab), topic pages people had published became standard SharePoint pages, AI-generated topic pages are no longer available, and Microsoft recommends using SharePoint to publish and organize knowledge so it can be discovered through Microsoft Search. If your tenant has a leftover Topic Center site, we review what is in it during the capture workshop and fold anything still useful into the new knowledge base.
A knowledge base captures and finds operational knowledge; it does not assign or track training. If what you need is proof that people completed required courses and reminders before certifications lapse, that is our SharePoint learning management system build — the two often link to each other, with a course pointing at the SOP it teaches. If you are still deciding whether your knowledge should live in a wiki product or in Microsoft 365 at all, start with our Confluence vs SharePoint comparison for small business; this page is for firms that have already chosen SharePoint. And a well-structured knowledge base is also the content a custom agent can later answer from — if that is on your roadmap, our Copilot Studio consulting services cover that build separately. Nothing in this engagement requires it.
It fits a firm of roughly 20 to 100 people that already uses Microsoft 365, where a few experienced people field most of the “how do we…” questions, onboarding means shadowing someone for weeks, and procedures exist in several versions nobody fully trusts. It fits best when one person — an operations manager, office manager or practice lead — is willing to own the knowledge base after handover. It is not the right engagement if the real problem is that files have nowhere sensible to live yet (start with document management), or if you want someone to write your procedures for you: we build the structure, templates and review process and convert existing material, but drafting new procedures stays with your subject-matter experts, who are the only people who know them. We serve all US states remotely from our Orange County, CA base.
Related services
Intranets, document libraries and file-server migration — the general SharePoint practice this build sits within.
Hub sites, navigation and a tenant-wide term store, designed before the content goes in.
Course libraries, role-based assignment and completion records for required training.
Further reading
Hand-written guides from our article library.
FAQ
A general SharePoint build organizes files: sites, libraries, permissions. A knowledge base organizes answers. Each SOP, policy and how-to page has an owner, a review date and a status, and is written as a page people read rather than a document they download. Search, navigation and an expert directory are designed around the questions staff actually ask.
No. Your subject-matter experts own the content, because they hold the knowledge and will keep it current. We build the templates, structure and review process, run the capture workshop, convert existing documents into pages in agreed waves, and coach owners on writing pages that answer one question each. Drafting new procedures stays with your team.
Microsoft retired Viva Topics on February 22, 2025. Topic pages people had published became ordinary SharePoint pages, and AI-generated topic pages are no longer available. Microsoft's own guidance is to publish and organize knowledge in SharePoint so Microsoft Search can find it, which is exactly what this engagement builds, on the licenses you already have.
Most builds land in a typical 2-4 weeks. After a free consultation you receive a written scope listing the knowledge areas, page templates, content waves and search setup, with one fixed price you approve before work starts. The fee covers the build, owner training and 30 days of post-delivery hypercare, with no hourly billing.
Every page carries a named owner and a next-review date as required fields. A scheduled Power Automate flow reminds owners before the date passes, and a review view shows the knowledge lead what is overdue. Pages past review are flagged to readers, so staff can tell current guidance from guidance nobody has checked lately.
Book a free consultation
Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.
The fastest way to reach us is the form — tell us the task and we’ll reply within one business day.