Bicycle and Pedestrian Exposure Data: Why Crash Counts Alone Mislead Policymakers

The policy question behind the street scene

A person arriving at a crossing or a station does not experience a capital program. They experience bicycle and pedestrian safety data: whether the route is understandable, whether the movement is protected, and whether the agency has made the decision before a complaint turns into a crisis. NHTSA states that exposure and contextual data are crucial because high crash figures can reflect high activity, while low figures can reflect actual or perceived danger that suppresses use. [1] The practical policy task is to turn that observation into a repeatable rule that designers, operations staff, and the public can inspect.

Start with a policy outcome, not a device list

Bicycle and Pedestrian Exposure Data: Why Crash Counts Alone Mislead Policymakers is best framed as a service standard. The desired outcome is a route that a person can use predictably without being asked to negotiate an avoidable conflict. That framing prevents a program from becoming a catalog of treatments applied because they are familiar. It also makes the program easier to explain: the agency is matching a response to a documented condition, then checking whether the response works. Federal guidance consistently places walking and bicycling within transportation planning and project development rather than outside the normal program. [2]

Build a screening record that can survive turnover

Every candidate location should receive the same short record. Record crash reports, activity counts, route choice, speed, land use, lighting, roadway design, and reporting limitations. Include photographs, a simple sketch, the date and time of observation, and the name of the staff member who reviewed it. Keep the data definitions stable from one corridor to the next. A record is not a warrant by itself; it is the agency’s evidence trail for deciding which sites need a more detailed engineering review. The record should also show what the agency does not know, because uncertainty is a reason to collect more information, not a reason to hide the decision.

A policy scorecard with room for judgment

The table is deliberately not an automatic ranking formula. It makes the basis for discretion visible. FHWA’s connectivity guidance describes measures as tools for identifying high-priority gaps, considering cost-effective solutions, and measuring long-term impacts of pedestrian and bicycle investments. [2] Agencies can use a score to sort work while retaining a documented exception path for urgent safety conditions, accessibility barriers, or coordinated utility and paving work.

Choose a response proportional to the condition

Once a site clears screening, the agency should compare options against the problem rather than select the most visible intervention. Crash counts remain important, but policy should pair them with exposure and context rather than treating a raw count as a complete measure of risk. [1] A concise alternatives memo can state the conflict to be addressed, the applicable control guidance, the alternatives considered, the expected operations and maintenance burden, and the reason for the preferred option. This is where legal, transit, emergency-response, maintenance, and accessibility staff can identify constraints before plans harden.

Make implementation an operating commitment

A policy is scalable only when it assigns work after adoption. Operations staff need timing or control responsibilities; planners need a map and pipeline; designers need cross-section and accessibility checks; maintenance teams need inventories; and communications staff need plain-language materials. The MUTCD is the national standard for traffic control devices, and FHWA’s current MUTCD page identifies the current edition and related resources. [3] Local policy should therefore direct staff to confirm current requirements during design rather than freezing a citation to a past edition.

Measure what the public can feel

Good follow-up includes data completeness, exposure coverage, severe outcomes, equity checks, and whether decisions change when denominators are used. Numbers should be paired with field observation. A new control can be technically installed while its approach, signs, snow clearance, curb ramps, or wayfinding still make the trip difficult. Publish a simple dashboard or annual memorandum that reports completed projects, projects in design, deferred sites, reasons for deferral, and the next review date. That practice lets residents see that a “no” is not disappearance from the program; it is a documented decision that can be revisited when conditions change.

Use equity and access as review questions

Equity is not satisfied by adding a demographic column after priorities are set. Ask whose destination access improves, whose route is interrupted, who relies on mobility devices, and whether the program collects reports in more than one format. U.S. DOT describes pedestrians and bicyclists broadly to include people walking, biking, using wheelchairs and mobility devices, taking transit, and using micromobility. [3] That broad view is useful because a policy can succeed for a confident adult traveler while failing for a child, an older adult, or a person pushing a stroller.

Turn the next cycle into a learning loop

The final policy section should specify a review cadence. Revisit assumptions after seasonal operations, construction, and observed use; compare the outcome with the screening record; then revise the standard if the evidence shows a recurring mismatch. Preserve the original decision and the revision in the public record. A disciplined loop—screen, design, deliver, review—keeps bicycle and pedestrian safety data from becoming a one-off promise and makes future budgets easier to defend. It also creates a practical bridge between high-level federal guidance and the local decisions residents encounter every day.

Implementation teams should state the responsible owner, the decision date, the data source, and the condition that would trigger reconsideration. This small discipline improves coordination, protects institutional memory, and gives the public a concrete way to follow progress.

• [1] https://www.nhtsa.gov/book/countermeasures-that-work/bicycle-safety/data-surveillance
• [2] https://rosap.ntl.bts.gov/view/dot/79217
• [3] https://rosap.ntl.bts.gov/view/dot/62355