Most Canadian brokerages run on memory. The intake sequence, the document chase, how conditions get triaged, the client update cadence — all of it lives in the head of whoever has been doing the job longest, and it gets passed on informally, if it gets passed on at all. That works until volume climbs, a team member leaves, or two files hit a snag in the same week — then the gaps show up as missed documents, inconsistent client updates, and conditions that sit longer than they should.
The fix is not a forty-page operations manual nobody reads. It is a short, specific standard operating procedure (SOP) for each of the ten moments in a file's life where a gap does the most damage, written in about an hour each using the same simple template. This playbook lists the ten SOPs to document first, in the order to tackle them, and the template that keeps each one to an hour instead of a project.
Step 1. Start with the 10 SOPs that touch every file, not the exceptions
A brokerage can eventually document dozens of processes, but ten of them touch every single file and cover the points where errors compound the most. Documenting these first, before the edge cases, is also the practical starting point behind the case for building systems before adding staff: an undocumented process does not get easier to hand off just because more people are trying to run it from memory.
- →Client intake & needs assessment — what gets captured and confirmed on the first call.
- →Document collection & tracking — the request list, the reminder cadence, and where files live.
- →File assembly & lender submission — the checklist before a file leaves the brokerage.
- →Condition clearing — how conditions are triaged, assigned, and confirmed cleared.
- →Closing-week coordination — the handoff to the solicitor and the final verification steps.
- →Post-close & referral follow-up — the touchpoints after funding that most brokerages skip.
- →Escalation & broker sign-off — when a file leaves the team and lands on the broker's desk.
- →Lender communication & status updates — how and when a lender gets contacted mid-file.
- →Compliance record-keeping — what gets filed, where, and for how long.
- →Tech & portal handling — how documents, e-signatures, and client data move between systems.
The test for “first ten”: if a new hire would need to ask a colleague how to handle it in their first week, it belongs on this list before anything more specialized.
Step 2. Write each SOP in about an hour with one five-part template
Every SOP on the list above can be written using the same five-part structure, which is what keeps each one to roughly an hour instead of turning into a drafting project.
- 01Purpose — one sentence on what this procedure exists to prevent or produce.
- 02Trigger — the exact event that starts it (a new lead, a condition received, a commitment signed).
- 03Steps — the numbered sequence, written for someone doing it for the first time.
- 04Owner — the role responsible, not the name of the person currently in that role.
- 05Exceptions — the two or three variations that come up often enough to name (a self-employed file, a rush closing, a second applicant).
Write for the role, not the person: naming an owner by role rather than by name means the SOP survives a hire, a leave, or a reorganization without a rewrite.
Step 3. Document the six file-stage SOPs first
Six of the ten sit directly on the path a file travels from lead to funded deal, and they are worth writing first because a gap in any one of them delays a closing.
| SOP | Trigger | What it prevents |
|---|---|---|
| Client intake & needs assessment | New lead assigned | Missing basics that resurface at submission |
| Document collection & tracking | Application started | The document chase eating the timeline |
| File assembly & lender submission | Documents complete | A submission bounced back for a missing item |
| Condition clearing | Commitment received | Conditions sitting unassigned past their window |
| Closing-week coordination | Conditions cleared | Last-minute surprises at the solicitor's desk |
| Post-close & referral follow-up | Funding confirmed | A satisfied client who is never asked for a referral |
Two of these — document collection and closing-week coordination — are exactly where files change hands most often, which is why they pair well with a dedicated file handoff playbook once the basic SOP exists.
Step 4. Document the four operational SOPs that hold the system together
The remaining four SOPs are not tied to a single file stage, but they determine how consistently the other six actually get followed.
- →Escalation & broker sign-off — without a written trigger for when a file goes to the broker, escalation defaults to whoever is loudest or most anxious that day; a written escalation matrix replaces judgment calls with a shared standard.
- →Lender communication & status updates — who contacts the lender, how often, and through what channel.
- →Compliance record-keeping — what gets retained, in what format, and for how long, aligned to the brokerage's regulatory record-keeping obligations.
- →Tech & portal handling — how a document moves from a client's inbox to the file, without a version living in three places at once.
Step 5. Pilot each SOP on a real file before calling it official
A brand-new SOP is a draft until it has survived contact with a real file. Run it once, watch where the person following it hesitates or improvises, and fix that step before treating the document as final.
- 01Pick one active file and follow the draft SOP exactly as written, without silently correcting it.
- 02Note every point where the person following it had to guess, ask a question, or skip a step.
- 03Revise those specific steps — not the whole document — based on what actually happened.
- 04Re-run it on the next similar file to confirm the fix held.
One pilot is enough: a single real file exposes most of the gaps in a first-draft SOP; do not wait for a perfect one before putting it to use.
Keep the library alive, not just written
A library of SOPs that never changes is a library that is quietly going stale. Assign an owner for the whole library (not each individual SOP), set a semi-annual review date, and require that any process change gets reflected in the document within a week — not eventually.
Building and maintaining ten SOPs from scratch is real work on top of running files — it is also close to exactly what Treadstone's fulfillment services already run as a built process, for brokerages that would rather plug into a documented system than build one from a blank page.