Create a maintenance plan: Template and practical guide

One Maintenance schedule is not a bureaucratic act, but the central instrument for ensuring plant safety, reducing downtimes and reliably documenting verification obligations. This guide provides an immediately usable Maintenance schedule template, a Step-for-Step-Instructions for data collection and prioritisation, practical tips for integration in CAFM-systems as well as KPIs and a rollout checklist for direct implementation.

1. define objective, scope and responsibilities

Clear objectives are not a luxury, but a prerequisiteWithout a defined goal for the maintenance plan, all planning remains tactical and reactive. Specify whether the plan primarily serves operational reliability, increased availability, compliance documentation or cost control - combinations are often necessary, but the priorities must be clear.

Sharpen the scope of application: Define directly which buildings, technical areas and system groups are included. Too big at once leads in practice to half-finished data sets; too small overlooks critical interfaces. A pragmatic tactic: pilot with 1-2 critical system classes, then successive rollout.

Practical rule for the scope

• Prioritise according to Risk: Start with security-relevant and critical (i.e. defined as highly available or production-relevant) assets.
• Select location depth: Floor/technical room is usually sufficient; component level only for high criticality.
• Mark regulatory obligations: References to relevant standards such as DIN EN 13306 attach.

Assign responsibilities practically: For each system, name the role of the system owner, the executing unit (in-house or service provider), and the CAFM-administration. Make sure that those responsible also have data responsibility - who maintains the asset ID, test result and spare part number.

In practice: short and manageable

Concrete example: The person responsible for the central heating system in Building A is appointed at facility management level; regular annual maintenance is carried out by the internal team, while safety-related pressure tests are performed by a certified service provider. The CAFM administrator ensures that test logs and spare part numbers are linked to the asset ID so that subsequent audits are reliable.

Assessment and limit: Many teams underestimate the effort required for data responsibility. If you only distribute responsibilities nominally, data quality remains poor and automatic scheduling in CAFM becomes useless. Next Stepsystematically build up the asset base and minimise the Master data per asset.

2. build up asset master and database

Hold on tight: A usable asset master is the basis, otherwise any automatic maintenance planning remains piecemeal. Without clear Asset ID, and basic documents, neither deadline scheduling nor spare parts linking work reliably.

Minimum data set and recording sequence

1. Indispensable: Asset ID, system name, building location (plant room/floor), manufacturer, Model, serial number.
2. Operating data: Date of installation/commissioning, operating hours (if available), current status labelling (A-B-C or numeric).
3. Maintenance-relevant information: Basic maintenance interval, assigned test protocols (link), qualification required for implementation.
4. Spare part references: Critical spare part numbers with minimum stock and delivery time estimate.
5. Documents & Evidence: Linked manuals, certificates, test reports, photo of the type plate.

Practical rule for recording: Start with the minimum data set for all assets and only enrich critical assets component by component. The temptation to immediately catalogue every screw costs time and delays the Automation.

Trade-off: Complete component structure increases the accuracy of maintenance intervals, but multiplies the effort and maintenance requirements. In practice worthwhile component detailing is only suitable for highly critical or expensive assets; everything else remains at device level.

Organise data collection pragmatically: Combine a one-off inspection with document import (manufacturer data, test certificates) and a downstream clean-up cycle. Define a small team for data owners: who is responsible for the assetData who uploads photos, who validates spare parts.

Practical case: For a heating circuit pump with the identifier P-123 enter: Asset ID P-123, Location: Heating centre EG, manufacturer/type, installation date 2016, last test bench: functional test 2025-02-10 (link to test log), critical spare part: seal 789-456, minimum stock 2. These entries allow automatic due date tracking and immediate creation of a work order in CAFM.

Important technical note: Barcode or QR tagging reduces capture errors and speeds up mobile capture, but entails costs for labelling and scanners. Decide according to cost-benefit: Tagging is usually economical for >200 assets; below this, structured labelling is sufficient. Excel/CSV with clean Asset ID-convention.

Important: The most common cause of incorrect maintenance plans is not a lack of Software, but a lack of consistent Asset ID-rules and verifiable document links.

Note integration: Prepare the export in CSV format so that field names match the target CAFM. First use the internal mapping on 20 test assets before running a mass import. For information on data quality, see our instructions on data quality and asset management.

