- Competitors are reminded that orienteering is an adventure sport and that they are responsible for their own safety when taking part in this event.
- In view of the exposed nature of the terrain, a policy of NO WHISTLE NO GO will be strictly enforced. Whistles will be on sale at the Map Masters stand in the Event Centre.
- Please note that the Country Code must be observed at all times and competitors must report to the finish even if they do not complete the course
- A decision on rain jackets (cagoules) will be taken on the morning of the event based on the expected weather. A notice as to whether cagoules have to be carried will be posted at the Event Centre on the way to the start. The policy will be strictly enforced by the start team, and competitors will be disqualified if they do not have their cagoule at the finish.
- All starters will be recorded by a start official. All finishers will also be recorded by the independent timing team at the finish line, and checked off against the start list to identify any missing competitors. By locating this function at the finish, it will ensure a quicker response in dealing with any missing competitors and will reduce the chances of ‘losing’ any competitors between the finish and the SI download point.
- The SI results team will identify the starters from interrogating the check box used at the start as required. By matching off the finishers who have passed through the download process they will be able to identify any missing competitors.
- The Organiser will be responsible for coordinating the rescue of any injured competitor, and for the organization of any rescue party.
- The Red Cross personnel will be located at the finish with their ambulance located as close to this as possible.
- In the case of a missing competitor, once all of the usual checks are made, the Organiser may decide to conduct a search of the area. A list of volunteers has been drawn up who can be called upon to conduct the search. At that stage the local police will be informed
- The Organiser will maintain an incident log
Last updated 23rd March 2010 |
|
