Debbie CuhaGet in touch
Back to field notes

How to Write a Real Estate SOP Your Newest Agent Can Follow

By Debbie Cuha, October 4, 2026. 6 min read

To write a real estate SOP, pick one task your team repeats, name one owner and the exact trigger that starts it, set a measurable standard, and list the steps in order with time limits. Then hand it to the least experienced person on your team and watch them do it without help. Wherever they stop and ask a question, the SOP is unfinished.

That last test is the one most people skip, and it's the only one that matters. I wrote the policies and SOPs for DirectLender's 280 offices, and the rule I used was simple: if a brand-new processor in a branch I'd never visited couldn't follow it, I rewrote it. This post walks through how I write one from scratch. For the full list of which SOPs a team needs, start with the pillar guide, Real Estate SOPs: The Complete Guide.

Why most real estate SOPs fail the newest-agent test

They're written by the person who already knows how to do the job. That person skips steps without noticing because the steps are automatic to them. "Set up the file" means twelve actions to the team leader and nothing at all to someone on day three.

The other common failures:

  • Too long. A 15-page procedure nobody reads.
  • No owner. "The team will follow up" means nobody follows up.
  • No trigger. The SOP says what to do, but not when to start.
  • No standard. "Respond quickly" is a wish. "First call within 5 minutes during business hours" is a standard.
  • Written once, never tested. It looked good on paper and broke on the first live file.

The 8-step method

1. Pick one task that repeats and keeps breaking

Not "operations." One task. Good first choices: responding to a new lead, launching a listing, the handoff when a contract is accepted. If it happens weekly and it has gone wrong more than once in the last month, write that one first.

2. Name one owner

One role, not a person's name and never "the team." Roles survive turnover. Names don't. If the role isn't hired yet, write "Team leader owns this until the listing coordinator is hired." Now everyone knows who answers for it today and who will tomorrow.

3. Define the trigger

What exact event starts this procedure? "A fully executed contract: every party has signed and initialed every page and addendum." That's a trigger. "When we go under contract" is not, because people will argue about when that was.

4. Set the standard

The standard is the measurable bar for done. Use times, counts and zero-tolerance items.

  • "Handoff form and executed contract sent to the transaction coordinator within 1 business hour of acceptance."
  • "MLS input proofed by two people before the listing goes active."
  • "Zero leads in the CRM without a next task."

If you can't measure it, you can't hold anyone to it, including yourself.

5. Record yourself doing it

Don't write from memory. Do the task for real and narrate it out loud, or record your screen while you work. Then transcribe it. You'll find the five steps you were about to skip. This is the fastest way I know to get what's in your head onto paper.

6. Turn the transcript into numbered steps with time limits

Each step starts with a verb and, where it matters, a time limit.

  1. Within 1 hour: Confirm the contract is fully executed.
  2. Within 4 hours: Review for missing signatures, initials, dates and addenda.
  3. Same business day: Enter every contract deadline on the shared calendar.

One action per step. If a step has the word "and" in it twice, split it.

7. Add the checklist, the scripts and the failure points

The checklist is what gets ticked on every live file. Scripts go in where the words matter (first call, voicemail, the "what happens next" call). Failure points are the ways this procedure usually breaks. Writing them down is how you stop repeating them.

8. Test it on your least experienced person

Hand it to your newest agent or admin. Don't explain anything. Watch. Every time they pause, ask a question, or do something you didn't expect, write it down. Fix the SOP, not the person. Then run it live for 7 days and review it at your next weekly meeting.

A sample one-page SOP

Here's what a finished SOP looks like when it's done right. Short enough to read in two minutes.

SOP: Under-Contract Handoff          Version: [date]
OWNER:    Agent sends. Transaction coordinator receives and owns the file.
TRIGGER:  Fully executed contract.
STANDARD: Handoff within 1 business hour. All deadlines on the shared
          calendar same business day. Intro email to all parties in 24 hours.

STEPS
1. Within 1 hour: Agent sends contract + handoff form to TC.
2. Within 4 hours: TC reviews for missing signatures, dates, addenda.
3. Same day: TC loads every deadline. Notes business vs calendar days.
4. Within 24 hours: TC sends intro email with timeline and contacts.
5. Within 24 hours: Agent calls client to explain what happens next.
6. By deadline: TC confirms earnest money delivered, saves receipt.

CHECKLIST
[ ] Contract fully executed     [ ] Handoff form complete
[ ] Deadlines on calendar       [ ] Intro email sent
[ ] Client call done            [ ] Earnest money receipt saved

FAILS WHEN: contract sits in the agent's email for two days;
            business vs calendar days miscounted.
COMPLIANCE: Give clients more than one vendor option. Broker reviewed [ ]

That one is pulled from SOP 7 in my free 12-SOP kit. The deeper version is in Under Contract to Close: The Transaction Coordinator SOP.

Rules for writing that a new agent can actually use

  • Plain words. Write the way you'd explain it standing at their desk.
  • One page when possible. Two at most. Put long reference material in an appendix.
  • Same template every time. People learn where to look.
  • Date every version. An undated SOP is a rumor.
  • Customize lines. End each SOP with blanks your team fills in: "Our first-touch standard is ___ minutes." Filling them in is how a template becomes yours.
  • Compliance last, but never skipped. Your managing broker reviews every SOP before it goes live.

"Don't ask the same question twice"

This was one of our rules, and it's the best test of whether a procedure is working. If someone asks you a question, answer it once, then put the answer in the SOP. The second time anyone asks, the answer is "check the SOP," and if it isn't there, that's on you, not them.

Over a few months, that rule quietly writes your whole operations manual for you. It's also how your team learns that the system is the source of truth, not your phone.

When to rewrite an SOP

Review one SOP a week in your team meeting on a rotating schedule, so all of them get a fresh look every quarter. Rewrite immediately when:

  1. The same step gets skipped twice.
  2. A new tool or platform changes how the work is done.
  3. Your broker, MLS or state rules change.
  4. A new person can't follow it without help.

FAQ

What should a real estate SOP include?

A purpose, one owner, the trigger that starts it, the tools used, a measurable standard, numbered steps with time limits, a checklist, any scripts, the KPIs that show it's working, common failure points and compliance notes your broker has reviewed.

How long should an SOP be?

One page if you can, two at most. If it runs longer, you're probably describing more than one task, so split it into separate SOPs that hand off to each other.

Who should write the SOPs on a real estate team?

The person who does the job best should record themselves doing it. The team leader or operations manager turns that into the template, and the newest person on the team tests it. The broker reviews it for compliance before it goes live.

If you'd rather start from twelve finished templates than a blank page, grab the free SOP kit.