Consequence: If you take a sloppy approach to the asset master, the planned Maintenance reactive. Invest the necessary hours in a lean, but binding Master data-After that, automated scheduling and spare parts management in CAFM pays off quickly.

3. select maintenance strategy and define intervals

Key point: The choice of maintenance strategy is the lever that creates or destroys predictability. When creating a maintenance plan, choose strategies that are asset-specific rather than generalised: time-based measures can be implemented quickly, while condition-based and predictive approaches require data maturity and change budget profiles.

Strategies short and sweet

Time-based: Good for legally regulated tests and simple, less critical components. Advantage: Simple implementation, often without sensors. Disadvantage: unnecessary interventions or missed outages with variable loads.

State-based: Useful when test signals without large Infrastructure are available (e.g. vibration, temperature, oil level). Restriction: only works with reliable measured variables and defined limit values; without clear measurement instructions, your maintenance log will only provide noise.

Looking ahead (predictive): Only use this where downtime costs are high and you have sufficient historical data. Data or can be retrofitted with sensors immediately. Practical judgement: Predictive reduces unplanned downtime in the long term, but requires investment in sensor technology and connection to the maintenance plan Software and data science resources.

1. Decision-making process: Prioritise assets according to criticality and failure sequence, check existing measurement data or test protocols, calculate investment and operating costs for sensors/software, and create a pilot for the top-critical assets.
2. Regulatory embedding: Check standards and regulations before selecting a strategy; safety-related tests must fulfil minimum intervals, see DIN EN 13306.
3. Resource synchronisation: Adjust the Strategy with personnel qualification and spare parts availability; predictive Maintenance is of little use if nobody can process the findings on site.

Example from practice: In one production hall, the time-based oil change control for transformers was supplemented by temperature trend monitoring. Within twelve months, the number of unexpected replacement orders fell because alarms signalled cracks in the insulating oil at an early stage. The pilot comprised three transformers, sensor installation and mapping of the alarm limits in the CAFM.

Valuation and pitfalls: Many teams overestimate the immediate efficiency gains from predictive maintenance. In practice, the most common source of error is a lack of data quality and unclear alarm definitions. Before you make extensive sensor upgrades, test a few critical assets and validate signals against real faults.

Important: Define interval logic and due date rules precisely in your maintenance plan template (e.g. 12 months or 5,000 operating hours, whichever comes first) - this prevents duplicate or contradictory orders in the CAFM.

The following course of action is recommended: Select the Strategy asset-by-asset, pilot the most technically demanding cases and write the interval rules so that they can be imported directly into CAFM. You can then define maintenance intervals and map them systematically in the template.

4. maintenance plan template: fields, structure and work instructions

Core thesis: A template only helps if it enforces structured mandatory fields instead of free text descriptions. Without precise field definitions, the result is a chaotic maintenance log that cannot be reliably imported into CAFM or automated.

Structure: Mandatory fields first, convenience fields afterwards

Concentrate the template on a small set of mandatory columns that are necessary for scheduling, qualification and verification. Write these fields as required into the CSV-/Excel-scheme and use drop-down codes for recurring values (e.g. qualification levels, interval types, check status). Free text fields only for short additional notes; long work steps belong in a linked worksheet or PDF.

Practical insight: Structured inspection characteristics (e.g. measuring point: target value: tolerance) are more important than detailed work instructions. Digital checklists and mobile inspection apps can only work with clear, machine-readable measurement instructions; narrative instructions often end up as unchecked, irrelevant text in the inspection report.

Limitation/trade-off: More fields increase data quality, but they also increase the amount of data entry required on site. Our recommendation: Make the minimum set mandatory, maintain extended fields only for assets with high criticality. For larger portfolios, a tiered data capture model is more efficient than a universal full data capture requirement.

Concrete example: Maintenance Boiler K-204: Task ID K-204-A01, asset ID K-204, interval 12M, preparation time 30 min, execution time 90 min, qualification TECH1, test characteristic flue gas temp: target < 250 C: tolerance 10 C, spare part seal 789-456, safety measure switch-off and de-energise, documentation: kesselK-204protocol.pdf. This entry allows automatic appointment allocation, mobile checklist and direct reordering of the spare part via the procurement interface.

