USDOT Safe Streets and Roads for All Grants

This opportunity is often summarized as a single sentence: competitive federal money to reduce roadway deaths and serious injuries for all road users through local action plans and on-the-ground safety investments. That sentence is accurate, but it hides the real work required to submit a strong application. This rewrite explains how this specific opportunity actually works today, who should apply, what a realistic application package looks like, and how to decide quickly whether the timing and scope fit your team.

The FY26 program is still listed as open on DOT’s official site during this cycle. The funding package is identified as DOT-SS4A-FY26-01 (Grants.gov). The posted close date is May 26, 2026 at 5:00 PM Eastern. The deadline and submission channel are strict: applications go through the DOT-managed Valid Eval system, not a standard Grants.gov form submission. If you are choosing between many road-safety opportunities, SS4A is usually the one you use when you need a federal program that explicitly ties funding to a comprehensive safety strategy and crash outcome goals.

At a glance

What this grant is designed for

SS4A is a data-informed safety improvement program for local, regional, and Tribal jurisdictions. The core concept is that money should go to plans and projects that address fatal and serious-injury crashes in a coordinated way instead of one-off fixes. The program requires that you start from a safety problem analysis, then align project activity, policy, and implementation sequencing with a comprehensive plan.

DOT frames SS4A around the Safe System Approach. That means your proposal should explain not only physical safety fixes, but how your package reduces crash risk through design, speed, enforcement, user behavior support, and post-crash response. Applications with a narrow lane-closure plan that does not connect to a broader system change are usually weaker than proposals that show how activities reduce risk in specific crash clusters.

In practical terms, the program tends to work best for jurisdictions that can answer four questions clearly:

• Where are the safety failures concentrated, and how do we know?
• What mix of interventions can reduce harm for all users, not just one mode?
• Which government unit will own maintenance, procurement, and implementation?
• What timeline and cost realism can we support from funding start to closeout?

Who should apply (and who should not)

This is a good fit if all of the following are true:

• You are a public applicant in a road-network jurisdiction: MPO, local public body, or eligible Tribal government.
• You already have crash data capacity or can partner with someone who does.
• You are ready to maintain a safety strategy over multiple years (24 to 60 months max, depending on award scope).
• You can provide a match and do not rely on ineligible pre-award costs.

This is usually not the right fit if:

• You are a private nonprofit with no legal status as a state-law unit or equivalent public safety planning responsibility.
• You are a state DOT trying to apply directly as the applicant.
• You intend to submit both an SS4A planning grant and SS4A implementation grant in the same cycle.
• You cannot define outcomes beyond “activity count” (for example, “paint lines and install signs”) without tying to crash burden reduction.

Because SS4A only allows one application per funding opportunity, applicant strategy matters: if you have both a planning need and an implementation-ready set of projects, you must choose one route and stay within it.

What you get from this opportunity

At a practical level, SS4A can fund a mix of actions but only through one of two structured tracks.

1) Planning and Demonstration Grants

These grants are typically for:

• Building a new comprehensive safety action plan.
• Updating or strengthening an existing plan to include current risk patterns.
• Running pilots or demonstration activities to test ideas before scaling.

A common misconception is that “planning grants” are low-value and should be skipped. In this program they are not. SS4A reserves a minimum of 30% of total funding for plan development and related activities. If your jurisdiction has never had a robust safety framework tied to crash data, this pathway is usually the best first step.

2) Implementation Grants

These require a qualifying Action Plan already in place (or in the required process window) and support implementation of identified roadway safety projects and strategies. Typical categories include:

• Infrastructure (for example, crosswalk upgrades, lane reconfiguration, speed reduction design, safe intersections, protected intersections, transit facility safety upgrades).
• Operational changes and behavioral measures tied to crash patterns.
• Project-level planning/design where tied directly to funded projects.

The key constraint: implementation activities must align with an adopted and qualifying Action Plan.

Applicant eligibility in plain language

Eligibility starts at two levels:

1. You can be selected as an applicant type.
2. Your proposal structure must match the selected grant track.

From DOT’s published criteria, eligible applicant types are:

• Metropolitan Planning Organizations.
• Political subdivisions of a State or territory (created under state law: cities, towns, counties, special districts, some transit agencies, etc.).
• Federally recognized Tribal governments.
• A multijurisdictional consortium of the above.

If you are applying as a public safety agency, transit authority, school district, university, or other public body, check whether your entity qualifies under state law as a qualifying unit or as a partner of one.

The NOFO’s stricter rule set includes timing and scope conditions:

• Plan-focused activity must generally be whole-jurisdiction, not only tiny fragments.
• If you are requesting demonstration activities only, you still need a qualifying Action Plan unless a specific exception applies.
• For implementation, you must show ownership, safety responsibility, or formal agreement with the agency that owns/maintains the roadways.
• States are not direct applicants.

Because DOT wants one lead applicant per political subdivision/jurisdiction, multiple internal offices should coordinate so you do not file competing submissions.

