The map tells the story your footage can't
Last autumn, a Lyft driver in Manchester sent us a message. She'd been in a minor collision at a busy roundabout, recorded the whole thing on Hawk, but when she tried to explain the sequence of events to her insurance company, they asked the question that stopped her cold: 'What was your exact position when the other car cut in?' She had the video. She had the timestamp. She didn't have a way to show, clearly and without argument, where both vehicles were at the moment of impact.
The dashcam paradox: footage without context
Here's something nobody tells you about dashcam evidence. The clip is only half the story. You've got the camera angle, the timestamp, maybe the speed overlay. But a lawyer, an insurance adjuster, or a magistrate watching your footage doesn't know the geography. They don't know if you were on a dual carriageway or a residential street. They can't see the road layout, the lane positions, or how the vehicles moved relative to the road itself.
We realised this during the first month of Hawk's launch. Support emails came in from people who had recorded perfectly good evidence but struggled to contextualise it. One person had a clip of a parking-lot scrape. Another had recorded a near-miss on the motorway. Both had solid video. Both found themselves explaining the scene verbally, which meant the person reviewing the evidence had to trust their interpretation rather than seeing it themselves.
That gap between what the camera sees and what the evidence needs to prove became impossible to ignore.
Drawing the line: how map replay works
We started with a simple question: what if we overlaid the clip's GPS data onto an actual map? Not as a data visualisation. As part of the evidence package itself.
Hawk's trip map replay takes the GPS coordinates from your clip and draws your exact route as a polyline on a real MapKit map. You can scrub through the video and watch your position update on the map in real time. Speed overlay, timestamp, direction of travel. All of it tied to the geography.
The first version was bare bones. Just the line. Just the position. But when we started getting feedback from rideshare drivers, we heard the same thing again and again: the ability to show where they were was the difference between a straightforward claim and a disputed one. One driver told us the map replay meant she didn't have to argue about whether she'd been in the correct lane. The evidence showed it. The insurance company approved the claim in three days instead of three weeks.
Evidence that stands up
What makes Hawk's approach different is that the map replay isn't some separate feature bolted onto the side. It's part of the evidence locker. Every clip is hashed with SHA-256 integrity, which means the GPS data can't be tampered with after the fact. When you export a clip for a dispute, the map data comes with it. The manifest includes the hash. Everything is defensible.
This matters more than you'd think in a courtroom or an insurance office. Someone reviewing your evidence wants to know that the data is genuine, that it hasn't been edited or cherry-picked. A video clip alone leaves room for questions. A video clip with cryptographically verified GPS coordinates and a clear map overlay leaves almost none.
We've had clips submitted to police forces via the NDSP reporting system, sent to insurance companies as part of dispute exports, and used in small-claims court. The pattern is always the same. The clearer you can make the geography, the faster the claim resolves. Ambiguity costs time and money. Clarity wins.
The moment map replay became essential
The real turning point came when we started using the feature ourselves. Our team drives. We commute. One of our developers was involved in a low-speed bump at traffic lights. Nothing serious, minor damage. But the other driver claimed he'd been in a different lane than he actually was, which changed the entire liability picture.
He opened Hawk, pulled up the clip, and hit the map replay button. Watched his position relative to the lane markings play out on the map, watched the other car's approach from the camera angle, watched the timestamp tick through. He downloaded the evidence export, sent the ZIP file to his insurance company, and they closed the file within a week. No argument. The geography was undeniable.
That's when we stopped thinking of trip map replay as a nice-to-have feature and started treating it as foundational. We weren't just building a dashcam. We were building a way for people to prove the truth of what happened, not with words, but with data and geography combined.
Why this changes how you think about evidence
Most dashcam apps show you video. Hawk shows you video plus the story of where you were when it happened. That distinction is small in description but enormous in practice.
When you're exporting a clip for a dispute, the map replay is your translator. It takes your camera's perspective and grounds it in the real world. Anyone looking at the evidence can see instantly what the geometry of the situation was. Not the version you're describing. Not the version the other person is describing. The actual layout, speed, position, timestamp. All verifiable.
It's particularly powerful for rideshare drivers, where passengers sometimes dispute the route or claim the driver was speeding. The map replay doesn't just show where you went. It shows where you went on the actual streets, and the timestamp and speed overlay prove the time and velocity. It's hard to argue with geography.
The best evidence is the kind that speaks for itself without needing an interpreter. Does your dashcam app show you where you were when it happened, or just what the camera saw?