Completion and overdue
What was due, what happened inside its window, and what is late — while you can still act on it.
Solutions › Maintenance › Planned Maintenance
Maintenance · Planned Maintenance on Site Assets
Planned maintenance that actually happens.
Every asset carries its own service schedule. The work appears, the technician completes the checklist on a phone, and the whole record lands on the asset — so the history builds itself.
Asset register · Service schedules · Checklists and readings · Certificates · Cost per asset
GEN-114 · standby generator · criticalRegional depot — Midrand
- Make / model
- Generic 220 kVA · serial 4471-A
- Interval
- Every 6 months, or 250 running hours
- Next service
- Due 12 Oct · scheduled, parts held
- Last service
- 14 Apr · checklist passed · signed
- History
- 9 services · 3 years on this asset
- Warranty
- Supplier cover to Mar 2027
- Cost to keep
- Labour and parts, accumulated per asset
The problem
The schedule and the service history are never where the technician is standing
The schedule is on somebody’s spreadsheet. The job card is paper. The asset’s history is in an engineer’s head. The first time anyone reads the record is after something has failed.
The schedule is one person’s spreadsheet
It works until they are on leave, or resign, or the estate grows past what a sheet can hold.
An invisible backlog
Planned work rarely gets cancelled. It slips — and nobody can see by how much until a failure or an audit.
History in a filing cabinet
No pattern, no warranty claim, and no basis for deciding whether to service again or replace.
Nobody knows the cost per asset
Capital gets spent on the assets that shout loudest, not the ones that cost the most.
How it works
An asset, through a year
The asset exists
Registered against a site with its make, model, serial, criticality, warranty and service interval.
The schedule runs
Services are generated ahead of time from the interval on the asset — no spreadsheet to maintain.
Work is planned
Assigned by skill, region and availability, with the parts identified before anyone travels.
On site
Scan the asset tag, work the checklist, take readings and photos, record parts, capture a signature — online or off.
Faults become work
Anything out of specification raises a corrective job instead of a note nobody reads.
The record grows
Service report or certificate issued, and every service, reading and part joins the asset’s own history.
What lands on the asset
The history builds itself
- Every serviceWhat was done, by whom, when, against which checklist
- ReadingsCaptured on site, in sequence, so trends are visible
- PartsWhat was fitted, and what it cost
- Photos and signatureEvidence from the service, and the client’s sign-off
- WarrantyWhat is still covered, and by whom
- CertificatesPer service, per asset or per site, ready to hand over
Scan the tag on the asset and the whole history is there — including the services you did not do.
1/4
- 01
The job is waiting
The service appears on the technician's dashboard, with the totals for the day.
- 02
The checklist, on site
Every inspection item is answered on the phone, against the asset.
- 03
Signed off
The technician signs and answers the closing questions before the job can close.
- 04
Done, and recorded
The job is confirmed complete and the record is saved.
The job is waiting
The service appears on the technician's dashboard, with the totals for the day.
The checklist, on site
Every inspection item is answered on the phone, against the asset.
Signed off
The technician signs and answers the closing questions before the job can close.
Done, and recorded
The job is confirmed complete and the record is saved.
Screens from the WorkWide app and portal, shown with demonstration data.
What you can finally see
The reporting a spreadsheet cannot give you honestly
What keeps failing
Recurring faults by asset, model or site, so the pattern shows up before the budget cycle does.
Cost per asset
What each asset has cost to keep, as the basis for service-or-replace decisions.
Evidence on demand
Twelve months of service history for one machine, in a minute rather than a morning.
Who it’s for
Built for equipment that is not in one place
Maintenance service providers
Power, generators, UPS, HVAC, fire and network equipment maintained on client sites under contract.
Facilities and property teams
Plant rooms, lifts, HVAC, generators and building services across a portfolio.
Healthcare facilities
Building services and equipment where servicing evidence is inspected.
Utilities and distributed infrastructure
Pump stations, reservoirs, treatment plant and substations.
Why WorkWide
Built for the technician, not the planner
The schedule creates the work
Intervals sit on the asset, so jobs appear and lateness is visible without anyone maintaining a sheet.
The record is made on site
Checklists, readings and photos captured where the work happens, offline if the site has no signal.
It lands on the asset
Not in a job folder — on the thing itself, for as long as you own it.
One platform for the rest of it
The same system runs reactive work, contracts, parts and client reporting when you need them.
FAQ
Questions maintenance teams ask
We don’t have an asset register. Can we still start?
Yes, and this is the usual position. The register can be built as the first round of services happens, so the data load and the work are the same exercise.
How do technicians identify an asset on site?
QR or barcode tags. Scanning the tag opens that asset’s schedule, checklist and history.
What triggers a service?
The interval held on the asset. Readings and failed checks raise corrective work alongside the planned schedule.
Does it work with no signal?
Yes. The job is completed offline and syncs when the phone is back in range.
Can we issue certificates to clients?
Yes — per service, per asset or per site.
Can we see what an asset costs us?
Yes. Labour, parts and services accumulate against each asset over time.
What share of last year’s services happened on time?
If the honest answer is “we think most of them”, that is the problem.