What should organizers check about participant waivers for challenge events?

Someone buys six places for your obstacle race. The payment arrives, the confirmation goes out, and your sales dashboard looks healthy. Then the team turns up with a different runner, a teenager you weren't expecting, and one person who thought the buyer had completed everyone's paperwork. Your first wave starts soon. Who can actually take part?

A race participant waiver needs to fit the activity, the people entering and the law where you operate. Have the wording and signing process reviewed by an appropriately qualified local lawyer, check the requirements with your insurer, and connect each required record to the person who will participate. Keep the course assessment, medical arrangements and permission to start as separate decisions.

The useful question is what your team needs to know before releasing someone onto the course. A signature can record something they agreed to. It cannot tell you whether the obstacle inspection happened, whether the signer was the participant, or whether the information they saw still describes today's event.

This guide is for businesses selling places at obstacle races, endurance challenges and similar participation events. We'll use a fictional adult obstacle event to work through registration, group bookings, document changes and race-day exceptions. Legal examples refer to England and Wales unless stated otherwise. Have advisers establish the applicable rules for your event, including any overseas entrants, rather than treating an example from another country as your answer.

Decide what each document is supposed to do

The first thing you want to do is separate the documents you've been calling the waiver. Ask whoever owns registration to lay out everything an entrant receives and everything you ask them to accept. You may find several different decisions packed into one checkbox.

Your participation information describes the experience. It explains the terrain, exertion, activities, equipment, restrictions and available alternatives so someone can decide whether to enter. Your entry terms explain the purchase, including changes, cancellation and transfers. A risk acknowledgement records the information presented and the participant's response. A proposed liability release tries to affect legal rights, which needs specific legal review.

A health declaration has a different job again. The medical lead should determine what information is needed and what action follows an answer. Permission for a child to attend, consent for promotional photography and permission to send future marketing also need their own consideration. Calling the whole bundle a waiver makes it harder to notice when one part is missing or inappropriate.

Write a purpose beside each document. Who uses the information? Which decision does it support? What happens when the person asks a question or declines? If nobody can answer those questions, you probably need to redesign that part of registration before adding another mandatory field.

For example, asking someone to confirm they can swim only makes sense if your approved activity involves a relevant swimming requirement and you have a defined response. It doesn't establish the safety of the water feature. Equally, an emergency contact gives you a person to contact under your procedure. It doesn't automatically give that person authority to sign documents or make every medical decision.

Keep the purchase and participation records connected, but allow them to show different states. You can have a paid order with an entrant still completing required steps. That distinction needs to be visible to customer support before race day, not discovered by the person handing out bibs.

Our paid-entry obstacle race guide covers the wider course and operating plan. This article concentrates on the information, agreements and checks for each participant. Use both when building registration, because the documents must describe an event your course team can actually deliver.

Give your lawyer and insurer the actual event

Sending a lawyer last year's PDF and asking whether it's fine leaves them guessing about the event. Start with a practical brief. Describe the legal entity taking entries, the site, the activities, the intended participants, the suppliers involved and the countries or regions relevant to the booking. Attach the participant journey as well as the proposed wording.

Explain whether you offer timed racing, a recreational challenge, team entries or different difficulty levels. Identify features such as water immersion, height, load carrying or remote sections when they are part of the approved plan. Include how entrants can decline an obstacle, withdraw or request support. Those details help advisers identify the questions that the document and process need to address.

In the UK, section 65 of the Consumer Rights Act 2015 prevents a trader using a consumer term or notice to exclude or restrict liability for death or personal injury resulting from negligence. Have your adviser explain its application to your event. You cannot settle that question by putting stronger language above a signature box.

The Competition and Markets Authority's guidance on fair customer contracts also makes clear that contract wording needs to be fair and understandable. Review the entry terms alongside the proposed release. A cancellation clause, broad change provision or declaration that everyone has understood everything deserves attention too.

Give the insurer the same activity description. Ask which documents, checks and records the policy requires, and who can confirm the answer in writing. Check the named insured, covered activities, age groups, exclusions, notification requirements and contractor arrangements with your broker or insurer. An insurance certificate alone doesn't explain whether your particular course and registration process meet the policy conditions.