CSV/Excel recommendations and mapping notes

Export the schema with clear column names and use ISO date formats (YYYY-MM-DD) and standardised interval definitions. When importing into CAFM, first check the field assignment on 10 test lines; frequent Error are incorrect asset IDs, different abbreviations for qualifications and deviating units for measured values.

• Mapping tip: In CAFM, create a lookup for Qualification code instead of importing free texts.
• Validation: Before the rollout, check that Inspection characteristic|setpoint by-rule is transferred to the mobile checklist.
• Fallback rule: If no measured value is possible, mandatory Status=Assessed instead of leaving it empty.

Important: Avoid using narrative work instructions as the sole control instrument. Enable structural data Automation, auditability and KPI evaluation.

Next step: Save the CSV schema as a control version, import 20 test lines into the CAFM and check whether mobile test protocols, spare part links and alarm rules are triggered correctly. If you are unsure, read the specifications in the standard reference list, e.g. DIN EN 13306, and consult the data quality checklist from our guide: Data quality and asset management.

5. planning, scheduling and resource management

Core thesis: Scheduling is not just a matter of filling the calendar, but of balancing due dates, staff availability and spare parts stocks. When you create a maintenance plan, plan capacity first, not tasks - otherwise you will shift problems to the backlog.

Scheduling logic and planning modes

Rolling plan instead of static list. Work with rolling 12-month perspectives that are recalculated monthly. Define blackout periods (maintenance-free production weeks) and prioritise dates according to criticality, not date alone. This minimises ad-hoc conflicts and reduces unplanned postponements.

Batching and set-up time optimisation. Bundle the same activities per location on one day to reduce set-up time. The trade-off: larger batches increase the probability that a plant shutdown will affect several assets at the same time. Decide on downtime costs versus travelling and set-up costs.

• Automatic repeat: Use CAFM functions to generate deadlines and set clear due date rules (e.g. ISO interval or operating hours).
• Buffer and failure rate: Plan a capacity reserve of 15-25 per cent for disruptions; otherwise the backlog will quickly increase.
• Spare parts reservation: For critical tasks, create a pre-reservation in the ERP/CAFM so that parts are not ordered when the order is opened.
• Outsourcing for Peaks: For seasonal peaks, short-term outsourcing is often more favourable than permanent overcapacity.

Capacity formula (practical): Use Technician hours required = number of tasks x average order duration and then Technicians required = Technician hours required / (hours available per technician x utilisation factor). Use a utilisation factor of 0.7 to 0.8 for realistic planning (breaks, travel, administration).

Concrete example: On a Campus There are 10 air conditioning units, each service package takes 2.5 hours including travelling. Annual task: 10 tasks x 2.5 h = 25 h. Available hours per technician per month ~ 120 h, with a utilisation factor of 0.75 results in an effective 90 h/month. One technician easily covers this annual task; with 100 devices, you need 250 hours, i.e. around 3 technicians (250 / 90 ≈ 2.8).

Interface control: Ensure that planned orders in CAFM automatically trigger material reservations and that work orders are provided with SLA types. When importing the maintenance plan template, check whether Spare part numbers and Storage location are mapped correctly, otherwise appointments are created but cannot be executed.

Practical limitation: Full automation usually fails due to missing or inaccurate data. If asset locations or spare parts references are incomplete, planned orders are either released without parts or repeatedly postponed. Therefore, prioritise data maintenance for assets with high maintenance volumes.

If you take the next step, integrate these planning rules into your CAFM template and test the mapping on 20 entries. For information on mobile execution and digital checklists, see our article on Maintenance and mobile technology.

Key realisation: Plan capacity conservatively and only automate schedule generation where asset data and spare parts maintenance are reliable. Otherwise your automatic maintenance plan will become a daily source of disruption.

6. integration into CAFM/EAM and use of mobile tools

Straight to the point: The integration of your maintenance plan into CAFM/EAM decides whether the procedure works in everyday life or in Excel-exports ends. If you Create maintenance plan as a one-off list, you are missing out on the leverage for automating deadlines, spare parts management and audit-proof documentation.

Practical integration steps

