Study guide

Data Process Reviews, Governance, and Investment Decisions

Road Safety Professional RSP

Track your progress as you read

Finished sections get a check mark.

1 Exam Orientation and Preparation

RSP1 Exam, Eligibility, and Certification Preparing Across the Five RSP1 Domains

2 Foundations: Definitions, Evidence, and Standards

Road Safety Definitions and the Public Health Burden Evaluating Road Safety Literature and Information Nominal and Substantive Safety: Standards and Performance

3 Foundations: Contributing Factors, Energy, and Users

Interacting Crash Contributing Factors Collision Severity, Speed, and Protective Layers Road User Characteristics, Abilities, and Vulnerability

4 Foundations: Partners and Safety Frameworks

Safety Partners, Responsibilities, and Multidisciplinary Perspectives Haddon Matrix and the Development of Safety Management Safe System Principles and Protective Layers Vision Zero, Toward Zero Deaths, and Safety Culture

5 Measurement: Data Collection and Quality

Safety Data Types, Sources, and Users Collecting Quantitative and Qualitative Safety Data The Six Safety Data Quality Attributes Data Process Reviews, Governance, and Investment Decisions

6 Measurement: Exposure, Severity, Models, and Effects

Crash Frequency, Exposure, and Rates Injury Severity, Crash Costs, and Weighted Measures Safety Performance Functions and Suitable Models Regression to the Mean and Empirical Bayes Interpretation CMF Definitions, Scope, and Evidence Quality

7 Human Factors: Perception and the Driving Task

Sensory Perception, Attention, and Workload Driving Task and Perception-Response Time

8 Human Factors: Behavior and Programs

Impairment, Distraction, Fatigue, and Speed Choice Enforcement, Licensing, and Behavioral Countermeasures Outreach, Social Norms, and Audience-Centered Programs

9 Human Factors: Infrastructure, Multimodal Design, and Guidance

Roadway Features, Expectancy, and Behavioral Adaptation Human Factors in Multimodal Planning, Design, and Operations Positive Guidance and Driver Expectancy

10 Problem Solving: Management, Screening, and Diagnosis

The Road Safety Management Process Site-Specific and Systemic Network Screening Crash Patterns, Collision Diagrams, and Diagnostic Hypotheses Field Investigation and Surrogate Safety Measures

11 Problem Solving: Countermeasures and Safety Audits

Countermeasure Sources, Mechanisms, and Selection Combining CMFs and Evaluating Treatment Trade-Offs Road Safety Audits and Documented Owner Responses

12 Problem Solving: Economics and Project Selection

Economic Appraisal: Benefits, Costs, and Discounting Prioritizing Projects and Nonmonetized Impacts

13 Problem Solving: Evaluation Methods and Planning

Evaluating Countermeasures: Before–After and Cross-Sectional Studies Planning Evaluations and Collecting Credible Evidence

14 Implementation: Statewide and Local Plans

Developing Strategic Highway Safety Plans Local, Tribal, and Regional Safety Action Plans

15 Implementation: Funding, Policies, and Practicality

Infrastructure Safety Funding and Program Eligibility Safety Policies, Behavioral Programs, and Practicality

16 Implementation: Teams, Communication, and Learning

Teams, Champions, Leadership, and Organizational Safety Culture Communication, Public Support, and Implementation Consensus Program Monitoring, Safety Targets, and Plan Updates

Data Process Reviews, Governance, and Investment Decisions

Key Takeaways Explain This Topic AI

Trace defects to their collection or processing mechanism.

Define owners, stewards, exchange rules, and revision procedures.

Prioritize upgrades by analytical needs and decision consequences.

Verify sustained quality and actual use after an improvement.

Last updated: October 2026

  • Data Process Reviews, Governance, and Investment Decisions
  • Review the workflow behind the dataset

A data-related process review examines how information is collected, transmitted, validated, stored, linked, revised, and supplied to users. It seeks the source of a quality problem rather than repeatedly correcting symptoms in an analyst's spreadsheet. If crashes are consistently assigned to the wrong road, the issue might involve field collection, map versions, interface design, or geocoding rules.

Begin with analytical needs. Network screening may require consistent locations and exposure; diagnosis needs narratives and detailed conditions; program evaluation needs stable definitions across periods. Interview users from engineering, planning, enforcement, health, and program management. A single department's convenient output may not serve the shared decision.