Keep the two reviews separate. A lawyer's review doesn't confirm insurance cover, and an insurer's requested form doesn't resolve every legal question. Record who approved which document, the scope of their advice and what changes require another review. Avoid telling staff that the event is fully protected because a form was approved.

Have the review done while you can still change the offer. If your advisers say an activity needs different arrangements, you want time to redesign it before people pay. Budget for this work as part of producing the event, alongside inspection and medical provision, rather than treating it as an optional cost once tickets are selling.

Explain the challenge before asking for acceptance

Think about what a first-time entrant pictures when they read your event page. Mud, teamwork and a finish-line photograph may sound appealing. They still need to understand what they'll be asked to do and what they can choose not to do. Exciting copy should help them picture the actual experience.

Describe the demands in ordinary language. Explain the route and relevant terrain, the kinds of obstacles, the expected preparation and any activity-specific requirements established by the course team. Say whether walking, assistance or bypasses are available and how those choices affect a competitive result. Avoid broad promises such as suitable for everyone when the operation has real restrictions.

Use our event risk assessment template to connect identified hazards with controls and responsible people. Then ask the competent course and medical advisers which information participants need before booking and which instructions they need immediately before an activity. The full assessment may be a specialist working document; the participant explanation should be readable without specialist knowledge.

Here's a fictional example. The course team approves an adult recreational route with a climbing obstacle and a marked bypass. The event page explains that entrants may use the bypass without a competitive penalty because the event is untimed. The briefing and obstacle signs repeat the same choice. A marshal who pressures someone to climb would undermine the experience you described.

If you later introduce timing and penalties, the original explanation no longer covers the offer. Update the rules, have the relevant documents reviewed and decide how existing buyers will be treated. Don't leave the marketing page describing a relaxed challenge while the start team enforces a competition.

Give people a useful way to ask questions before paying. A named support contact can explain the published activity, arrange an access conversation and refer technical or medical questions to the right person. The support team should know when to stop answering and refer, especially when someone asks whether a health condition makes participation appropriate.

Check language and presentation as part of this work. Can a person read the information on a phone, enlarge the text and use the form with their usual accessibility tools? Where a translation is necessary, arrange a reliable reviewed version. A friend giving a hurried summary in the queue is a poor substitute for an accessible process prepared in advance.

Match the signer to the participant

A group buyer is often the easiest person to reach and the wrong person to answer questions about everyone else. Build the process around individual entrants. The buyer can manage payment and distribute the next steps, while each participant completes the parts that require their own information or agreement under your reviewed process.

Use a stable participant reference that connects the entry, the required document and the race-day record. A name alone can be ambiguous, particularly when several people share it or a team uses nicknames. Keep the information you need to distinguish records, but don't collect identity documents by default. Agree proportionate identity checks with your advisers and explain them before arrival.

For our fictional six-person booking, the order reference identifies one purchase. Six participant references identify six places. The record should let support see which people have completed the current requirements without assuming the whole team is ready because the buyer responded. If a completion link fails, staff need a way to correct that person's record without duplicating the paid entry.

Make name changes and transfers explicit. A substitute needs to meet eligibility requirements and complete the required steps in their own capacity before starting. The original participant's signature belongs to the original participant. Renaming a bib or forwarding a ticket doesn't establish that the replacement received the information or agreed to the relevant document.

Decide how to correct an honest mistake. If someone enters the wrong email address or chooses the wrong wave, support needs to distinguish a correction from a transfer to a new person. Keep a record of the authorised change and update the affected systems. Repeating the whole process unnecessarily can confuse the entrant, while silently replacing the original information can make the record difficult to explain later. Establish the correction procedure alongside the signing process.

Give transfers a deadline and a supported route that match your operational capacity and reviewed terms. Decide who can approve a late change, whether it can move someone between waves, and how it updates timing, emergency contact and participation records. Communicate the decision to every affected team. Otherwise registration may accept the substitution while the course team still holds the old name.

