How to build a PPM schedule that actually gets done

Most facilities teams don't lack a PPM schedule. They lack one that gets finished. A spreadsheet or wall planner with every asset's service interval mapped out looks like coverage, right up until three-quarters of the tasks on it are quietly overdue and nobody's tracking which ones. A schedule that exists on paper but doesn't reflect what's actually getting done is, in a real sense, worse than having no schedule — it tells a duty holder they're covered when they aren't.

Start from the asset register, not a template

A generic PPM template pulled from a supplier's website will never fit a specific estate. The starting point has to be an accurate asset register — what you actually have, where it is, and what condition it's in — because a schedule built against assets that were decommissioned two years ago, or missing ones that were installed last spring, is fiction dressed up as a plan.

Match frequency to consequence, not habit

It's tempting to set every asset of a given type to the same interval because that's what's always been done, or because a manufacturer's default suggests it. A better starting question is what actually happens if this specific asset fails between now and the next scheduled visit — for some plant that's an inconvenience, for a fire door or a piece of lifting equipment it's a safety issue. Frequency should track consequence and criticality, not just habit or a manufacturer's generic guidance sheet.

Build in slack for a busy week

A schedule that assumes every week runs at full capacity will fail the first time someone's off sick or a reactive job eats the morning. Realistic PPM planning leaves deliberate slack — a task due this week can usually tolerate being done a few days either side without becoming a compliance problem, and building that tolerance into the plan explicitly is more honest than pretending every date is rigid and then quietly missing half of them anyway.

• –Tasks assigned to a role rather than a named person, so cover gaps don't leave a job with no clear owner
• –No visibility into what's actually overdue versus what's merely upcoming, so everything blurs into one long list
• –Frequencies copied from a manufacturer's manual without any local adjustment for actual usage or condition
• –A schedule that only the manager can see, so the person doing the work has no reason to treat dates as real
• –No route back from a missed task to what happens next — it just sits there, unresolved, indefinitely

Who actually owns a missed task

The single biggest predictor of whether a PPM schedule survives contact with reality is whether a missed task has an obvious next step. If a task slipping past its date just sits there with no clear owner and no forced follow-up, it will keep slipping. The fix isn't more discipline from the same team running the same process — it's making the overdue item impossible to ignore, whether that's a standing weekly review or a system that surfaces it automatically rather than relying on someone remembering to scroll back through last month's rows.

It's also worth deciding upfront how planned maintenance and reactive work interact, because the two compete for the same hours in the same week — see our look at balancing planned against reactive work if that tension is a live problem for your team.

The schedule that looked fine in January

A single-site team builds a schedule with 340 planned tasks a year — sensible frequencies, every asset covered, evenly spread on paper. By April it is running at roughly sixty per cent completion, and the tasks being dropped are not random: they are the ones on the top floor, the ones needing a contractor booked, and the ones scheduled in the same week as the quarterly board report. Nobody decided to drop them. They were simply the most expendable things in a week that was already full.

The schedule was not wrong about what needed doing. It was wrong about how much time existed to do it in, and because it assumed a week with no reactive load, every genuine emergency came directly out of planned work. A schedule built at eighty per cent of available capacity survives contact with a normal month; one built at a hundred per cent fails in the first busy week and then keeps failing.

Common mistakes

• –Building the schedule at full capacity, so every reactive job displaces planned work
• –Spreading tasks evenly across the year without regard to when the team is already busy
• –Scheduling contractor-dependent tasks without allowing for their lead time
• –Treating a missed task as closed at the end of the month rather than carrying it forward visibly
• –No named owner for a task, so an overdue item belongs to nobody in particular
• –Measuring completion percentage without looking at which tasks are consistently the ones dropped