Please email your details, as follows, to firstname.lastname@example.org :
- First name and surname
- Contact details – one email address and one phone number
YOU MAY NOT SUBMIT A REQUEST TO BE PLACED ON A WAITING LIST ON BEHALF OF A FRIEND, RELATIVE, RUNNING PARTNER OR ANYBODY ELSE. ONE NAME PER EMAIL ONLY – THE PERSON APPLYING MUST PROVIDE OWN PERSONAL EMAIL ADDRESS (there is more than one good reason for these rules).
- Please notify us of any change in your contact details.
- Please notify us, by email, if you are no longer available to take part.
PLEASE NOTE: ENTRIES FOR THE 2017 THREE PEAKS CHALLENGE ARE, IN THEORY, ALREADY FULL. AN UPDATED WAITING LIST WILL BE PUBLISHED AS SOON AS IT IS AVAILABLE.
The waiting list extends, potentially, to the year 2018 and beyond. Entry criteria are currently being revised and are expected to come into effect in time for the 2018 event.
For anybody joining the waiting list now, the chance of an entry for 2017 will depend on the amount of people ahead of you on the waiting list being available or not, or the number of people who drop out of the event closer to the time, in which case you may stand the chance of coming in as a late replacement.
Should you not get an opportunity to take part in 2017, your name will remain on the “General Waiting List”, for possible inclusion in subsequent years’ events. Should you get an opportunity to take part, your name will be removed from the list once your entry has been received. Coming in as a late replacement is treated in the same way as any other entry – you have the right to decline the offer and retain your place on the waiting list for a future event, or to accept the entry, in which case your name will be removed from the list and you will have to rejoin at the bottom of the list (as explained below).
Note: once you have completed the event – or withdraw during the event – you will need to request, in writing, to the organisers, to rejoin the waiting list at the bottom of the list. This must be done after the cut-off at 19h00 and not while the event is still being run.