Visit dates alone do not define the programme. The delivery team needs identifiable assets, an explicit task scope and a clear requirement for information returned after attendance.
1. Establish the asset list
Assign consistent references and useful locations. Include type, manufacturer, model, served system and dependencies where relevant. Locate building elements such as doors and roofs clearly even when they have no serial identifier.
Reconcile the register with the site scope. Flag inaccessible, unknown or unverified assets and assign verification actions. Keep removed equipment outside the active schedule while preserving its earlier history.
2. Define the tasks and their basis
Establish tasks from manufacturer documents, applicable requirements, assessments and competent advice. Retain the source and version supporting each instruction so future changes can be evaluated.
work-equipment maintenance guidance supports planned maintenance using manufacturer instructions and competent people. It also addresses safe access and arrangements for carrying out the work; include those requirements in preparation.
Replace generic labels with executable instructions. A ventilation task needs the particular equipment, activity, procedure and required results. Several activities on the same asset may require separate records rather than one service entry.
3. Establish timing and next due dates
Specify elapsed time, operating hours or another defined trigger. Calculate the next due point from the relevant requirement and reliable history. Where evidence is absent, obtain technical input to establish a justified baseline.
HSE’s inspection guidance relates inspection need and frequency to risk assessment, conditions, use and manufacturer recommendations. Preserve separate maintenance and inspection requirements even if they are coordinated into one attendance.
4. Make the programme deliverable
Plan access, permits, shutdowns, materials and affected users. Check task sequencing before combining visits; some work depends on another activity finishing first. Geographic grouping does not override individual due points.
Agree operational effects where equipment serves occupied areas. Schedule preparation and client decisions far enough ahead to make the intended work window achievable.
5. Set completion requirements
Define the evidence required: tasks performed, findings, measurements or test documents and follow-on actions. Record access failure as an exception, not completion of work on an asset that could not be reached.
A completed maintenance activity may reveal a separate defect. Keep its task result and the linked remedial action distinct, preserving both the service history and visibility of remaining work.
A practical schedule structure
For instance, similar fans serving different spaces may run for different hours. Their entries need to retain those differences so technical advice and the programme reflect their actual operating duty.
Keep the schedule current
Review affected tasks after replacement, changed use, recurring faults or revised technical information. Record approval and reasons for changes. Preserve original due dates for late work and explain the delay instead of resetting the schedule to hide it.
At handover, transfer active assets, task definitions, current dates, supporting sources, completed-work history and unresolved exceptions. The incoming team should establish what is due from these records rather than reconstructing it from invoices.
Common questions
Can we start with an incomplete register?
Yes. Define the known scope and prioritise verification gaps. Develop the supported programme while keeping incomplete asset information and responsibility for resolving it visible.
Should every asset receive the same service frequency?
No. Duty, condition and requirements determine each task. Similar equipment can need different treatment, and separate activities on one asset can follow different triggers.
Can several tasks be completed during one visit?
Yes, if due points, competence, access and sequencing permit it. Record each task separately so completion and remaining exceptions are identifiable.
Does a missed visit mean changing the next due date?
Not automatically. Record the omission and obtain the relevant decision on recovery and future timing. Retain the original requirement and justification for any adjustment.
Develop the programme
Develop Asset Maintenance, Planned Preventative Maintenance and Planned Replacement together where needed. Use what a PPM schedule should include to check the contents of the task schedule.
Explore all services, projects, sectors and locations, or discuss your maintenance schedule with the register and known programme gaps.
