Build a mortgage support knowledge base people can use

Organise a mortgage support knowledge base around the tasks people are trying to complete, with one current instruction for each task, a named owner and a clear route for unresolved questions. A large folder of documents is not enough if a new team member cannot identify which version applies.

This guide sets out a practical structure for a brokerage’s internal operating knowledge. It covers finding and maintaining instructions. It does not replace current lender information, your aggregator’s guidance or decisions that belong with the responsible broker.

Start with the questions that interrupt work

Collect a week of recurring operational questions without copying customer details. Group them by the task being attempted: receiving a new file, recording a document, routing a broker question, updating a status or handing over unfinished work. Use the language the team actually searches for.

Prioritise questions that are frequent, slow to answer or easy to answer inconsistently. Do not begin by writing a page for every theoretical situation. Ten well-maintained task pages can be more useful than an extensive library whose owners and currency are unknown.

Separate “how our team performs this task” from external policy or product information. The internal page should point to the approved source for changing external requirements and state when a question must be checked with the responsible person. Copying a whole external manual creates another version to maintain.

Use a simple task-based structure

Collection	Example page	What belongs there
Start a task	Accept a preparation-ready file	Required inputs and ownership
Perform recurring work	Record an incoming document	Steps, expected result and exceptions
Resolve a blockage	Raise a missing-instruction question	Evidence to include and decision owner
Hand over work	Prepare the daily queue handover	State, next action and checkpoint
Maintain the library	Propose a procedure change	Review, approval and version process

Atlassian’s knowledge-management guidance discusses organising and sharing knowledge in Confluence. The task structure here is a proposed brokerage method that can be implemented in your existing approved tool; it does not require Confluence or imply that Mortgage Talent provides a linked knowledge-base integration.

Give every instruction a small, consistent header

Record the page owner, status, last reviewed date, review trigger and applicable workflow. Use statuses such as draft, current and superseded. A last-edited date alone is not enough: someone may have corrected a spelling mistake without reviewing the procedure.

State the trigger, inputs and finished output before the steps. A reader should know whether the page applies before following it. Include a short “stop and ask” section for missing inputs or decisions outside the role. Link to one maintained template instead of attaching separate copies to several pages.

The mortgage support SOP template provides the procedure body. This knowledge-base structure adds the navigation, ownership and maintenance around those individual procedures.

Make a search test part of publication

Ask a colleague who did not write the page to find it using a realistic task question. Do not give them the exact title first. Note the words they search, the page they open and the point where they become uncertain. Improve the title, summary or navigation based on that observation.

Then ask the colleague to explain the task’s entry condition, expected output and escalation point. This checks understanding without requiring a live customer file. If the page needs the author standing beside it to make sense, it is not yet a reliable handover aid.

Add common alternative terms as short descriptive text where useful, but avoid cluttering titles with every possible synonym. One clear page with helpful cross-links is easier to maintain than several near-duplicate pages written for different search phrases.

Work through a fictional first-ten-pages rollout

A brokerage collects eighteen recurring questions from its support team. Six concern document receipt, five concern task ownership, four concern where to record follow-up and three concern unfamiliar requests. The manager groups the questions into ten pages rather than publishing eighteen disconnected answers.

For the document page, the first draft says “upload and mark complete”. A practice review reveals that readers cannot tell whether complete means received or reviewed. The revised page separates those states and links to the document request tracker. A fictional example shows an item waiting for review.

For unfamiliar requests, the library provides a question template and decision owner instead of a guessed answer. The team tests all ten pages with fictional tasks, publishes the approved versions and assigns a review owner for each. This is a constructed rollout example, not a claim about a client’s results.

Handle changes without leaving competing instructions

When a process changes, update the current page and record what changed, who approved it and when it takes effect. Retain version history through the chosen system. Mark superseded pages clearly and direct readers to the current instruction so old bookmarks do not silently lead to obsolete steps.

Review related pages and templates at the same time. A change to the handoff fields may affect the daily summary, onboarding exercise and quality checklist. Keep a short dependency list on important pages so those relationships are visible when an owner makes a change.

Use a review trigger as well as a calendar date. A new system screen, changed workflow or repeated question can justify review sooner than the planned interval. Conversely, do not mark a page reviewed simply because its scheduled date has arrived; record what the owner actually checked.

Measure whether the library helps people work

• Can a new team member find the right instruction without knowing its exact title?
• Can they distinguish current instructions from drafts and old versions?
• Do recurring questions reveal a missing page or an unclear step?
• Are page owners resolving proposed changes?
• Does a fictional practice task reach the expected result?

Use those findings in the first-month onboarding plan. If you are preparing to bring in support, discuss the role and workflow with Mortgage Talent. A usable library makes the work easier to explain and the training requirement easier to scope.