Debbie CuhaGet in touch
Back to field notes

Why Teams Ignore Their SOPs (and How to Make Them Stick)

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

Teams ignore their SOPs for three reasons: nobody owns them, nobody checks them, and following them earns nothing that skipping them doesn't. SOPs stick when every procedure has one owner, the numbers are reviewed every week in front of the team, and the rewards clearly match the effort. Culture isn't a poster on the wall. It comes from systems so clear that performing is the only option.

I've written procedures for 280 offices and about 3,000 people at DirectLender.com, a brokerage closing 500 to 750 transactions a year, Dominion Partners (a real estate private equity fund), and a construction company. The procedures were never the hard part. Getting people to run them on the worst day of the month was. If you haven't written yours yet, start with the complete guide to real estate SOPs or the free 12-SOP kit.

The 6 reasons SOPs get ignored

1. Nobody owns them

"The team" owns the lead follow-up SOP, which means nobody does. Every process has a protocol, and every protocol needs one owner: a role that answers for it when it breaks.

2. They were announced, not installed

The team leader writes ten SOPs over a weekend, sends a link in the group chat, and calls it done. Nobody walked through them. Nobody role-played the scripts. Nobody ran them live for a week. An announced SOP lasts until the first busy Tuesday.

3. They live in a place nobody goes

Three versions in three folders, one in someone's personal drive, one printed in a binder from two years ago. If there are two versions, there are zero versions.

4. Nobody checks

If following the procedure and skipping it produce the same result in the weekly meeting, people will skip it. Not because they're bad people. Because they're busy, and the SOP feels optional.

5. They're too hard to follow

Fifteen pages, written by the person who already knows the job, with half the steps missing because they were automatic to the writer. I covered the fix in How to Write an SOP Your Newest Agent Can Follow.

6. The rewards don't match the effort

This is the one nobody talks about. If the agent who runs every checklist and the agent who wings it get treated the same, you've told the whole team the checklist doesn't matter.

Fix the structure and the people follow

When a team ignores its systems, the instinct is to blame the people. Motivate them. Lecture them. Replace them. In my experience, that rarely works for long, because the next person walks into the same broken structure.

Fix the structure first:

  1. One owner per SOP. A role, written at the top.
  2. One shared folder. Pinned in the team chat. Dated versions only.
  3. Install, don't announce. Walk it through, role-play it, run it live for 7 days, review it, lock it.
  4. Inspect what you expect. Every week, the numbers show whether the SOP ran.
  5. Make the right way the easy way. Load the action plans into the CRM. Put the checklist in the transaction platform. If following the SOP takes more clicks than skipping it, fix the tools.
  6. Reward what you want repeated.

The month-end war, and Cabo

At DirectLender, month end was a war. Seventeen-hour days. Every desk working a stack of loans that had to fund before the calendar flipped. Nobody pretended it was easy.

And then, the first week of every month, the winners flew to Cabo.

Here's why that worked, and it wasn't the beach. Everyone knew exactly what winning meant, because the procedures and the numbers made it visible. There was no mystery about who earned the trip and no politics about who got picked. The reward matched the effort, and the effort was measured by a system everyone could see.

That's what I mean when I say culture comes from systems. People will work extraordinarily hard when three things are true:

  1. They know exactly what good looks like.
  2. They can see where they stand, every week.
  3. The reward is real, and it goes to the people who did the work.

You don't need a trip to Cabo. You need rewards that are clear, earned and proportional: first pick of leads, a bigger split tier, public recognition with real numbers behind it, a day off after a record month. What matters is that everyone can see the line and knows what it takes to cross it.

"Don't ask the same question twice"

This rule does more to make SOPs stick than any meeting. When someone asks a question, answer it once and put the answer in the procedure. The next time anyone asks, the answer is "check the SOP." If it isn't there, that's on the leader, not the person asking.

Within a few months, your team learns that the system is the source of truth. They stop texting you for answers, and you stop being the bottleneck.

The weekly rhythm that keeps SOPs alive

SOPs don't die in a day. They erode, one skipped step at a time. The defense is rhythm:

  • Weekly numbers meeting. The same 7 KPIs, every agent reporting their own numbers. If a number is off, the first question is "which SOP didn't run?" The full meeting is in The Weekly Numbers Meeting: 7 KPIs.
  • One SOP review per week, on a rotating schedule, so all of them get a fresh look every quarter.
  • The 30-day review for every new hire, with one question that tells you more than any audit: "Which SOP did you skip, and why?"

A quick SOP health check

Score each of your procedures. Anything under 5 is at risk.

SOP: ______________________                  Yes / No
[ ] Has one named owner (a role)
[ ] Lives in the one shared folder, dated
[ ] Was walked through and role-played with the team
[ ] Has a checklist used on every live file
[ ] Has KPIs reviewed in the weekly meeting
[ ] Was reviewed in the last 90 days
[ ] Following it is rewarded, skipping it is noticed

Where coaches and systems meet

If you work with a coach, you already know the feeling: a great session, a clear plan, real energy, and then the week happens. Systems are what make that plan survive the week. Your coach helps you decide what to do and holds you to it. SOPs make sure it gets done the same way on a Tuesday afternoon when nobody is watching. They're on the same side.

FAQ

Why don't employees follow SOPs?

Usually because the procedure has no owner, nobody checks whether it ran, it's hard to follow, or following it earns nothing that skipping it doesn't. Fix those structural problems before deciding the people are the problem.

How do you get a real estate team to actually use SOPs?

Install each one instead of announcing it: assign an owner, walk it through, role-play the scripts, run it live for 7 days and review it in the weekly meeting. Then review the numbers every week and reward the people who run the system.

How do systems create culture on a team?

Systems make it obvious what good looks like and show everyone where they stand every week. When rewards clearly match that measured effort, performing becomes the norm. The culture follows the structure, not the other way around.

If your team has SOPs it doesn't follow, let's talk about fixing the structure.