A work order can look complete on a screen and still be impossible to execute.
It may have:
- a priority;
- an estimated duration;
- a technician;
- a due date; and
- a place on Thursday’s schedule.
Then Thursday arrives and the required seal is not in stores.
The schedule did not fail on Thursday.
The job was committed before it was ready.
Ready does not mean perfect
A ready job is not a job with every possible uncertainty removed.
That would cause small teams to over-plan routine work.
A practical definition is:
A job is ready when enough uncertainty has been removed that assigning it to a competent technician is reasonable.
The amount of preparation depends on the work.
A familiar inspection may need very little.
A multi-trade gearbox replacement in a short shutdown window may need substantial coordination.
Keep four decisions separate
Small teams gain control when they distinguish:
- Priority - How important is the work and what is the consequence of delay?
- Planning - What will the job require?
- Readiness - Are the important requirements sufficiently controlled?
- Scheduling - Are we committing capacity to this job in a defined period?
A P2 urgent job can be not ready because a part has not arrived.
A P3 routine job can be fully ready and available to fill a capacity gap.
A ready job does not automatically belong on this week’s schedule.
That distinction gives the scheduler choices instead of pressure.
The six-part Ready Gate
Before work enters the ready backlog, check six headings.
1. SCOPE
Ask:
- Is the correct asset or location identified?
- Is the intended work clear enough?
- Are the important boundaries understood?
- Can the team recognize what completion means?
- If the job is diagnostic, is the diagnostic scope bounded?
A work request describes a problem.
A job plan describes the work intended to address it.
Those are not the same thing.
“Oil leaking from gearbox” can lead to several different scopes.
Until the intended job is clear, labor, parts, access, and support cannot be planned reliably.
2. PEOPLE
Ask:
- What skill or trade is required?
- How many people are needed?
- Is specialist competence or authorization required?
- Is the labor estimate usable for weekly scheduling?
- Do several trades have to interact at a particular point?
Estimate labor-hours, not just elapsed time.
Two technicians working together for three hours consume six labor-hours.
If one electrician must join two mechanical technicians for part of a job, make that dependency visible.
3. MATERIAL
Ask:
- Have required parts been identified?
- Does the physical part actually exist?
- Is the quantity sufficient?
- Is the correct revision or specification available?
- Does important material need reservation?
- Should a multi-item job be kitted or staged?
“In stock” is not always the same as “controlled for this job.”
A CMMS record can be wrong.
Another breakdown can consume the last spare.
The wrong revision can be on the shelf.
For significant planned work, distinguish states such as:
Identified → Ordered → Received → Reserved → Staged
Not every nut and bolt needs reservation.
Use the level of control that matches the cost of a material failure.
4. ACCESS
Ask:
- Can production realistically release the equipment?
- Is the required access window long enough?
- Does operations need to empty, clean, cool, drain, or otherwise prepare the equipment through approved site arrangements?
- Can the technician physically reach the job?
- Is temporary access equipment required?
- Does a contractor need site access, passes, induction, or an escort?
“Machine stopped” may not mean “machine ready for maintenance.”
Access is a planning input, not a Thursday-morning surprise.
For jobs where production controls the window, use the production and maintenance access guide to move that agreement earlier.
5. SUPPORT
Ask:
- Are non-standard tools available?
- Is the current drawing or technical information available?
- Is a contractor arranged?
- Is another trade required?
- Is specialist test equipment needed?
- Are lifting or special-access dependencies known?
- Does every significant support dependency have an owner and next action?
Writing “need scaffold” into a work order is not enough.
Who is arranging it?
By when?
How will readiness be confirmed?
A dependency moves when somebody owns the wait.
6. CONTROL
Ask whether the job depends on formal site controls such as:
- equipment isolation or energy control;
- permit-to-work;
- authorized or competent personnel;
- electrical, lifting, hot-work, confined-space, pressure, chemical, or other specialist controls;
- production preparation;
- required post-maintenance checks; or
- formal return to service.
The planner’s role is to identify the dependency.
The planner should not invent technical safety procedures from memory or inference.
If an important control requirement is unknown, the job is not ready.
Urgency changes how quickly competent people may need to respond.
It does not remove the requirement.
Use a practical not-ready rule
If a material readiness requirement is unresolved, move the job to the appropriate waiting state and record:
- what is missing;
- who owns the next action; and
- when the condition will be checked again.
Examples include:
- Waiting - Part
- Waiting - Production Access
- Waiting - Engineering Decision
- Waiting - Contractor
- Waiting - Quote
- Waiting - Shutdown
- Waiting - Technical Information
This is much more useful than leaving everything marked “open.”
Conditional readiness needs a controlled condition
Some work can be ready subject to a predictable condition.
For example:
- access is confirmed for a defined production window; or
- a contractor is booked for a defined time and all other requirements are controlled.
Be careful with optimistic language.
“Part expected next week” is not the same as “part received, checked, and reserved.”
A ready label should mean something.
A smaller accurate ready backlog is more valuable than a large fictional one.
Readiness protects technician time
The Ready Gate is not paperwork for its own sake.
It is designed to remove predictable waiting before the technician reaches the job.
Typical avoidable losses include:
- searching for material;
- discovering access was never agreed;
- locating an unusual tool;
- waiting for another trade;
- clarifying a vague scope;
- finding an obsolete drawing; or
- discovering that a formal site requirement was never identified.
Planning does not need to eliminate every surprise.
It should remove uncertainty where the cost of not removing it is greater than the preparation effort.
Keep more ready work than the week needs
A healthy ready backlog acts as a buffer.
If production withdraws access to one job, another ready job with the right skill requirement can be pulled in deliberately.
This is different from improvising from the whole backlog.
The weekly schedule can then distinguish:
- committed work - what the team expects to complete; and
- candidate work - ready jobs available if capacity opens.
The weekly maintenance capacity guide shows how to decide how much work can realistically move from ready backlog into weekly commitment.
If the work entering the system is still vague or pressure-driven, begin one step earlier with the work-request standard.