Eligibility traps to check before applying

• Corridor-only planning: If you call something an Action Plan but it is truly only one road segment, the application will likely be weak or non-qualifying.
• Wrong applicant type: Consulting firms and private-sector entities may support, but cannot be the lead applicant.
• Missing match evidence: Applicants sometimes assume pre-existing local budget lines automatically satisfy match. In SS4A, match is budget-based and must be demonstrated as eligible non-federal cost share at the time you justify totals.

Funding, match, and budget realism

SS4A’s standard federal/non-federal split is a maximum 80% federal share. In practical terms, your total eligible project cost includes both sources, and the non-federal side is typically 20% minimum.

DOT publishes this clearly as part of funding rules, and it is not a “bonus” multiplier. Putting in extra match does not improve your score by itself, and it can create extra reporting complexity if you do not have a reliable accounting process.

Match nuances to confirm now

• Match can be cash and in-kind.
• Ineligible match examples include most staff attendance costs, general administration, food/social events, and fundraising activity.
• Costs incurred before grant obligation are usually not eligible for reimbursement unless DOT expressly authorizes in specific circumstances.
• Tribal applicants and insular area applicants may have special treatment in limited scenarios; do not assume it applies broadly.

In plain language: if your team is building the budget from a rough estimate, build a separate match ledger with explicit cost lines and keep evidence ready for audit review.

How to decide which SS4A route is right for you

Use this quick screening test:

• Do you already have a qualifying Action Plan that is current and complete?
  • Yes: choose Implementation unless your plan is still too weak to support award-level project scope.
  • No: choose Planning and Demonstration first.
• Is your jurisdiction’s crash priority map already approved and shared across departments (public works, policing, EMS, planning)?
  • No: strengthen this before applying.
• Are your expected projects mostly pilots that de-risk a future expansion?
  • Yes: planning/demo can be a better lead.

DOT also requires one route in a given opportunity, so do not dilute effort across both.

Application process, step by step

1) Build your internal package

Before touching Valid Eval, line up:

• A lead applicant officer and alternate.
• Active UEI and updated SAM profile.
• Evidence of jurisdiction geography and road stewardship.
• A data brief: fatalities, serious injuries, high-injury network list, and underserved community context.

2) Download official instructions and forms

Use DOT’s SS4A “How to Apply” page first, then follow the relevant tracks:

• Planning and Demonstration: use the planning/demo forms/template set.
• Implementation: use implementation-specific forms and budget sheets.

Both routes require SF-424, and the grant type determines whether SF-424A/B or SF-424C/D is required. All applicants also need SF-LLL.

3) Choose the correct portal URL

DOT’s FY26 package provides explicit Valid Eval links for each grant type:

• /usdot_ss4a_2026_planning_demo/signup
• /usdot_ss4a_2026_implementation/signup

Using the wrong one is a common process error and can delay or invalidate submission.

4) Build the required technical packet

At minimum, your package should include:

• Completed standard forms.
• The required narrative.
• A map in PDF and spatial format.
• A budget table that shows federal request, non-federal match, total project cost, and other federal funds if used.
• Required letters/coordination if overlapping jurisdictions with existing SS4A activity are identified.

5) Meet the page and formatting rules

For a compliant submission, the narrative should be a PDF with readable formatting and required font/page margins. SS4A applies specific page limits by track and funding request size; verify current track instructions again before final upload, because instructions can vary by version.

Required materials checklist (by track)

Planning and Demonstration

• Lead applicant and contact details.
• UEI and SAM confirmation.
• Narrative aligned to Safety Context criteria (and concise enough for requested page limit).
• Action Plan description or existing plan update summary.
• Demonstration or supplemental planning description as applicable.
• Two-route map requirement:
  • PDF map.
  • Spatial map (Shapefile or KML).
• Budget table and proof of coordination with neighboring overlapping jurisdictions where applicable.

Implementation

• Lead applicant details and governance responsibilities.
• Action Plan evidence (new, updated, or in-progress under allowed conditions).
• Narrative responding to implementation merit criteria.
• Project-level planning/design/development budget lines, if included.
• Match and full spending breakdown.
• Same map and spatial deliverable requirements.

Application timeline

Typical planning sequence:

1. Weeks before launch: finalize data scope, map, and internal approvals.
2. 60–90 days before deadline: draft narrative and budget; request technical clarification if needed.
3. Pre-application window: if your request depends on pre-application Action Plan review, submit by the published technical deadline (April 24, 2026 at 5:00 PM EDT in this cycle).
4. Submission day: submit through Valid Eval well before 5:00 PM EDT on May 26, 2026.
5. After submission: you should not expect edits once submitted, and late technical rescue is only for Valid Eval platform failures under very narrow conditions.

Because SS4A is competitive and review-ready, don’t wait for the final day.

What DOT looks for during review

DDedicated technical quality and fit to criteria matter most. In high-level terms, reviewers assess:

