industry
The PPM calendar, and everything that interrupts it.
A portfolio of buildings, each with its own SLA, its own asset list and its own monthly report that has to be right.
what is different here
Planned and reactive, same trades.
-
Tenant calls eat the planned programme
A reactive job at one building pulls the engineer who was booked for a PPM visit at another. The calendar slips quietly and only shows up at month end.
in Etaprise → displaced PPM visits re-scheduled and visible the same day
-
The subcontractor holds the evidence
Lifts, fire systems and specialist plant are on a subcontractor panel. Their certificates and worksheets arrive by email, late, in whatever format they use.
in Etaprise → panel work issued and returned on the same record as direct labour
-
One lapsed certificate is a portfolio problem
An expired inspection on a single asset in a single building is what the client audit finds, and it is asked about at portfolio level.
in Etaprise → certification status tracked per asset, across every site
On site
the setup
The modules that carry most of the weight here.
The other eleven are still there. Sector setup changes which forms attach to a job, which certifications gate an assignment, and what a closed job has to prove, not which software you are running.
what a rollout looks like
In order, and with honest timings.
The planned programme is the contract, and the reactive queue is the thing that damages it. This sequence gets the calendar onto the system first, then makes the interruptions measurable rather than invisible.
-
weeks 1–3
Contracts and the PPM calendar
Load each building's scope, its response and rectification targets, and the planned visit frequencies. Recurring work is predictable, which makes it the safe first load.
-
weeks 2–5
Asset registers per site
Plant, lifts, panels and fire equipment with location, condition and statutory dates, built up as PPM visits touch them rather than surveyed in one pass.
-
weeks 4–8
Reactive intake and the panel
Tenant-raised jobs enter the same queue as planned work, and subcontractors are issued and return evidence through the same record instead of by email.
-
ongoing
The monthly client report
PPM completion, reactive volumes, SLA performance and open compliance items assembled from the work itself, so the report stops being a week of collation.
questions from this sector
The objections we hear, answered plainly.
That is the normal case, not the exception. Response and rectification targets sit on the contract for that site, and a job raised there inherits them, so the clock a dispatcher is working to is the one the client agreed.
Panel firms are issued work orders with the same forms, photographs and sign-off the client audit expects, and the returned evidence lands on the asset record. Live status on their engineers depends on whether they use the app; the evidence does not.
It will still compete for the same trades. What changes is that a displaced planned visit is re-scheduled rather than forgotten, and you can see which sites keep absorbing the disruption instead of discovering it at month end.
The report is assembled from completed work rather than retyped: what was planned, what was done, what slipped, what is outstanding on compliance, and the evidence behind each line. Layout and branding are configured to your account's format.
further reading
Further reading
Bring us a month of your portfolio.
One site's PPM calendar and its reactive log. We will build the client report from it.
Book a demoother industries