Start with a clear master data decision: which system is the source of the data? Truth for asset master data, who keeps parts lists and storage locations up to date. In many projects, an incorrectly selected master causes duplicate work and incorrect deadline releases. Determine at an early stage whether the CAFM or a ERP/SAP EAM The system controls the parts inventories and sets up an API or CSV interface for bidirectionality (REST/SOAP depending on the system).

• Import check: Test the CSV mapping with 20 assets, check asset IDs, qualification codes and units, and document deviations as mapping fixes.
• Escalation logic: Define rules in CAFM for what happens if an inspection result is out of tolerance (automatic work order, block indicator, notification to the person responsible for the system).
• Upgrade resistance: Avoid heavy customising in standard fields; any customisation increases Risk and costs for system updates (Planon, IBM Maximo, SAP EAM are robust, but rigid when changes are made).

Practical objection: many teams believe that additional fields solve all problems. In practice, too many mandatory fields slow down the technicians on site. Rely on a tiered validation model: minimalrequired for triggering an order, extended fields only for critical assets.

Mobile use: offline, usability and verification

Key message: Mobile Tools are only as good as their workflow design. Ensure that checklists are short, measurement-orientated and offline-capable; poor usability leads to technicians continuing to keep inspection logs on paper and later transferring them incompletely into the system.

• Offline-first: Mobile app must support synchronisation, conflict resolution and retry logic, otherwise data will be missing after fieldwork.
• Quick identification: QR/barcode scanning reduces mismatches; require scan before log start, not as an option.
• Audit trail and signature: Digital signature and photo evidence are mandatory for test certificates and external audits.

Concrete example: When rolling out on a Campus the team imported the maintenance plan template into CAFM, mapped inspection features to mobile checklists and activated QR tagging. Technicians scan the nameplate, the app automatically pulls the correct inspection protocol, photos and digital signature field are requested. Result: compliance rate increased by a visible percentage point within a month, and repeat orders for spare parts were automatically triggered to the ERP.

Important trade-off: real-time integration delivers immediate Transparency, but requires stable wireless networks and more complex error handling. Offline synchronisation is more robust in harsh environments, but brings latency for error messages and material reservations. Weigh up the network quality and process criticality.

Tip: Start integration and mobile technology in the pilot with 1-2 system classes, check mapping, offline behaviour and parts workflows, then roll out in stages. Read our guide to digital maintenance and mobile technology.

7. key figures, audit and continuous improvement

Clear key figures determine whether your maintenance plan is alive or merely fulfils reporting obligations. Don't measure everything, but rather the few key figures that directly show whether planning, execution and documentation are working - and whether CAFM is really making work easier.

Which key figures really help

Practical limitation: High PMP is good - but not at the cost of ignoring critical ad hoc tasks. Too much focus on percentage targets encourages KPI gaming (e.g. misclassifying tasks). Design KPIs in such a way that they are easy to audit and difficult to abuse.

Audit practice and documentation

Audit means more than submitting lists. Inspection logs must be stored in the CAFM in an audit-proof manner, with a digital signature, photo as proof and a clear link to the asset ID. Use audit runs to uncover process weaknesses: random mobile checklist reviews often reveal operating errors or misleading inspection features.

• Audit checkpoints: Random samples of 5-10 completed orders, verification of measured values against target/tolerances, verification of spare parts removal and approval processes.
• Focus: In the event of deviations, don't just sanction the employee; analyse whether the test feature, training or mobile usability was the problem.
• Standard reference: Documentation requirements for safety-related tests in accordance with DIN EN 13306 and verification obligations; for questions relating to occupational safety DGUV consult.

Trade-off in audit frequency: Find frequent audits more Error, but cost time. The goal is not zeroError, but measurable process improvement - e.g. fewer recurring errors per audit cycle.

Continuous improvement: concrete workflow

Set a simple, repeatable cycle: record baseline → analyse cause (Pareto) → adjust maintenance measure or checklist → pilot → KPI measurement. Choose small, time-limited experiments (2-3 months) instead of large rollouts without measurement.

Concrete example: In a campus pilot, mobile checklists for chillers were improved and critical spare parts were reserved. Result: PMP rose from around 55 % to 78 % within four months; MTTR fell by a good 20 % because technicians no longer had to reorder parts. The change was not a technology effect alone, but a combination of data maintenance, parts reserves and a customised checklist.

