Build a multi-site preventative maintenance schedule with asset records, risk-based intervals, clear responsibilities and a process for overdue work.

A preventative maintenance schedule has to connect the right task to the right asset, site and person. Across several buildings, that means accounting for different equipment, access arrangements, client responsibilities and due dates.

When you manage several sites, a missed visit or an out-of-date asset list can quickly throw the plan off course. The steps below will help you build a schedule your engineers can follow and your clients can understand.

Quick Guide: Build Your Schedule in Seven Steps

1. Agree Scope and Responsibilities: Confirm covered assets, tasks, decision-makers and client handovers.

2. Build a Site-Linked Asset Register: Identify each asset, location and available service history.

3. Prioritise by Risk and Criticality: Assess failure consequences, condition, use and existing controls.

4. Set Tasks and Intervals: Record each task, due date and supporting rationale.

5. Plan Capacity, Access and Resources: Match competent people, parts and access to work.

6. Record Work and Escalate Exceptions: Capture results and assign ownership for unfinished work.

7. Review and Adjust: Examine overdue tasks, findings and the schedule’s assumptions.

How to Build a Multi-Site Preventative Maintenance Schedule

1. Agree Scope and Responsibilities

Start each contract by identifying the sites, asset groups and activities included in your service. Confirm exclusions, required reports, response arrangements and who can authorise additional work. A site contact may arrange access but have no authority to approve a repair.

Agree who arranges specialist examinations, supplies asset information, approves shutdowns and receives urgent findings. Record the contact and an alternative for each handover. Use the principles in your scope management process to document changes rather than relying on informal assumptions.

Site mobilisation checklist: For each location, record its use and operating hours, areas and assets covered, access restrictions, site contact and alternate, central approver, reporting requirements and outstanding records. Confirm the information with the client before the first scheduled visit.

Use a shared task and reporting framework across the portfolio, while recording site-specific access windows, equipment and contract requirements. Consistency means applying the same decision process, not imposing identical intervals everywhere.

A contract clarifies operational responsibilities; it does not automatically transfer legal duties. Check the position for the equipment, activity and jurisdiction involved.

2. Build a Site-Linked Asset Register

Give each asset a reference that distinguishes it from similar equipment. Record the customer, site, building, floor or room, asset type, manufacturer, model and serial number where available. Decide who is responsible for keeping those details up to date.

Add installation information, instructions, previous visits, reported condition and relevant documents. Flag missing information rather than inventing a last service date. Your asset management process should also cover newly installed, replaced and removed equipment.

Organise records in a consistent hierarchy: client → site → system → individual asset. Keep the client’s asset reference alongside your own so both parties can reconcile reports and work orders.

When inheriting a contract, request the existing register, available service history and relevant examination records. Compare them with a site walk-through; log missing or conflicting information, assign an owner and a review date, and confirm which reference engineers should use. Record an unknown history as unknown rather than assuming work was completed.

3. Prioritise by Risk and Criticality

Prioritise maintenance by considering what could happen if an asset fails, how it is used and how quickly deterioration might be detected. A system supporting a critical service may need a different planning approach from a non-critical asset at the same site.

Include operating conditions, known defects, past failures and the effect on safety or service delivery. Have a competent person review the assessment. Record the reason for the priority so the team can revisit it when use or condition changes.

For example, a team might classify a system whose failure could seriously affect safety or a critical service as critical; equipment whose failure causes significant disruption as important; and a non-essential asset with limited consequences as routine. These are illustrative categories, not universal ratings. Assess the actual asset, record the reason and have a competent person approve it.

Risk ranking supports planning; it does not permit you to move an applicable legal deadline simply because another job appears more urgent.

4. Set Tasks and Intervals

Set an interval for each defined task, not one blanket interval for every asset. Record the source: applicable legal requirements, a relevant examination scheme, manufacturer instructions, competent advice, operating conditions or the maintenance history.

For UK building-services contracts, SFG20 maintenance specifications may be a useful reference where relevant to the contract. Its task ratings distinguish statutory or legal, business-critical, optimal and discretionary work. SFG20 is not legislation, and it is not the sole basis for setting intervals; check the current requirements and local rules, particularly for sites in the Republic of Ireland.

Keep routine servicing, checks, formal inspections and statutory examinations distinct. They can have different purposes, competent-person requirements and evidence. A completed service does not automatically substitute for a required examination.

For work equipment in Great Britain, HSE inspection guidance explains how risk assessment, operating conditions and manufacturer recommendations inform inspection needs and intervals. Some equipment requires inspection after installation or events that could affect safety. Check the precise requirements for the task rather than treating these examples as a universal timetable.

Check Northern Ireland and the Republic of Ireland separately. For example, the Irish HSA guidance on electrical installations describes requirements for competent inspection and testing that depend on the installation and circumstances. It is not a general interval for every asset.

5. Plan Capacity, Access and Resources

Build a rolling view of work due by site, asset and required completion window. Group compatible tasks where that makes sense, but keep their individual due dates and requirements visible. Grouping visits must not delay work beyond a required deadline.

