CIHT Road Safety Audit Guidelines Update

Transcription

1 CIHT Road Safety Audit Guidelines Update SoRSA Conference 26 June 2018 John Barrell BSc CEng FCIHT FSoRSA AMRSGB SoRSA Chair

2 Current Guidelines Published 2008 Covered more than just Audit Produced to support HD 19/03

3 Need for Change? Current Guidance in HD 19/15 as standard. More onerous training and experience. Restrictive on non trunk road schemes. LAs still struggling to comply. Wider adoption of varying practices worldwide Less certainly in what in accordance with HD19/15 means.

4 Proposed Approach Fundamentals of Road Safety Audit well known. Means of application and understanding of process needs clarification. Role of key parties in delivering robust process. Input from worldwide practitioners. Flexible framework with HD19/15 at its core. Development of interactive web-based document that can be updated and structured to meet varying requirements.

5 Key is the Audit Process Identify key responsibilities at each stage. Focusses on actions outside of HD 19/15. Aware that guidelines will have an international audience and needs to cover a wide range of issues/applications. Different approaches to HA/developer requirements. Full text now developed with templates and examples!

6 Questionnaire responses (60) Incorporated in document where possible: Risk assessment omitted GD/04 Flexibility in reporting style Additional stages of audit Less waffle and ambiguity hopefully Interface between designers/ auditors Independence not isolation Detailed guidance on brief content Single line memo and plan NOT acceptable Need to be backed by clear local procedures No longer use generally o accordance with HD 19 Clear guidance on developer led schemes

7 Responsibilities Key roles still as described in HD 19. Client - will always be the highway/road s authority as they have the statutory duty for road user safety. If the project is either local authority or developer led then a scheme manager will be identified in the relevant organisation - will need to liaise with the HA. Design Team - is the group that is always responsible for the technical aspects of the design. Audit Approval lies with highway authority as client!

8 Need for Audit Now clearly defined - set against local approved procedures. It will be for the Project/Scheme Manager within the highway authority to determine if an audit is necessary in accordance with currently defined local practices.

9 No audit (examples)

10 Need for Audit (examples)

11 LA Procedures Covers any audits NOT fully compliant with HD19 Need to be explicit on what aspects of HD19 are NOT being applied and why. May relate to: Stages of audit Qualifications/experience/number of audit team Scheme coverage Opening/closing meetings And anything else! Must be approved by formal Member resolution.

12 Specific Scheme Manager Person within a local authority/developer organisation who is responsible for the project requiring a road safety audit. Responsible for commissioning/verifying the need for audit and ensuring that it is carried out in accordance with the highway local authority s defined audit procedures. If a Developer s scheme, the local authority needs to appoint identify an authorised officer to ensure that the audit is carried out in accordance with the local authority s adopted procedures prior to acceptance. In addition to the above, they need to liaise with the Developer s Representative to ensure audit recommendations are incorporated in final design.

13 Audit Brief Prepared (or delegated) by Scheme Manager and approved by Highway Authority Typical Content: -short description of the scheme and its purpose -design standards adopted -programme for implementation -scheme plans, including a location plan at an appropriate scale to identify any design issues -any Departures and Relaxations from Design Standards -the latest 36 months of personal injury collision data for the site and its approaches, including a plot of collision locations and narrative e description of incidents (LA base rather than just Crashmap) -a design statement (including environmental considerations) if available -a traffic impact assessment including existing and forecast traffic flows, if available -previous road safety audit reports relevant to the current scheme, including design decisions made as a result of the previous audits -The Exception report from any earlier audit this will inform the audit team as to the risks within the design that have already been accepted by the local highway authority, and hence should not be mentioned again in the current audit unless the design has changed significantly. -Swept paths, Speed, and current traffic flows -Appropriate times for undertaking site visit i.e. school times if required Templates being developed!

14 Appointing Audit Team Scheme Manger Responsibility. Variation from national standards need to be documented and approved. Approved by Highway Authority in line with local standards.

15 Verification of information Audit team responsibility. Clear instruction in brief and understanding of requirements both in terms of design and programming. Any missing or unclear instructions Must be confirmed before undertaking the audit. No assumptions in report be specific!

16 Carrying out the audit! Be sure what standard you are working to and specific requirements (ie site visits) if necessary!

17 Reporting Audit team to prepare. Only relates to safety problems that will result in road user injury. Comments/non-safety issues! reported separately. Initial report sent to LA with copy to Developer ( if relevant). Scheme manager forwards to design team for response Subsequent revisions/amendments clearly documented.

18 Discussion of Responses/Recommendations Opportunity needs to be identified in local procedures. Takes place between Design Team and Scheme Manager (LA!). Differences should include discussion with Audit Team Leader. Final desicion on acceptance or refusal lies with Scheme Manager (LA). Any refused recommendations need to be documented Exception Report.

19 Document Publication Once all issues have been resolved Final document including all design responses and Exception Reports distributed to all parties. Document retention Audit report stays with project H&S file. Length of time for external copies dependent upon individual document retention polices. 25 years?

20 Next steps Reshape content to identify/repeat for each role Engage with web designer to develop layout and user options. Unlikely to be finished by Dec Next conference?

21 Thank you Any Questions/Comments/Contributions Contact