Set up by us. Then it runs without you.
Councils do not self-serve their way through a signup wizard — a compliance portal is only as good as the boundary data behind it. Here is the day-to-day, and here is what rollout actually involves.
Three steps, and only one of them is yours.
The crew finishes the job
Your contractor works exactly as they do today. Their field app captures position, time, service type and photographs while they are on site.
Verdue verifies and records it
The submission is tested against the site boundary, deduplicated, and written to an immutable record with its evidence attached.
Your map updates
The site changes status the moment the record is accepted. Overdue sites surface on their own — nobody has to go looking.
Five steps from GIS handover to go-live.
Typically four to six weeks end to end. The implementation is a one-off engagement quoted with your subscription — it covers the import, configuration, contractor onboarding and training below.
- 1
GIS data import
You hand over your parks and reserves data in whatever form you already hold it — Shapefile, GeoJSON or an ArcGIS export. We convert it to PostGIS geometry and load it, boundaries intact. Nothing is re-drawn by hand, so what you see on the map is the same geometry your GIS team maintains.
- Shapefile, GeoJSON or ArcGIS export accepted
- Boundaries, centroids and areas derived on import
- Sites grouped by your existing categories and zones
- 2
Maintenance schedules configured
For each site category we configure the frequency and service types your contracts actually specify — Category A parks on a fortnightly mow, corridors on a seasonal slash, environmental overlays where they apply. This is what turns a date into "overdue".
- Frequency and service types per category
- Environmental overlays where they apply
- Due-soon and overdue thresholds set to your terms
- 3
Contractors onboarded
Each contractor on your maintenance contracts is added and connected. Contractors on Stipa are linked with a signed webhook and start submitting immediately. Others submit through the same documented interface, or are set up with manual entry. No contractor is excluded because of the software they run.
- Stipa contractors connected via signed webhook
- Other software submits through the same interface
- Manual entry available where there is no software
- 4
Council accounts and notifications
We create your council administrator, invite your contract managers, and set who is notified about what. Most councils want overdue alerts to the contract manager and the monthly report to a wider list — that split is configured here.
- Administrator and contract manager roles
- Per-user email notification preferences
- Report distribution list configured
- 5
Go live
We run the first compliance snapshot with you in the room, walk your contract manager through the dashboard, and book a check-in for thirty days out. From that point the map is live and the monthly report generates on its own.
- First compliance snapshot run with you
- Walkthrough for contract managers
- 30-day check-in scheduled
Four things, and one of them is a calendar invite.
The implementation work is ours. What we cannot do without is the data only your council holds, and an hour of the person who knows how the contracts are written.
- GIS data
- Parks, reserves and corridors as Shapefile, GeoJSON or ArcGIS export
- Contract terms
- Service frequencies and categories, per contract
- Contractor list
- Businesses on your maintenance contracts, with a contact each
- One workshop
- About 90 minutes with your contract manager