PM scheduling looks simple until you're managing 300 assets across 40 sites with different contract frequencies, seasonal access restrictions, and technicians who don't update job status in real time.
Preventive maintenance scheduling sounds simple. You have a list of assets. Each asset has a service frequency. You put the visits in a calendar. You assign technicians. Done.
This model works at low volume, with one or two technicians, and a handful of clients. It stops working when you have 300 assets across 40 sites, different contract types with different service frequencies, seasonal access restrictions, technician certification requirements that vary by equipment type, and clients who call to change access arrangements the morning of the visit.
Most service companies start their PM scheduling in a spreadsheet. The spreadsheet is extended over time — new columns for contract dates, new tabs for different clients, a colour-coding system that only the person who built it fully understands. It works, until the person who built it is unavailable. Then it becomes a risk.
The structural problem with spreadsheet-based PM scheduling is that it is static. It shows you what was planned. It doesn't show you what was actually completed versus what was missed, whether completion records are up to date, when each asset was last serviced relative to its contract frequency, or which certificates are approaching expiry. Getting this information requires manual cross-referencing — which requires time, and introduces errors.
The PM scheduling problem is compounded by the diversity of contract types in most service companies. One client requires quarterly service on all assets. Another requires semi-annual on most equipment but monthly on specific high-risk items. A third has a PPM schedule derived from a statutory requirement that is frequency-based but also condition-based — the interval changes depending on the finding of the last visit.
Managing this complexity manually requires constant attention and is vulnerable to the kind of errors that come from managing many variations simultaneously. The practical consequence is that some assets get serviced too often (wasting engineer time) and others get serviced too infrequently (creating compliance risk and, eventually, contract disputes).
Site access restrictions are one of the most underestimated scheduling complexities in service operations. A visit planned for Tuesday is unachievable if the client's facilities management requires 48 hours notice. A visit planned for the second week of December is unachievable if the client is a retail business that doesn't permit contractor access in the weeks before Christmas. A visit planned for any Monday is unachievable at a site that has a standing all-day Monday management meeting in the only room that gives access to the plantroom.
These restrictions are rarely captured in a PM schedule. They exist in the collective memory of the team, in email threads from three months ago, and on sticky notes on the ops manager's desk. When they're forgotten, a visit is aborted. The technician's day is wasted. The visit needs to be rescheduled. The PM frequency slips.
Not all technicians are qualified to service all equipment. In fire protection, a technician who is competent for fire alarm servicing may not be qualified for suppression system inspection. In electrical, an engineer who handles periodic inspection may not hold the certification required for certain high-voltage equipment. In water hygiene, a technician who handles routine TMV servicing may not be qualified to conduct a full Legionella risk assessment.
Scheduling a PM visit without checking whether the assigned technician holds the right certification for the specific equipment is a compliance failure — and one that is easy to make when scheduling is done manually and certification records are held separately.
Many PM contracts produce regulated certificates — fire safety certificates, water hygiene compliance records, electrical periodic inspection certificates. These certificates have validity periods. When a certificate expires, the client's compliance position changes — sometimes with legal consequences, sometimes with insurance implications.
Most service companies do not have a systematic process for tracking certificate expiry across all clients and alerting in advance of lapse. The tracking is either manual or reactive — the client calls because their auditor has flagged a lapsed certificate. In a properly structured system, certificate expiry generates a scheduling trigger automatically.
A PM scheduling system that works at scale needs to do five things. Generate visit schedules automatically from contract data — frequency, asset type, site requirements. Match visits to qualified technicians automatically, based on certification records. Track completion against schedule in real time, surfacing gaps without anyone having to query for them. Capture access restrictions per site and apply them to scheduling. And trigger certificate expiry alerts with enough lead time to schedule a renewal visit before the lapse.
None of these are technically complex requirements. But they require the contract data, the asset data, the technician certification data, and the site access data to be in the same system — not distributed across a spreadsheet, a shared calendar, a word processor, and individual email accounts. The integration is the product.
Next step
We run a focused operational review — no sales deck, no generic demo. We look at how your workflows actually run and show you where the system would change the outcome.