Released, but not ready to start: readiness in maintenance work

It is half past seven in the morning. The mechanical technician is standing next to the return sludge pump with a toolbox, the work order in hand, and the part has arrived. But the electrical panel has not been locked out yet, because the morning electrician has gone to another breakdown. The technician waits half an hour, then moves on to something else. By noon, when the electrician is free, the technician is at the other end of the plant.

Anyone who has worked in maintenance knows this scene. The work order was “approved”, but the job was not “ready to start”. This note is about the gap between the two.

Approval is a moment in the past

When the maintenance supervisor releases a work order for execution, they are saying: “the plan for this job is right, the procedure is known, the requirements are clear, and this job is authorised.” That approval happens at a specific moment, with the information available at that moment.

But conditions change after approval. A permit may expire. A part that was in the store may be used for a more urgent job. The standby pump may itself fail, so the duty pump can no longer be taken out of service. None of this makes the earlier approval “wrong”; it only shows that approval and readiness are two separate things.

Being released for execution is not the same as being ready to start.

If the two are treated as one, one of two things happens. Either every small change pulls the approval back and sends the job round the planning cycle again, which makes work slow and tiresome. Or approval is taken to mean “ready”, and in the morning the technician waits next to the pump.

Evaluate readiness for each action

A better approach is not to treat readiness as a fixed property of the work order, but to evaluate it for each action, at the moment it is taken. Readiness to “start work” is one question; readiness to “record completion” is another; readiness to “close” is a third.

To start work, these usually matter:

• Safety requirements such as electrical isolation and lockout are met.
• The permit, where one is needed, is valid.
• The owner team and the person doing the work are known.
• The execution window has opened.

To record completion the questions are different: does every task have a result? Has the expected evidence, such as a post-repair photo or a leak test result, been recorded?

When readiness is evaluated per action, there is no need to roll the whole work order back for every small change. The job stays “released”, and only “start” is unavailable until the blocker is resolved.

A blocker has to explain itself

“Not ready” on its own is not enough. The technician, the planner and the supervisor need to know why it is not ready and what would make it ready. A good blocker says four things:

1. Which action does it block? For example “start work”.
2. What is the reason? “Pump electrical isolation not confirmed.”
3. Where does it come from? “This work order’s requirements.”
4. How is it resolved, and by whom? “Record the isolation confirmation at MCC-02; electrical team.”

When the blocker is visible on the work order like this, the planner can act before the morning: coordinate with the electrician, or bring another job forward. And the technician does not wait for nothing.

A part shortage is not a blocker

One distinction needs to be stated clearly: a part that is not in stock is different from a blocker like isolation. A shortage must be visible and followed up, but it should not stop the job from being planned and released.

The reason is that a shortage is solved by planning and supply, not by stopping the work. If a work order cannot be released just because its part has not arrived, planning falls behind, and when the part does arrive the job still has to go through every step. It is better for the shortage to show as a warning on the work order, for the planner to request supply from right there, and for the warning to clear when the part arrives.

Emergency work

Of course, there is not always time for all of this. When the inlet pump trips at two in the morning and sewage is about to overflow, nobody waits for full planning. There has to be a way to start work as an emergency, but with minimums that cannot be dropped: the target, one immediate task, the reason for the emergency, the person who authorised it and the owner team.

What matters is that the controls bypassed in an emergency are recorded and followed up later. Emergency work should not be rewritten afterwards as an ordinary planned job; the history should say what really happened that night.

Readiness in the weekly plan

This distinction does not only help on the morning of the job; it helps with the weekly plan too. As the planner reviews the week’s released jobs, they can see next to each one whether anything blocks its start. A job blocked by isolation gets coordinated with the electrical team, a job whose permit is about to expire gets brought forward, and a job with a shortage warning is placed later, after the part arrives.

The result is a plan that falls apart less often in mid-week, and technicians who wait less.

In short

• Release for execution is a moment in the past; readiness is the state of today.
• Evaluate readiness separately for each action: start, record completion, verify, close.
• Every blocker should say what it blocks, why, where it comes from and how it is resolved.
• A part shortage is a warning, not a blocker.
• Emergency work has its own minimums, and the controls it bypasses are recorded.

The next morning, if the isolation blocker was visible on the work order the night before, the electrician goes to MCC-02 first, and by the time the technician arrives, the job is ready to start.