Black-box reading looks wrong: what to do before an insurer cancels

An alert says the car exceeded the limit. The driver remembers a different road. The map may have matched the wrong carriageway, a journey may have been attributed to the wrong person, or the data may be right and the explanation may simply be incomplete. Treat the alert as urgent evidence to investigate—not as proof that the insurer is wrong or that cancellation is automatically unfair.

First protect the insurance position

Read the notice carefully and write down the proposed action, date and time. Ask the insurer, in writing if possible:

1. Is the policy active now?
2. Is this a warning, a restriction, a price change or a cancellation notice?
3. What policy term is being relied on?
4. What deadline applies for a response or improvement?
5. What happens if the dispute is still open when that deadline arrives?

Do not assume that making a complaint pauses cancellation. Do not drive after cover ends unless suitable replacement insurance is in place. GOV.UK says it is illegal to drive on a road or in a public place without at least third-party insurance and lists possible penalties (GOV.UK).

If the insurer says the policy will end, ask for the exact effective date and arrange alternative advice promptly. Keep paying or settling the policy as the terms require while you establish the position; stopping a direct debit is not the same as cancelling correctly.

Build a useful evidence pack

Save the warning, full email headers if available, app screenshots, policy schedule, terms, journey date, route and any calls. Keep original files rather than only cropped screenshots. Record who was driving and why you know that. A parent can help, but the policyholder should be involved and may need to authorise the insurer to discuss the account.

For a disputed speed, make a simple table:

Do not manufacture precision. A navigation screenshot taken later may show a changed limit. A passenger’s recollection can support context but is not automatically better than the device record. Explain uncertainty instead of filling gaps with a confident story.

Ask the right technical questions

The FOS says that when a consumer disputes telematics data, it may ask how the insurer checked accuracy, whether the correct limit was applied, and whether the car was actually on a nearby road with a higher limit. It can also examine data over time and the insurer’s warnings (FOS telematics guidance).

Ask the insurer to explain, in plain language:

• the event time and location used;
• the speed and speed limit it applied;
• whether the system can distinguish parallel roads or slip roads;
• whether the reading was converted between miles and kilometres;
• whether another driver, vehicle or account could be involved;
• what quality checks or anomaly review were done; and
• which part of the policy turns the event into a warning or cancellation.

An “incorrect road” challenge needs more than “the map is wrong”. Identify the two roads, the direction and the sign or limit that applied. For a “wrong driver” challenge, say what evidence is available and what is not. For power or device problems, keep repair, installation and contact records; do not claim a hardware fault without evidence.

What final Ombudsman decisions show

FOS decisions are individual fact findings, not a prediction of your outcome.

In DRN-4616852, West Bay relied on a 115 mph record even though the car’s manufacturer specification listed a 99 mph maximum. Earlier readings had already been discarded, and the Ombudsman identified continuing GPS drift and anomalies. Cancellation was found unfair. The remedy included waiving charges, discharging broker fees, refunding any balance due, recording cancellation at the customer’s request, providing no-claims evidence and removing negative credit markers if any, plus £250 compensation (final decision). The lesson is the quality of the contradictory evidence, not a rule that a high speed can never be recorded.

In DRN-4607488, the Ombudsman accepted cancellation after reviewing serious speeding data and repeated alerts. The driver disputed the readings and road layout, but the available data supported the insurer’s position. A separate message about a kilometres-per-hour error had been corrected and did not explain the events relied on (final decision). A complaint can be unsuccessful when the insurer’s checks and warnings are persuasive.

In DRN-5753505, Haven cancelled after its telematics supplier suspected GPS blocking. The Ombudsman’s final decision upheld the complaint because Haven had not explored possible device or signal faults with the policyholder before cancelling. Haven was required to refund replacement insurance for the remaining period to 14 January 2025, refund receipted transport costs until replacement cover was bought (both with 8% interest), and pay £350 for distress and inconvenience (final decision). The decision followed an earlier provisional view, but the final outcome is the one to rely on. It does not mean every suspected jammer or connectivity gap makes a cancellation unfair.

Make the formal complaint specific

Use a short chronology. State what you dispute, what you accept, the evidence attached and the remedy sought. For example: “I dispute the 14 August event because the recorded coordinate appears to be on the parallel road. Please provide the event location, applied limit, checks completed and the policy term relied on. Please confirm whether cover remains active while this is reviewed.”

Ask for a correction or re-review rather than demanding a predetermined compensation figure. If cancellation was unfair, relevant remedies can include correcting the record, refunding charges, reimbursing evidenced additional insurance costs or compensation for distress. FOS says it considers evidence from the consumer, insurer and relevant third parties, including policy documents, calls, screenshots, contact notes and telematics data.

Complain to the insurer first. For most complaints, the firm has up to eight weeks to issue a final response. You can usually refer the complaint to FOS after an unsatisfactory final response, or once eight weeks have passed without one, normally within six months of the final response (FOS time limits).

If the reading is correct

A fair complaint is not a way to erase a real breach. Ask what improvement is possible, what future event would trigger cancellation and how warnings will arrive. If you cannot comply with the policy’s conditions, replacement insurance may be the safer practical route. Keep the complaint focused on the disputed event or process rather than claiming every telematics policy is unreliable.

A separate family feedback option

Oculamor can give a family a car-based journey record to review together, independent of the driver’s phone for collecting vehicle journeys. That may help discuss a route, speed-limit context or an unfamiliar trip. It does not verify an insurer’s data, pause cancellation, replace insurance or guarantee that its record will be accepted by an insurer. Keep the insurance dispute with the insurer and the complaint route; use a separate family tool for family feedback. The published Standard price checked on 6 September 2026 is £7.99 per month or £81.50 annually, plus a £30 device per vehicle. Check the cost page and checkout for the offer and terms that apply when you buy; see the dashboard preview before sign-up.