SOP-001: Realtor Partnership Acquisition

Version: Premium 4.08 | Effective Date: 2025 | Review Cycle: Quarterly

Owner: Mortgage Operations Manager | Approver: Branch Manager / Compliance Officer

1. PURPOSE & SCOPE

The complete standard operating procedure for identifying, approaching, converting, and onboarding real estate agent referral partners.

This SOP applies to all loan officers, processors, assistants, and administrative staff involved in the subject process. Deviation from this SOP requires written approval from the operations manager.

2. DEFINITIONS & TERMINOLOGY

• SLA: Service Level Agreement — the maximum allowable time between steps

• KPI: Key Performance Indicator — quantifiable performance measures

• CRM: Customer Relationship Management system (Surefire, HubSpot, Salesforce)

• LOS: Loan Origination System (Encompass, Calyx, Floify)

• CTC: Clear-to-Close — final underwriting approval

• CD: Closing Disclosure — final fee and cost disclosure

• LE: Loan Estimate — initial disclosure within 3 days of application

3. ROLES & RESPONSIBILITIES

4. PROCEDURE — PHASE 1: PREPARATION

Before initiating the process, verify that all required tools, templates, and access credentials are available:

• [ ] CRM login active with proper permissions

• [ ] LOS access confirmed and pipeline configured

• [ ] Document templates loaded and current

• [ ] Communication channels tested (email, text, video)

• [ ] Compliance checklist printed or digitally accessible

Document current state metrics before implementing this SOP:

• Current cycle time (if applicable)

• Current conversion rate by stage

• Current error rate or rework percentage

• Current client satisfaction score (NPS or equivalent)

Alert all parties who will be affected by this process execution:

• Internal team members with dependencies

• External partners (realtors, builders, attorneys) with touchpoints

• Client (if process directly involves client interaction)

5. PROCEDURE — PHASE 2: EXECUTION

Trigger the process using the standardized entry point. Record the initiation timestamp in the CRM. Assign a unique identifier to this process instance for tracking.

Execute each sub-step in order, documenting completion and any exceptions:

When a deviation, error, or unexpected condition occurs:

6. PROCEDURE — PHASE 3: QUALITY ASSURANCE

Before marking the process complete, verify:

• [ ] All required steps executed in sequence

• [ ] All required documentation completed and saved

• [ ] All SLAs met or exceptions documented and approved

• [ ] Client/partner communication sent and confirmed

• [ ] CRM updated with correct status and next steps

• [ ] Handoff to next process owner documented (if applicable)

Operations manager spot-checks 10% of process instances monthly for:

• Adherence to documented procedure

• Documentation completeness

• SLA compliance

• Client satisfaction outcomes

7. PROCEDURE — PHASE 4: CLOSURE & HANDOFF

Update the process status to "Complete" in the tracking system. Archive all documentation per the document retention policy (minimum 7 years for loan files, 3 years for marketing).

Record the outcome metrics:

• Total time elapsed

• SLA compliance (yes/no for each step)

• Quality score (if applicable)

• Client feedback (if collected)

• Revenue impact (if measurable)

If any new insight, tool improvement, or process innovation emerged during execution, document it in the SOP Improvement Log for quarterly review.

8. KEY PERFORMANCE INDICATORS (KPIs)

9. TOOLS & SYSTEMS REQUIRED

• Primary LOS: Encompass or Calyx Point

• CRM: Surefire CRM, HubSpot, or Salesforce

• Communication: BombBomb, Mailchimp, ActiveCampaign

• Document Management: Floify, DocuSign, Dropbox

• Analytics: Excel, Google Sheets, Tableau

• Compliance: Compliance EAGLE or equivalent

10. COMMON MISTAKES & PREVENTION

11. TRAINING & CERTIFICATION

All personnel executing this SOP must complete:

12. REVISION HISTORY

13. APPENDIX: EXACT SCRIPTS & TEMPLATES

"[Name], I have completed [step] for [client/file]. Status: [complete/exception]. Next step is [action] with SLA of [time]. All documentation is saved in [location]. Please confirm receipt."

"[Name], your file has moved to [stage]. This means [explanation in plain English]. The next milestone is [next stage] on approximately [date]. I will update you again by [time]. Questions? Reply or call me directly."

"Exception logged for [client/file] at [step]. Condition: [description]. Impact: [high/medium/low]. Proposed resolution: [action]. Awaiting approval to proceed."

Clozo Academy Proprietary Standard Operating Procedure — Premium Edition v4.08

