Road hazards, ready for the responsible team.
Road operators use a separate list of road hazards. Reports arrive in the authority’s inbox for review and a recorded decision.
Receive the report
The app comes in two builds: one for traffic offences and one for road hazards.
The citizen follows the report through four steps: Submitted, Pre-check, Road operator review, Outcome.
The road operator will review your report. Not every report leads to action; that is a normal part of the process.
First, photograph what you saw
A photo or video is enough
- Take with Camera
- Choose from Gallery
- Record Video
It's fine if you don't know — the photo is enough
You can change anything before sending
What the system measures
For road reports, visibility, illumination and surface are measured from the image, each with a confidence level. The measurement supports the report; it does not replace confirmation on site.
Road conditions · measured
| Road condition (measured) | Confidence |
|---|---|
… image is consistent with reduced visibility. Officer confirmation required before this is treated as a road condition.
| medium |
Low-light capture — night or unlit section
| high |
Specular pattern on the carriageway consistent with a wet or contaminated surface
| low |
The measurement supports the report; it does not replace confirmation on site.
Physical measurements only. This module does not determine whether a condition exists; it reports what the image is consistent with and what it cannot exclude.
Route the report
Each report type maps to the responsible roles with a proposed urgency, and the reason is stored with the report. A type with no rule is shown as held for manual assignment.
Routing proposes recipients and urgency. It does not task a crew.
A queued routing entry does not prove delivery or a person's acknowledgement.
See where reports cluster
A location is listed once the same condition is reported twice within about 150 metres and 30 days.
The hotspot view groups reported locations into cells and lists the busiest cells alongside the map.
Reference CV-FC-0184
Validated
Handheld phone use while driving
Submitted 02 Nov 2026 · 10:14 UTC
Conduct offence · no machine assessment
Evidence seal · SHA-256
c48a7f2d91b6…
capture.jpg · 842 KB · sealed 2026-11-02 10:14:08 UTC
- Camera recorded as Aster C7
- Lens and exposure metadata present
- Content Credentials present (not validated here)
Why these findings?
Machine inspection reports observations, not conclusions — the assessment is yours.
The system does not assess the driving itself. The authority decides whether an offence has occurred.
A matching digest checks the file bytes. It does not prove that an event occurred.
This console is read-only. Decision controls are disabled. Open the authority console (read-only)
Keep the decision with the officer
The system does not assess the driving itself. The authority decides whether an offence has occurred.
Open the evidence with the report
The case brings the submitted recording together with the results of its metadata checks. The reviewing officer makes the assessment.
Review and record
An officer can validate, forward, act on or close a report. The legal basis and the officer’s note are recorded with the case.
A case moves through recorded states: New, Under review, Validated, Forwarded, Acted, Closed.
The decision form records a legal basis and an officer note with the outcome. Changing an outcome needs a key with the case_write scope.
Follow the work in the audit log
The audit log records views, changes and exports with the user, time and stated justification.
Access follows roles: the case officer sees cases and evidence, the management view sees aggregates only, and the IT view sees the audit log, webhooks and keys but no case content.
A case file can be printed with a signature block for the reviewing officer, the date and the outcome or file number.
A report from before the seal was introduced says so, instead of showing an upload-time digest.
| Export and delivery |
|---|
| CSV |
| Excel workbook |
| DATEX II v3.5 |
| GeoJSON |
DATEX II export is for road reports and is a generic v3.5 test publication. National profiles and real publication are not enabled.
For road reports, a Common Alerting Protocol 1.2 envelope of the routing decision can be downloaded on request. It is an interoperable format.
Discuss your authority’s workflow.