The Catalog Entry That Invites Scope Creep

Why this matters

Scope creep is usually blamed on the conversation at the job site, a customer asking "while you're here, can you also..." and a tech saying yes without pricing it. That is real, but it is only half the story. A lot of scope creep is baked into the catalog before the tech ever arrives: an entry written vague enough that "included" and "not included" were never actually decided. If the catalog itself does not draw the line, no amount of on-site discipline will hold it, because the tech has nothing firm to point to when a customer pushes.

The catalog patterns that create scope creep

Vague scope language. "Full inspection," "complete service," "as needed" sound thorough but commit to nothing measurable. A customer reasonably reads "full" as "everything," and when the tech's actual list is shorter than that, the gap gets filled on site, usually for free, to avoid an argument. Compare that to a written line-by-line scope: there is no ambiguity to negotiate away.

Bundled entries with an unstated boundary. A catalog entry that bundles several tasks together but never states where the bundle ends invites "one more thing" logic. If task four in the bundle blends naturally into an unlisted task five, most techs will just do task five rather than stop and explain why it's excluded.

"And similar" or "etc." in a written description. Any catalog language that trails off into an open category rather than a closed list hands the customer, and the tech, permission to expand the job on the spot.

No stated time or unit boundary. An entry priced flat with no stated cap on duration, quantity, or area implicitly promises unlimited effort for a fixed price. The customer isn't wrong to expect the job to be "done properly" for a flat price; the catalog just never told them what "properly" was bounded by.

A diagnostic entry that quietly becomes a repair entry. If the catalog does not clearly separate "we come look and tell you what's wrong" from "we come look and fix it," a tech under pressure will often just start fixing rather than stopping to write a separate estimate, especially if the fix looks quick.

What a scope-creep-resistant entry looks like

• A closed list of included steps or components, not an open category. "Includes X, Y, and Z" rather than "includes general servicing."
• An explicit exclusions line. State what is commonly assumed to be included but is not, directly in the entry. This does double duty: it protects margin and it sets the customer's expectation before the job starts, not during it.
• A stated boundary condition (a duration cap, a unit count, an area limit) with a clear next step when the job exceeds it: a change order, an add-on line item, or a re-quote, named in the entry itself so the tech has language ready.
• A clean split between diagnosis and repair where that split makes sense, so "look and tell you" and "look and fix" are never the same priced line item unless the entry explicitly says so.

Giving the tech language, not just a boundary

A well-scoped catalog entry only prevents creep if the tech actually uses it in the moment. Pair every bounded entry with a short, ready phrase the tech can say without it feeling like a confrontation: "That's outside what's covered in this visit, let me write it up as a quick add-on so it's priced fairly for both of us." A tech who has to invent that line on the spot, under a customer's expectant look, usually just does the extra work instead. A tech who already has the line memorized because the catalog entry taught it to them holds the boundary far more often.

The audit question to ask of every entry

For each catalog line item, ask: if a customer stood in front of the tech and asked for one plausible extra thing at the edge of this service, does the written scope give the tech a clear, immediate answer for whether that's included? If the answer is "it depends" or "the tech would have to use judgment," the entry is a scope-creep risk waiting for the wrong day to happen, and it belongs on the list for the next catalog audit.

References

• See related: Building the Catalog Entry for a Brand-New Service Line
• See related: One Price vs a Price Range in the Catalog Decision Tree
• Trade-standard practice for written scope-of-work definitions
• See related: Auditing the Catalog for Dead or Unprofitable Entries