For company or charity teams, check who is paying and who is participating. An employer's purchase order or fundraising relationship doesn't answer the participant's individual questions. Send the team organiser a clear distribution task and the entrants their own steps where required. Avoid copying personal health answers into a team captain's shared inbox.

The same distinction applies when someone buys a gift. Explain what is bought immediately, what the recipient must do later and what happens if they cannot meet the published conditions. Sort out those terms before selling gift places. Customer support should be able to explain the purchase without improvising a promise about eligibility or refunds.

Treat junior entries as a separate offer

If you plan to admit children, build the junior offer deliberately. Ask the relevant legal, safeguarding, sporting, medical and insurance advisers to establish the appropriate age rules, permissions, supervision and signing arrangements. Don't add a junior price to the adult race and assume a parent checkbox completes the work.

A child attending with a school, a club or a friend's family creates different practical questions. Who is authorised to provide each permission? Who supervises the child before, during and after the activity? Who collects them? What happens if the adult expected at registration doesn't arrive? Resolve these questions in your process and communications, with appropriate safeguarding advice.

The NSPCC's advice for parents supporting children in sport includes collection by an approved adult known to the activity. For an organizer, that makes arrival and collection arrangements part of the operating plan. They need an owner and a way to handle a change, rather than a note buried in an entry form.

Keep the child's experience in view. Explain the activity and the available choices in an age-appropriate way, under the arrangements agreed with your advisers. A signed adult document doesn't tell you whether a frightened child wants to attempt an obstacle. Staff need clear instructions about stopping, declining and seeking help without pressure from the queue or the accompanying group.

Check the legal effect of any proposed release for a minor in the relevant jurisdiction. Don't tell parents that signing removes all rights or assume the adult form works unchanged. Where you can't establish suitable arrangements for a particular age group, postpone that offer. It's better to sell a narrower event you can operate properly than take entries you cannot responsibly accept.

For an adult-only event, state the restriction before payment and agree how staff check eligibility. Prepare the response to a buyer who enters the wrong date of birth or arrives with a younger substitute. The admissions team needs an escalation contact and a consistent customer response, including how the reviewed entry terms apply.

Ask only for health information you can use properly

Before you add medical questions, ask the medical lead what decisions the information supports. Then decide how it will reach the appropriate people. Collecting a long history without a review process creates sensitive records while leaving the operational question unanswered.

A participant might disclose something that needs a private conversation, ask for an adjustment or report a change since entering. Decide who reviews each kind of message, how quickly they respond and what appears in the admissions record. A front-desk volunteer shouldn't interpret a diagnosis or decide that a signature overrides a concern.

Under the UK data protection framework, health information can be special category data, which receives additional legal protection. The ICO's rules on special category data explain the need for an Article 6 lawful basis and a separate Article 9 condition. Have the appropriate adviser establish your approach. The ICO flags this guidance for review following legislative changes, so verify the current position when setting up the event.

Design the staff view around the action they need to take. Admissions may need to know that a review is pending and which authorised person to contact. Medical personnel may need access to relevant health information through their own agreed arrangements. The marketing team has no reason to receive the answers just because all three teams work on the same event.

Give participants a clear privacy explanation when you collect information. Identify who holds it, the purposes, relevant recipients, how to ask a question and how retention is decided. Check the arrangements with external form providers and medical contractors. A secure-looking form doesn't tell you who can access its exports or what happens when the supplier relationship ends.

Keep emergency contact information current and collect it for a defined purpose. Explain how it is used, and have your privacy adviser address information about people who didn't fill in the form themselves. Give entrants a way to update a contact without sending medical details to the general support queue.

Avoid treating a health declaration as a medical clearance certificate. Whether a particular activity requires further assessment, and who can make that assessment, belongs with qualified advisers. Your registration process should support those decisions and record the relevant outcome. It shouldn't invite admissions staff to make them because the participant is already wearing a race bib.

Make online completion easy to understand and prove

Once the wording is reviewed, test what the entrant actually sees. Does the page identify the event and participant? Is the relevant document available before the action that records acceptance? Can the person ask for help, correct a mistake and keep a copy? Treat the screen sequence as part of the review, because a suitable PDF can still be presented badly.

