Road Safety Audit

Session 2: RSA Procedures

Process, Players, and Best Practices

Master's Level Course in Road Safety Engineering

Learning Objectives

• Identify the three key players in RSA and their respective roles and
responsibilities

• Understand the complete RSA process flow from initiation to completion

• Describe the content and structure of a professional RSA report

• Explain the purpose and application of RSA checklists

• Recognize best practices for effective audit conduct and stakeholder

engagement
The RSA Ecosystem
Road Safety Audit success depends on three key players working collaboratively:

Client/ Design Team RSA Auditor

Road Authority

Commissions Creates Reviews

& Implements & Responds & Recommends
Player 1: The Client / Road Authority

Key Responsibilities:
Commission RSA: Initiate audit at appropriate project stages, engage qualified auditors

Provide Documentation: Supply complete design drawings, traffic data, crash statistics

Facilitate Site Access: Arrange site visits, coordinate with designers and contractors

Review Recommendations: Assess audit findings, make informed decisions on implementation

Document Responses: Prepare formal response to audit report, justify non-implementation decisions

Oversee Implementation: Ensure approved recommendations are incorporated into project

Player 2: The Design Team

Key Responsibilities:
Provide Design Information: Submit complete, current design documentation to auditors

Attend Inception Meeting: Clarify design intent, discuss project constraints and objectives

Respond to Findings: Review audit recommendations, provide technical feedback

Propose Solutions: Develop design modifications to address safety concerns

Document Changes: Update drawings reflecting incorporated recommendations

Explain Constraints: Justify instances where recommendations cannot be fully implemented

Player 3: The RSA Auditor

Key Responsibilities:
Conduct Independent Review: Systematically examine project for potential safety hazards

Perform Site Inspection: Visit project site, assess context and surrounding conditions

Apply Professional Judgment: Use experience, standards, and best practices to identify issues

Prepare Detailed Report: Document all findings with clear, evidence-based recommendations

Facilitate Discussion: Present findings, discuss feasible solutions with stakeholders

Maintain Independence: Remain objective, free from conflicts of interest

RSA Auditor Qualifications
Essential Qualifications: Desirable Attributes:
• Education: Engineering degree (civil,
transport) • Communication skills
• Experience: 5+ years in road design/safety • Diplomatic approach
• Training: Formal RSA training certification • Attention to detail
• Knowledge: Design standards, crash • Multi-disciplinary perspective
causation

Independence is Critical
Auditors must NOT be involved in project design or have financial interest in outcomes
Organizational independence: Different company or separate division
Professional independence: Objective assessment without bias
The RSA Process: Step-by-Step
Initiation Analysis
1 Client commissions audit
6 Identify safety issues

Appointment Report Preparation

2 Auditor engagement
7 Document findings

Inception Meeting Presentation

3 Stakeholder briefing
8 Discuss with stakeholders

Document Review Client Response

4 Examine design materials
9 Decision on
recommendations

Site Inspection Implementation

5 Field assessment
10 Incorporate changes
RSA Process: Initiation Phase
STEP 1: Initiation & Commissioning
• Client identifies need for RSA based on project stage
• Budget allocation and approval obtained
• Scope of audit defined (which RSA stage, extent of review)

STEP 2: Auditor Appointment

• Selection of qualified, independent auditor or audit team
• Contract negotiation covering scope, timeline, deliverables
• Confirmation of auditor independence and qualifications

STEP 3: Inception Meeting

• Introductory meeting with client, designers, and auditors
• Project briefing: objectives, constraints, design philosophy
• Agreement on audit schedule, access arrangements, reporting format
RSA Process: Assessment Phase
STEP 4: Document Review
• Examine design drawings, cross-sections, plan-profile sheets
• Review traffic studies, crash data, speed surveys
• Study design reports, geotechnical investigations, environmental assessments

STEP 5: Site Inspection

• Visit project site to assess context: existing roads, adjacent land use, topography
• Observe current user behavior patterns and vulnerable road user movements
• Photograph critical features, document site conditions

STEP 6: Analysis & Identification of Issues

• Systematic review using checklists and professional judgment
• Identify potential safety deficiencies: sight distance issues, unclear geometry, hazardous features
• Consider all road user types: motorists, pedestrians, cyclists, motorcyclists
RSA Process: Reporting & Implementation
STEP 7: Report Prep STEP 8: Presentation

• Document all findings • Present findings to client

• Clear recommendations • Discuss with designers
• Supporting evidence • Clarify recommendations
• Photos, sketches • Answer questions

STEP 9: Client Response STEP 10: Implementation

• Review recommendations • Revise design drawings

• Assess feasibility • Incorporate changes
• Make decisions • Update specifications
• Document response • Monitor construction
Structure of an RSA Report
A professional RSA report follows a standard structure:

1 Executive Summary
Overview of key findings and critical recommendations

2 Introduction
Project description, audit scope, team composition