Rating: KPIs without process anchoring are useless. Measure, but then invest in concrete corrective measures (training, precision of inspection characteristics, parts management). Prioritise measures according to failure costs and compliance risk - not according to the level of KPI deviation.

Next step: Define 3 KPIs for your pilot (e.g. PMP, MTTR, compliance rate), measure a four-week baseline, carry out a 3-month test and then decide which measures should be scaled. This is more pragmatic than immediately rebalancing the entire portfolio.

8 Implementation roadmap, pilot and rollout checklist

Core assertion: A structured pilot with clear go/no-goCriteria is the only reliable method for scaling a functioning maintenance plan. Without defined cancellation criteria and a data freeze for the pilot assets, the rollout ends in endless rework.

Phases of the implementation roadmap

Plan the rollout as a series of short, controlled phases with measurable results per phase. Each phase needs a responsible owner, a defined duration and a clear success criterion that either leads to progress or to a reset.

1. Preparation (1-2 weeks): Select pilot assets, freeze data on basic master data, create field mapping plan.
2. Data cleansing & import test (1 week): Import 20 test lines, document returns, rectify top 5 errors.
3. Shadow Run (2 weeks): Technicians carry out paper-based and digital work in parallel and record deviations.
4. Live pilot (4-8 weeks): Mobile checklists active, parts reservation tested, daily stand-ups for troubleshooting.
5. Rollout stages (staggered): 20 per cent of the assets, then 50 per cent, then full roll-out; review and approval after each stage.
6. Review & stabilisation (6-12 weeks after rollout): KPI check, sharpening processes, training as required.

Trade-off to be considered: Shorter pilots cover routine processes but overlook rare failure cases. Longer pilots show robustness under failure conditions, but delay benefit realisation. Choose duration based on complexity of assets and availability of technicians.

Change management measures: Create a stakeholder map, appoint change ambassadors in the technical teams and plan proof of competence via digital signature after the training has been completed. Use feature flags in CAFM to gradually activate new fields or check rules.

Concrete example: Twelve identical ventilation units in a wing of a university campus were selected as a pilot. During the first import, around 30 per cent of the spare part numbers were missing; the team set up a one-week data correction shift, introduced QR tagging and then started the live pilot. After six weeks, reliable mobile protocols and automatic material reservations were available, enabling a staggered rollout.

• Essential rollout checklist (12 points): Define and release pilot scope
• Set up data freeze for pilot assets
• Perform mapping review and 20 test imports
• Document and prioritise top 5 data errors
• Create mobile checklists and test offline
• Provide QR/barcode tagging for pilot assets
• Check spare parts reservations in CAFM/ERP
• Training: short practical session + competence signature
• Shadow run with paperless Comparison carry out
• Establish weekly stand-ups and ticket management
• Criteria define for go/no-go meeting (e.g. error rate < X, mobile feedback positive)
• Decision gateway for rollout with defined scope

A common mistake is to make the pilot too broad. Instead, choose a locally focussed asset group with medium complexity. This minimises logistical effort, allows control and provides usable insights for the use of maintenance plan templates and mobile documentation. For technical details on mobile implementation, read our article on digital maintenance and mobile technology and check standard requirements such as DIN EN 13306 for safety-relevant tests.

Next step: Select pilot assets this week, define the success criteria and run the first 20 test imports before the next sprint. Use the pilot data to decide whether to adopt the maintenance plan template unchanged or make specific adjustments.

9. templates and practical examples

Short and to the point: Download packages contain two things that you need immediately: an importable Excel/CSV-Template for direct import into CAFM and tested practical examples (order entries), which serve as a reference for interval and inspection specifications.

Scope of delivery (file names) - just an example, you have to assemble the templates yourselfMaintenance planTemplateMinimalYYYYMMDD.xlsx, maintenance planTemplateCompleteYYYYMMDD.xlsx, CSV import schemaCAFMYYYYMMDD.csv, sample orderHeatingBoilerK-204.csv, sample orderLiftA-01.csv, KPI dashboardTemplateExcelYYYYMMDD.xlsx, ReadmeImportMapping.pdf.

