Local, Tribal, and Regional Safety Action Plans

Local, Tribal, and Regional Safety Action Plans

Translate safety priorities into local action

A local road safety plan provides a structured way for a community to identify problems, select strategies, assign responsibility, and measure progress. Tribal and regional plans serve similar purposes within their own governance and network contexts. The plan should fit available data and capacity while retaining a clear focus on reducing fatalities and serious injuries. A small jurisdiction does not need to reproduce a state's entire analytic apparatus to make defensible decisions.

Begin by defining the geography, road users, ownership, and agencies involved. A city may control local streets while a state agency controls the arterial through downtown. Transit access, school travel, freight routes, emergency response, and neighboring jurisdictions can affect the same safety problem. Invite those partners early. The FHWA local road safety resources help local agencies connect planning with implementation.

A plan's title does not establish grant eligibility. A Vision Zero plan, local road safety plan, or Tribal safety plan may meet a particular program's requirements, but the applicant must demonstrate the required contents and adoption status. Check the current notice of funding opportunity rather than assuming that any document mentioning safety qualifies.

Diagnose local and systemic needs

Use fatal and serious-injury history, other relevant crashes, roadway features, exposure where available, and input from road users and responders. Map locations and investigate patterns, while protecting privacy and recognizing imprecise geocoding. A high-injury network is a useful description of concentration, but no universal percentage of streets must contain a predetermined percentage of injuries.

Combine site-specific and systemic analysis. One intersection may have a repeated turning-conflict pattern suitable for focused diagnosis. Across a rural county, curves with certain risk features may warrant a consistent low-cost program even though severe crashes are dispersed. Both can appear in the same plan. Avoid allowing the absence of a recent recorded crash to prove that an accessible crossing or other proactive safety improvement has no purpose.

Gather community information in a way that includes users often missed by a standard public meeting: people with disabilities, children and caregivers, transit users, residents with language barriers, and rural or Tribal communities. Document how input changes the analysis or proposed strategies. Consultation should reveal travel needs and barriers, not merely collect endorsements after decisions are made.

Understand the current SS4A framework

The Safe Streets and Roads for All (SS4A) program supports comprehensive safety planning and implementation. Its authorization provided $5 billion over fiscal years 2022–2026; that historical authorization does not guarantee a later funding round. The current action-plan page, updated March 27, 2026, lists seven components:

The seven components are the current framework; do not reuse an older eight-component checklist as if it were unchanged. The eligibility worksheet and current NOFO govern detailed requirements. For example, state-level SHSPs are not themselves qualifying established SS4A action plans, even though local plans should coordinate with statewide priorities.

Eligible applicants include MPOs, political subdivisions, federally recognized Tribal governments, and qualifying multijurisdictional groups. State DOTs and other state-level agencies are not direct eligible applicants, though they may be partners. An applicant's legal status matters: a nonprofit or consultant does not become eligible simply because it provides safety expertise.

Build a deliverable implementation program

Turn strategies into a prioritized list of projects and activities. State the diagnosed need, evidence, responsible lead, partner roles, anticipated cost, funding path, schedule, and evaluation measure. Include near-term actions and longer-term capital changes where useful. A priority crossing can receive an interim operational improvement while a permanent project is designed, but evaluate interactions rather than counting both treatments' full benefits independently.

Policy actions may include routine safety review in resurfacing projects, maintenance of clear sight lines, speed-management procedures, or better data collection. Check authority and applicable standards before promising a change. A plan cannot authorize a camera where law prohibits it, nor replace required accessibility compliance with a favorable benefit-cost score.

For a small county, a practical program might combine a curve-risk inventory, a package of eligible signing and marking improvements, a prioritized roadside program, and an agreement for better crash geocoding. Assign each action to someone with the resources and authority to deliver it. “Seek funding” without a sponsor, eligibility check, or schedule leaves an implementation gap.

Keep the plan public and useful

Report both outcomes and implementation progress in accessible language. The current SS4A action-plan framework includes annual public reporting on progress toward reducing fatalities and serious injuries and posting the plan online. Use stable measures and explain data lags. An early report can honestly show completed actions and remaining barriers while long-term injury evidence is still developing.

Review priorities when land use, travel patterns, data, or treatment evidence change. Preserve the connection between the original safety diagnosis and each adjustment. A successful local plan is a continuing decision process with public accountability, rather than a one-time document prepared solely to satisfy an application checklist.