Define ownership and accountability

Data governance identifies who defines an element, collects it, maintains it, validates it, authorizes access, and resolves conflicts. A data owner is accountable for the domain; a steward can manage definitions and quality practices; system personnel support technical operation. Agencies may use different titles, but responsibilities must be clear.

A traffic-records coordinating body can connect organizations managing the different systems. Include frontline collectors as well as analysts: an officer, dispatcher, or inventory crew may explain why a field is difficult to complete. Users should explain why it matters rather than treating collection as a purely administrative obligation.

Use agreements for shared definitions, exchange formats, revisions, privacy, and dispute resolution. Governance is not established merely by purchasing one central database. A technically integrated system can still contain incompatible categories and uncertain ownership.

Trace a defect through the process

Suppose a review finds many crashes coded at an intersection when narratives describe events upstream. Sample records and compare location fields, coordinates, narrative, map versions, and collection instructions. Determine whether the problem is widespread or limited to one source, time, or interface.

Then inspect the handoffs. Does the field application force an intersection choice? Are coordinates captured from the officer's parked vehicle rather than the crash location? Does a batch import shift records to the nearest junction? Each hypothesis requires evidence. Avoid blaming a collector before checking the system constraints.

Select a correction that targets the mechanism: revised collection instructions, a better map interface, validation rules, or a corrected import method. Preserve source records, document any retrospective changes, and verify the correction on a suitable sample. A new error rate should be compared with a similarly defined baseline.

Prioritize improvements by decision value

Not every data upgrade provides equal value. Compare cost, implementation time, coverage, maintenance, training, privacy requirements, and the analyses enabled. A small location improvement on local roads may unlock a more useful screening process than an expensive dashboard displaying already available totals.

Consider the consequence of the current defect. Missing pedestrian exposure may limit interpretation of rates. Poor severity mapping may change emphasis-area rankings. Delayed reporting may obscure emerging problems. State which decisions improve when the data improve, and which uncertainty remains.

Do not claim a direct fatality reduction merely because a data system was upgraded. Better information can support better decisions; the eventual safety benefit depends on how the information changes program selection and delivery. Track both quality outcomes and the use of the resulting data.

Choose quality controls and training

Controls can include required-field logic, valid-range checks, consistency checks, duplicate detection, location validation, review queues, and periodic audits. Mandatory fields can improve completion but also encourage arbitrary values if “unknown” is improperly prohibited. Design the interface around the real collection task.

Train collectors in definitions and why the fields matter. Give feedback on recurring errors and provide usable reference material. Analysts also need training in limitations, linkage, and appropriate comparisons. A model cannot repair a fundamentally incompatible outcome definition merely through a sophisticated formula.

Document procedures and monitor after changes. Staff turnover, new equipment, or revised law can alter data quality. A one-time cleanup is not a sustainable quality program. Assign resources for maintenance and periodic review.

Work a small investment decision

Imagine an agency choosing between an electronic crash-report upgrade and a new visualization portal. The upgrade could reduce delay and improve geolocation, while the portal could improve access to existing information. First measure the current delays, location errors, request times, and user needs. Estimate costs for installation, training, support, and continuing operation.

If location errors prevent valid screening, the upgrade may address a more consequential barrier. If data are reliable but inaccessible to local partners, the portal may have greater immediate value. The answer depends on the evidence and needs, not on which technology looks newer. A phased plan can sometimes address both, with defined quality targets at each stage.

Trace the data lifecycle

Collection: definitions, interface, and source conditions.

Processing: validation, imports, referencing, and revisions.

Use: access, documentation, analysis, and decisions.

Interpret the review and feed back to programs

Report findings in decision terms: which analyses are reliable now, which require caution, which need better information, and who owns each improvement. Include timelines and measures. If a before-after comparison crosses a reporting-definition change, reconcile or redesign the evaluation instead of presenting the series as unchanged.

After an improvement, verify delivery and quality results. Ask whether users adopted the data and whether planning or treatment decisions changed. If the improvement missed the target, investigate process fidelity and technical performance. FHWA safety-data quality measures support systematic assessment, while local governance makes the improvements practical and sustained.

A good review connects collection, quality, analysis, and action. It turns a statement such as “our data are poor” into a specific problem, an accountable correction, and a measurable contribution to better safety decisions.