How to Prioritize Maintenance Work Orders When Everything is Priority 1

"This is priority 1!" "No, THIS is priority 1!" "Everything is priority 1!"

If everything is priority 1, nothing is. Yet this is the reality in most plants. Production wants everything fixed now. Maintenance can't do everything now. Chaos ensues.

You need a systematic approach to work order prioritization. Here it is.

Why Prioritization Fails

Failure 1: Everything is Priority 1

When requesters can set priority, they set everything to 1. Why? Because their request is important to them.

Result: No prioritization. FIFO (first in, first out) by default.

Failure 2: Priority by Volume

The loudest requester gets priority. The squeaky wheel gets the grease.

Result: Important work gets ignored while noisy work gets done.

Failure 3: No Clear Criteria

Priority is based on gut feel, not criteria. Different people prioritize differently.

Result: Inconsistent priorities. Important work missed.

Failure 4: Static Priorities

A priority set on Monday isn't reviewed on Friday. But conditions change.

Result: Stale priorities. Urgent work buried.

The Prioritization Framework

The Two Dimensions

Every work order has two dimensions:

Criticality — How important is the equipment?
Urgency — How soon does it need to be done?

Combine these to get priority.

Criticality Matrix

Criticality A (Critical):

Production stops if this fails
Safety risk if this fails
Environmental risk if this fails
Examples: Main production lines, safety systems, environmental controls

Criticality B (Important):

Production reduced if this fails
Redundant equipment (backup exists)
Examples: Secondary lines, backup pumps, non-critical utilities

Criticality C (Normal):

Limited impact if this fails
Easy to work around
Examples: Auxiliary equipment, office systems

Criticality D (Low):

Minimal impact if this fails
Run to failure acceptable
Examples: Non-essential equipment, aesthetics

Urgency Matrix

Urgency 1 (Immediate):

Fix now (within 1 hour)
Production down, safety risk, environmental release

Urgency 2 (High):

Fix today (within 8 hours)
Production impacted, impending failure

Urgency 3 (Medium):

Fix this week (within 5 days)
Preventive maintenance, minor issues

Urgency 4 (Low):

Fix this month (within 30 days)
Routine work, improvements

Urgency 5 (Planning):

Schedule for future
Projects, upgrades, non-urgent

The Priority Matrix

Combine criticality and urgency:

	Urg 1 (Immediate)	Urg 2 (High)	Urg 3 (Medium)	Urg 4 (Low)	Urg 5 (Planning)
Crit A	P1	P1	P2	P3	P4
Crit B	P1	P2	P2	P3	P4
Crit C	P2	P2	P3	P4	P5
Crit D	P3	P3	P4	P5	P5

P1: Do now (emergency) P2: Do today P3: Do this week P4: Do this month P5: Schedule for future

How to Assign Priority

Who Assigns Priority?

Not the requester. The requester always thinks their work is priority 1.

The planner or maintenance manager assigns priority, based on the matrix.

When is Priority Assigned?

At triage. When the work order is reviewed (daily or more often).

Can Priority Change?

Yes. Priorities should be reviewed:

Daily for P1 and P2
Weekly for P3
Monthly for P4 and P5

Conditions change. Priorities should reflect current reality.

The Triage Process

Step 1: Review New Work Orders

Each day, review all new work orders:

Verify criticality (correct equipment classification?)
Assess urgency (when does this really need to be done?)
Assign priority

Step 2: Review Active Work Orders

Check in-progress work:

Still on track?
Blocked? (Re-prioritize or escalate)
New information? (Update priority)

Step 3: Review Backlog

Review lower-priority work:

Has urgency increased? (Bump priority)
Can it be grouped with other work? (Batch it)
Should it be deferred further? (Push out)

Step 4: Balance the Day's Work

For today's work:

