← All episodes
Field Notes · · 7 min read

We Do Not Serve That Town

The coverage page is corrected. The old promise can still survive in a reply or in the material that writes the next page. Follow one correction through its uses.

One correction I passed along was about a town the business did not serve.

Simple fact. The correction had to reach the location pages, the rules used to create those pages, the coverage wording, and the information used to prepare quotes. It also called for checking the old routes and the coverage that should remain.

The interesting part was how far a short correction had to travel.

If you run operations, you may be the person carrying that distance. Somebody gives you the right answer. You change the obvious place. Then you need to find the other places still speaking for the business.

Here’s the thing. You have not finished correcting a business fact while the places that repeat it still make the old promise.

The page says one thing. The reply says another.

Take a hypothetical business with a settled service area. One town is outside it. The team has corrected the coverage page, and the page now reflects the actual boundary.

The person answering an inquiry opens a reusable reply. It includes the old coverage list. The town is still there, followed by an invitation to arrange a visit.

Nobody in this imagined business has decided to expand the area. Nobody answering the inquiry is trying to make a promise they cannot keep. They are using material the business gave them.

“I used the standard reply.”

That can be a completely honest explanation of a completely wrong promise.

The corrected page does not travel into that reply by itself. The reader gets the version in front of them. They might reasonably think the business will come to their town, because the business has just said so.

Now the operations person has two jobs: correct the reply and find out why it still contained the old answer.

Start with the decision that is already made

For this example, the territory question is settled. Keep it settled while you fix the things representing it.

The Professional Recipe calls a hard stop a Guardrail. Here the rule is straightforward: do not offer service outside the business’s approved coverage.

Context supplies the current facts for the particular request. Where is this person asking for service? Which approved coverage information applies? The person or AI preparing the answer needs both the boundary and the facts that let it apply.

“We said not to make things up.”

That instruction can miss this problem. In our hypothetical, the old reply contains a specific list. Someone following it can repeat the wrong claim without inventing a word.

The work is finding which information still has permission to speak as current.

Use the existing record of the business decision. If it is unclear which coverage rule is current, get that settled by the person responsible. A new draft cannot decide the service area just because it needs an answer.

But when the fact is clear, move on to its uses. Repeating the decision in another meeting does not update the reply.

Fix what makes the next version

Suppose the ops lead edits the reusable reply and removes the excluded town.

That corrects this piece of material. Now follow the page a step backward.

In our imagined setup, AI helps prepare location pages from a supplied coverage list. The finished page was corrected by hand, but the list feeding the next draft still includes the town.

Ask for the page again and the old promise has a route back in.

That is the part a visible edit can hide. The page looks right because somebody repaired the final words. The material used to produce those words has not caught up.

Right? You can fix the result and leave the next mistake fully prepared.

Follow that one claim back to what supplies it. It might be a business record, a reusable instruction, an example treated as current, or a list someone copies into the request. You do not need to learn the whole system to ask what the next version will use.

Then correct the relevant source through the normal process and prepare a fresh draft.

More precisely, inspect that fresh draft. Changing the source is a reason to expect a different result. Looking at what comes back tells you whether this attempt actually changed.

Ask the people who use the answer

A search for the town name is a useful start. It is not the whole job.

In the hypothetical business, a reply might promise service across the entire surrounding area without naming individual towns. A map might shade an area the written list excludes. Both deserve a look even if a text search finds nothing.

Ask the people who answer the question: where do you get the coverage information, and what do you give the customer?

You need the route people actually take when answering, including the version they reach for when they are busy. A document labeled current in a shared folder tells you where the answer should come from. The person doing the work can tell you whether it does.

The person replying may know about a saved message the website owner has never seen. The person preparing quotes may work from a different set of notes. Those are uses of the same business fact, even though they are different kinds of work.

“I thought the website was the official answer.”

It may be. That does not stop another current piece of material from contradicting it.

This is why the correction needs someone responsible for following it across the known uses. Each person can do their own edit correctly while the wider promise remains inconsistent.

Keep the scope on this fact. You are tracing a service-area correction, not asking the team to inventory everything it knows.

An old mention is not always a current promise

There is a distinction worth keeping while you search.

An old work record might accurately say the business once served that town. A dated message might preserve what someone actually told a customer. Those records can matter precisely because they show the previous state.

Removing the town from every historical sentence would make the record less truthful.

Ask whether the material is being used to answer today’s question. Is the old message simply a record, or has somebody copied it into a reusable reply? Is the old page clearly historical, or can a visitor still encounter it as current coverage?

Same town name. Different job.

Retire outdated guidance from current use while preserving the history that should remain. You can label or separate an old reference so it stops being offered as today’s instruction.

Here’s the thing. The target is the wrong current promise. A clean search result is only useful if it tells you something about that promise.

Check the remaining coverage too. Removing the excluded town should not accidentally make the business stop describing an area it still serves. The correction needs to preserve the right answer as well as remove the wrong one.

Leave the unfinished part visible

Back to our hypothetical ops lead.

The coverage page has been checked. The reusable reply has been corrected. A fresh page draft now uses the current list. The person responsible for quote preparation has not yet inspected the notes they use.

Is the correction finished?

You know which part is still open. Say that.

“Page and reply checked. Fresh page draft checked. Quote notes still need review.”

That is useful information for the person deciding what remains to be done. It gives them one next action instead of a confident completion message they have to trust or investigate from scratch.

You are not claiming that every possible use has been found. You are saying which uses you identified, what you observed, and where another person still owes the correction some work.

Does that make sense? The aim is a promise the business can stand behind, with the remaining work visible enough to finish.

Your Monday Move

Choose one recently settled correction to a territory, service, or operating fact. Bring the person who maintains that fact and the people who use it.

Confirm the current decision. List its known current uses and the material that will create their next versions. Ask where the answer is copied, reused, or turned into another format.

Correct those uses through the normal process, or put a name beside the remaining change. Inspect the actual outputs and one freshly prepared example. Check that the information which should remain is still right.

In the existing work record, distinguish what you checked, what still needs changing, and what nobody has inspected yet. Preserve historical material without letting it masquerade as current guidance.

Then close the correction to the extent those checks support, or give the first unfinished use a clear next action.

The fact may fit in one sentence. Finishing the correction means following where that sentence has gone.

Follow the correction as far as the promise travels.

Original framework. Distilled from client work.

~ keep going up next
~ if you got value here

Reu talks about this stuff on stages too.

Keynotes, panels, workshops. For conferences, operating companies, and trade associations.

Book Reu to speak →