For England and Wales, the Law Commission's statement on electronic execution of documents explains that an electronic signature can execute a document where the signer intends to authenticate it and applicable formalities are satisfied. That doesn't establish that a particular race form is enforceable. Ask your lawyer to review the signing method, evidence and any formalities for the document you intend to use.

Agree the evidence you need to retain. It may include the participant reference, the signer's capacity, the exact document version, the action taken and the time recorded. Check which system can produce that evidence and whether you can retrieve it after a supplier account closes. Don't collect device or identity information simply because a form provider makes it available; justify it through the reviewed process and privacy arrangements.

Test assisted completion too. Some entrants will need a staff member to read information aloud, help navigate a device or explain where to find an answer. Agree what assistance is appropriate and how the process records it. The helper shouldn't answer personal questions or accept on the participant's behalf simply to finish the booking. Where someone cannot use the standard method, refer them through the reviewed alternative rather than excluding them automatically or inventing an exception.

Keep optional choices separate where appropriate. Someone should be able to understand which action is required for participation and which relates to a separate purpose, such as promotional contact. Have your advisers review the actual labels and choices. A large accept-everything button can hide distinctions that your internal documents describe perfectly well.

Test with a group booking and a transfer, not only a single adult buying for themselves. Include a person who completes the form later on another device, someone using assistive technology and someone who needs help with the language. Check that a repeated click or a reopened link doesn't attach the wrong response to another entrant.

There is a commercial reason to care about the journey too. In Loopyah's Event Attendee Insights Report, a Pollfish survey of 500 US attendees fielded on 11 November 2025, 19.8% selected slow sites or errors as a reason for abandoning a ticket purchase in the previous year. Login issues were selected by 17.8%, and payment failure by 12.4%. Respondents could choose up to three reasons.

Source: Loopyah Event Attendee Insights Report, Q13, unweighted counts of 99, 89 and 62 out of 500 respondents. The labels shorten slow site/app or errors, required account creation/login issues, and payment declined/verification failed. These are selected answers from a general attendee survey, not a measure of race-waiver abandonment or proof that a particular signing process changes sales.

Use that context to justify testing the whole registration journey. It doesn't justify removing information participants need. Show the requirements before purchase, make the next steps clear and give people a reliable route to finish them. When completion happens after payment, explain the deadline and consequences in the offer and reviewed terms so a paid confirmation isn't mistaken for permission to start.

Keep the version someone saw

Imagine a participant completes your process in April. In June, the course changes and you edit the document at the same web address. By race day, that link shows the new text. You now need to know which information the April entrant received, rather than simply opening today's page.

Give each approved document a version identifier and an effective date. Keep an unchanged copy with the review record, and connect completed responses to that version. The identifier can be simple, provided staff and systems use it consistently. Avoid relying on filenames such as final, final-new and latest-final to distinguish what people saw.

Separate the public current document from the archive. The current page helps new entrants complete the right process. The archive helps authorised staff retrieve the earlier wording and evidence. Control access to personal records separately from the document text, and test the retrieval rather than assuming the provider's dashboard keeps everything indefinitely.

Set a change procedure with your advisers. A corrected typo, a revised start time and a newly introduced activity don't necessarily need the same response. Have the appropriate reviewer decide what changes need fresh information, further acceptance, a different participation offer or another customer remedy. Record the decision and which entrants it affects.

Don't overwrite the old response when someone completes a new version. Preserve the sequence under your agreed retention arrangements, showing why the new step was requested and when it was completed. That makes support conversations clearer and avoids presenting a later response as though it existed at the time of the original purchase.

For example, a route alteration might remove an activity rather than add one. The course team should still assess the revised operation, and support needs an accurate explanation of the change. Whether it requires a fresh document step or a remedy under the entry terms needs review. Simply emailing everyone that the waiver has changed doesn't establish what the change legally achieves.

Keep communication delivery separate from acceptance. An email being sent, delivered or opened doesn't prove the participant completed the required action. Use your communication system for the notice and your reviewed signing process for the record. Reconcile unresolved entrants before the event so customer support can help while there is still time.

Keep ticketing and participation records connected

