PPM Schedule Software
The reason PPM software gets abandoned half-configured is that somebody has to write the schedule. Deciding what a chiller needs, how often, and what each visit covers is specialist work, and it is the work most teams were hoping the software would do. PM Assist supplies it: register an asset and its maintenance programme is generated from a published task library, already grouped by frequency.
Where PPM Programmes Actually Fail
A PPM programme fails in one of three ways, and none of them is the scheduling engine.
It fails at setup, when the effort of writing hundreds of task lists means the programme covers the plant somebody got round to and nothing else. It fails at drift, when visits carried out late are recorded as the new anniversary — a quarterly service run a fortnight late four times a year quietly becomes a three-visit-a-year schedule, and nobody notices because each individual visit looks fine. And it fails at evidence, when a completed visit is recorded in the maintenance system while the certificate it produced is filed somewhere else entirely, so the compliance position and the maintenance record have to be reconciled by hand.
All three are design problems rather than discipline problems, and all three can be designed out.
Schedules Generated From the Asset, Not Typed
PM Assist holds a library of maintenance tasks covering 123 asset types, each task already tagged with the frequency it belongs to. Registering an asset generates its schedules from that library: a passenger lift produces its monthly alarm test and its six-monthly LOLER thorough examination, with the tasks written and the statutory duty each one discharges already linked.
Generation is previewable and idempotent. The button reports how many schedules and how many visits a year it would create before it creates anything, and running it again after adding more plant adds only the new schedules rather than duplicating what is there.
The tasks are copied onto the schedule at the moment it is created rather than read live. That matters for evidence: editing a published checklist must not retroactively change what an engineer was told to do last year, because a record that a later edit can rewrite is not a record.
- 123 asset types with tasks already grouped by frequency
- Preview the schedule count and annual visit count before creating anything
- Idempotent — run it again after adding plant without creating duplicates
- Statutory duties linked automatically where the interval matches
- Tasks snapshotted at creation, so a completed visit cannot be rewritten
A Late Visit Does Not Move the Cycle
A service due on 1 March and carried out on the 14th is next due on 1 June, not 14 June. The cycle is computed from the due date rather than the completion date, so running late does not permanently shift the schedule.
The one exception is a visit completed so late that the next date has already passed. There the cycle is re-based forward, because handing somebody a due date that is already overdue the moment it is created is not a schedule, it is a reproach.
Skipping a visit is recorded as a decision rather than a gap. A skip requires a reason, because a skipped statutory visit with no reason recorded is indistinguishable from one that was forgotten — and the difference between those two is the whole of the defence.
Completing a Visit Creates the Evidence
Where a schedule discharges a statutory duty, completing the visit can write the compliance record in the same action: the occurrence, the schedule advance and the certificate record all in one transaction. The maintenance programme and the compliance register stop being two systems that have to agree.
The planner itself projects the calendar rather than storing it. A schedule holds its next due date and its frequency, and the dates beyond that are computed when somebody looks. That keeps a daily plant check from becoming three and a half thousand rows, and means changing a frequency takes effect immediately rather than requiring every future visit to be rewritten.
Compliance & CAFM
Compliance, maintenance and documents in one place
PM Assist is building compliance software with the O&M manuals built in: every paid plan includes the compliance register, planned maintenance and mobile inspections.
- The compliance register is set up from each building's property type, with gaps shown for duties that have no record.
- Planned maintenance is generated from the asset register, with the tasks and frequencies already written.
- AI reads your certificates and proposes the dates and remedial actions; a person checks them against the source document before they count.
Frequently asked questions
Do I have to write the maintenance tasks?
What if we have equipment the library does not cover?
Can schedules be set to intervals the standard frequencies do not cover?
How does it handle contractors?
Can we see the whole portfolio's maintenance in one place?
Build a maintenance programme in an afternoon
Register your assets and we will generate the schedules — every task on the right frequency, from a published library. Start free on one building.
- Upload and organise building documentation
- AI-powered search across all your manuals
- Source-cited answers for every query
- Team collaboration and access control
- No credit card required to start