How to Write a Real Estate Team SOP Your Agents Will Actually Open

Most real estate team SOPs are written once, in a burst of good intentions after a bad month, and never opened again. You know the folder. "Team Procedures FINAL v3." Forty pages, a cover image, and a section on buyer consultations that still mentions a lender who left two years ago.

A real estate team SOP doesn't fail because it's wrong. It fails because it's long, nobody owns it, and it lives somewhere other than where the work happens. So this post isn't a template library. It's one complete SOP, written the way we'd write it, plus the rules behind it and the questions team leaders ask us about them.

What a real estate team SOP is for

An SOP answers one question for one situation: "This just happened. What do I do now, and who does it?"

That's narrower than most people think. A team SOP isn't your mission statement, your scripts or your training curriculum. Those matter, but they're different documents. If a page doesn't tell someone what to do next on a real deal, it's not an SOP.

We'd also be honest about who reads them. Experienced agents won't, mostly. New agents, admins, TCs and the person covering for someone on vacation will. Write for the person covering on vacation. If they can follow it without calling anyone, it's done.

A sample SOP, start to finish

Here's a real one for a common moment. Copy the shape, not the details. Your timelines, roles and vendors will be different, and the time windows below are examples.


SOP: New listing agreement signed

Trigger: Seller has signed the listing agreement and it's uploaded to the deal.

Owner of this SOP: Operations manager. Reviewed every quarter.

Goal: Listing is live on the MLS, marketed and showing ready within the timeline promised to the seller.

Step Who When
Confirm the signed agreement and seller disclosures are on the deal Listing agent Same day
Send the seller our prep checklist and a photo date Listing agent Same day
Book photography and any measurements or floor plan Admin Within 2 business days
Order the yard sign and lockbox Admin Within 2 business days
Draft MLS remarks and feature list Listing agent Before photos are delivered
Review remarks, price and showing instructions Team leader Within 1 business day of draft
Enter the listing on the MLS as coming soon or active, per the seller's choice and local rules Admin After leader review
Schedule the first weekly seller update Listing agent Before going active

If something's stuck: If photos aren't booked within two business days, the ops manager is notified and calls the photographer. If the seller isn't ready by the photo date, the listing agent reschedules and notes why on the deal.

Done when: Listing is active, the sign is up, and the first seller update is on the calendar.


That's the whole thing. It fits on one screen. Notice what's missing: there's no paragraph about why great listing service matters, and nothing about how to win the listing in the first place. Those belong in training.

The rules we follow when writing them

Start from a trigger, not a topic. "Listings" is a topic. "Listing agreement signed" is a trigger. Topics turn into essays. Triggers turn into steps.

Every step gets a role and a timing. Not "the team." A role, like listing agent, TC or admin. And a timing tied to the trigger ("within 2 business days"), not to a weekday. A Friday signing breaks "by Tuesday." Our post on real estate task management for teams goes further into why single owners matter.

Say what happens when a step slips. This is the part almost every procedures manual skips, and it's the part that saves you. Somebody should hear about it, and the SOP should say who.

Keep it to one screen. If it scrolls past two, split it into two SOPs. "Under contract" and "clear to close" are different moments.

Write the way your best TC talks. Short. Specific. "Send the executed contract to the lender" beats "ensure all relevant parties receive appropriate documentation."

Name an owner for the SOP itself. Someone whose job includes noticing that it's out of date. Without that, it rots.

The SOPs we'd write first

You don't need forty. Start with the moments where a dropped ball costs you a client or a deadline. For most teams that's something like:

  • New lead assigned
  • Buyer consultation booked
  • Listing agreement signed
  • Offer accepted, under contract
  • Inspection response due
  • Clear to close and closing day
  • Deal falls through
  • Agent joins the team (see our agent onboarding plan)
  • Agent leaves the team (and our agent offboarding checklist)

Nine is plenty for year one. Write them over a month, one a week or so, and test each one on a live deal before you call it finished.

How to build one in an afternoon

Grab your TC and one agent who does things the right way most of the time. Pull up a deal that closed recently. Walk it from the trigger forward and write down every step that actually happened, who did it, and how long it took.

Then cut. Anything that didn't change the outcome goes. Anything that happened only because someone forgot an earlier step tells you the earlier step needs a better timing or owner.

You'll end up with something close to the sample above. It won't be pretty the first time. That's fine.

Where SOPs should live

Here's where we have a strong opinion. A document in a shared drive is a reference. It's fine for training, and you should keep one. But the version of the SOP that matters is the one built into your system, where the trigger creates the tasks, assigns them to the right role and sets the due dates automatically.

When the SOP lives only in a document, following it depends on someone remembering it exists. When it lives in the workflow, the next step just shows up for the right person. That's the difference between a procedure and a repeatable workflow, and it's the main reason teams that write great SOPs still drop balls.

So we'd write the SOP in plain language first, agree on it as a team, and then build it into your CRM and transaction process. The document explains why. The system makes sure.

Questions team leaders ask about SOPs

How detailed should a real estate team SOP be? Detailed enough that someone covering for a week can follow it without calling anyone. Not so detailed that it explains how to send an email.

Who should write them? The people doing the work, with the team leader signing off. If you write them alone, they'll describe how you wish the team worked.

How often should we update them? Look at each one quarterly, and any time a deal goes wrong in a way the SOP should have caught. That second trigger matters more.

What do we do when an agent ignores the SOP? First check whether the SOP is the problem. If three agents skip the same step, the step is probably pointless or badly timed. If one agent skips everything, that's an accountability conversation, not a writing problem.

Do top producers have to follow them? On anything that touches a client deadline, a contract or compliance, yes. How they run a listing appointment is their call.

Where BILLIONS fits

BILLIONS is an all-in-one platform for real estate teams, built on Salesforce, with custom pre-built workflows for listings, buyer and wholesale deals, plus contract to close coordination, milestone and deadline notifications, and personalized task alerts. Your SOPs stop being a document people have to remember and become the steps that show up on each deal for the right role. It comes already built out by operators who run real estate teams, so you're adjusting a working process instead of designing one from scratch.

If you want to see your listing SOP running as a workflow, schedule a demo.

See BILLIONS in action

The all-in-one CRM for real estate teams, built on Salesforce. Zero build-out required.

Schedule a Demo →

One short demo

See BILLIONS in action

Real results. Real speed. One short demo.

Schedule a Demo →