The standard didn't break. It drifted.

Nobody announces that a standard is dead. It just gets missed once, and nothing happens, and then it gets missed on a Tuesday when you're at a 20-group, and then a rep who started in March never learns it existed in the first place.

Six weeks later you're in a meeting saying "we do a trade walk on every appraisal" and three people are looking at their shoes.

That's process drift. It doesn't come from bad reps. It comes from missed occurrences that were never closed out.

The fix isn't a bigger speech at Saturday meeting. It's a four-step reset you run on a single missed occurrence, within a day or two of it happening:

  1. Document the exception — what specifically didn't happen, on which deal, on what date.
  2. Remove the obstacle — figure out whether the standard was even executable that day.
  3. Restate ownership — say out loud who owns the step and what "done" means.
  4. Inspect the next occurrence — go look at the very next one, on purpose, and tell the rep you're going to.

Four steps, maybe twelve minutes. Do it right and the standard holds. Skip step four and you've just had a conversation.

Step 1: Document the exception, not the pattern

Most managers wait until they have a pattern. "I've noticed you've been skipping the trade walk lately." That's a losing sentence. It's vague, it's plural, and it invites the rep to argue about "lately."

Document one occurrence with four facts: the deal, the date, the step, and the evidence.

"Stock 41182, the Traverse deal on Thursday. Our standard is a walkaround on the trade with the customer present before the number goes to the desk. The appraisal came over at 2:40 and you were still with the customer at the desk at 2:55. Walk me through what happened."

Notice what that isn't. It isn't "you always." It isn't "the team has been sloppy." It's one thing, one day, with a timestamp the rep can check.

This matters for a reason that has nothing to do with tone. A single occurrence is fixable. A pattern is an identity. When you tell a rep they "always" skip a step, you're describing who they are, and people defend who they are. When you tell them Thursday's Traverse deal missed a step, you're describing an event, and events get fixed.

Write it down somewhere you'll see it again — the one-on-one doc, a note in the CRM, a running list on your phone. Not for HR. For step four.

Step 2: Remove the obstacle before you assign blame

Here's where most resets die. The manager assumes the answer is "the rep didn't care," delivers a correction, and moves on. Two weeks later, same miss, because the actual cause was structural.

Ask one question and shut up: "What made it hard to do it that way on this one?"

Real answers you'll hear on a showroom floor:

  • "The used car manager was at auction and I couldn't get a number without the walk documented, so I did the walk after."
  • "The customer wouldn't get out of the chair. She wanted the payment first."
  • "I don't have the appraisal form on my tablet, it's on the desktop in the tower."
  • "Nobody told me that was the order. I've been doing it the other way since I started."
  • "I know the standard. I got busy and I cut the corner."

Only the last one is a performance conversation. The other four are your problem, not the rep's.

And you have to actually remove the obstacle before you go to step three, because if you restate ownership on top of a broken process, you've just told a rep to own something they can't execute. That's how you lose good people quietly.

If the obstacle is the customer — "she wanted the payment first" — that's not an excuse, that's a script gap. Give the rep the words:

"Absolutely, I'll get you a number. To get you the most I can for the Traverse I have to put eyes on it with you — two minutes, we'll be right back at this table. Grab your keys?"

Now the standard is executable in the exact situation that broke it.

Step 3: Restate ownership out loud

Short and unambiguous. Who does it, when it happens, and what proof looks like.

"So going forward: on every appraisal, you do the walk with the customer before the appraisal request goes to the desk. Not the porter, not me — you. And 'done' means the four photos and the condition notes are attached to the appraisal in the CRM. If the used car manager isn't here, you still do the walk and note it. Are we clear on that, or is there a scenario where that doesn't work?"

Two things earn their keep in that paragraph.

"What 'done' means." Most dealership standards fail because "done" was never defined. "Do a proper trade walk" is a suggestion. "Four photos and condition notes attached before the request goes to the desk" is a standard. If you can't tell whether it happened by looking at something, you don't have a standard — you have a preference.

"Or is there a scenario where that doesn't work?" You're inviting the objection now, in the office, instead of discovering it later on the floor. A rep who says "what about the after-hours ups?" just saved you three weeks of drift.

Step 4: Inspect the next occurrence — and say that you will

This is the whole thing. The first three steps are a conversation. Step four is what makes it a reset.

Tell the rep exactly what you're going to look at:

"Your next appraisal, whenever it comes in — today, tomorrow — I'm going to open it and look for the photos and the notes before it hits the desk. Not to catch you. So we both know it's back on track."

Then actually do it. Set a reminder. Check the next appraisal that rep submits, not "sometime this week."

Three outcomes, three responses:

  • It happened, correctly. Say so, that day, in ten words. "Saw the walk on the Equinox. That's the standard. Thanks." That ten-second message is what converts a corrected miss into a habit. Skip it and the rep learns that only misses get attention.
  • It happened, but sloppy. Two photos, no notes. That's not defiance, that's a definition problem. Tighten "done" and inspect the one after that.
  • It didn't happen. Now, and only now, you have a genuine accountability conversation — because you documented, removed the obstacle, defined done, and announced the inspection. Nothing is ambiguous. This is the point where a rep either changes or tells you something honest about whether they want the job.

One occurrence, not a report

The temptation is to turn step four into a monthly compliance audit across twelve reps. Don't. Audits tell you about the population. You're trying to reset one person on one standard, and that takes one inspection of one deal, close to the event.

The other reason to keep it narrow: you'll actually do it. A monthly audit gets skipped in a bad month. Checking one appraisal takes ninety seconds.

What this looks like across a month

You're not running this on everything. You're running it on the two or three standards that actually drive gross and CSI at your store — trade walk, financeability check on the first pencil, whatever your version is.

Realistically that's four or five resets a month per manager. Documented in a line each:

DateRepStandard missedObstacle foundNext occurrence inspected
3/12DanaTrade walk before deskForm only on tower desktop3/13 — clean
3/14MarcusPayment before credit pullNone. Corner cut.3/15 — clean
3/19EllisTrade walk before deskNever taught in onboarding3/20 — 2 photos, retighten

Five lines like that tell you something a dashboard can't: which of your standards keep breaking for structural reasons. If three different reps hit the same obstacle, that's not a coaching problem, that's a process you need to rebuild. Ellis's line above is a signal your onboarding is missing a step, and no amount of individual coaching will fix that.

That's the quiet payoff. Running the reset consistently doesn't just hold the standard — it tells you which standards were never really installed in the first place.

If you're already reviewing recorded calls and appointment-setting conversations, this is where the evidence for step one comes cheap: you don't have to remember what happened on the Traverse deal, you can go listen. Tools like MoreSignal exist to surface exactly which step got skipped on which conversation, so the reset starts with a fact instead of a hunch.

But the tool isn't the point. The point is that a missed standard needs a closed loop with a date on it — otherwise you're just repeating yourself in Saturday meeting and calling it accountability.