Unauthorized distribution prohibited. For licensed use only.

The Behavioral Economics of Standard Operating Procedures

Most loan officers resist SOPs because they feel restrictive. The reality is that SOPs create freedom. When every step is documented, you stop wondering what to do and start executing. When every decision is systematized, you stop agonizing over choices and start optimizing outcomes. When every process is repeatable, you stop reinventing the wheel and start compounding results.

Creativity thrives within constraints. Jazz musicians improvise within chord structures. Writers create within grammatical rules. Loan officers produce within process frameworks. SOPs are not cages — they are scaffolding that supports higher performance.

• Implementation Intentions: "When [trigger], then I will [action]." This format increases follow-through by 40%.

• Commitment Devices: Publicly announcing your SOP adoption to partners or team members creates social accountability.

• Loss Aversion: Frame SOP adoption as "preventing the loss of deals, time, and reputation" rather than "gaining efficiency."

• Social Proof: Share SOP success stories from other producers. "Sarah implemented this SOP and reduced her days-to-close by 6 days."

The Exact Setup Checklist for This SOP

• [ ] Read this SOP in full

• [ ] Identify the stakeholders who need to know it

• [ ] Schedule a training session

• [ ] Gather required tools and templates

• [ ] Document current state metrics

• [ ] Execute this SOP on 3-5 instances

• [ ] Note deviations and exceptions

• [ ] Collect feedback from all participants

• [ ] Identify bottlenecks

• [ ] Measure results vs. baseline

• [ ] Adjust SOP based on pilot learnings

• [ ] Update templates and scripts

• [ ] Re-train team on revised version

• [ ] Set performance targets

• [ ] Create dashboard for tracking

• [ ] Roll out SOP to full operation

• [ ] Monitor compliance daily

• [ ] Celebrate early wins

• [ ] Address resistance quickly

• [ ] Document lessons for future SOPs

The Technology Configuration Details

• Pipeline stages aligned with SOP phases

• Custom fields for SOP-specific data capture

• Automated status change triggers

• Reporting dashboards for SOP compliance

• Exception flagging rules

• Contact records linked to SOP instances

• Communication templates loaded

• Automated follow-up sequences activated

• Partner notification rules configured

• Client update templates assigned

• Template library organized by SOP

• Version control system activated

• Access permissions configured

• Audit trail enabled

• Retention schedules set

The Measurement Framework

• SOP initiation rate

• Step completion timeliness

• Exception frequency

• Training completion percentage

• Tool utilization rate

• Cycle time reduction

• Error rate decline

• Client satisfaction improvement

• Revenue per process increase

• Cost per process decrease

• SLA compliance percentage

• Rework rate

• Escalation frequency

• Stakeholder complaint rate

• Process abandonment rate

The Continuous Improvement Protocol

• Review KPI dashboard

• Identify top 3 friction points

• Brainstorm solutions

• Implement one improvement

• Full SOP audit

• Stakeholder interviews

• Competitive benchmarking

• Technology upgrade review

• Training refresh

• SOP rewrite if needed

• Complete system overhaul consideration

• Industry best practice integration

• Regulatory update incorporation

• Strategic alignment verification

Common Resistance Patterns & Solutions

Solution: Show data on outcomes. "Your way produces X results. The SOP produces Y results. The difference is $Z per month."

Solution: Simplify first. Implement 20% of the SOP that produces 80% of the benefit. Add complexity incrementally.

Solution: Time-block SOP implementation. Show that 2 hours of setup saves 10 hours per month.

Solution: Customize the SOP for their specific context while maintaining core principles.

Solution: Create urgency. "Every day without this SOP costs $X in lost efficiency or errors."

The Financial Impact Model

• Hours saved per process instance: [X]

• Hourly value of employee: $[Y]

• Process instances per month: [Z]

• Monthly time savings: $[X × Y × Z]

• Error rate before SOP: [A]%

• Error rate after SOP: [B]%

• Cost per error: $[C]

• Process instances per month: [Z]

• Monthly error savings: $[(A-B) × C × Z]

• Conversion improvement: [D]%

• Average revenue per conversion: $[E]

• Opportunities per month: [F]

• Monthly revenue increase: $[D × E × F]

Total Monthly SOP Value: $[Time Savings + Error Savings + Revenue Increase]

SOP ROI: [Total Value / SOP Implementation Cost]:1

Clozo Academy Proprietary Standard Operating Procedure — Premium Expanded Edition