Observed conduct. An officer’s decision.
Civesto prepares citizen traffic reports for review by a police officer. The system checks the evidence; the authority makes the legal assessment.
From a report to a decision
Citizen
System
Officer
Authority
- Receive the reportCitizen
- Keep the file bytes verifiableSystem
- Review the evidenceSystem
- Route the reportSystem
- Record the decisionOfficer
A report takes about a minute. All you need: one photo.
The citizen sends photos or a video, chooses what they saw from a list and can add a note.
The app adds the time and, when the citizen allows location sharing, the location.
The most common types are one tap away; the rest are in a searchable, grouped list.
Before sending, the app tells the citizen if similar reports were made nearby in the last 30 days. The citizen can still send.
With no connection, the report waits on the device and is sent when the connection returns.
The citizen follows the report through four steps: Submitted, Pre-check, Officer review, Outcome.
An officer will review your report. Not every report leads to action; that's 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
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.
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.
Fit the installation to the authority
Civesto can run on your infrastructure or be hosted by Touman Studio. The hosting country for a hosted deployment is stated in the contract.
Discuss your authority’s workflow.