The One Page SOP That Keeps The Review Ask Alive After You Stop Reminding People

You have already done this once.

You got fired up about reviews, told the team at a Monday meeting, maybe printed something. For about two weeks it worked. Reviews came in. You felt good.

Then it slowed down. Then it stopped. And the honest reason it stopped is that the only thing holding it up was you remembering to bring it up.

That is not a discipline problem on your team. That is a design problem. You built a habit that runs on your attention, and your attention has a hundred other jobs.

The fix is a page. One page, that a new hire can read in ninety seconds, that names one person and one moment.

Why the ask dies in three weeks

Anything that depends on somebody remembering will lose to anything that does not.

Your team is not refusing to ask. They are doing eleven things at the counter and the review ask is the twelfth. It is the one with no consequence attached, no customer waiting on it, and no reminder in front of them. So it drops off the list the same way it always does.

The stuff in your business that never dies is the stuff attached to a trigger. Card gets run, receipt prints. Job closes, invoice goes out. Nobody has to remember those because something else in the day pulls them along.

The review ask has to get attached to a trigger like that, or it will keep dying, and you will keep restarting it every few months and calling it a team problem.

One page, or it does not get read

Every business that has ever tried to fix this has a longer document somewhere. Six pages, scripts for every scenario, a flowchart.

Nobody has read it. You know they have not.

The version that works fits on one page and can be taped to the back of the counter, because the entire point is that a person can look at it, take the one thing they need, and get back to work. If it takes more than ninety seconds to read, it is a binder, and binders are where systems go to die.

The five lines the page needs

That is the whole document. Five lines.

The trigger. One specific moment, named exactly. Not "after a good interaction." That is not a trigger, that is a vibe. "When the tech hands the keys back." "After the second visit." "When they say the dog looks great." A moment somebody can point at.

The owner. One person by name. Not the team, not the front desk, not whoever is closest. A name.

The script. One sentence, written out word for word. People do not improvise well while doing something else, and an improvised ask comes out apologetic. Give them the words.

The tool. Where the thing is and what they do with it. The card lives here. You tap it here. That is it.

The number. What gets counted and when somebody looks at it.

If your page has more than those five things on it, cut until it does.

Name a person, or nobody owns it

This is the line most businesses skip and it is the one that decides whether the whole thing survives.

If the SOP says "the team asks," then when reviews stop coming in, there is nobody to talk to. Everybody assumed somebody else had it. That is not a character flaw, it is arithmetic. Shared responsibility with no name on it is unowned by default.

Put a name on the page. Not because that person does all the asking, but because that person is who you ask about it. They notice when it stops. They tell the new hire. They are the reason the system has a heartbeat when you are not in the building.

If you are a one person business, the name is yours, and the page still matters, because the version of you on a bad Thursday is a different employee than the version of you writing the page today.

Do this

1. 1Write the page today. Five lines, one page, no more.
2. 2Name one specific trigger moment. If you cannot point at it in your day, it is too vague.
3. 3Put one person's name on it as the owner.
4. 4Write the ask out word for word and use those exact words.
5. 5Put the tool where the trigger happens. Not in the office, not in a drawer.
6. 6Pick one number to check. Reviews this month is fine. Nothing more complicated.
7. 7Look at that number once a week, same day, for four weeks. That is what keeps it alive.
8. 8Read the page to every new hire in their first week. That is how it outlives the people who were there when you wrote it.
9. 9Put the page somewhere physical. A shared drive folder is where it disappears.

The real test is leaving

Here is how you find out if you actually built a system or just ran another push.

Stop mentioning it. Completely. Do not bring it up at a meeting, do not text anybody about it, do not say the word review for two weeks.

Then look at the number.

If reviews kept coming, you have a system and it belongs to the business now. If it stopped the week you went quiet, you never had a system. You had yourself, standing over it, which is exactly the thing you were trying to get out of.

That test is uncomfortable on purpose. Most owners already know the answer before they run it.

The tool part of that page should be the easiest line on it, so we make a tap card that does the whole ask in one motion, at shop.optechsol.llc.

Write the page this week. One page beats another Monday meeting every time.