Building a Preventive Maintenance Schedule

Planned maintenance exists to find problems before patients do. A schedule that is built on risk, written down clearly and backed by evidence of completion turns equipment care from a reaction to failures into a managed, defensible routine.

Planned and Corrective Work Are Different

Corrective maintenance is what happens after something breaks: the fault is reported, diagnosed, repaired and verified. Planned maintenance happens before that, on a cycle chosen in advance, whether or not the device has shown any sign of trouble.

Both are necessary, and they compete for the same hours. A programme that is all corrective work is constantly firefighting; one that is properly planned reduces the number of fires without pretending that none will ever start.

The balance between the two shifts over time. A healthy programme gradually reduces the share of hours spent reacting, not because failures stop happening but because more of them are found early enough to be handled calmly.

Choosing What Goes on the Schedule

Not every device needs the same attention. The starting point is the risk classification and the manufacturer's recommended service interval, adjusted for how the device is actually used in your setting.

Devices that are safety-critical, heavily used or easily misused belong on a shorter cycle. Devices whose failure would be obvious and harmless can be checked less often, which frees time for the equipment that genuinely needs it.

Frequency of use is often more informative than the risk class alone. A low-risk device used constantly can deserve more attention than a higher-risk device that is seldom touched, and the schedule should reflect the difference rather than the label.

Practical Habits That Keep a Schedule Alive

• Publish the due list in advance so departments can plan around the downtime.
• Group work by location as well as by date, to cut wasted travel between sites.
• Keep a small buffer in the week for the work that always overruns.
• Escalate overdue safety-critical checks rather than letting them slide quietly.
• Feed every unexpected failure back into the review of the interval that missed it.

Setting the Interval Honestly

Manufacturer intervals are a recommendation, not a law of nature, and they assume ordinary use. Where a device is used far more than the manufacturer expected, or in a harsher environment, the interval should shorten rather than lengthen.

Whatever interval is chosen has to be justified and written down, including the reasoning behind any deviation. A decision to service less often than recommended should be a documented, risk-based choice, never a silent one.

It is worth recording why an interval was chosen, not only what it is. Years later, when someone asks whether the interval should change, the original reasoning is the fastest route to a sensible answer, and its absence invites guesswork.

Writing the Procedure, Not Just the Date

A schedule that says only when a device is due is half a programme. Each entry should point to a procedure describing what the check actually involves, what results count as a pass and what must be done when something fails.

The procedure is what makes the work repeatable. Two technicians following the same written steps should reach the same conclusion about a device, which is exactly what an audit or an investigation needs to be able to rely on.

Procedures should also say what the technician is not expected to do. Knowing the limits of an in-house check, and when a device must go back to the manufacturer, prevents both overreach and the quiet assumption that anything not mentioned was covered.

Deciding the Interval

Proving the Work Was Done

Completion has to leave a trace: who did the work, when, what was found, what was adjusted or replaced and whether the device was returned to service or withdrawn. A record that says only that a check happened is barely better than no record.

The trace matters most when something goes wrong later. Investigators will want to know what the device's status was before the event, and the maintenance history is often the only honest answer available.

Records are most useful when they are searchable by device rather than by date alone. Being able to pull up everything that has happened to a single unit turns a scattered set of notes into a history that can actually be interpreted.

Reviewing the Schedule as It Runs

A schedule is a hypothesis about where failures will come from, and reality is the test. Reviewing the balance of planned work, unexpected failures and repeat faults shows whether the intervals are set sensibly.

Where failures cluster on one model, or repeat on one unit, the answer is not simply to shorten every interval. It is to look at why that device keeps failing, which may point to user training, environment or a design problem instead.

Reviewing the schedule with the clinical teams, not only within the technical department, usually improves it. The people using the equipment often know where the risk really sits, and that knowledge is easily lost when planning happens away from the bedside.

A preventive maintenance schedule is really a risk decision written down in advance and then tested against reality. Set intervals deliberately, document the procedure, prove the work and review it honestly when failures slip through.