|Back to Road Safety Audits (RSA)|
Previous Page | Next Page
Using RSA prompt lists.
The purposes of RSA prompt lists are to help the RSA team identify potential safety issues and to ensure that they do not overlook something important. The prompt lists may also be used by designers to help them identify potential safety issues proactively as they develop their design.
RSA prompt lists, even the most detailed ones, should be viewed as a prompt only. They are not a substitute for knowledge and experience; rather, they are an aid in the application of knowledge and experience. The RSA high-level prompt lists appended to this guideline are not all-inclusive, nor will they cover all potential issues and circumstances.
High-level prompt lists and an example of a detailed prompt list are included in this section. They provide a high-level outline of the topics typically considered to be within the scope of RSAs conducted at each stage and highlight areas that should be examined for safety issues. More detailed prompt lists are provided on the FHWA website at http://safety.fhwa.dot.gov/rsa.
The RSA prompt lists provided are organized as follows:
Prompt lists for each RSA stage.
More detailed prompt lists are available at http://safety.fhwa.dot.gov/rsa.
The prompt lists are for use during RSAs when:
During project data and plan review, prompt lists may assist the RSA team in identifying missing information relevant to the scope of the RSA .
During pre-construction phase RSA site visits, a review of prompt lists may assist the RSA team in visualizing and assessing how the proposed design will integrate with existing road and environmental features. During construction phase and post-construction phase RSA site visits, the prompt lists provide a means of ensuring no safety-related elements are overlooked.
When filled out during project data and plan review, and during the field visits, the information contained in the comment fields of the prompt lists may subsequently be used to facilitate writing the audit report more rapidly and accurately.
Prompt lists should not be appended to the RSA report. The written RSA report should contain a sufficient explanation of the identified safety issues, the extent of safety concern, and the resulting suggestions, without any need to refer to notes or prompt lists.
Using prompt lists to facilitate RSAs.
Prompt lists, if used, should be applied in a way that best meets each RSA team member's needs. The prompt lists are structured to support the RSA team regardless of how they choose to undertake their work (independently then collectively, by progressing through the project in the same manner as a road user, or by examining each feature as it manifests itself in the project). Just as there is no single way to identify safety issues, there is no single way to use prompt lists.
Even the most detailed prompt lists cover only the more common elements of design and practice. Prompt lists are not exhaustive. RSA team members should use their own skills and judgment about the safety of any feature. If a listed topic is not apparently relevant to the project being audited, a broad view of the topic should be taken to see if it prompts a relevant question. For example, sight lines may be obstructed by features not listed in the prompt lists, but only at particular times of day or during a particular season of the year. Where a land use development proposal forms part of the design, may impact the design, or may impact the adjacent road network, the prompt list for the land use development should be used to complement the prompt lists for the related RSA stage. An understanding of the general environment around the project will help auditors make the best use of prompt lists.
Approach to using prompt lists.
The following outlines a general procedure of using prompt lists:
Previous Page | Next Page
back to top