industry
A resident is waiting. So is the inspection programme.
Parks, playgrounds, roads, drainage, lighting and buildings out of one works depot, with published response times and an audit trail that has to hold up years later.
what is different here
Reactive requests and statutory programmes, one depot.
-
Requests and programmes want the same crew
A reported pothole and a scheduled playground inspection are both due on Tuesday, and the programme is what quietly gets pushed.
in Etaprise → both on one board, with what slipped shown
-
The audit question is always “prove you inspected it”
Doing the inspection is not the hard part. Producing who did it, when, and what they found, long after the fact, is.
in Etaprise → the inspection record held against the asset
-
A ratepayer wants a date, not a queue position
The person on the phone can see that the request was logged, and nothing about when a crew will actually be in that street.
in Etaprise → the scheduled date visible to whoever takes the call
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.
Requests arriving from residents against published response times, inspection programmes carrying statutory obligations, and both drawing on the same depot. The reactive side goes first because it is the work that is already being counted.
-
weeks 1–3
Requests and response times
Resident-raised requests land as work with the response time attached, categorised the way your service standards already describe them, so the clock is on the job rather than in a spreadsheet.
-
weeks 2–5
The asset register
Playgrounds, drainage, street lighting, road segments and buildings brought in class by class, built up as crews attend them rather than waiting on one complete data load.
-
weeks 4–8
Inspection programmes
Statutory and routine inspection cycles generated against the register, each with the form and photographs the obligation calls for, and a defect raised straight from a failed inspection.
-
ongoing
Panels and reporting
Contracted panels issued work the same way as in-house crews, and reporting for elected members and auditors drawn from the same records the depot already works from.
questions from this sector
The objections we hear, answered plainly.
Both sit on one board, so a request that displaces a programmed inspection shows what it displaced and when that inspection is now due. It does not create crew capacity you do not have; it stops the trade-off happening silently.
Every inspection is held against the asset with who attended, when, what they recorded and the photographs taken, queryable across a period rather than retrieved one document at a time. Missed and overdue inspections are as visible as completed ones.
Panel contractors receive work orders and return the same forms, photographs and completion evidence as in-house crews, so the record does not change shape depending on who did the job. Live status depends on whether they use the app.
Reporting comes off the same records the crews close, broken down by asset class, ward or service area, which means the number in the report and the job in the depot cannot drift apart. Where a corporate reporting platform owns the presentation, the data goes to it.
further reading
Further reading
Bring us a week of your depot.
Bring a day of resident requests and one inspection programme. We will run them together.
Book a demoother industries