Fragmented evidence
Images, reports and updates can sit across separate systems, making review and comparison slower.
Road intelligence for highways teams
Auztec is building ARCH for councils, highways teams and contractors that need clearer defect visibility, practical prioritisation and a traceable route from road evidence to action.
The operational gap
Highways teams already receive inspection records, resident reports, images and contractor updates. The challenge is deciding what needs attention first, recording why that decision was made and keeping the evidence connected as work progresses.
ARCH is being developed as the intelligence and workflow layer between captured road evidence and the systems used to inspect, approve, deliver and report maintenance activity.
Images, reports and updates can sit across separate systems, making review and comparison slower.
A defect signal alone does not explain operational risk, urgency or the appropriate next step.
Authorities and contractors need a clear record of what was reviewed, decided, assigned and closed.
ARCH product evidence
The current interface brings together work items, map context, evidence, approvals, capture-node status and audit history. Backend and capture integration are the next development stages.
What ARCH is intended to do
Receive route capture, inspector submissions or agreed third-party road-condition data.
Present the suspected defect, location, imagery and supporting metadata for human review.
Accept, reject, reprioritise or request further evidence with the reviewer and reason retained.
Prepare an approved work item for assignment, export or integration with existing systems.
Keep status changes, evidence, approvals and completion records connected throughout the lifecycle.
Partner outcomes
The council and contractor propositions are related but distinct. The initial field work will validate where ARCH removes friction rather than adding another reporting burden.
For councils and highways teams
Contractor workflow under validation
These outcomes are pilot hypotheses and are not presented as proven customer results.
Primary pilot hypothesis
An initial evaluation should test one end-to-end workflow on an agreed route or operating area. It should not attempt to replace an authority's existing asset-management or work-order platform.
A pilot partner contributes
A pilot partner receives
Operational evaluation brief
A practical overview for highway authorities and maintenance contractors covering ARCH's current stage, the operational workflow, evaluation scope, partner responsibilities, expected outputs and governance approach.
Governance summary
Scope and ownership: routes, users, outputs, data ownership and responsibilities agreed in advance.
Privacy and security: DPIA screening, retention, access controls and processing terms considered where applicable.
Evaluation route: discovery first, then a separate formal agreement before any live pilot or deployment.
Contact Auztec
Initial conversations are focused on operational fit, field-validation requirements and whether ARCH could address a defined evidence or prioritisation problem.