Failure history improves preventive maintenance when teams translate past breakdowns into clearer tasks, better intervals, smarter inspections, and stronger root-cause learning. The point is not to do more PM; it is to do the right PM for the way assets actually fail.
Reliability Learning NoteMain point: Failure history improves preventive maintenance when teams translate past breakdowns into clearer tasks, better intervals, smarter inspections, and stronger root-cause learning. The point is not to do more PM; it is to do the right PM for the way assets actually fail. Treat this as an educational guide. Construction and maintenance decisions should be checked against project documents, local codes, manufacturer instructions, and qualified professional advice.
For extra context, this article refers to CIBSE maintenance engineering guidance and other relevant construction or facility guidance where it helps clarify the decision. Links are included in paragraphs so the article remains easy to read.
What failure history can reveal
Failure history includes work orders, breakdown notes, alarms, inspection findings, parts replacements, downtime, technician comments, photos, and repeat complaints. When organized well, it shows which assets fail, how they fail, how often, how severe the impact is, and whether existing PM tasks are preventing anything meaningful. Maintenance engineering guidance such as CIBSE Guide M treats maintenance as a managed technical discipline, not just a calendar of recurring jobs.
Clean the data before drawing conclusions
Bad history creates bad PM. Standardize asset names, failure codes, cause codes, locations, and work-order closeout requirements. Separate symptoms from causes. “Unit not cooling” is a symptom; a failed belt, fouled coil, bad sensor, low charge, or control issue may be the cause. If technicians are rushed into vague notes, the history will not support better planning. A small improvement in closeout quality can improve every analysis that follows.
Sort failures by impact
Not every failure deserves the same response. Rank history by safety impact, occupant impact, production or revenue impact, compliance exposure, repair cost, downtime, and recurrence. A low-cost nuisance that happens every week may deserve attention because it consumes labor and frustrates occupants. A rare but severe event may require a different control. The goal is to match PM effort to risk, not simply to assets with the most work orders.
Turn patterns into task changes
Once patterns are clear, update tasks. Add inspection points where early warning signs exist. Remove tasks that do not address a credible failure mode. Shorten intervals where failures occur before scheduled service. Lengthen intervals where clean history and condition readings support it. Add measurements, not just checkboxes: temperature split, vibration reading, amperage, filter pressure drop, run hours, leak rate, or belt condition. For concrete or building fabric issues, lessons from The right way to cure concrete in hot and cold weather can also inform future inspection criteria.
Use vendors and contractors carefully
Vendor service notes are part of failure history, but they need enough detail to be useful. Require clear cause, action, and recommendation fields. When outside work is competitively priced, the article on Bid leveling tips for comparing subcontractor proposals can help teams compare scope, exclusions, and assumptions. Good maintenance decisions depend on knowing whether a repeated failure is caused by poor design, poor installation, harsh operating conditions, skipped service, or unrealistic expectations.
Review PM changes after implementation
A PM improvement is a hypothesis. After changing a task or interval, review whether failures decrease, downtime improves, parts use changes, or technician time shifts. If nothing improves, revisit the failure mode. Avoid declaring victory from one good month. Also document why changes were made so future managers do not reverse them without understanding the evidence.
Where a standard, guidance note, or public resource is relevant, teams should compare project-specific requirements with BCA Design for Maintainability.
How to make technicians part of the analysis
Technicians often know failure patterns before dashboards show them. Ask what they see repeatedly, which assets are hard to access, which alarms are ignored, which parts fail after specific conditions, and which PM tasks feel pointless. Then compare those observations with work-order data. When field experience and history point in the same direction, the case for changing PM becomes stronger.
Make closeout notes easy to write well. A form with three useful prompts is better than a long form no one completes. Good prompts include: What failed? What likely caused it? What would help catch it earlier? Add required readings only when they will be used. If every work order demands irrelevant fields, technicians may rush through all of them.
Celebrate removed work as well as added work. Many teams only add PM tasks, which eventually overloads schedules and weakens compliance. If history shows a task does not address a meaningful failure mode, revise or retire it with documentation. A leaner PM program can be more reliable when every task has a reason.
A final review should include three practical checks. First, confirm that the people doing the work understand the decision, not just the document. Second, confirm that evidence will be captured in the normal workflow instead of in a separate system no one opens. Third, confirm that someone will review the result after the work is complete. Construction and maintenance improvements often fail because the first two steps happen during planning, while the third step disappears after turnover or closeout.
Use plain language in records. A future manager, technician, estimator, or owner representative should be able to understand what was decided, what was excluded, what risk remained, and what evidence supported the decision. That clarity is especially valuable when staff changes, warranties are questioned, or a similar project starts later. Good documentation does not need to be fancy. It needs to be findable, specific, and honest about uncertainty.
When the decision affects safety, code compliance, structural performance, life-safety systems, or contract liability, pause and involve the right licensed or qualified professional. Editorial guidance can frame the question, but project-specific advice must come from the responsible professional team.
Failure-history response matrix
| Failure-history signal | Possible PM response | Caution |
|---|---|---|
| Same part fails repeatedly | Inspect related conditions or change replacement strategy | Check installation, environment, and operating load first |
| Failures occur before PM date | Shorten interval or add condition trigger | Avoid over-maintaining without cause evidence |
| Many vague work orders | Improve closeout codes and technician notes | Data cleanup may be needed before analysis |
| Low failure but high consequence | Add risk-based inspection or redundancy review | Do not rely only on frequency |
Practical action framework for failure history preventive maintenance
- Define the decision or risk in one sentence before comparing options.
- List the people who must approve, perform, inspect, maintain, or document the work.
- Separate verified requirements from preferences, assumptions, and vendor claims.
- Record exclusions, open questions, and handoff requirements before work begins.
- Review the outcome after completion so the next project or maintenance cycle improves.
Make every breakdown teach the plan
The best PM program learns from the building. Every failure should make the next inspection sharper, the next task clearer, and the next decision easier to defend.
Informational disclaimer: This article is for general educational use only and does not provide professional engineering, legal, compliance, safety, procurement, or project-management advice. Always consult qualified professionals and the applicable project documents, codes, standards, and manufacturer instructions before making construction or maintenance decisions.
