It's 5:40am pre-shift. The superintendent opens the open-notification list and scrolls past 380 lines. The hydraulic hose weeping on Excavator 12 appears three times — logged by three operators on three shifts, each time as a brand-new issue. The oldest entry is 71 days old. Nobody ignored it on purpose; it just never became anyone's job. That is what weak maintenance backlog management looks like on a mine site: not a lazy crew, but a list nobody can read. This guide shows how to prioritise, age and close out the pile, and how HVI turns flagged defects into aged, trackable work orders so the list stops lying to you.
Same Six Weeks of Work. Very Different Risk.
Backlog size tells you volume. Backlog age tells you health. Switch between two sites with an identical backlog and see why one is fine and one is a breakdown waiting to happen.
- 0–7 days
- 8–30 days
- 31–90 days
- 90+ days
Those numbers explain why a long list isn't the real enemy. Backlog is simply approved work waiting for hours: divide the total labour hours in the queue by the hours your crew can really deliver each week. The trouble starts when old, unscoped or duplicated items sit inside that number and make it look either scarier or safer than it is. A demo of aged work orders per asset shows the difference in minutes. HVI's own backlog prioritisation case study covers how severity-based reporting cut one fleet's queue without adding technicians.
Maintenance backlog prioritization: a four-tier response ladder for mine sites
Most sites rank the backlog by whoever is loudest on the radio. Rank it by consequence instead. Give every notification a tier the day it's raised, and the weekly meeting becomes a short conversation about exceptions rather than a two-hour read-through.
| Tier | What goes here | Response window | Who owns it |
|---|---|---|---|
| P1 | Safety-critical: brakes, steering, cracked structure, fire suppression, seat belts | Same shift. Tag out until fixed | Maintenance superintendent |
| P2 | Production-critical: defects on A-class haul trucks, shovels, or the crusher feed | Within 7 days, built into the next window | Planner |
| P3 | Planned corrective: weeping seals, worn pins, cab faults that don't stop the machine | 2–4 weeks once parts are on hand | Planner and scheduler |
| P4 | Deferred or improvement: cosmetic items, nice-to-haves, repeat requests | Monthly review. Approve, fold into a PM, or cancel | Reliability engineer |
Tiering works best when it follows asset criticality, so start with an asset criticality ranking and your P2 list writes itself. A note for US readers: MSHA's 30 CFR 56.14100 (57.14100 for underground) expects safety defects on equipment to be corrected in a timely way, hazardous equipment to be taken out of service, and uncorrected defects to be reported and recorded. That's why P1 can't wait for Friday. Outside the US, check your regulator's equivalent.
From maintenance notification to closed work order
A notification is the “something's wrong” flag; the work order is the plan to fix it. Backlogs bloat in the gap between the two, when a flag is raised but nobody turns it into a scoped job with parts, people and a window. Here's the path every item should travel.
- 1Raised from the walk-around, with photo and voice note
- 2Triaged to a tier; duplicates merged
- 3Planned with parts, mechanic and permit
- 4Scheduled into a PM or shutdown window
- 5Closed with labour, parts and sign-off
In HVI, steps one to three are largely one motion. The operator marks an item Repair or Replace during the daily inspection, back-office is notified straight away, and a single click creates the work order with the mechanic assigned and parts consumed from parts and inventory. Steps four and five lean on meter-based preventive maintenance schedules, so corrective jobs can ride along with a service already booked. If your site raises notifications in SAP, HVI also offers an SAP integration. See how it works on your own fleet in a short maintenance workflow demo, and read how good mining planners and schedulers turn defects into jobs crews can actually execute.
Overdue maintenance work orders: age them, don't bury them
An overdue order isn't automatically a problem. A P3 waiting on a rebuilt component for three weeks is normal. A P2 sitting for 40 days with no parts request is a failure of follow-up. Sorting by age shows which is which, and each age band needs a different response.
Fresh: triage
Assign a tier, merge duplicates, confirm the asset and fault. This is the cheapest moment to catch a mislabelled P1.
Active: plan and source
Parts requested, permit identified, window booked. Anything here without a parts status gets chased this week.
Aging: escalate
Raise it at the weekly review with a named owner. Growth in this band often precedes a run of breakdowns.
Stale: verify or kill
Re-inspect the machine. If the fault is gone, cancel with a note. If it's real, it jumps a tier.
This is the kill-list habit: once a month, walk the 90-day-plus items and either confirm, escalate or cancel them. Because every HVI work order is timestamped with progress notes, age is visible rather than guessed, and analytics and reporting roll maintenance activity into weekly summaries for management. If you're ready to stop scrolling a spreadsheet, you can start free and put your open defects in one place. For recurring faults that keep coming back, pair this with a defect elimination program.
From a maintenance superintendent on a copper pit fleet
We had 412 open notifications on the haul fleet and I couldn't tell you which ones were real. About a third were the same leaks logged again by the next shift. I'd spend Monday morning just cleaning the list before I could plan anything.
Now a defect comes off the walk-around with a photo, becomes a work order, and has a date on it. At the weekly review I only look at what's over 30 days. Last quarter that was a short list, and every item on it had a name next to it.
Mining maintenance workflow: before and after
Here's how the daily friction changes when defects, orders and schedules live in one mining maintenance management platform instead of radios, shift sheets and spreadsheets.
- Defect reported over the radio or on a shift sheet
- Re-typed into a work order, often a day later
- Age of an item unknown until someone digs
- PM due dates kept in a planner's head
- Weekly report assembled by hand on Friday night
- Flagged in the walk-around with photo, voice note and signed PDF
- One click from inspection to work order
- Every order timestamped, with status and progress notes
- Meter or calendar schedules notify the mechanic when service is due
- Weekly maintenance and cost summaries delivered automatically
Maintenance backlog checklist for mining teams
Run this once a month. If you can't tick six of eight, the backlog is managing you. A quick demo of the HVI backlog workflow shows how each item maps to a real screen.
Every notification has a tier
P1 to P4 assigned on the day it's raised, not at the weekly meeting.Backlog measured in weeks
Ready hours divided by real weekly crew capacity, tracked by trade.Age bands reviewed weekly
Anything over 30 days has a named owner and a next step.Duplicates merged
One fault, one order, however many shifts reported it.Parts status on every planned job
On hand, ordered or unavailable, so waiting orders are visible.Safety defects closed with records
P1 items tagged out, fixed and signed off, with photos and dates.Monthly kill-list review
90-day-plus items verified, escalated or cancelled with a note.Corrective work linked to PM
Open defects ride along with the next scheduled service.Maintenance backlog management comes down to one weekly habit
The mines that get on top of their backlog don't have more technicians. They tier every notification, keep one path from defect to closed order, and look at age every week. Keep the ready backlog near two to four weeks, review anything older than 30 days by name, and kill the stale items monthly. Do that, and the list becomes a planning tool again instead of a graveyard.
If you want that discipline built into the daily walk-around instead of a spreadsheet, try HVI free on a few of your haul trucks. For safety follow-through, see how sites close out hazards in this guide to hazard reporting and corrective action tracking, and for the reporting side, read about automating mining maintenance reporting.
Maintenance backlog management: your questions answered
What is maintenance backlog management in mining?
It's the routine of tiering, planning, ageing and closing approved maintenance work so it doesn't pile up unseen. The aim isn't an empty list but a visible, owned one with enough ready work to keep crews busy.
How many weeks of backlog is healthy?
SMRP guidance puts ready backlog at about two to four weeks per crew, calculated as ready labour hours divided by weekly crew capacity. Consistently above six weeks usually means demand is outrunning capacity.
How do you prioritise a maintenance backlog?
Rank by consequence: safety first, then production-critical assets, then planned corrective work, then deferred items. Pair the tier with asset criticality and age so nothing important quietly drifts.
What's the difference between a maintenance notification and a work order?
A notification reports a problem. A work order is the approved plan to fix it, with scope, parts, labour and a schedule. Many sites also keep them in separate systems, such as SAP.
How does HVI help track overdue maintenance work orders?
HVI turns inspection defects into timestamped work orders in one click, with assigned mechanics, parts and progress notes. Weekly summaries then show management what's open and what it's costing.
Make your backlog a planning tool, not a graveyard
Run daily inspections from the cab, convert defects to work orders in one click, auto-schedule PM by meter reading, and give management weekly maintenance summaries. One platform for haul trucks, excavators, loaders, drills and support equipment.
Free trial · One-click work orders · Meter-based PM schedules
