What the Driver Should See

Almost every design decision in this field is made about people who never see the interface. Changing that costs little and changes a great deal.

What they should see

Their own events, with the context — speed, location, the clip where one exists.

Their own score and how it was calculated, which requires the formula to be visible.

The thresholds that apply to their vehicle type.

Their trend over time, against their own history rather than against colleagues.

And when their footage was viewed, and by whom.

The score explanation specifically

A driver told their score is sixty-eight and not told how deserves the answer they will invent.

Which is usually that it is arbitrary, and that belief is very hard to reverse.

Show the components: events by type, exposure, weights.

If the vendor will not expose this, that is a procurement finding rather than a fact of life.

Disputing an event

A route to say "that was a defensive manoeuvre" or "that limit is wrong".

With a named reviewer and a response time.

And a visible outcome: upheld, removed, or explained.

A system with no dispute route treats its own output as fact, which the false positive rate in the data quality note shows it is not.

Why this improves the data

Drivers correct what nobody else can: the map error, the mounting fault, the event that was a pothole.

And a dispute route surfaces these systematically rather than through complaints.

A programme with no disputes is not accurate; it is one where nobody bothers, which is a worse position because the errors remain.

The access right

In most jurisdictions drivers can request the personal data held about them, which here includes events, scores and footage.

Routine self-access satisfies most of that need in seconds rather than in a statutory response period.

And it means records must be retrievable per person and free of anything you would rather not show them, which is a useful discipline in itself.

The measure

Disputes raised and their outcomes.

Time to resolution.

And whether drivers look at their own data at all, because an available screen nobody opens means the programme is still something done to them.

Show the viewing log

The feature that most changes how the programme is received.

When their footage was viewed, by whom, and why.

Unusual, cheap to enable where the product supports it, and checkable.

It also surfaces the pattern nobody else would find: one manager repeatedly viewing one driver.

Connect policy and data

The choices in this note can be compared with see the service-operation example. Keep the written purpose in control and enable only the information needed at this boundary.

Independent reference

For a thematic point of reference, see the European Data Protection Board. Use the current material as an outside check before turning the principle into a system rule.