Build an internal knowledge base by collecting your brokerage’s existing guidance, testing two platforms with real content and giving each section an owner and review date. Start with the questions your staff ask repeatedly so the first pages help them complete actual work.
The result is a private, searchable reference for brokers and support staff. A small brokerage can usually start with a cloud platform and expand once the team uses it.
What Goes Into a Brokerage Knowledge Base
Keep the guidance staff need to complete a file in your internal knowledge base. Separate it from client-facing material and organise these five content types:
- Lender credit policies, serviceability notes and turnaround observations.
- How-to guides for your customer relationship management (CRM) software, aggregator portal and other tools.
- Compliance checklists and updates issued by your licensee.
- Process checklists that carry a file from first contact to settlement.
- Templates for common client emails and follow-ups.
Gather what already exists before choosing software. Collect guidance from inboxes and shared folders, then ask experienced staff which answers they keep giving verbally. Mark duplicated or superseded material so it does not become a second version in the knowledge base.
Your brokerage policy and procedures can sit alongside the practical instructions that explain how staff follow them. Keep each approved document in one place and link to it from related pages.
Why It Earns Its Keep
A knowledge base reduces repeated questions when staff can find a clear answer themselves. Senior brokers spend less time explaining the same process, and staff can use the agreed instructions.
Time-sensitive documents get an owner and review date. Lender policy notes and licensee updates need someone responsible for checking the source and correcting the team’s guidance when it changes.
New staff can learn your file process from written steps. A checklist gives them a starting point, while linked examples show what a completed task looks like. Experienced colleagues can then help with exceptions instead of repeating the basics.
Choosing the Type of Knowledge Base
Choose internal knowledge base software your team can maintain, with costs and access controls that fit the brokerage. Subscription versus open-source describes how you obtain the software. Cloud versus self-hosted describes who runs it.
| Option | What You Take On | When It Fits |
|---|---|---|
| Subscription software | Recurring fees, plan limits and the provider’s support terms. | You want a maintained product and a defined support route. |
| Open-source software | Licence terms, configuration and responsibility for ongoing maintenance. | You have technical help and need control over how the software works. |
| Cloud hosting | Vendor selection, account administration and the provider’s data-handling terms. | You want to start without running a server. |
| Self-hosting | Hosting, backups, upgrades and someone responsible for keeping it running. | Your requirements justify running and maintaining the system yourself. |
Confluence’s licensing terms describe progressive per-user pricing for monthly paid subscriptions, alongside a free plan. Zendesk’s pricing page describes a base subscription charged per agent, with some usage charges and optional add-ons. Avoid assuming every staff member who reads a page needs the same paid role.
Open-source software can remove subscription licence fees, but hosting and maintenance still cost money or staff time. It can be self-hosted or supplied through a managed hosting service.
The right choice depends on your budget, the technical skill available in-house, how quickly you need it running and your licensee’s requirements.
Check your CRM software before buying a separate platform. Some CRM and help-desk products include a knowledge base module. CRM knowledge management keeps guidance inside the system staff already open for each file. Trial that module with the same content as any standalone tool.
During the trial, ask a staff member to search for a lender note using the wording they would use on a file. Have a section owner update the note and confirm that ordinary readers cannot make unapproved changes. Test the export process too, so you know how to keep your guidance if you move platforms.
A small brokerage can usually start in the cloud. Use the guide to data security for mortgage brokers when assessing access and data handling. Store reusable guidance in the knowledge base and keep client files in the systems approved for them.
How to Build It Step by Step
Build a small working version before importing every document. Have an owner who can approve the content, access to existing material and permission to trial the shortlisted tools.
- List the problems the knowledge base must solve. Record repeated questions, slow onboarding tasks and instructions staff struggle to find. Choose one task that will show whether the first version helps.
- Collect existing material. Identify the current version of each document, set aside superseded copies and note the gaps. Ask the relevant broker or section owner to resolve conflicting instructions before you publish them.
- Trial two platforms with the same real content. Add a lender note, a software how-to and a file checklist to each. Use guidance without client identifiers. Compare search results, editing effort and access settings.
- Structure pages around how a file moves through your business. Use consistent names and one home for each document. Your mortgage pipeline process can guide the order of the file checklists.
- Pilot with two or three staff. Ask them to find an answer and follow its instructions without help from the author. Fix unclear page names or missing steps, then train the whole team on finding and flagging content.
- Assign section owners and review dates. Give each time-sensitive page a named reviewer and a way to report a problem. Before launch, confirm every pilot page has an owner and staff can find the answer using their usual terms.
If a pilot user cannot find an existing page, compare their search words with its title and add the wording staff actually use. If two pages conflict, have the owner choose the authoritative version and archive the duplicate.
Keeping It Accurate After Launch
Keep the knowledge base accurate through assigned reviews and a simple way for staff to report outdated guidance. Give staff a feedback button, a comment field or one shared inbox that the section owners monitor.
Each lender policy page needs its source, when the team last checked it, its owner and the next review date. Link to the lender’s policy document or broker portal so staff can judge the note’s currency and trace the underlying rule.
Review time-sensitive guidance when its scheduled review falls due and when a lender or licensee announces a change. If a review is overdue, identify the page as needing review and direct staff to the source before they rely on the note.
Use page views and search analytics to decide what to improve. Repeated searches with no results point to a missing page or unfamiliar naming. A heavily viewed page deserves attention because an error there affects more staff.
A page that attracts little use may be hard to find or no longer needed. Ask its owner which applies before archiving it, and update any links from other pages.
Where to Start
Pick the question your team asks most often and document the answer today. Give that first entry a clear title, a source and an owner so another staff member can find and use it.
Spend the next week taking an inventory of your existing material. Then shortlist two platforms and trial both with the same content. Choose the one staff can search and maintain, and confirm they can complete the pilot task before moving the rest of the material.