• Excel variant: Flexible for customisation, convenient drop-down fields, good for pilot teams.
• CSV import schema: strictly formatted, UTF-8 with ISO date format (YYYY-MM-DD), mandatory for automated CAFM imports.
• Example orders: real values, test points with target/tolerances, predefined qualification codes and spare part references.

Practical insight: PDF exports are useful for audits, but they are not importable. If you want to make the transition to digital work, plan the work in two tracks: 1) audit-ready PDFs/logs; 2) structured CSV/Excel for CAFM. Many teams underestimate the effort involved in converting narrative inspection steps into structured inspection characteristics - expect manual rework here.

Mapping instructions for Planon / IBM Maximo / SAP EAM: Vote Qualification code to the CAFM lookup (no free texts). For intervals, use ISO periods (P6M for 6 months) or a field IntervalType plus IntervalValue (e.g. MONTHS / 6). Spare part numbers must be linked to the ERP/parts catalogue - import parts master data first, otherwise you will generate non-executable orders.

Concrete example: File sample orderLiftA-01.csv contains task ID A-01-REV, asset ID A-01, interval P6M, qualification ELEK2, inspection characteristic:rope tension:target=1100:N. When importing into Planon, we mapped Interval on the field frequency and Qualification to a predefined skillset. Result: automatic appointment generation and mobile checklist with mandatory photo. The pilot required 2 hours of mapping customisation and a correction shift for 12 incorrect asset IDs - this is normal.

Restriction / Trade-off: Free Excel templates reduce entry barriers, but they often generate unstructured free text. If you Create maintenance plan With the aim of automation, you invest time in standardising the codes and a small lookup repository. Without this preparatory work, the import remains error-prone.

Important: Test each import with 10-20 assets first; then perform a quality round before performing bulk imports.

Licence and use: The templates are released for internal use; check the exact licence details in the readme. For standard references see DIN EN 13306 and for practical tips on data quality, see our guide to data quality and asset management.

Next Step: Download the ZIP, open ReadmeImportMapping.pdf, Perform the 20-line test import and document all mapping fixes - only then scale. This is the only guarantee that your templates will actually speed up the transition from Excel to productive CAFM.

Answers to real problems

• How often to update the maintenance plan: At least once a year; immediately after safety-relevant changes or incidents. Practical rule: Annual review + ad-hoc updates following incidents.
• Import into the CAFM possible? Yes - but test with 10-20 lines first and document each mapping. Pay attention to ISO date formats and consistent qualification codes, otherwise you will generate non-executable work orders.
• Time-based or state-based? Choose hybrid: time-based for statutory inspections, condition-based for rotating machines, predictive only with clear cost-benefit data. Restriction: Predictive requires data management and evaluation expertise.
• Which fields are mandatory? Essential: Asset ID, task ID, interval definition, inspection characteristic with target/tolerance, qualification, verification template. Without these fields, automation remains piecemeal.
• Referencing legal requirements? Yes, link to relevant standards such as DIN EN 13306 in your plan; but leave legal assessments with the legal department or external experts.
• Offline mobile problems: If wireless is unstable, rely on offline-first apps with conflict resolution. Trade-off: Latency in material reservation vs. reliability of on-site recording.

Practical limitation: A common mistake is to believe that a single master Excel solves data quality. In practice, you need a small governance unit (1-2 people) for mapping fixes, lookupStandardisation and version control.

Concrete example: When importing a pilot into a CAFM, 14 out of 50 asset IDs did not match the asset master, causing appointments to be created without a parts reservation. Solution: 1) Stop mass import, 2) Correction run for asset IDs and spare parts references, 3) new test import. Afterwards, automatic material reservations and mobile checklists ran as planned.

Practical judgement: FAQs only work if they are accessible and versioned. Teams that scatter FAQs in emails lose control. Instead, create a central FAQ page in CAFM and link it to pilot assets.

Next steps, immediately realisable: Version your readme, perform a 20-line test import, note top 5 mapping errors, and designate a data owner for 8 weeks.

Once these measures are in place, link the FAQ to the pilot dashboard and schedule a weekly check-in (15 minutes) to resolve any issues that arise. This will prevent small problems from stopping the rollout. And nobody wants that ;-)