Allow for travel, specialist availability, parts, access permissions and client shutdowns. Reserve capacity for reactive work and make the person rescheduling a visit responsible for checking the original requirement before agreeing a new date.

Test the plan against capacity: Add estimated task, travel and preparation hours, then compare that demand with engineer hours available after leave, training and a realistic reactive-work allowance. For example, 100 task hours plus 25 travel and preparation hours require 125 hours; if the team has 110 available, there is a 15-hour shortfall. Arrange suitable additional capacity or revisit the agreed plan, while keeping any legal deadlines intact. Check specialist skills separately: total hours alone do not prove the right people are available.

Issue a clear work order with the location, scope, site contact, task instructions and required evidence. Confirm the engineer has the information and competence needed for that specific work.

6. Record Work and Escalate Exceptions

For each visit, record the asset reference, date, person attending, work completed, findings, evidence and any limitation. A job card can help capture a consistent handover, but tailor the record to the task and any specific documentation requirements.

Keep the outcome of the visit separate from the status of a defect. A completed inspection can lead to a repair awaiting approval. Give that finding an owner, an appropriate escalation route and a target date supported by a competent assessment.

If an engineer finds an urgent safety concern, contact the responsible person directly. Don’t assume someone has read an uploaded report. If the engineer is working offline, use another agreed way to get the information to the office.

7. Review and Adjust

Review due, completed, overdue, deferred and cancelled work by site and asset. Preserve the original due date when a visit is moved so the reason for the change remains visible.

Investigate patterns rather than automatically changing an interval. Repeated defects may warrant a technical review, a revised task, a different interval or replacement. Check applicable requirements and obtain competent approval before changing an inspection or examination arrangement.

Agree the counting rules with your client. Your facilities management reports should distinguish a visit completed within its agreed window from a visit merely booked, and show unresolved findings separately.

For example, if 18 of 20 visits due in a month were completed within their agreed windows, the on-time completion rate is 18 ÷ 20, or 90%. Keep both remaining visits in the denominator, and report their individual overdue or deferred statuses separately. Agree how cancelled, partially completed and unknown-status visits are treated before comparing sites; flag missing records rather than assuming completion.

What Should a Multi-Site Maintenance Schedule Include?

A useful schedule links each task to an identifiable asset and explains when, why and by whom the work should be carried out. The following is an illustrative starting point, not a statutory template.

• Location: Client, site, building and precise asset location.

• Asset: Unique reference, type, model, condition and relevant history.

• Task: Description, category, required competence and evidence.

• Timing: Last completed date, original due date, permitted window and next review.

• Basis: Manufacturer instruction, assessment, contract term or applicable requirement used to set the task and interval.

• Responsibility: Planner, assigned provider, site contact and escalation owner.

• Outcome: Completion status, findings, outstanding actions and report reference.

For example, a record for an air-handling unit could identify the site and plant room, list the agreed filter-check task and show the interval approved for that particular unit. Record the source of that interval; do not apply the example to other equipment without review.

How Should You Handle Missed or Deferred Visits?

Use a consistent recovery sequence: detect the missed visit against its original due date; prioritise it with a competent assessment of risk and applicable deadlines; assign an owner to notify the right person and arrange the next action; and record the reason, assessment, notifications and decision. Distinguish a client access issue from a lack of engineer availability or parts; each needs a different response.

Escalate overdue safety-critical or legally required work promptly to the appropriate duty holder and competent person. Establish whether the equipment can continue to be used under the applicable rules and circumstances. A revised appointment does not, by itself, extend a statutory deadline.

When the work is finally completed, retain the actual completion date and any outstanding findings. Do not backdate a record or describe a partially completed visit as fully complete.

How Fieldmotion Supports Planned Maintenance

Fieldmotion brings scheduling, asset records and mobile job forms into one platform. Your team can use recurring maintenance scheduling to organise planned work and retain job information alongside the assets and sites you manage.

Engineers can capture forms, photos and signatures using the mobile app, including when offline. Agree how the office checks the records and follows up on defects; the system supports the process but does not replace competent assessment or the responsibilities of the duty holder.

For more on the benefits of planned work, read our guide to planned preventative maintenance.

Frequently Asked Questions

How often should a maintenance schedule be reviewed?

Choose a review frequency that suits the sites you manage, and revisit the schedule when equipment, usage, condition or requirements change. Deal with overdue work and safety-critical issues sooner. A management review does not replace a required inspection or examination.

Who is responsible for a multi-site maintenance schedule?

The client and contractor should agree who maintains the operational schedule, arranges access and acts on findings. Legal duties depend on the activity, equipment, parties and jurisdiction. A contract should clarify responsibilities, not assume they have all moved to the contractor.

Is servicing the same as a statutory examination?

No. Servicing maintains equipment; a required examination has its own purpose, scope and competence requirements. Check the applicable rules for the asset and retain the appropriate evidence for each activity.

Can one maintenance interval apply to every site?

Not safely as a general rule. Equipment use, environment, manufacturer instructions and legal requirements can differ. Establish and document a justified interval for each task and asset, then review it when conditions change.