Many facilities have a maintenance calendar and still spend most of their time responding to failures. The calendar may list tasks without identifying critical equipment, the consequences of downtime or whether recurring faults are being resolved.
A better starting point is a small, usable maintenance system. The following 90-day sequence is an illustrative implementation plan, not a prescribed inspection interval. Adapt it to the facility, equipment instructions and applicable requirements.
Days 1–30: Establish what you have and what matters most
Create an asset register that staff can maintain. Record a unique identifier, location, function, make and model where available, operating responsibility, available documentation and known condition concerns. Start with the systems essential to the facility’s safe and reliable operation.
Then assess the consequence of failure. Ask what happens to safety, users, production, water supply, business continuity or the environment if the asset is unavailable. Also consider whether a working alternative exists and how long repair or replacement might take.
The US Department of Energy’s Operations and Maintenance Best Practices Guide distinguishes reactive, preventive and predictive approaches and discusses equipment criticality when selecting a maintenance mix. Those concepts are useful beyond federal facilities; the actual programme must reflect local conditions.
An illustrative comparison makes the point: failure of one decorative light and failure of the only water-supply pump do not deserve identical priority merely because both are on the same inventory.
Separate urgent defects from planned work
Keep a visible list of unresolved defects with a responsible person and next action. A concern affecting safety or essential operation should not wait for the end of the 90-day exercise. Arrange assessment and appropriate controls through competent personnel.
Do not equate “still running” with “no action required.” Record repeated leaks, unusual noise, overheating reports or frequent protective trips for investigation. Their significance needs competent assessment rather than guesswork from a checklist.
Days 31–60: Turn tasks into useful work orders
A maintenance instruction should state the asset, task, required competence, access or isolation arrangements, relevant procedure, evidence to record and what finding needs escalation. Frequency should be based on the manufacturer’s requirements, duty, environment and applicable obligations, then reviewed as evidence accumulates.
“Service the pump” gives a technician little context and gives the manager little evidence. A better work order points to the agreed procedure, identifies the pump, records observations and captures any corrective action or outstanding defect.
Preserve the distinction between a scheduled task and an investigation prompted by condition. The DOE O&M challenges and solutions resources discuss the evolving mix of maintenance approaches. New monitoring tools can help, but only when someone interprets the information and can act on it.
Plan for access, shutdowns and essential spares
Review which tasks require an operational interruption and when those interruptions are possible. Coordinate with the people who use the building. A task repeatedly deferred because “the equipment cannot stop” needs a management decision about access and resilience.
For critical assets, discuss realistic repair lead times and which spares are justified. Avoid buying parts without confirming compatibility, storage requirements and who controls the inventory. Record where manuals, warranties and supplier details can be found.
The Whole Building Design Guide’s ongoing commissioning guidance describes a systems manual that brings together design and construction information, operating guidance, maintenance and training records. Even a simpler facility benefits from keeping these records connected.
Days 61–90: Review evidence and recurring problems
Choose a few measures that lead to decisions: overdue critical tasks, repeat failures, time out of service and defects awaiting action. Count completed work only where it has a useful record. A high completion percentage can conceal poor maintenance if tasks were closed without checking the condition.
Hold a short review with operations and maintenance staff. For each repeated problem, ask whether the previous action addressed the cause, whether operating conditions have changed and whether the equipment remains suitable for its duty.
Do not promise a fixed percentage saving. Reduced downtime and better cost control are sensible objectives, but the outcome depends on the starting condition, resources and follow-through. Establish a baseline first.
A maintenance system simple enough to keep using
- One asset register with consistent identifiers.
- A prioritised defect list and named owners.
- Task instructions linked to the appropriate procedures.
- A schedule matched to actual operating conditions.
- Traceable work records and a small set of review measures.
- A monthly discussion that converts findings into action.
A spreadsheet may be sufficient initially. Maintenance software becomes useful when it supports a workable process; it cannot compensate for missing responsibilities, inaccessible equipment or an unresolved backlog. Build the process around those realities first.
Planning work on your site? Discuss your project with EEACL, including the location, intended use and any drawings or photographs already available.
Research checked 9 October 2026. This article supports project planning; specifications, testing and approvals must be agreed for the actual site and intended use. Photographs are illustrative images from the EEACL portfolio.
Share this article