3 Audit Process
Methodology, documents reviewed, site visit details

4 Findings & Recommendations

Detailed safety issues with specific solutions

5 Positive Features
Recognition of good safety design elements

6 Conclusion
Summary of overall safety assessment

7 Appendices
Photos, drawings, checklists, references
Writing Effective Recommendations
Good recommendations are:
SPECIFIC: Clearly state the problem and proposed solution (not vague)
ACTIONABLE: Provide practical solutions that can be implemented
EVIDENCE-BASED: Reference standards, research, crash data
PRIORITIZED: Indicate severity (critical, significant, minor)
LOCATION-SPECIFIC: Reference exact chainage, station, or drawing number

Poor Example: ✓ Good Example:

"The sight distance is inadequate and should be "At Ch 2+450, sight distance is 120m (measured).
Recommend lowering approach grade by 2% to achieve
improved."
160m sight distance per standard for 80 km/h design
speed."

Problem: Vague, no specific location or solution Strength: Specific location, measured data, clear solution with
justification
RSA Checklists
Checklists are systematic tools that ensure comprehensive review:

Purpose of Checklists: Typical Checklist Categories:

• Ensure consistency across audits • Alignment & geometry
• Prevent oversight of critical items • Intersections & junctions
• Guide less experienced auditors • Traffic control devices
• Document systematic approach • Vulnerable road users

Important Notes:
• Checklists are GUIDES, not substitutes for professional judgment

• Every project is unique - auditors must adapt checklists to context

• Checklists should be tailored to RSA stage and project type

• Many countries have developed national RSA checklists (e.g., South Africa, Uganda, Kenya)
Sample Checklist Items
Example items from a typical RSA checklist:

Alignment Are horizontal curves consistent with posted/design speed?

Sight Distance Is adequate stopping sight distance provided at all locations?

Intersections Are conflict points minimized in intersection design?

Signage Are advance warning signs provided at appropriate locations?

Markings Are edge lines continuous except at intersections?

Lighting Is lighting provided at intersections and pedestrian crossings?

Pedestrians Are pedestrian crossing locations clearly marked and visible?

Cyclists Are bicycle facilities separated from high-speed traffic?

Roadside Are fixed hazards removed or protected by barriers?

Drainage Are drainage structures designed to minimize vehicle entrapment?

Best Practices for Effective RSA
Foster Collaboration Communicate Clearly Be Constructive
Build positive relationships with Use plain language; avoid jargon;
Acknowledge good design features;
designers and clients; RSA is not explain the 'why' behind
focus on solutions, not just problems
adversarial recommendations

Maintain Independence Prioritize Issues Document Thoroughly

Include photos, sketches,
Remain objective; avoid conflicts of Distinguish critical safety concerns
measurements; evidence strengthens
interest; focus on safety above all from minor observations
recommendations
Common Challenges in RSA

Incomplete Documentation Request all necessary materials early; conduct inception meeting to clarify
gaps

Time Pressure Negotiate realistic timelines; prioritize critical issues if pressed

Defensive Designers Emphasize collaboration; acknowledge design constraints; present alternatives

Budget Constraints Provide range of solutions with cost implications; identify no-cost
improvements

Late Involvement Advocate for early RSA; document cost of late changes to support future early
audits

Recommendation Rejection Require documented justification; escalate critical safety issues appropriately
Case Study: Effective RSA Process
Context: Major highway connecting Nairobi to Mombasa, high traffic volumes, frequent serious crashes
A2 Highway Realignment - Kenya
RSA Stage: Detailed design (RSA Stage 3) conducted by independent team

Process Highlights:
• Comprehensive inception meeting with Kenya Highway Authority, design consultants
• Two-day site inspection covering full 45 km project length
• Structured use of national RSA checklist adapted to project conditions
• Collaborative workshop to discuss findings before finalizing report

Key Findings:
• Inadequate pedestrian crossing facilities near 3 schools (high risk)
• Poor sight distance at 4 horizontal curves due to roadside vegetation
• Missing advance warning signage for upcoming intersections

Outcome: Client accepted 92% of recommendations; budget increased by 1.5% to implement safety
improvements; estimated 30% crash reduction in first 3 years of operation
Session Summary
Key Takeaways:
• RSA involves three key players: client, designer, and auditor - each with distinct but
complementary roles

• The RSA process follows 10 systematic steps from initiation through implementation

• Professional RSA reports follow standardized structure with clear, specific, evidence-
based recommendations

• Checklists ensure comprehensive review but must be supplemented with professional

judgment

• Effective RSA requires collaboration, clear communication, and maintained

independence

• Success depends on early involvement, adequate resources, and commitment from all
stakeholders
Coming Up Next...

Session 3
Practical Exercise: RSA Process

• Hands-on exercise: Construct RSA process flowchart

• Group discussion of roles and responsibilities
• Practice writing effective recommendations
• Review sample RSA reports
 Thank You
Questions & Discussion