Residention

Property Operations Intelligence · Guides & analysis

What PPM actually means

A credible PPM connects recurring maintenance to assets, obligations, costs and evidence. This article sets out what the plan should contain and how it should inform day-to-day work and capital decisions.

Published · Updated

A list of recurring maintenance tasks can look complete while missing the things that matter. “Service boiler annually” does not identify the boiler, explain the frequency or say what the engineer must record.

PPM stands for planned preventative maintenance: recurring work carried out to keep plant, building fabric and safety systems serviceable, rather than waiting for something to fail and then repairing it. In property, it usually includes statutory servicing, manufacturer-recommended maintenance, routine inspections, warranty conditions, insurance controls and condition-driven interventions.

A credible PPM must be able to explain, months later, why a task was due on a particular date, for a particular asset, at that cost and with that supplier—and prove it was done. Without those answers, it is a calendar. With them, it becomes an operating plan.

Start with the asset and the reason for the work

The unit of control is the planned maintenance occurrence: one defined task, on one defined asset or scope, due for a stated reason. A schedule that survives scrutiny does more than display dates.

At a minimum, each planned task needs:

  • The asset and its context: identity, location, what it serves, installation date where known, condition, criticality and relationship to the wider building.
  • The maintenance activity: a precise description of what is expected, whether that is to inspect, test, clean, calibrate, service, replace, exercise or certify.
  • The trigger and frequency: calendar recurrence, operating hours, condition, a statutory interval, warranty terms, an inspection finding or a risk-based rule.
  • The source of the requirement: a maintenance library, manufacturer instruction, statutory duty, insurance condition, contract, internal policy or asset strategy.
  • The delivery conditions: required competence, supplier entitlement, access, tenant communication, permits, expected duration and operational dependencies.
  • The cost basis: the relevant budget, contract or other basis for the planned cost.
  • The evidence and follow-up: the required readings, reports, photographs, certificates or checklists, and any finding, remedial work or escalation that follows.

This begins with the real assets and fabric that require care, not a list of rooms, a spreadsheet of contracts or a collection of PDFs. The asset record should capture what is known, identify what is uncertain and improve through inspections, work and verified evidence.

A PPM should not become a separate master of asset data. It should use the same property and asset context as the rest of the operation, including the relationships between equipment, the areas it serves, service agreements and open remedial actions.

Frequency also needs a source, not a guess. Different sources carry different authority: some are mandatory, some are guidance, and some apply to one asset type but not another.

A maintenance library can bring consistency to activities, intervals, skills and expected evidence. But a wording match against a library entry is not a classification, and a library is not the law. The plan must retain the reason a requirement was applied so that teams can review it when the asset, building use, condition or obligation changes.

Build a plan that can be delivered and priced

A PPM should be technically correct and operationally practical. Four tasks due in the same building, on the same floor and within the same access window may be better delivered through one coordinated attendance than four isolated visits.

That does not mean combining work carelessly. Each requirement still needs its own scope, evidence and completion status, even when delivery is grouped.

The plan should account for:

  • routes through the estate and opportunities to group work;
  • contractor availability and competence;
  • access restrictions and tenant impact;
  • seasonal windows, shutdowns, permits and dependencies;
  • materials, lead times and contract entitlements;
  • the operational consequence of delay.

A ceiling for labour, contractor visits or annual spend is not proof that the resources exist. The annual plan should be tested against supplier capacity, internal workforce availability, access constraints and work already committed.

Where there is a shortfall, it should appear as a decision: change scope, sequence differently, appoint capacity, approve additional spend or accept a managed risk. A schedule nobody can resource is an intention with dates.

Maintenance costs need the same discipline. Every planned cost should carry its calculation basis and the date that basis was valid.

A sound plan distinguishes:

  • List price: a reference price, not a commitment.
  • Contract price: an agreed commercial entitlement, subject to its terms.
  • Budget estimate: a planning assumption.
  • Committed cost: a purchase order or approved instruction.
  • Actual cost: what was invoiced and accepted.
  • Restated cost: an earlier figure adjusted using an inflation or index assumption.

Restating a historic estimate may help planning, but it does not make that number a transaction. A missing price does not mean a replacement will be free.

::: Planning discipline Unknown is not zero. A missing cost, duration, condition rating or capacity figure must remain visible as unknown. :::

Keep completion, evidence and acceptance separate

A technician may have completed a visit while the required reading, certificate or report is still missing. A contractor may have uploaded a document that has not yet been reviewed. The work order can be operationally closed while the compliance or assurance position remains unresolved.

Closed is not evidenced.

A defensible PPM keeps important states apart:

  • Planned is not performed: a scheduled task is an intention with a due date, not proof that work took place.
  • Performed is not evidenced: a recorded visit may still lack the expected report, reading or certificate.
  • Evidenced is not necessarily accepted: submitted evidence may require review, clarification or rejection.
  • Past its declared life is not failed: age can influence risk and planning without proving immediate failure.
  • Never observed is not good condition: a missing inspection or unverified asset record is not reassurance.
  • Computed is not certified: a modelled score, forecast or recommendation does not replace a qualified inspection, review or approval where required.

These distinctions preserve the credibility of the plan when it is challenged by an auditor, insurer, lender, board or operations team. They also change what a portfolio view needs to reveal.

Reporting the percentage of tasks marked complete is not enough. Leaders need to see assets without a planned regime, overdue tasks, missing evidence, capacity or access problems, estimated costs, findings without remedial actions and completed work awaiting verification.

AI can help teams work through the volume. It can read guidance and reports, identify possible assets and dates, detect missing evidence, compare tasks with their history, highlight stale cost assumptions, propose work groupings and prepare a prioritised review.

But it should not silently change the plan, appoint a supplier, alter a budget, confirm a warranty position or declare a compliance duty fulfilled. Those material actions require human authority and a clear decision record. AI prepares; people decide.

Connect recurring maintenance to capital planning

PPM is the short operating cycle: this week, this quarter, this year. It manages servicing, testing, maintenance and known requirements against real assets.

A long-term maintenance plan looks further ahead to major renewals, replacements, condition deterioration and larger capital expenditure, over a horizon that may extend from ten to thirty years. Both are necessary, but they become dangerous when they use different asset references or carry contradictory assumptions.

A chiller cannot be due for major replacement in the long-term plan while being treated as fully serviceable, with no replacement consequence, in the annual PPM—unless that contradiction is visible and deliberately accepted. Holding both views against the same asset register makes the relationship clearer.

A condition inspection may change the projected replacement year. Service history may show excessive maintenance cost. A replacement project may retire an asset and stop future routine occurrences, while a warranty may affect whether a repair is an operating expense or recoverable elsewhere.

The operational and capital views should learn from one another. Inspection, condition updates, revised plans, budget decisions, work execution and verified evidence form the asset lifecycle, not separate reporting exercises.

The cost basis matters here too. A board needs to know whether a projection rests on current market evidence, a contract, a modelled assumption or an outdated library value. The decision may still be to proceed, but the basis should remain visible.

What this means

The purpose of PPM is not to create more tasks: it is to give every important asset the right intervention, for a known reason, at the right time, and show what happened next. Connected to assets, inspections, suppliers, costs, long-term planning and evidence, it becomes a living operating plan. That is the standard Residention is built around: planned work with context, evidence and accountability.

  • Check that each task identifies its asset, requirement source and expected evidence.
  • Test the schedule against real capacity, access and cost assumptions.
  • Keep performance, evidence and acceptance separate.
  • Make disagreements between annual maintenance and capital planning visible.