One road incident needs more than one interface

A road incident may begin as one event, but it does not create one information need.

The driver needs to understand what to do next under pressure. A response team needs to see what requires attention. A road agency needs verified infrastructure context. A national road-safety institution needs coverage, quality and patterns rather than an oversized version of the driver screen.

This is one of the central product decisions emerging from After Impact, a Dial8 venture currently in pilot preparation. The product is being designed around a shared incident record with different, purpose-limited views—not one universal dashboard for every stakeholder.

Begin with the person at the roadside

The driver experience is built for the first hour after an accident. Its job is not to present every fact that may eventually matter. It is to reduce the next decision.

The current product flow includes a deliberate activation, plain-language triage, location capture, coordination states, guided evidence capture, insurance information and optional legal support. It also treats failure as part of the experience. Location permission can be denied. Coordination can fail. A service can be unavailable. Direct emergency calling must remain accessible.

That creates a strict hierarchy:

• Immediate safety before administration.
• One necessary action before a complete case history.
• Plain language before institutional terminology.
• Honest unavailable states before false reassurance.
• Explicit consent before optional information sharing.

The driver does not need a national trend view while standing beside a damaged vehicle. The interface must protect attention.

Operations need a queue, not the driver journey

The same incident looks different to an operations team.

An operator needs to distinguish active incidents from completed records, see which coordination steps are pending or failed, review evidence completeness and understand which requests require a person. The useful unit is no longer only the next screen. It is the state of work across incidents.

This is why the After Impact operations experience uses incident status, response stages, timelines and consent state. Those fields help answer practical questions:

• Which incident needs attention now?
• What has already happened?
• What failed or remains unavailable?
• Which evidence exists?
• What may this team access?
• Who owns the next action?

The product cannot simply expose everything collected by the driver app. Operational access needs a purpose, a role and a boundary.

Institutions need distinct questions

Road-safety organisations do not all make the same decisions.

The current After Impact work includes separate stakeholder workspaces built around a shared incident contract. The RTMC-oriented workspace focuses on national oversight, coverage, data quality, corridor and province signals, research controls and stakeholder coordination. The Roads Agency Limpopo workspace connects incident signals to road assets, inspections, maintenance, structures, traffic and authorised project records.

These are related views, but they are not interchangeable.

A national oversight team may ask whether province or source-organisation coverage is sufficient to support a comparison. A roads agency may ask whether repeated incident signals near a route should be checked against an authoritative asset record or inspection process. A responder needs an actionable case, not a research dataset. A department needs information limited to its mandate and permissions.

The product decision is to design around each institution's real question instead of cloning one generic public-sector dashboard and changing the logo.

A shared record is not a shared conclusion

After Impact's common incident shape can carry a reference, time, route, municipality, captured location, severity, response stages, evidence count and timeline. It can also record whether important fields—such as road condition, response time or source organisation—are present.

That shared structure creates continuity. It does not make every value verified or every conclusion valid.

Citizen-captured information can provide an early signal. Evidence completeness can show whether expected fields are present. Neither automatically certifies accuracy, legal admissibility, official crash classification, infrastructure condition or institutional verification.

The stakeholder interfaces therefore need to preserve three distinctions:

• Captured information versus authoritative records.
• Available fields versus missing coverage.
• A signal worth reviewing versus a decision already made.

For example, the RAL-oriented workspace is designed to complement authoritative road-asset and engineering processes. It does not replace inspections, maintenance work orders, procurement controls, official crash records or claims decisions.

That boundary is part of the product, not a disclaimer added after the interface is finished.

Missing data must remain visible

Dashboards often look more convincing when every metric is populated. In a pilot-stage product, that can be dangerous.

The After Impact stakeholder workspaces are being designed to show explicit collection and connection gaps. If province metadata is not collected, the province view should say so. If a road-asset feed is not connected, the interface should not invent condition, traffic, kilometre, budget or backlog values. If source organisations are not identified, stakeholder coverage is unknown—not zero.

An honest empty state does more than prevent a misleading chart. It identifies the operational work required before the view can support a decision:

• Which organisation owns the missing source?
• Is there permission to collect and use it?
• What standard or authoritative system should it be compared with?
• Who is responsible for resolving the gap?
• What decision must remain blocked until then?

In institutional products, unavailable data is itself a readiness signal.

The next stage is institutional validation

After Impact has working driver, operations and stakeholder interface foundations. That is evidence of product development, not evidence of institutional adoption or road-safety impact.

The next meaningful stage gate is a scoped institutional conversation that tests the operating model: the stakeholder, decision, permitted fields, authoritative sources, responsibilities, pilot boundary and success measure.

The product must learn whether the role-specific views match how an institution actually works, which data agreements would be required and what a credible controlled pilot could measure. Until that happens, the work remains pilot preparation.

This is what product in progress looks like at Dial8. The visible interfaces matter, but the deeper product is the agreement between people, records, permissions and decisions. Building one shared system does not mean giving everyone the same screen. It means helping each authorised participant see the smallest truthful view they need to act.