Key takeaways
- Document the processes that are frequent and risky first: new-lead handling, buyer consultations, listing launch, contract to close and wire safety.
- Keep each SOP to a page: trigger, owner, steps, tools, standards and exceptions, with a version date.
- Build SOPs into tools people already use; only 46 percent of REALTORS use a CRM, so many teams must start there[1].
- Deals are fragile, with 47 percent of sellers having at least one offer fall through[2]; written contract-to-close steps catch problems earlier.
Why teams need written procedures
On a small team, the way things are done lives in the team lead's head. That works until the lead is on vacation, a new agent joins, the assistant leaves, or the team grows to the point where the lead can no longer check everything. Then quality starts to depend on who happens to handle a client, and mistakes repeat because nobody wrote down how they were fixed last time.
Standard operating procedures, or SOPs, are short written descriptions of how the team handles a recurring task. They make the client experience consistent, make onboarding faster, and make the business less dependent on any one person, which matters for the team lead's own time and for any future succession plan.
They also reduce risk in the parts of a deal that go wrong most often. Zillow found 47 percent of US sellers had at least one offer fall through, down from 54 percent the year before, and financing issues were the top reason[2]. A written contract-to-close procedure that checks financing milestones early will not save every deal, but it surfaces problems while there is still time to act.
Source: Zillow Research, 2026[2]
Show the data
| Item | Value |
|---|---|
| 2025 | 54% |
| 2026 | 47% |
Decide what to document first
Score each recurring process on two questions, from 1 to 3: how often does it happen, and how bad is it when it goes wrong? Multiply the scores and start at the top. Processes that are rare and low-risk can wait or never be written at all.
| Process | Frequency (1 to 3) | Risk if done badly (1 to 3) | Priority score |
|---|---|---|---|
| New lead response and handoff | 3 | 3 | 9 |
| Contract to close timeline | 3 | 3 | 9 |
| Wiring and payment safety | 2 | 3 | 6 |
| Buyer consultation and buyer agreement | 3 | 2 | 6 |
| Listing launch | 2 | 3 | 6 |
| Showing scheduling and feedback | 3 | 1 | 3 |
| Post-close follow-up | 2 | 1 | 2 |
| Office supplies and signs | 2 | 1 | 2 |
Most teams end up with the same short list at the top: lead handling, contract to close, money safety, buyer consultations and listing launch. Write those five well before writing twenty mediocre ones.
A one-page SOP template
- Title and purpose: one sentence on what the procedure achieves for the client and the team.
- Owner: the role responsible for the process and for keeping the SOP current.
- Trigger: the event that starts the process, such as a new lead arriving or a contract being signed.
- Steps: numbered, each starting with a verb, each assigned to a role, with time limits where they matter.
- Tools: the systems used, with links to templates or checklists.
- Standards: what good looks like, such as response times or documents required.
- Exceptions: what to do when the normal path does not fit, and who decides.
- Version: date of the last review and who approved it.
If an SOP does not fit on a page, it is probably two procedures. Split it.
How to write one that people use
Record the real process
Have the person who does the task best talk through it while doing it, or record their screen. Capture what they actually do, not what the team thinks they do.
Draft in plain steps
Turn the recording into numbered steps with a role and a time limit for each. Cut anything that is a preference rather than a requirement.
Test with a newcomer
Ask someone who has never done the task to follow the SOP while the expert watches silently. Every question they ask is a missing step.
Revise and approve
Fix the gaps, have the team lead approve it, and check anything with legal or compliance content with the managing broker.
Publish where the work happens
Link the SOP from the CRM task, the transaction checklist or the shared drive folder people already open.
Worked example: new buyer lead to consultation
Example (fictional team SOP). Owner: inside sales or the agent on duty. Trigger: a buyer inquiry arrives by phone, web form, portal or text.
- Within 5 minutes during shift: call the lead; if no answer, leave a voicemail naming the property and send a text with your name and team.
- Within 1 hour: log the lead source, contact attempts and any details in the CRM.
- On contact: ask about timeline, area, price range, financing status and whether they already have an agent.
- If qualified: offer two consultation times within three days and send a calendar invite.
- Before the consultation: send the buyer packet and a plain-language summary of the written buyer agreement.
- At the consultation: walk through the agreement; no tours are booked until it is signed.
- After: update the CRM status, set the next follow-up and hand the file to the assigned buyer specialist.
The agreement step reflects current rules: buyers working with a REALTOR must enter a written agreement before touring a home, in person or virtually, though visiting an open house alone or asking about services does not require one[3]. Putting it in the SOP means every agent handles it the same way.
Worked example: payment and wiring safety
Example (fictional team SOP). Owner: transaction coordinator. Trigger: a contract is signed.
- Day of contract: send the client the team's wire-fraud warning, stating that wiring instructions will never change by email.
- Never send, forward or confirm wiring instructions; direct the client to the title or escrow company's verified process.
- Any message asking to change payment details is reported to the team lead the same day and confirmed by phone using a known number.
- Multi-factor authentication is required on every account used on the file.
The stakes justify the formality. The FBI's Internet Crime Complaint Center reported US real estate fraud losses of $275.1 million in 2025, up from $173.6 million in 2024[4].
Rolling SOPs out without resistance
Experienced agents sometimes hear “standard procedure” as “you do not trust me.” Frame SOPs as the team's promise to clients and as protection for agents, not as supervision. The aim is that a client gets the same quality whichever team member they deal with, and that nobody has to remember forty small steps under pressure.
- Involve the people who do the work in writing the SOP, and credit them in the version note.
- Start with one procedure everyone agrees is painful, such as contract-to-close deadlines, so the first SOP visibly saves time.
- Separate must-do steps, such as compliance and money safety, from recommended practice where agents can use judgment.
- Use SOPs in onboarding: a new agent's first two weeks should include walking through the top five.
- Review one SOP at each monthly team meeting and ask what has changed since it was written.
Measure whether they work. Track the numbers each SOP is meant to improve, such as lead response time, missed contract deadlines or files returned by compliance, for a quarter before and after it goes live. If nothing moves, the procedure is either not being used or is not addressing the real problem, and both are worth knowing.
Keep SOPs alive
An SOP that nobody updates becomes a trap: people follow it, it is wrong, and they stop trusting all of them. Give every SOP an owner and a review date, at least yearly and whenever a rule, tool or role changes. Keep them in one place with a simple index. When a mistake happens, ask whether the SOP was followed; if it was, fix the SOP; if it was not, fix the training.
Make them part of the tools. NAR found 96 percent of REALTORS use the MLS and 79 percent use e-signature tools, but only 46 percent use a CRM[1]. Teams that put SOP steps into CRM tasks and transaction checklists get far more use from them than teams with a binder. Technology training helps too: 63 percent of REALTORS say the learning curve is their biggest challenge in adopting new tools[1], so pair each new SOP with a short hands-on walk-through.
For where SOPs fit in a growing team, see succession planning for brokers and teams, agent productivity benchmarks and franchise vs independent brokerage, where playbooks are part of what a franchise sells. SOPs matter most when the team brings in new people or works apart; see recruiting experienced agents vs new licensees and office space vs virtual brokerage.
Frequently asked questions
What SOPs does a real estate team need?
Start with new lead response and handoff, buyer consultation and agreement, listing launch, contract to close and wiring safety. Add showing coordination, post-close follow-up and onboarding once those are working.
How long should an SOP be?
About one page: purpose, owner, trigger, numbered steps with roles and time limits, tools, standards, exceptions and a version date. If it runs longer, split it into two procedures.
Where should a team keep its SOPs?
In one shared place with an index, and linked from the tools where the work happens, such as CRM tasks and transaction checklists, so people see the steps at the moment they need them.
How often should SOPs be updated?
At least once a year, and whenever a rule, tool or role changes. Each SOP needs an owner responsible for keeping it current.
References
National Association of REALTORS® (2026). REALTORS® Adopt Technology to Save Time and Improve the Client Experience, NAR Report Finds (2026 REALTORS® Technology Report) (opens in a new tab) ↑
Zillow Research (2026). Sellers: Results from the Zillow Consumer Housing Trends Report 2026 (opens in a new tab) ↑
National Association of REALTORS® (2024). Consumer Guide: Written Buyer Agreements (opens in a new tab) ↑
FBI Internet Crime Complaint Center (IC3) (2025). Federal Bureau of Investigation Internet Crime Report 2025 (opens in a new tab) ↑