Start with P1 (emergencies)
Then P2 (today's must-dos)
Fill remaining time with P3 (this week)
P4 and P5 wait

The CMMS Role

Your CMMS should support prioritization:

Automatic Priority Calculation

CMMS calculates priority based on criticality and urgency. Planner confirms or adjusts.

Visual Priority Indicators

Color coding in work queues:

Red: P1
Orange: P2
Yellow: P3
Blue: P4
Gray: P5

Priority-Based Sorting

Work queues sorted by priority, not by date created.

Aging Alerts

Alerts when high-priority work is aging:

P1 older than 4 hours
P2 older than 1 day
P3 older than 1 week

Reporting

Reports on:

Work orders by priority
Average time to complete by priority
Backlog by priority

Handling Conflicts

Conflict 1: Too Many P1s

If you have 10 P1 work orders, you have a priority problem.

Solution: Only true emergencies are P1. Use P2 for "important but not emergency."

Conflict 2: Production vs. Maintenance

Production wants to keep running. Maintenance needs to do PMs.

Solution: Schedule PMs during production changeovers, slow periods, or weekends. Negotiate, don't argue.

Conflict 3: Short-term vs. Long-term

Fix it now (short-term) vs. fix it right (long-term).

Solution: Do the short-term fix to restore production. Schedule the long-term fix as a separate work order.

Conflict 4: Competing P1s

Two emergencies at once. Which first?

Solution: Safety always wins. Then environmental. Then production impact (dollar value).

The Rules of Prioritization

Rule 1: Safety First

Any work involving safety risk is P1. No exceptions.

Rule 2: PMs Protected

Don't bump PMs for low-priority reactive work. Skipping PMs creates future emergencies.

Exception: P1 emergencies can bump PMs. But reschedule the PM immediately.

Rule 3: No "Permanent" Priorities

Every priority is subject to review. What's P1 today might be P3 next week.

Rule 4: Document Decisions

When you prioritize, document why. "P1 because production line down, losing $5K/hour."

This helps with:

Future similar situations
Justifying decisions to stakeholders
Continuous improvement

Rule 5: Communicate

When you change priority, tell the requester. "Your work order was P2, now it's P3 because [reason]. Expected completion: [date]."

Common Prioritization Mistakes

Mistake 1: Requester Sets Priority

Problem: Everything becomes P1.

Fix: Planner sets priority based on criteria.

Mistake 2: Ignoring the Matrix

Problem: Priority based on gut feel, not criteria.

Fix: Use the matrix consistently. Train everyone on it.

Mistake 3: Never Re-Prioritizing

Problem: Priority set once, never reviewed.

Fix: Daily triage. Review and adjust.

Mistake 4: Not Communicating

Problem: Priorities change but requesters don't know.

Fix: Notify requesters of priority changes and expected completion.

Mistake 5: Confusing Important with Urgent

Problem: "This is important" becomes "this is urgent."

Fix: Important (criticality) and urgent (timing) are separate. Something can be important but not urgent.

Measuring Prioritization Effectiveness

Metric 1: Priority Distribution

What percentage of work orders are each priority?

Healthy distribution:

P1: 5-10%
P2: 15-20%
P3: 40-50%
P4: 20-25%
P5: 5-10%

Red flag: P1 is 30%+. You have a prioritization problem.

Metric 2: Time to Complete by Priority

P1: <4 hours
P2: <8 hours
P3: <5 days
P4: <30 days

Metric 3: Aging

P1 older than 4 hours: Investigate
P2 older than 1 day: Investigate
P3 older than 1 week: Investigate

Metric 4: PM Compliance

Are PMs being skipped to do reactive work? Target >90% compliance.

The Bottom Line

Prioritization isn't about saying "yes" to everything. It's about making tradeoffs explicitly and systematically.

Use the matrix. Criticality × urgency = priority. Triage daily. Review and adjust. Protect PMs. Don't sacrifice prevention for reaction. Communicate. Tell requesters what's happening and why.

When everything is priority 1, nothing gets done well. When priorities are clear, the right work gets done first.

Drowning in "priority 1" work orders? OpexMX provides automatic priority calculation, visual queues, and aging alerts. Bring order to chaos.