Safety Funding and Formal Studies (HSIP, SS4A, RSA)

Where the money behind safety scopes comes from, and the formal study type (RSA) that both programs love to fund. The through-line: every one of these is data-driven by rule, so the crash summaries, rates, and B/C work in this folder are not report filler — they are the eligibility case.

HSIP — the core federal safety program

FHWA HSIP program page · 23 U.S.C. 148, regulated under 23 CFR 924.

• A core Federal-aid program whose purpose is a significant reduction in fatalities and serious injuries (K+A — see KABCO Injury Scale) on all public roads, including local and off-system roads, not just the state highway system.
• Funds infrastructure safety projects. To be eligible, a project must be consistent with the state’s Strategic Highway Safety Plan (SHSP) and correct or improve a hazardous location/feature or address a highway safety problem — demonstrated with data.
• “Data-driven, strategic approach” is the program’s own language: sites are identified through network screening (crash frequency/severity/rates/EB — Crash Rate Calculation, Highway Safety Manual (HSM)) and treatments are justified with expected crash reductions.
• In Florida, FDOT administers HSIP and selects projects through its safety program processes tied to the Florida SHSP #status/verify current FDOT district HSIP intake process.

Practical consequence for the EIT: when a scope says “HSIP-eligible,” your crash analysis is being written to satisfy 23 CFR 924’s documentation logic — pattern, countermeasure, expected benefit.

SS4A — grants to locals, not states

USDOT SS4A program page · Bipartisan Infrastructure Law program, $5B appropriated over FY2022–2026.

Two grant types:

1. Planning and Demonstration Grants — develop, complete, or update a comprehensive safety Action Plan (Vision Zero plans generally qualify), do supplemental safety planning, or run quick-build demonstration projects that inform the plan.
2. Implementation Grants — build the projects and strategies identified in an existing, eligible Action Plan. No qualifying plan, no implementation money.

Eligible applicants are MPOs, political subdivisions (cities, towns, counties), federally recognized Tribes, and multijurisdictional groups — states are not eligible applicants, which is why this program shows up in local-agency scopes.

Why local Vision Zero plans matter to consultants: the Action Plan is the gate. A city with an adopted plan and HIN (Vision Zero and the HIN (Tampa Bay)) can chase implementation dollars, so scopes and RFPs quote the plan’s language, and study recommendations that cite the adopted HIN and plan strategies are simultaneously building the client’s next grant application. Cycle amounts, set-asides, and NOFO deadlines change every round — check the program page before quoting any figure or date to a client #status/verify.

Road Safety Audit — the eight steps

An RSA is a formal safety performance examination of an existing or future road by an independent, multidisciplinary team — proactive (it doesn’t wait for a crash history) and usable at any project stage from planning to in-service. It’s also an FHWA Proven Safety Countermeasure. FHWA’s process (RSA eight steps):

1. Identify the project or in-service road to be audited
2. Select the RSA team (independent, multidisciplinary)
3. Conduct a pre-audit meeting to review project information
4. Perform field observations under various conditions (day and night)
5. Conduct the audit analysis and prepare a report of findings
6. Present findings to the project owner / design team
7. Project owner / design team prepares a formal written response
8. Incorporate findings into the project when appropriate

The formal response (step 7) is what separates an RSA from a drive-through with opinions — every finding gets an answer on the record.

The EIT’s role on an audit team

You won’t lead one, but you make it run:

• Pre-audit data package (step 3): crash pull and summary per How to Pull Crashes from Signal Four Analytics and How to Summarize 5-Year Crash Data, AADT/speed data, as-builts, prior studies.
• Field observation support (step 4): photo log, measurements, and structured notes on the day and night reviews — bring the prompt lists from FHWA’s RSA guidelines.
• Findings report drafting (step 5): pattern → risk → suggestion format, with the team’s senior members owning the judgments.
• Response tracking (steps 7–8): a comment-response matrix — same pattern as Comment-Response Matrix Pattern.
• Independence rule: you cannot audit a design your firm produced — flag the conflict before the kickoff, not after.

B/C — the thread that ties funding to analysis

HSIP project selection and SS4A implementation applications both lean on benefit-cost: expected crash reduction (CMFs applied to the documented pattern) × per-severity crash costs vs project cost. That whole chain — pattern integrity, CMF quality, severity weighting — lives in Countermeasure Selection and CMFs and KABCO Injury Scale. A grant application inherits every weakness in the crash analysis under it.

Tip

Recommendations drawn from FHWA’s Proven Safety Countermeasures list (linked in Countermeasure Selection and CMFs) map cleanly onto both programs’ eligible-activity language — citing one by name does real work in a funding narrative.

Warning

Program rules are perishable: NOFO cycles, deadlines, set-asides, match requirements, and even eligible-activity lists change between rounds (and with reauthorization). Verify against the live FHWA HSIP and USDOT SS4A pages before any client-facing statement — the bullets above describe the durable structure, not the current round.

See also: Countermeasure Selection and CMFs · Vision Zero and the HIN (Tampa Bay) · KABCO Injury Scale · Crash Rate Calculation · FHWA Resources