Writing Down How Your Business Runs

Understanding Brain-Dumping and SOPs

In a mortgage brokerage, SOPs are not “nice to have.” They are what keep your pipeline moving while you’re on calls, reviewing files, and handling rate-lock decisions. Think of SOPs as the exact playbook your team follows to move a loan from first conversation to clear-to-close—without you needing to be in every step.

A strong goal is simple: make it so a new processor, junior loan officer, or administrative assistant can perform the core steps at about 80% quality on their first day just by following your instructions. That means fewer delays, fewer missing documents, and fewer “Which checklist do we use for this lender?” questions.

The Importance of Brain-Dumping

Brain-dumping is the process of getting the “know-how” in your head onto paper or a shared system your team can use. In mortgage brokering, that know-how is everywhere: how you talk to borrowers about docs, how you spot red flags on paystubs, how you explain credit timelines, how you prepare a file for underwriting, and which lender guidelines you trust for different income types.

If you keep all of that in your head, your business grows only as far as you personally can carry it. But when you document it, your business can run even when you’re on the phone, in meetings, or away for a couple days.

Real-World Example: You know that when a self-employed borrower’s bank statements don’t match their deposits, you don’t panic—you ask the right clarifying questions and you document the rationale early. Without an SOP, your team might ask the wrong questions, or wait too long, which can turn a smooth underwriting into a stalling file.

Creating Effective SOPs

To write SOPs that actually get used, follow this structure.

1. Why: Start with why the task matters. In mortgage, “why” keeps the team from treating steps like busywork.
- Example: Why we collect VOE (or employment verification) early is because it reduces underwriting churn and avoids last-minute delays.

2. What: List the exact steps the team should do.
- Example: What to do after the initial application: confirm loan type, verify borrower details, collect ID, pull credit consent, request income docs, and confirm the loan officer’s next scheduled action.

3. Outcome: Define what “done” looks like.
- Example: “Success” is a completed application with correct borrower names/DOB/SSN, doc checklist generated, conditions captured in a single place, and the file ready for review within 24 hours.

Real-World Example: A common SOP in mortgage is “How we prepare a file for lender submission.” Your outcome could be: all borrower pages uploaded, income and asset docs clearly labeled, explanations added for any irregularities, disclosures uploaded, and an underwriting-ready checklist completed.

Organizing Your SOPs

Your SOPs need one job: be easy to find during real work. If your team can’t locate the right steps in 30 seconds, the SOP won’t get used.

Store SOPs in one centralized location that matches how people work:
- A shared SOP vault (Notion, Google Drive, or Confluence)
- Clear naming (example: “Loan Intake—Doc Checklist Start”)
- A simple index page or table of contents

Real-World Example: Your team should be able to open the SOP vault and quickly find “Self-Employed Income—Bank Statement Review Questions” when a borrower sends docs that require additional clarification.

The Loom-First Approach

In mortgage, many steps are visual and “how it looks” matters: how you label documents, how you review a paystub for dates, how you capture conditions, how you run through a lender portal workflow. Use Loom (screen recording) to record yourself doing the task.

Then convert those Loom recordings into short written SOPs. The recording becomes the proof, and the written version becomes the quick reference.

Real-World Example: Record yourself setting up a new borrower file in your CRM, generating the doc checklist, and creating the first task sequence. Your team can watch it, then follow the checklist the same way next time.

Building a Culture of Self-Reliance

Your team needs permission and a habit: check the SOP vault before asking you for the answer. This isn’t about avoiding questions—it’s about speeding them up.

Make it normal to say:
- “Let me check the SOP first.”
- “I’ll follow the ‘Loan Submission Prep’ steps and flag anything unclear.”

Real-World Example: A processor asks how to handle an employer verification delay. Instead of answering from memory, you point them to the SOP “Employment Verification Delay—Escalation Timeline and Notes to Borrower.”

When you set up SOPs like this, your operation becomes less fragile. Your team can execute consistently, your borrowers get faster answers, and you earn back time to grow—without sacrificing loan quality.