Run the day · The visits that keep the book paid
Not a reminder on a whiteboard. A work order that generates itself from the agreement's schedule, routes with nearby stops, and reports against a compliance record when it's done.
What it is
A preventive-maintenance visitin Thermal is a work order generated from a service agreement's schedule against specific covered equipment — not a manual reminder someone has to remember to place on the board. It carries its own inspection checklist, and its completion feeds the compliance and safety scorecards.
PM is where service agreements and equipment meet the dispatch board — the schedule comes from the contract, the visit is for a specific unit, and the result becomes part of that unit's permanent history. That's the record behind planned maintenance percentage and PM completion rate.
A PM visit is a work order like any other — the difference is it generates itself from the agreement's schedule against the equipment it covers, and lands on the board with the unit's history already attached.
One account. Every site under it.
The address, and the branch that covers it.
The unit the visit is for, with its history.
The schedule, frequency and coverage rules.
Generated here, worked in the field.
You are hereBuilt from the work, minus what's covered.
The schedule comes from the service agreement, the visit targets a specific unit, and the completed checklist is appended to that unit's history and read by the dispatch board the same way any other job is.
| Work order | Unit · Site | Frequency | Route | Due window | Status |
|---|---|---|---|---|---|
| PM‑0911 | EQ‑1201 · Cedar Park DC 3Mississauga | Quarterly | R-4 East | 2026‑08‑14 | Overdue |
| PM‑0914 | EQ‑1188 · Riverside FoodsWalk-in A · Winnipeg | Monthly | R-2 West | 2026‑08‑30 | Scheduled |
| PM‑0917 | EQ‑1142 · Northgate MedicalRoof B · Ottawa | Quarterly | R-1 Ottawa | 2026‑09‑18 | Generated |
| PM‑0919 | EQ‑1215 · Harbour PointPenthouse · Halifax | Semi-annual | R-7 Halifax | 2026‑10‑05 | Generated |
| PM‑0922 | EQ‑1222 · Westfield Distribution4 sites · Prairie | Quarterly | R-3 Prairie | 2026‑09‑11 | Generated |
Seven pieces of one preventive-maintenance program — all shipped, all connected to the same records.
PM work orders generate from the agreement's own schedule rather than relying on someone to remember to book them — the visit shows up on the dispatch board on its own when it comes due, with the unit, the checklist, and the last visit's readings already attached. The only person who has to do anything is the technician who turns up.
PM visits group by route from the same schedule the service agreement generates them against, so a technician's maintenance day covers nearby stops instead of crossing town between every unit. The routing is branch-aware too, so a multi-branch shop keeps each branch's visits on that branch's trucks.
A job-hazard-analysis check completes on arrival before work starts, giving the technician and the office a documented safety record for every visit, not just the ones where something went wrong. The check is a required step, not an optional field, so a clean crew-safety record is something a shop can point to.
Work that needs a compliance follow-up — a flagged inspection, an outstanding deficiency — lands in a dedicated queue instead of getting buried in the general work-order list, so it can't quietly drop off a busy day. A flagged visit stays in that queue until a person acts on it, and the office sees the queue, not a folder of paper — the same source data behind PM compliance rate.
Response-time commitments and refrigerant-tracking obligations report against the agreement's own terms, so a compliance gap surfaces on the record before it becomes a regulatory problem. The same reporting is what refrigeration and fire-and-life-safety contractors run hardest on.
Safety-check completion rolls up into a scorecard view, giving a branch manager one place to see whether arrival checks are actually happening across the crew, not just on paper in a drawer. If a truck is skipping the step, it shows in the score, not in an incident later.
Every PM visit adds to the specific unit's permanent service history — so the next technician who touches that equipment sees exactly what the last inspection found, and a callback connects to a cause instead of starting over. The full record lives on the equipment page.
Three boundaries that keep a maintenance program honest.
The inspection steps on a visit are the ones you define for that agreement and unit. Thermal doesn't generate model-specific task lists from an external catalogue — your procedures are your own.
A visit that comes due and doesn't get done lands in the compliance queue for a person to act on. Nothing re-books itself in the background, and a missed PM can't silently turn into a compliance gap nobody saw — it stays visible until someone decides what happens next.
PM is generated from the agreement and lands on the same work-order record everything else reads from — there isn't a parallel schedule to keep in sync with the real job list.
If a capability isn't on this page, assume it isn't built. We'd rather lose a deal on a missing feature than win one on a sentence that turns out to be aspirational.
A PM visit is a generated work order — these are the records it flows between.
The ones that come up when a shop has been keeping PM in someone's head.
No — PM work orders generate from the service agreement's own schedule against the equipment it covers, so a visit shows up on the dispatch board when it comes due instead of relying on someone remembering to book it. Frequency, season and route rules all come from the agreement.
The technician completes a safety (JHA) arrival check, works through the visit's inspection checklist, and the results feed the unit's permanent service history plus the compliance and safety scorecards. Everything the visit produced lands on the record it came from.
SLA commitments and refrigerant-tracking obligations report against the agreement's own terms, and any flagged inspection or outstanding deficiency lands in a dedicated compliance queue rather than the general job list. A gap surfaces before it becomes a customer meeting or a regulatory problem.
Yes — PM visits generated from the same schedule group by route, so a technician's maintenance day can cover nearby stops instead of crossing town between every unit. Branch-aware routing keeps a multi-branch shop's visits on the right trucks.
On the specific unit's equipment record — every PM visit adds to that unit's permanent service history, so the next technician who works on it sees exactly what the last inspection found, and the office can answer any follow-up from the same record.
Bring an agreement with visits you've been chasing by email and watch the schedule generate, route, and report against compliance on the call.