Every facility has them: work orders that sit at "in progress" or "on hold" for weeks while everyone assumes someone else is handling them. The repair itself is rarely the problem. The job is waiting on a part, a key, a permit, a dry day, an approval, or a vendor, and nobody has named the wait or owned it. Blocker analysis turns those silent delays into categorized, measurable, and fixable causes. This guide shows how teams define blocker states, review them weekly, and use Oxmaint work order management software to keep stuck jobs moving.
WO Blocker Analysis: Why Work Orders Get Stuck
A stuck work order is a work order with an unnamed blocker. Name the blocker, assign an owner, set an expected clear date, and review the list on a fixed rhythm.
The hidden cost of vague hold states
A generic "on hold" status is a parking lot. It tells nobody what is wrong, who must act, or when the job will move again.
Vague hold status
- No reason recorded, so the same delays repeat
- Nobody owns the unblocking action
- Aging jobs hide inside averages
- Requesters hear "still pending" with no detail
- Technicians lose track of what they can restart
- Backlog reports look worse than the real workload
Named blocker states
- Every hold carries a reason code and a note
- One person owns each unblocking action
- Aging is measured by blocker type
- Requesters receive a specific explanation and date
- Technicians see exactly when work can resume
- Backlog separates workable jobs from waiting jobs
A blocker taxonomy that works in commercial buildings
Keep the list short enough that technicians pick the right code in seconds, yet specific enough that the weekly review can act on it.
| Blocker | Typical cause | Who owns the clear | Standard unblocking action |
|---|---|---|---|
| Waiting on parts | Item not stocked, supplier delay, wrong part ordered | Storekeeper or buyer | Confirm order, expected date, and interim workaround |
| Waiting on access | Tenant space locked, key holder unavailable, restricted area | Building or tenant coordinator | Book an access window and confirm it with the requester |
| Waiting on approval | Quote needs sign-off, spend above authority limit | Approving manager | Escalate with cost, risk, and decision deadline |
| Waiting on weather | Roof, facade, or external work in rain, wind, or heat | Supervisor | Reschedule against the forecast and secure the area meanwhile |
| Waiting on vendor | Contractor not yet scheduled, specialist call-out pending | Contractor coordinator | Confirm visit date and record it on the work order |
| Waiting on shutdown | Needs a power, water, or HVAC outage window | Operations manager | Include in the next planned outage and notify occupants |
| Waiting on information | Missing drawings, unclear description, unanswered question | Dispatcher | Contact the requester or technician and set a reply deadline |
| Waiting on another trade | Dependent work must finish first | Supervisor | Link the dependent jobs and agree the sequence |
Rules every blocked work order must satisfy
A blocker state is only useful when it is complete. Make these four rules mandatory, so a job cannot be parked without them.
- Reason codePick from the standard list. No free-text reason replaces the code.
- Named ownerA person, not a team, is responsible for clearing the block.
- Expected clear dateA realistic date, reviewed and revised when it slips.
- Interim actionAny temporary fix, barrier, or signage that keeps people safe meanwhile.
Make every delay visible and owned
Record why work is waiting, who must act, and when it should clear, so stuck jobs stop hiding in your backlog.
Reading aging by blocker
Average completion time hides the worst offenders. Group blocked jobs by how long they have waited, then by the reason.
The weekly blocker review in thirty minutes
A short, fixed meeting beats an occasional long one. Keep it focused on decisions, not status reading.
- Sort by age and priorityStart with the oldest high-priority blocked jobs.
- Confirm each ownerAsk for the action taken since last week and the next date.
- Escalate what cannot moveTake approval and funding questions to the person who can decide.
- Look for patternsNote repeated causes, such as the same part or the same tenant area.
- Assign a systemic fixTurn one pattern into a stocking change, a standing access slot, or a revised limit.
Turning blockers into permanent fixes
Clearing a single stuck job helps once. Fixing the cause helps every future job of the same type.
Common blocker analysis mistakes
Too many codes
A list of thirty reasons produces random choices. Start with six to ten and add only when a recurring cause has no home.Blocked time counts as work time
If waiting time is mixed into repair time, technicians look slow. Measure hands-on duration and waiting duration separately.No consequence for stale dates
An expected date that never changes is meaningless. Require a reason when it moves.Reviews that only read lists
If the meeting never leads to a decision or a systemic fix, attendance drops and the list grows.Blocker KPIs worth reporting
Blocked share of open orders
Blocked work orders divided by all open work ordersAverage blocked duration
Mean days spent in any blocker state, by reason codeTop three blockers
Reason codes that account for the most blocked days this monthHands-on versus waiting time
Ratio of active work hours to elapsed calendar timeDate slip rate
Blocked jobs whose expected clear date moved at least onceAged blocked orders
Blocked jobs older than the escalation thresholdHow Oxmaint helps clear stuck work orders
Oxmaint is maintenance management software. It gives your blocker process a place to live, while your team chooses the codes and review rhythm that suit your sites.
Work order status and notes
Record the reason a job is waiting, who owns the next action, and the date it should move.Inventory and spare parts
Track stock levels and reorder needs so common parts delays are caught early.Scheduling
Plan outage-dependent and weather-dependent work into the right windows.Mobile updates
Technicians flag a blocker from the site with a note and photo the moment they find it.Dashboards and reports
Review open and aging work by status, priority, and building to prepare the weekly meeting.Asset history
See whether the same asset keeps producing blocked jobs, which points to a deeper fix.Hands-on time versus waiting time
Elapsed time from open to close mixes two very different things. Separating them shows whether delay comes from the work itself or from everything around it.
Hands-on time
Hours a technician actually spent working on the job. It reflects task difficulty, skill, tooling, and how well the job was planned before the visit.Waiting time
Calendar time spent in a blocker state. It reflects stocking, access arrangements, approvals, supplier lead times, and scheduling discipline.Queue time
Time between request and the start of work when nothing is blocked, only unassigned. It points to capacity and dispatch practice, not to blockers.Why the split matters
Hiring more technicians cannot fix a job that spends most of its life waiting for parts. Measure the split before investing in a remedy.Parts blockers in depth
Parts are usually the largest single blocker in a reactive maintenance team. The causes are different, so the remedies should be too.
| Cause | Early signal | Prevention | Fallback when it happens |
|---|---|---|---|
| Item not stocked | Repeated purchases of the same part | Add it to stock with a reorder point based on usage | Check sister sites and local suppliers for a same-day source |
| Wrong part ordered | Returns and second orders on the same job | Record part numbers and nameplate data on the asset | Confirm the nameplate on site before reordering |
| Long supplier lead time | Quoted delivery in weeks rather than days | Hold critical spares for single-supplier equipment | Arrange a temporary repair and note the residual risk |
| Part received but not issued | Goods sitting in receiving | Notify the job owner automatically on receipt | Walk the receiving area weekly against open orders |
| Obsolete component | Supplier no longer lists the item | Flag aging equipment and plan replacement early | Seek a compatible substitute or refurbish the unit |
Access and tenant blockers
Access delays are the most frustrating because the technician is ready and the problem is known. They are also among the easiest to reduce through agreements made in advance.
Approval blockers: authority limits that match risk
An approval queue works best when each tier has a clear owner, a clear limit, and a clear response time. The limits below are placeholders for your own policy.
Dependency blockers: sequencing work across trades
Some jobs cannot start until another has finished. Without a recorded dependency, the second trade turns up too early or too late.
- Identify the predecessorName the work order that must finish first, such as isolation before electrical repair.
- Link the recordsConnect the jobs so the dependent order shows as blocked by a specific, visible record.
- Agree the handoverDefine what counts as finished, such as drained, isolated, cooled, or tested.
- Release the next tradeNotify the next technician the moment the predecessor closes, with a booked time.
- Close the loopClose all linked jobs together and record the total elapsed time for the whole repair.
Telling requesters why their job is waiting
A specific, honest message about a delay is received far better than silence. Match the message to the blocker type.
Parts
Say which part is on order, the expected arrival, and whether a temporary fix is in place.Access
Offer visit windows and ask the requester to confirm one, with a backup contact.Approval
Explain that cost approval is pending and when a decision is expected.Weather
Describe the conditions needed and the next suitable day on the forecast.Vendor
Share the contractor's confirmed visit date, or the date by which one will be given.Shutdown
Give the planned outage date, which areas are affected, and the expected duration.A supervisor checklist for blocked jobs
Use these questions on every blocked job during the weekly review. Together they take only a minute or two per record and keep the list honest.
Is the reason still true?
Parts may have arrived or access may have opened since the code was set. Reopen the job for scheduling as soon as the block has cleared.Does the owner know?
Confirm that the named person is aware of the action expected from them, and has agreed to the date shown on the record.Is the site safe meanwhile?
Check that barriers, signs, or temporary repairs remain in place, and that the interim action is recorded on the work order.Should the job be split?
If part of the work can proceed, split it so the unblocked portion is completed while the remainder waits for its own blocker.Stuck work order FAQs
How many blocker reasons should we start with?
Six to ten is usually enough: parts, access, approval, weather, vendor, shutdown, information, and dependency. Add more only when a repeated cause does not fit.
Should blocked jobs count against technician performance?
No. Waiting time usually sits outside the technician's control. Report hands-on time and blocked time separately to keep measures fair.
Who should lead the weekly review?
The maintenance supervisor or planner, with the storekeeper and contractor coordinator present. They own the most common clearing actions.
What if the same blocker keeps recurring?
Treat it as a process problem, not a job problem, and assign a systemic fix. Oxmaint reporting shows which reasons repeat.
How do we start with minimal effort?
Begin by requiring a reason and owner on every held job. Book a demo to plan the status setup.
Keep work orders moving to completion
Give your team a clear view of what is stuck, why, and who will clear it, week after week.
