The Safe Streets and Roads for All (SS4A) program has distributed billions in federal funding since 2022, helping communities across the country develop safety action plans and implement life-saving infrastructure projects. Competition is fierce—thousands of applicants compete for each round of funding.
Having reviewed what makes successful applications stand out, we’ve distilled the process into 7 data-driven strategies that strengthen your SS4A grant application. Whether you’re applying for an Action Plan Grant or an Implementation Grant, these tips will help you build a more compelling case.
SS4A by the Numbers
Explore the SS4A Award Map to see which communities have received funding and how awards are distributed geographically.
7 Tips for a Stronger SS4A Application
Lead with Crash Data, Not Anecdotes
USDOT reviewers evaluate applications based on demonstrated safety need. Quantify your problem: How many fatalities and serious injuries occurred in the past 5 years? What’s the trend? Where are crashes concentrated?
Strong applications include specific numbers: “Our jurisdiction experienced 47 traffic fatalities and 312 serious injuries between 2019 and 2023, a 23% increase over the prior 5-year period.” Weak applications say “traffic safety is a growing concern.”
Build a High-Injury Network (HIN) to identify the corridors with the highest crash concentrations. This demonstrates analytical sophistication and shows reviewers you understand where the problems are.
Show a Clear Methodology
Don’t just present crash totals—explain how you analyzed the data. Reference established methodologies like the Highway Safety Manual (HSM), network screening, or the FHWA Systemic Safety approach. Reviewers want to see that your analysis follows recognized best practices, not ad hoc spreadsheet work.
Key methodologies to reference:
- Network screening — Systematic identification of high-risk locations using performance measures
- EPDO weighting — Severity-adjusted crash scoring that prioritizes fatal and serious-injury locations
- Crash typing — Analysis of crash patterns (rear-end, angle, pedestrian, etc.) to inform countermeasure selection
- Expected crash frequency — Statistical methods that account for regression to the mean
Address All Seven Required Elements
SS4A Safety Action Plans must address seven specific elements defined by USDOT. Missing even one weakens your application significantly:
- Leadership commitment and goal setting — Adopt a goal of zero roadway fatalities and serious injuries
- Planning structure — Describe governance, stakeholder engagement, and plan development process
- Safety analysis — Comprehensive analysis of crashes, risk factors, and contributing circumstances
- Equity considerations — Analyze how safety problems affect underserved communities
- Strategy and project identification — Connect analysis findings to specific countermeasures and projects
- Progress and transparency — Define metrics, monitoring plans, and public reporting commitments
- Supplemental planning — Integration with other local plans (comprehensive, transportation, climate)
Embed Equity Throughout
Equity is not a checkbox—it’s a lens through which your entire application should be evaluated. USDOT scores equity-focused applications higher. Go beyond demographics:
- Overlay crash data with census tract data on income, race, age, and disability status
- Identify whether high-injury corridors disproportionately affect communities of color or low-income areas
- Analyze access to transit, sidewalks, and safe pedestrian infrastructure in underserved areas
- Describe how your stakeholder engagement reaches historically excluded communities
- Show how proposed projects prioritize areas with both high crash rates and high social vulnerability
Connect Data to Countermeasures
The strongest applications create a clear chain from data → analysis → countermeasures → expected outcomes. Don’t just list safety projects you want to build—show how your crash analysis led you to select them.
For example: “Network screening identified Corridor X as having 3x the expected crash frequency for similar roadways. Crash typing revealed 68% of crashes are rear-end collisions at unsignalized intersections. Based on CMF Clearinghouse data, we propose roundabout conversions at the three highest-risk intersections, with an expected 35–40% reduction in total crashes.”
This evidence-based chain is exactly what reviewers look for.
Demonstrate Readiness and Capacity
USDOT wants to fund projects that will actually get completed. Strengthen your application by showing:
- Organizational capacity — Describe your team’s experience with similar projects and safety analysis tools
- Stakeholder buy-in — Include letters of support from elected officials, community organizations, and partner agencies
- Matching funds — While not always required, local match demonstrates commitment
- Timeline feasibility — Present a realistic project schedule with clear milestones
- Prior SS4A work — If you received a previous Action Plan Grant, show progress on that plan
Use Visualizations That Tell a Story
Reviewers read hundreds of applications. Make yours memorable with clear, compelling visuals:
- High-Injury Network maps showing crash density on your road network
- Trend charts showing crash frequency and severity over time
- Heat maps highlighting crash clusters at key intersections
- Equity overlays showing the relationship between crash concentrations and vulnerable communities
- Before/after comparisons for implementation grants, showing expected safety improvements
Interactive dashboards that reviewers can explore independently add extra credibility. A public-facing crash data dashboard signals transparency and technical capability.
Common Mistakes to Avoid
- Vague safety descriptions — “We have a safety problem” is not compelling. Quantify everything with specific data.
- Disconnected countermeasures — Proposing bike lanes where the main problem is rear-end crashes at intersections shows a gap between analysis and action.
- Ignoring vulnerable road users — Pedestrian and cyclist safety is a top SS4A priority. Even if your jurisdiction is car-centric, address VRU safety explicitly.
- Boilerplate equity language — Generic statements about “serving all communities” without data-backed analysis won’t earn equity points.
- Missing the deadline — SS4A NOFOs have firm deadlines. Start your data analysis early—gathering and cleaning crash data takes longer than most teams expect.
Timeline: Planning Your SS4A Application
4 Months Before Deadline
Gather crash data from your state DOT. Begin data cleaning, geocoding, and validation. Identify your analysis team and tools.
3 Months Before
Run crash analysis: build your High-Injury Network, conduct network screening, identify top crash corridors and intersections. Begin equity analysis overlays.
2 Months Before
Select countermeasures based on crash patterns. Develop visualizations, maps, and supporting graphics. Begin stakeholder engagement and gather letters of support.
1 Month Before
Write the narrative. Integrate data, visualizations, and countermeasure recommendations into the application format. Internal review and revision.
Final 2 Weeks
Executive review, final edits, budget verification, and submission.
Strengthen Your Next SS4A Application
Roadway Insights provides the crash analysis, network screening, and visualization tools that make SS4A applications data-rich and compelling—in days, not months.
Schedule a Demo