Ready to optimize your next project? Call Us at +1 815 603 2871

Engineering & Procedure Development

The Checklist Is Not the Commissioning Plan

November 5th, 2027

Hand holding a thermal imaging camera in front of electrical switchgear.

Somewhere on every project there is a checklist with a lot of boxes. It has been reviewed, formatted and issued. It may be printed and clipped to a board.

It is a useful document. It is not a plan.

A checklist answers a narrow question: did we remember this item? A commissioning plan answers a harder one: what has to happen, in what order, by whom, and what will we do when it does not go that way?

The confusion between the two is one of the quiet reasons startups get into trouble.

What a Checklist Does Well

Checklists are excellent at catching omissions. They stop a crew from forgetting the torque record, the lubrication check or the temporary blind removal. They make a repeated task consistent. They give a reviewer something concrete to sample.

They are also good at capturing knowledge from the last startup. The item that caused a problem last time becomes a line on the list this time. That is valuable, and it should keep happening.

But a checklist is a memory aid. It does not decide. It does not sequence. It does not tell you what to do when box seven cannot be checked because the vendor is not on site.

Where the Checklist Runs Out

The trouble starts when the checklist becomes the plan by default, because it is the only document in the room.

A checklist can say "verify the interlock." It cannot tell you which interlock matters most for the first energization, who signs it, what the acceptance criterion is, what happens if the test fails or which system is allowed to proceed while the fix is being planned.

A checklist can say "flush the system." It cannot tell you the flush loop, the velocity, the acceptance standard or the sequence relative to the neighboring system that is still under construction.

Those are plan decisions. They require someone to think about the specific plant, not just the standard list.

A Plan Has a Spine

A commissioning plan connects the work to the milestone. It should make four things visible:

  • Systems and boundaries: what is included, what is excluded and who owns the interface.
  • Sequence and prerequisites: what must be true before each activity can start.
  • Acceptance: what evidence closes each step and who signs it.
  • Contingency: what happens when a step slips, fails or depends on someone else.

A checklist can sit inside that structure. It cannot replace it.

The Difference Shows Up at the Gate

A plan is tested when the project reaches a hold point and something is not ready. The checklist says the item is open. The plan says what happens next.

Does the system stay isolated while the rest proceeds? Does the milestone move? Does the vendor get escalated? Does the work continue at risk, and who accepts that risk? These are the decisions that keep a startup moving without pretending the gap is not there.

Teams with a plan make those calls quickly. Teams with only a checklist tend to wait for someone senior to decide, which is another way of saying the plan does not exist.

Use Both, in the Right Order

The order matters. Build the plan first. Then build the checklist from the plan.

When the plan defines the sequence, the acceptance criteria and the owners, the checklist becomes a field tool that confirms the plan is being followed. When the checklist comes first, the plan becomes whatever is left over after the boxes are formatted.

Review both before the milestone, not after. Walk the plan with the field team and ask where the checklist does not cover the real work. Add what is missing, remove what is obsolete and fix the sequence before it becomes a delay.

Progress Is Not a Full Board

A wall of checked boxes feels like progress. It can hide a startup that is not ready, because the checklist does not know what the milestone actually needs.

The plan knows. Keep it close, keep it current and keep asking the question the checklist cannot answer: what has to be true for this system to be handed over?

At Volantis Group, Inc., we develop commissioning plans and procedures that connect system boundaries, sequence, acceptance criteria and ownership before the field work starts. If your checklist is doing a plan's job, contact our team.

Posted in: Engineering & Procedure Development