Your ticketing system should handle the sale and the ticket record. The participation process needs to show whether each entrant has completed the additional requirements for your event. Decide how those records will be matched and reconciled before choosing the tools. A feature called custom forms doesn't automatically answer questions about signatures, document versions or sensitive data.

Loopyah's ticketing tools support ticket types, release quantities and QR-ticket check-in by staff using their phones. Use those capabilities for the entry offer and admissions work they provide. Verify any separate form or signing connection for your setup before relying on it. Check waiver signing, medical reviews and participation approval in the separate process you've selected.

If the processes are separate, assign someone to reconcile them and establish which record controls each decision. Staff must be able to match the current participant to the right entry without exposing unnecessary personal information. Test a failed update and a duplicate name. A neat report is only useful if it stays accurate when a booking changes.

For participant communications, Loopyah's attendee email tools let you send event updates to ticket holders. Use them to explain the required steps and deadlines, with a clear contact for questions. Check how individual participants receive the information when a team buyer holds the booking; reaching the buyer isn't evidence that every entrant saw the message.

Keep reminders practical. Tell the recipient which event the message concerns, what remains to be done, when it is due and where to get help. Don't include a diagnosis in a subject line or copy a sensitive answer into a general campaign. Where the reminder relies on a separate completion record, check that the audience is correct before sending.

Decide who owns the last reconciliation before check-in opens. The report should distinguish paid entries, current document completion, outstanding referrals, cancellations and transfers. An overall percentage can be useful for workload planning, but admissions needs the state of the individual in front of them. A nearly complete team can still contain one person who needs attention.

Plan race-day exceptions before they fill the queue

Put yourself beside registration at the busiest arrival time. A participant has no signal, another shows a completion screenshot, and someone else wants to sign on behalf of a friend who is parking. The queue needs to move, but staff need a consistent response that fits the reviewed process.

Prepare an exceptions desk or private help point appropriate to your event. Give routine ticket checks to admissions and unresolved participation issues to trained staff with a named escalation contact. Decide what information can be discussed in public and where someone can raise a health or safeguarding concern privately. Make the help point easy to find before people join the wrong queue.

A screenshot may help find a record, but agree which evidence staff must verify. Check the participant, event and version through the authorised process. Don't let an image of another person's completion or last year's document become today's approval. Explain the rule politely and give staff the means to resolve a genuine system problem.

Plan for a connectivity failure. Ask your lawyer, insurer, privacy adviser and operating team whether an alternative completion method is acceptable, what information it must capture and how it is secured and reconciled. Test the approved method. Printing an old form from a volunteer's laptop at the last minute can introduce the wrong wording and leave you with records nobody knows how to store.

Set a latest resolution point that works with the wave plan and published terms. An entrant who needs more time may require a later available wave, another permitted option or a decision under the agreed customer policy. Moving them must respect capacity and course arrangements. The starter shouldn't squeeze someone into a full wave because they spent longer at the help desk.

Allow the start team to hold participation when a requirement remains unresolved or conditions have changed. In Great Britain, HSE's event management guidance emphasises controlling risks, coordinating work and monitoring arrangements during the event. Your operating team still needs to make the current decision, even when the participant's document record is complete.

The same applies when someone becomes unwell, arrives without required equipment or reports a new concern. Refer them through the established procedure. A completed form shouldn't make staff reluctant to stop and ask for help. Keep the decision and its reason in the appropriate record, with only the access needed by the people doing that work.

Give the process enough staff time

Completion before race day reduces some registration work, but you still need capacity for legitimate exceptions. Build that workload into the operating budget. Include support before the event, the help point, the person reconciling records and the time needed to train staff. A cheaper form provider can leave you paying more for manual corrections.

Here's a fictional workload example, not a staffing recommendation. Suppose your plan allows 24 unresolved entrants to arrive in one hour and each needs five minutes of individual attention. That is 120 minutes of work. Two people provide 120 staff-minutes in an hour only if both work continuously with no interruption. There is no spare capacity for a difficult case, a break or a burst of arrivals.

