How GEO.works fits with Street Manager, one.network, Confirm, and your GIS

GEO.works doesn't replace the systems your team already relies on.
It's the operational layer that sits between them: permit review, financial reconciliation, evidence and audit trail, and reinstatement cost recovery under NRSWA 1991 (ss.70–72), connected straight through to the TTRO decisions your network platform already manages.

Diagram of the GEO.works technology stack, showing how it connects and coordinates Street Manager, one.network, Confirm, and ESRI/GIS

Where GEO.works fits in your stack

You already run four systems for street works. None of them talk to each other. GEO.works is the layer that makes them work as one.

Statutory foundation

Street Manager

Handles statutory notices and compliance, the legal backbone of every street works job. GEO.works integrates with it, not around it.

Network visibility

one.network

Coordinates and communicates roadworks and disruption at network level. A different problem to permit workflow, and one GEO.works complements.

Asset management

Confirm

Manages highway assets, inspections, and maintenance records. Strong on audit and compliance, and in places a direct commercial alternative.

Spatial foundation

ESRI / GIS

The maps, spatial data, and geodatabases underneath everything. GEO.works builds its business rules and conflict detection directly on top.

Operational coordination layer

GEO.works

One place to run every road activity from application to audit: workflows, approvals, conflict detection, GIS intelligence, inspections, payments, documents, and reporting. The work none of the four systems above fully cover, done in one layer with full visibility.

What sitting in the middle actually delivers

  • Better coordination. Everyone works from the same real-time information.
  • Faster approvals. Automated workflows cut delays and backlog.
  • Lower risk. Compliance, audit trails, and conflict detection built in.
  • Real savings. Fewer disruptions, less rework, less admin.