Reporting dangerous road conditions as a cyclist starts with choosing the right platform for your situation. You have several dedicated options: the Close Call Database for comprehensive incident tracking, WABA Crash Tracker if you’re in the Washington DC area, Fill That Hole for potholes and infrastructure damage, or newer apps like Pothol, Stan, and RateMyRoads that focus specifically on road hazards. For serious incidents captured on video, the Nextbase Dash Cam Safety Portal provides a centralized reporting mechanism.
Each platform serves a different purpose—some focus on near-misses and crashes, others on specific road damage like potholes—so understanding which tool matches your situation is the first step toward making your report count. The fragmentation of reporting platforms exists because cycling safety involves multiple stakeholder groups: advocacy organizations, municipal infrastructure teams, traffic safety agencies, and other cyclists. A pothole report might need to reach your city’s public works department, while a dangerous traffic pattern might be more useful to advocacy groups documenting systemic safety issues. This article will walk you through the major reporting platforms, what types of incidents each handles best, how to gather evidence, what limitations you’ll encounter, and what happens after you hit submit.
Table of Contents
- Understanding Which Reporting Platforms Work for Your Situation
- Deep Dive into Platform Features and Data Handling
- Why Reporting Matters—The Scale of Cycling Injury and Infrastructure Failure
- Gathering Evidence—When Documentation Matters
- Limitations and Challenges in the Reporting Ecosystem
- What Happens After You Submit—From Report to Action
- The Evolution of Reporting Tools and Future Infrastructure Advocacy
- Conclusion
Understanding Which Reporting Platforms Work for Your Situation
Different platforms collect different types of data, and your choice depends on what you witnessed. The Close Call Database is a global crowdsourced platform with concentrations in the US and UK that accepts reports of near-misses, crashes, and dangerous conditions from cyclists worldwide. The WABA Crash Tracker, operated by the Washington Area Bicyclist Association, accepts reports of bike lane obstructions, crashes, near-misses, and dangerous road conditions while keeping submissions confidential—you can choose whether to share your report with local officials and the Department of Transportation. The Nextbase Dash Cam Safety Portal serves cyclists who have helmet camera or dashcam footage of serious incidents, providing a single submission point rather than navigating individual police departments or news outlets.
For infrastructure-specific reporting, Fill That Hole from cycling UK has received over 200,000 pothole reports across 16 years and remains mobile-friendly without requiring an app download. The newer platforms—Pothol (founded 2025), Stan The App (which uses computer vision technology and partners with the RAC), and RateMyRoads (launched May 1, 2025)—focus specifically on road defects and hazardous conditions. However, these newer tools have smaller user bases and may not have the same integration with municipal repair systems that Fill That Hole has developed over its longer history. If you’re reporting in a region where one of these tools has strong municipal partnerships, your report carries more weight toward actual repairs.
Deep Dive into Platform Features and Data Handling
The major platforms differ significantly in how they handle your personal information and where your data flows. The WABA Crash Tracker explicitly offers confidentiality—your contact information is kept private, and you control whether the report reaches officials. In contrast, the Close Call Database operates as a public crowdsourced map where anyone can view reported incidents (though you can control what personal details appear in your submission). The Nextbase Dash Cam Safety Portal takes a different approach entirely, aggregating serious incidents into a database that can be provided to authorities and insurers when needed.
One critical limitation: newer apps like Pothol and RateMyRoads are still building relationships with municipal repair departments. Pothol explicitly markets itself as providing real-time data to cities for repair prioritization, but whether your local government has actually integrated their system remains a question worth checking before investing time in reports through that platform. Stan The App’s partnership with the RAC gives it credibility in the UK, but US cyclists might not see the same municipal integration. Cycling UK’s Fill That Hole bypasses this problem by having already processed hundreds of thousands of reports through local councils over 16 years, though its interface lacks the computer vision automation that Stan offers.
Why Reporting Matters—The Scale of Cycling Injury and Infrastructure Failure
The statistics underscore why reporting systems exist at all. In 2023, 1,166 bicyclists were killed in traffic crashes in the United States, and an estimated 49,489 were injured in similar crashes. That’s a baseline that doesn’t capture the full picture—the National Transportation Safety Board notes that collisions without motorized vehicles and non-fatal crashes are significantly underreported, and roughly one-third of bicycle injuries actually occur in off-road areas where traditional crash reporting doesn’t apply. What this means for reporting: when you submit a near-miss or road hazard report to the Close Call Database or WABA, you’re not just venting about inconvenience—you’re feeding a system that documents patterns authorities might otherwise miss. The infrastructure side compounds the problem.
The UK road repair backlog would require 12 years and £18.62 billion to fix all local roads in England and Wales as of 2026. This isn’t a UK-only crisis—similar backlogs exist across North America and Europe. Fill That Hole’s 200,000+ reports over 16 years represent a mechanism for citizens to pressure repair priorities upward. When protected bike lanes are installed, injury crashes drop by 40% for all road users in cities like New York, and exceed 50% in some locations. Reports about missing bike lane protection or degraded infrastructure don’t just help cyclists; they create the documentation that advocates use to justify infrastructure spending.
Gathering Evidence—When Documentation Matters
How thoroughly you document a road hazard determines how useful your report becomes. For serious incidents, dashcam or helmet camera footage is gold—this is why the Nextbase Dash Cam Safety Portal exists as a dedicated channel. If you don’t have video, photographs showing the specific pothole, debris, missing pavement, or damaged bike lane are the next tier of evidence. Include multiple angles if possible, the location (exact address or intersection), the date, and the time of day.
For near-misses or traffic pattern issues, written description of what happened, where, when, and any vehicle details (license plates, descriptions) matter. However, there’s a practical tradeoff: the more detailed your report, the longer it takes to submit. Most platforms offer quick reporting paths for time-sensitive issues (you can file a basic report in 30 seconds on many of these tools) and detailed reporting paths for comprehensive documentation. The platforms with computer vision like Stan The App do some of the documentation work for you—you point your phone at the pothole and the app analyzes it—but this only works if the tool covers your region. For most cyclists in most locations, the fastest reliable reporting method remains a quick text submission to Fill That Hole paired with a smartphone photo rather than waiting to gather comprehensive video evidence that might never materialize.
Limitations and Challenges in the Reporting Ecosystem
Even well-intentioned reporting faces significant friction. The biggest challenge is fragmentation: there’s no central registry that covers all regions with equal quality. A cyclist in London has excellent options through Cycling UK and the official highways reporting system; a cyclist in rural areas of North America might find the Close Call Database as their only meaningful option. This means that dangerous conditions in underserved regions often go unreported because there’s no obvious platform to use, and the platforms that do exist might not have municipal integration in that area.
Another limitation: underreporting persists despite these tools. Cyclists often don’t report because they don’t know where to report, distrust whether reporting will result in action, or simply never think to document an incident after moving on. The NTSB findings about underreporting suggest that even with dedicated platforms in place, actual incident documentation captures only a fraction of what happens on roads. Additionally, platforms like RateMyRoads and Pothol being brand-new means there’s minimal historical data to show whether reports lead to actual repairs. Some road hazards also fall into gray areas—is crumbling asphalt a city responsibility or the cyclist’s responsibility to avoid? Unclear jurisdiction slows repairs.
What Happens After You Submit—From Report to Action
Submitting a report doesn’t automatically trigger repairs or investigations. Fill That Hole routes pothole reports through local council systems, and approximately 60-70% of reported potholes get fixed within a few months in areas with active council engagement, though this varies widely by region. The WABA Crash Tracker aggregates submissions into public maps and safety reports that advocates use in policy conversations; individual reports sometimes trigger DOT reviews of particularly dangerous intersections. The Close Call Database exists primarily as a documentation tool—your report contributes to a global dataset showing where cyclists face danger, used by researchers and advocacy groups rather than directly triggering municipal action. The newest platforms make different promises.
Pothol says cities can access their live data dashboard, but whether your local city has chosen to integrate with Pothol is your responsibility to verify beforehand. Stan The App’s RAC partnership in the UK creates a clear path to action; US-based cyclists using Stan might find their reports less actionable unless their city has separately adopted Stan’s data. For serious incidents involving crashes, Nextbase reports can be shared with police and insurers, creating a different action pathway than infrastructure reporting. The practical reality: always cross-reference your report by contacting your city’s public works or transportation department directly after submitting through a platform. A report in a system is a start; a report that also reaches an actual human in the responsible department increases the likelihood of action.
The Evolution of Reporting Tools and Future Infrastructure Advocacy
Cycling incident and hazard reporting is evolving rapidly, particularly around automation and computer vision. Stan The App’s computer vision approach removes the need for cyclists to manually describe road damage; just point your phone and the system identifies the defect. Pothol’s 2025 launch and RateMyRoads’ May 2025 debut suggest growing momentum in specialized road-condition apps. However, this expansion also creates a fragmentation problem—cyclists now face more platforms, not fewer, making it harder to know where to report in any given area.
The long-term trend suggests consolidation may come through municipal adoption rather than app-level standardization. If cities begin accepting reports through a small set of dominant platforms (similar to how 311 systems work for general complaints), reporting friction will decrease. Until then, the Close Call Database remains a reliable global option, Fill That Hole dominates in the UK, and regional platforms like WABA serve specific areas well. The emergence of computer vision-based tools suggests that future reporting may require minimal effort from cyclists—a quick photo that algorithms parse for you—making comprehensive incident documentation the default rather than a special effort.
Conclusion
Reporting dangerous road conditions as a cyclist means identifying which platform serves your immediate need: the Close Call Database for global incident tracking, WABA Crash Tracker for regional near-miss patterns, Fill That Hole for pothole-specific reports with municipal integration, or newer tools like Pothol and RateMyRoads if you want computer vision-assisted reporting. Each platform contributes to a larger ecosystem where individual cyclist reports accumulate into safety data that can justify infrastructure spending, inform advocacy campaigns, and document patterns of danger that might otherwise remain invisible. The immediate next step is straightforward: document what you observed (photo, dashcam footage, or careful description), choose the platform most relevant to your situation and location, and submit your report.
Then, if the issue is serious enough, follow up with your local public works or transportation department directly—the report you file is most powerful when it reaches both the advocacy databases and the actual decision-makers responsible for repairs. Over time, as municipal systems integrate with platforms like Pothol and as computer vision tools like Stan become standard, reporting may require less effort from cyclists. For now, the most effective cycling safety advocates are those who document and report the conditions they encounter.
