Job Plans Are Not Documents. They Are Execution Designs.

Written on: November 18, 2026

Two job plans for the same work.

The first says: "Repair pump P-101A."

The second says: replace the inboard bearing on P-101A, using the verified procedure, with the bearing and seal kit staged, the lift plan for the motor, the alignment tolerances and method, the isolation and permit requirements, the torque values, and the acceptance criteria that say when the job is actually done and the pump is fit to run.

Same failure. Same asset. Same craftspeople, maybe. But those two plans produce completely different days. The first sends a crew to figure it out in the field, on the clock, with whatever they can find. The second sends them to execute a job that's already been thought through. One is a work request wearing a planner's name. The other is an execution design.
In the last post we looked at why thin plans fail. This one is about what a real plan actually is, and why building it well is one of the highest-leverage jobs in the whole plant.

Planning Is Not Clerical Work
Somewhere along the way, a lot of organizations decided that planning is paperwork. The planner is the person who fills in the fields, attaches the estimate, and moves the work order along so the schedulers and crews can do the "real" work. Treated that way, planning becomes a clerical bottleneck, and the best planners get pulled off it the moment there's an emergency to chase.

That's a serious misread of what planning is. A planner isn't transcribing a job. They're designing how it will succeed: anticipating what the crew will face, resolving the problems in advance that would otherwise be discovered at the work front, and turning scattered asset knowledge into a package anyone qualified can pick up and run. Done well, planning removes variation, cuts discovery work, reduces safety exposure, and breaks the plant's dependence on a handful of veterans who happen to remember how this particular pump comes apart. That's not clerical. That's engineering the execution.

What an Execution Design Actually Contains
So what separates a real execution design from "repair pump"? A handful of things, and each one removes a question the crew would otherwise have to answer in the field:
  • Clear scope and verified equipment identification, the right work on the right physical asset, confirmed.
  • A sequenced set of steps, the actual order of operations, not just a task name.
  • Skill and labor requirements, who and how many, with a realistic duration.
  • Parts, consumables, and a complete bill of material, down to the gaskets and fasteners, not just the headline component.
  • Tools, lifting, scaffold, and specialty support, the enabling gear the job quietly depends on.
  • Safety and permit requirements, the isolations, controls, and clearances named up front.
  • Operational interfaces, what has to be coordinated with operations and with other crafts.
  • Drawings, procedures, specifications, and quality checks, the technical references the crew needs at hand.
  • Restoration and acceptance criteria, how the asset gets returned to service and how you know the job is truly done.
Not every job needs all of it at full depth. But every one of those elements is a question. Answer it at a desk, in advance, and the crew executes. Leave it unanswered, and the crew answers it in the field, slower, at higher risk, and probably differently every time.

Standard Job Plans Are Living Assets
Here's where the leverage compounds. Most plants do the same jobs over and over, the same pump overhaul, the same valve rebuild, the same exchanger cleaning, and yet re-plan them from scratch every time, or worse, wing them.

The fix is the standard job plan: a proven execution design for recurring work, built once and reused. But a standard job plan only stays valuable if it's treated as a living asset, not a frozen template. Every time a crew runs it, they learn something, a step that was out of order, a part number that changed, a tool that wasn't listed, a duration that was always wrong. If that feedback flows back into the standard, the plan gets a little better every cycle, and the work gets a little easier every time. If it doesn't, the standard slowly drifts out of date until people stop trusting it and go back to winging it. A living standard job plan is one of the highest-return assets a maintenance organization can build. A frozen one quietly becomes another document nobody uses.

Experience Belongs in the System, Not Just in People's Heads
Good planners lean hard on experience, and they should. But there's a difference between using experience and depending on it.

When the knowledge of how a job really goes lives only in a veteran planner's head or a senior tech's memory, the plant is one retirement away from losing it. The whole point of a good execution design is to move that knowledge out of individual heads and into a package the system owns. The planner's experience shows up in the quality of the plan, the sequence that avoids the trap, the note about the fitting that always seizes, the tool that saves an hour, not in their personal availability the day the job runs. That's how you get consistency without cloning your best people, and how you make sure their hard-won knowledge outlasts their time on site.

Don't Over-Design Either
One caution, because this cuts both ways. Not every job deserves a full execution design, and treating a bearing swap and a two-bolt filter change with the same rigor is its own waste.
Match the depth to the work. A simple, low-risk, repetitive job needs a light plan and a clear parts list, and nothing more. The heavy design effort belongs on the complex, the high-consequence, and the recurring work where getting it right, once, pays off many times over. Over-planning simple jobs burns planner capacity you need for the jobs that actually reward it, and it teaches crews to ignore the paperwork because most of it is overhead. The skill isn't planning everything to the same depth. It's knowing which jobs earn the full design and which ones just need the essentials.

The Bottom Line
A job plan is not documentation you complete before work. It's the execution designed before the crew arrives, the difference between "repair pump" and a package that tells a qualified crew exactly how the job succeeds.

Build that design well, keep the recurring ones alive with field feedback, and move the knowledge out of people's heads and into the system, and planning stops being a clerical step and becomes what it should be: one of the highest-leverage disciplines in the plant. The crew's day is decided long before they pick up a tool, at the desk where someone either designed the work or just described it.

Next in the series, we turn to a number leaders love to trust and shouldn't take at face value: schedule compliance. Because a high compliance score can hide as much as it reveals.

John Crager, CMRPPrincipal Advisor, APVantage LLC

APVantage helps industrial organizations optimize their maintenance execution practices by helping teams not only understand the problem but develop solutions that actually fit their unique situations.

Interested in learning more?

Contact us today to discuss the details of your project or maintenance event needs. We look forward to working with you.

Contact Via Email
Call Us at +1 832-240-4994