If those same 24 people arrive in the first 20 minutes, the average hourly calculation hides a queue. Before choosing staffing, test the arrival pattern, space, service times and escalation arrangements against your event. Reduce avoidable problems beforehand, provide a suitable holding area and agree a response when demand exceeds the help team's capacity. Never speed up by skipping a required check.

Run the help process under realistic conditions before the event. Give the team a fictional incomplete entry, a replacement with the old person's screenshot and a participant with a private question. Check whether staff can find the right owner without announcing personal details across the queue. Time the whole resolution, including waiting for an authorised decision, rather than just the moment someone types into the form. Use those observations to revise the operating plan; the arithmetic above is only a starting assumption.

Keep the budget honest about what software replaces. Automatic reminders can reduce repeated messages, while trained people still handle questions and decisions outside the system's scope. Record the actual work during the first edition. Use it when deciding whether to improve the form, change the deadline or add support next time.

The cost of refusing an entry also needs a prepared response. Have the terms and applicable consumer obligations reviewed, identify who decides a remedy and explain how support records the outcome. Staff shouldn't offer different refunds depending on how strongly someone argues. Equally, a blanket no-refunds slogan shouldn't replace the reviewed policy for the actual situation.

Use our guide to choosing event medical cover for the separate provision and response questions. The time spent resolving paperwork doesn't reduce the medical resource the event needs. Keep the medical lead's responsibilities and availability clear so routine registration problems don't consume people appointed for clinical work.

Decide what happens to records after the finish

Once the last wave is home, remove access that was only needed for event delivery. Account for downloaded lists, paper records, shared devices and contractor copies as well as the main system. Tell each person responsible what to return, retain securely or delete under the agreed policy. Closing a dashboard tab doesn't close the record process.

The ICO's storage limitation guidance doesn't prescribe one universal retention period for personal data. It asks organisations to justify retention against their purposes. Agree a schedule with your legal, insurance and privacy advisers that addresses the record types you actually hold, including any relevant arrangements for minors and potential claims.

Keep an active incident or claim from being swept into routine deletion. Follow advice about preserving relevant evidence, restricting access and meeting applicable reporting or notification requirements. Preserve the record as it existed rather than rewriting a completion time or editing a document after the fact. Later explanations should be identifiable additions, with their own author and date.

For medical records, establish the provider's responsibilities and retention arrangements rather than assuming the organizer should receive a complete copy. Customer support may need an outcome or reference for a complaint while clinical information remains with the appropriate provider. Agree the handover before contracting so you aren't negotiating access after an incident.

Review the process using practical evidence. Count unresolved cases, record the reasons and inspect a sample of completed journeys. Look for wrong-person responses, inaccessible pages, confusing instructions, missed transfers and records that couldn't be retrieved. Don't interpret a high completion rate as evidence that the legal wording or course operation was adequate.

Turn the findings into specific changes with named owners. If entrants didn't understand the bypass rule, improve the event description and briefing. If replacements inherited old completion statuses, fix the transfer process. Have the relevant advisers review changes within their scope before the next edition, and keep the new approved version separate from this year's archive.

Run one complete entry through the process before sales open

For the fictional six-person booking, choose one entrant and trace their journey with the team. Show the information available before payment, the participant reference, the document version and the completed action. Then change the entrant, introduce a question and simulate a failed connection. Watch which person takes responsibility at each point.

Ask your lawyer to confirm the reviewed wording and signing method for the actual offer. Ask the insurer or broker to confirm the relevant policy requirements. Ask the course, medical and safeguarding leads to confirm the decisions within their roles. Have registration demonstrate how the resulting instructions appear in the working process, including refusals and unresolved cases.

Give the admissions lead a short operating sheet. It should say what they can verify, what they must refer, who can resolve it and what happens when resolution isn't possible before the start. Keep sensitive details out of that sheet. Put the current document references and contact route where trained staff can retrieve them without searching a public inbox.

Finally, test the explanation with someone who hasn't helped build it. Can they tell you what they bought, what they still need to complete and when they'll be allowed to start? If their answer differs from your team's, fix the page or the process before taking the next booking. That's the point at which you still have room to change the experience people are about to pay for.