The mechanic had the pump volute off. The impeller was out. He was there to replace a bearing — planned work, scope frozen six months back.
He ran a bore gauge across the wear rings. Clearance was double what the drawing specified. Not borderline. Double.
He wrote it on his clipboard, set the clipboard aside, and started installing the new bearing.
When his supervisor asked him why he didn't call it, he said the crew lead told him they weren't on scope for the wear rings. The Additional Work Request (AWR) process was buried. The Turnaround (TAR) manager was two units over, dealing with a fired heater outage. Nobody wanted to slow the job down.
Eighteen months later, that pump was running at 72% of design flow. Pulling excess amps. Operations had been complaining for a month before anyone pulled the trend data and traced it back. The wear ring clearance was the problem on the bench the day they had the machine open. The equipment told them. Nobody was listening.
There are exactly two categories of unplanned work in a TAR.
The first is scope creep. This is work that shows up after the scope freeze date and isn't warranted by equipment condition. Someone's wish list. A contractor suggests, "while we're in here." A manager who didn't hold the line when operations asked to add one more job. Scope creep is a management failure. It blows schedules, inflates costs, and gives contractors more opportunity to introduce errors during reinstallation.
The second is emergent scope. This is the work the equipment generates when you open it. Wear beyond tolerance. Corrosion that wasn't visible from the outside. A crack in an impeller nobody knew was there until the inspection tech got a flashlight on it. Emergent scope isn't optional — it's condition-driven. The machine opened its jacket and showed you something you couldn't see during normal operation. Now you have a choice: address it in an active TAR window with the machine already disassembled, or defer it and send the machine back into service knowing what's in there.
Both categories look identical on a scope change request form. Both show up as "additional work after freeze." That's exactly the problem.
What each one looks like on the floor
Scope creep doesn't trace back to a condition finding. You can't point to a measurement, an inspection report, or a failure mechanism. Someone decided to add the work. The equipment didn't ask for it.
Emergent scope leaves evidence. The wear ring is out of spec — there's a number. The seal face is grooved — you can photograph it. The shaft journal has a score mark that only appears when the bearing comes off — you can measure it against the Original Equipment Manufacturer (OEM) drawing tolerance and tell anyone who asks exactly why the work is warranted.
The discipline isn't about having a tougher posture on scope additions. It's about having a fast, repeatable method for telling the two apart while standing in front of an open machine.
The four questions that give you the answer
Before you approve or reject an AWR on an open piece of equipment, run it through four criteria. These are the four standard bases that justify scope addition in a structured TAR environment:
1. Condition threshold. Is there a measurement that puts this item outside the specification? Not "it looks rough" — an actual number against a drawing tolerance. A bore gauge reading. A vibration baseline comparison. A wear measurement against the OEM spec. If the answer is yes, the work has a defensible basis. If no measurement exists, you don't have an emergent scope finding. You have an opinion.
2. Risk mitigation. If this item goes back into service as-found, what's the realistic failure mode and timeline? You don't need a full Failure Mode and Effects Analysis (FMEA) on the floor. You need someone who knows the equipment to say: here's the expected failure path, here's roughly when. Low risk plus a near inspection window means deferral is a real option. A three-year run to the next TAR changes that calculus.
3. Regulatory requirement. Does the condition create a compliance obligation? Some inspection findings don't get a vote — statute or code takes the decision out of your hands. Know this before the conversation starts.
4. Opportunity work is accessible only during this window. Can this work only be done with the machine in its current state — disassembled, depressurized, isolated? If yes, the cost of doing it now is a fraction of doing it after reinstallation and restart. This criterion gets confused with scope creep most often. The difference is that legitimate opportunity work is defined by access, not desire. Replacing wear rings on a machine that's already open — with clearances measured outside spec — is different from adding a lube system flush because someone thought of it.
If a scope addition can answer all four honestly — measurement exists, risk is real, timing is either regulatory or access-driven — it's an emergent scope. The work should be done.
If none of the four criteria can be answered honestly — no measurement, no real risk case, no regulatory obligation, no genuine access argument — that's scope creep. Hold the line. A regulatory requirement or a genuine access case stands on its own, even without a measurement.
What the wrong call costs you — in either direction
The cost of approving scope creep is visible: schedule growth, budget overrun, more contractor-hours on the floor, and creating more opportunity for installation errors.
The cost of refusing an emergent scope is less visible in the moment and far more expensive later.
Industry average scope growth from freeze to execution is 19%. Top-quartile performers hold it to 7%. (AP-Networks Turnaround Database, 1,350+ observations.) The companies at 7% aren't saying no to everything. They're better at separating condition-driven additions from the other kind. The discipline runs in both directions: trace the work request back to a condition finding, or it doesn't belong in the scope.
The pump in the opening story? The mechanic had the answer on his clipboard. Clearance: 0.028 inches. Drawing spec: 0.012 to 0.014 inches. That's all the AWR needed. The number was there. The process to act on it wasn't.
Before your next TAR closes
Pull the last three AWRs that were rejected during your most recent TAR. Ask: Was each one rejected because it lacked a condition finding, or because someone said no without checking?
Then pull the three that were approved. Ask: Does each one trace back to a measurement?
Approvals without measurements: scope creep in your closed-out paperwork. Rejections that had numbers attached: deferred emergent scope running in the field right now.
That's where your next early-life failure is waiting.
See you next Friday.
Have you ever been in the room when a scope add got called — rightly or wrongly? What made the difference? Reply and tell me what happened. I read everyone.