• Safety context and clarity.
• Demonstrated safety impact and need.
• Underserved community benefit.
• Project readiness for implementation and procurement realities.
• For implementation: whether proposed actions can be executed with realistic management, permitting, and cost assumptions.

A few practical scoring implications:

• Vague narrative language without measurable baselines is a frequent weakness.
• Good applications always connect each requested project to a specific crash problem.
• Overlap/conflict management matters: if a neighboring SS4A jurisdiction is working a nearby corridor, explain coordination.
• If your submission lacks evidence of implementation readiness, high-level ideas become weaker than smaller, well-justified projects.

Common mistakes (and how to avoid them)

1. Submitting both grant types.

   • Not allowed. Choose one.

2. **Applying with a plan that is too narrow.

   • Action Plan logic should be geography-wide for the applicant jurisdiction and all relevant modes.

3. Treating pre-award costs as match.

   • This is one of the highest-risk errors. Unless explicitly authorized, pre-obligation costs are not eligible.

4. Underestimating procurement lead time.

   • If your activities require design, permitting, or right-of-way steps, include those timing constraints in narrative and budget sequencing.

5. **Ignoring coordination requirement.

   • If adjacent/overlapping recipients are active, include proof of communication to avoid duplication concerns.

6. Using vague outcomes language.

   • “Improve safety” is not enough. Say how: fatality and serious-injury trend reduction, high-injury network interventions, crash type reduction, and expected implementation outcomes.

7. **Not using whole-dollar budgets.

   • SS4A budget tables are expected in whole numbers.

8. Confusing SS4A scope with routine maintenance.

   • Maintenance-only work is generally ineligible unless directly tied to safety-related activity.

If you are unsure it is worth your time

Use this quick value test before you invest a full application cycle:

• Can you explain your most dangerous locations with data?
• Can you show how each budget line directly supports a qualifying action plan component?
• Can your council/commission adopt a clear implementation plan with match sources confirmed?
• Can you meet the May 26, 2026 submission timeline with clean documentation?

If you can answer “yes” with evidence, this is usually worth pursuing. If the answers are uncertain, build a pre-application work package first (data, match, governance, and scope narrowing), then apply next round if needed.

Next-step blueprint for teams

If you are ready to apply

1. Create a 10-page internal draft package with:
   • one-page problem statement,
   • two-page corridor/network analysis,
   • two-line implementation sequencing,
   • one-page budget with explicit match.
2. Assign reviewers from public works, police/fire/EMS, and finance.
3. Confirm SF form version and submission portal.
4. Convert narrative and attachments to approved PDF specs.
5. Submit early and keep a timestamped screenshot of the confirmation page.

If you are not ready

1. Submit a data improvement plan first.
2. Build the Action Plan baseline and map layer architecture.
3. Secure written coordination with adjacent entities and service agencies.
4. Re-enter next cycle with stronger readiness evidence.

Frequently asked questions

Can private nonprofits apply?

No, unless they are explicitly eligible under state-law and public responsibility conditions matching state political subdivisions. In most cases they are not lead applicants.

Can we apply if we do not have a fully developed Action Plan?

Yes, through the planning and demonstration route. Implementation generally requires stronger existing plan qualification unless you are in specific transition scenarios.

Is there a hard minimum match?

In this cycle, federal share is capped at 80%; local non-federal resources are generally expected to cover at least 20% of total eligible cost.

Can I apply on Grants.gov directly?

The opportunity posting is on Grants.gov, but SS4A applications for this round are submitted through Valid Eval.

Can we get a waiver?

Match waivers are limited. Some tribal and insular area conditions are treated separately, so consult official terms for your status.

Can applicants reuse an old road plan?

Only if it satisfies eligibility elements and timing requirements and is not disqualified by the NOFO’s action-plan rules.

Useful official links

• Program overview and notices: Safe Streets and Roads for All (SS4A) Grant Program
• Current NOFO: FY26 SS4A Notice of Funding Opportunity
• How to apply: How to Apply for the SS4A Opportunity
• Eligibility details: Eligible Applicants
• Action Plans: Comprehensive Safety Action Plans
• Matching guide: Matching Funds for SS4A
• Grants.gov listing: SS4A on Grants.gov

What to carry forward into your internal checklist

Before this round closes, make sure your internal file contains:

• Verified applicant type and single lead applicant confirmation.
• UEI registered and active in SAM.
• Clear determination of planning vs implementation.
• Current Action Plan status and jurisdictional scope.
• Map files in both required formats.
• Budget with clear federal/non-federal split and no pre-award-only costs.
• Matching source documentation and timeline assumptions.
• Signed coordination evidence where overlapping jurisdictions exist.
• Draft narrative that answers the merit criteria directly.

The goal of this page is not just to help you “pass the form,” but to help your team submit something that can actually be funded and then implemented. SS4A is still one of the strongest federal tools for locally led safety transformation when the package is built around evidence, realism, and execution readiness.