Skip to content
Maintenance Management | Part 4 of 10

One Path for Every Maintenance Job

Notification, planning, scheduling, execution and feedback: a work order process with clear statuses, priority rules and cause codes that make the data usable.

A technician fixes a sensor on the way back from another job. The machine runs again, the operator is happy, and the repair disappears without a trace. Multiply that by a few hundred jobs per month and the plant has no idea where its maintenance hours go or which machines really fail.

A work order process gives every job the same path, emergencies included.

Five steps, five statuses

Step What happens Status
Notification Asset, symptom, priority, who noticed it Open
Planning Steps, hours, skills, parts, tools, permits Ready
Scheduling Placed in the week and in a production window Scheduled
Execution Done safely, as prepared Done
Feedback Actual hours, cause code, text, open points Closed

The status “Ready” is the most important one. It means the job can start without searching, waiting or asking. Only ready jobs go into the weekly schedule.

Priorities by rule

Without written rules, priority follows the loudest voice. Four levels are enough:

  1. Safety or environment at risk, or the bottleneck stopped: start immediately.
  2. An A or B asset stopped or quality at risk: start within the shift.
  3. The asset runs with limits, the job can be planned: next weekly schedule.
  4. Improvement or cosmetic, no effect on output: when capacity allows.

Test the rules with three real cases from last week. If the rules would have produced a different order than reality, discuss which one was right.

Emergencies are recorded too

Emergencies are repaired first and recorded afterward, at the latest by the end of the shift. Without the record there is no MTBF, no MTTR and no list of bad actors. This single rule often improves the data more than any software project.

Feedback that is usable

Ask for four things on every closed order: actual hours, downtime, component and cause code. Keep the cause list short so that technicians actually use it: wear, lubrication, contamination, operating error, design weakness, wrong setting, external, unknown. Eight causes and a handful of components are enough for a useful Pareto.

A short text completes the record: what was done, what is still open. “Fixed” is not a text.

Ten minutes every Friday

Every Friday, the planner checks the orders closed during the week: hours filled in, cause code set, text readable. Incomplete orders go back the same day. This routine costs ten minutes a week and keeps the data usable for everything that follows: backlog, key figures, bad actors and strategy reviews.

Paper, board or system

The path works on a whiteboard, in a spreadsheet or in a maintenance management system. Start with what the team will actually use tomorrow. A system makes the path faster and the data easier to analyze, but it does not create the discipline. Write the path down first, then choose the tool that fits it.

The next part shows how ready jobs become a weekly schedule.

Newsletter

One Lean idea.
Every week.