One of Waze's greatest strengths is its community reporting system. However, Waze is much better at creating and confirming reports than it is at efficiently removing stale reports when conditions change.

As a result, users often encounter reports that were once accurate but are no longer valid because police have moved on, traffic has cleared, roadworks have finished, hazards have been removed, or weather conditions have changed.

The goal of this suggestion is to make Waze reports more current, accurate, and self-correcting by allowing users to safely confirm not only that a report is still valid, but also that it is no longer valid.

Please add hands-free confirmation and removal of Waze reports.

When Waze announces a report ahead, users should be able to respond by voice with:

"Still there"

or

"Not there"

Waze should associate these commands with the most recent report the user has approached or passed, using GPS position and direction of travel.

To improve accuracy, Waze should create a speed-sensitive confirmation corridor around the report location rather than relying on a fixed distance.

For example:

• On urban roads, confirmations could be accepted within a few hundred metres before and after the report location.
• On freeways, confirmations could be accepted within a larger corridor reflecting higher travel speeds.

This would accommodate GPS inaccuracies, traffic lights, delayed reporting, rider and driver reaction times, and the fact that reports are often submitted slightly before or after the actual hazard location.

The same functionality should also be available through the touch interface so that voice and touch users contribute data in the same way.

This system should apply to all Waze report types, including police, crashes, traffic jams, stopped vehicles, roadworks, potholes, objects on the road, weather hazards, flooding, fog, ice, and other reported hazards.

Importantly, a single "Not there" response should not immediately remove a report. Users can make mistakes, press the wrong button, or miss a hazard.

However, recent negative confirmations should carry greater weight than older positive confirmations. For example, if a report has accumulated many confirmations over time, a small number of recent "Not there" responses should be sufficient to indicate that conditions have changed and the report is no longer valid.

This would allow reports to expire more accurately while remaining resistant to accidental taps, voice-recognition errors, or individual mistakes.

The result would be safer operation for motorcyclists, new drivers, truck drivers, Android Auto users, CarPlay users, and anyone who should not be interacting with a screen while moving.

Most importantly, it would improve the accuracy and freshness of Waze data by making it as easy to remove stale reports as it is to create and confirm them.