Running Club Waiver Template: What Yours Must Cover
A running club waiver template is only as strong as what it covers. Here is what belongs in yours, who has to sign, and how to keep signatures current.

Most clubs solve the waiver problem in about fifteen minutes. Somebody searches for a running club waiver template, finds a PDF, pastes the club name at the top, drops it into the signup form, and never thinks about it again.
Two years later that club has three hundred people on the roster, a Saturday run that draws forty, and no way to tell you whether the guy who rolled an ankle last month ever signed anything.
That is the real problem, and it is not a wording problem.
What should a running club waiver cover?
A running club waiver should name the specific risks of group running, state that the participant knowingly assumes them, release the club and the individual people who lead it from liability, confirm the runner believes they are physically fit to participate, and carry a dated signature from every participant, guests included, before they run a step with you.
That is the document. Everything below is about the part clubs actually get wrong, which is almost never the wording.
One thing up front. This is operational guidance from people who build software for club organizers, not legal advice. State law varies a great deal on what a liability release can do. Have a lawyer licensed in your state read your final document before you rely on it.
Why this matters more now than it did two years ago
Strava's 2026 Community Report found that running club creations rose 3.5 times year over year through the back end of 2025, and club-organized events rose 1.5 times over the same period, as reported by Running Lookout on May 9, 2026.
Translate that into your parking lot. There are more clubs than there were two years ago, hosting more organized runs, and more of the people who show up on a given Saturday have never been to your club before. Paperwork built for a twelve-person crew of friends is now covering forty people, six of whom the run leader has never met.
The five parts of a waiver that actually do work
1. Assumption of risk, written for running specifically. Traffic and intersections. Uneven pavement, curbs, and trail surfaces. Loose dogs. Heat, cold, and weather exposure. Darkness and low visibility. Collisions with other runners. The plain fact that no medical or emergency staff is on site. A generic template is weakest exactly here. Specificity is the entire point of this section.
2. Release language that names the humans, not just the club. Most templates release "the Club" and stop. The people who tend to get named in a complaint are the officers, the run leaders, and the volunteer sweeping the back of the pack. Your release should name the club, its officers and directors, its run leaders, its volunteers, and anyone acting on the club's behalf. If you founded the thing, that clause is partly about you.
3. A medical fitness declaration and an emergency contact. This does two jobs at once. The declaration is the participant affirming they believe they are fit to do this. The emergency contact is the operational half, and it is the one that matters at 7:40 on a Saturday when someone goes down at mile four and a run leader is standing there with a phone. Most clubs collect that number somewhere completely different from the waiver, or never.
4. Photo and media consent. Nearly every club posts group photos every single week. Nearly no club ever asked. One short paragraph covers it.
5. Signature, date, and a parent or guardian line for minors. An undated signature is close to worthless, because you cannot tie it to a specific run or a specific membership year. For minors, a parent or guardian signs, and be aware that in many states a parent cannot fully waive a minor's own future claim. That is one more reason the lawyer review is not optional.
Who has to sign, and how often?
The Road Runners Club of America requires member clubs to obtain waivers of liability from their members and participants during the join or renew process, and states plainly that all guests to club training runs or programs must sign a waiver as well.
So the schedule looks like this:
- Members sign at join, and again at every renewal.
- Guests sign before their first run. Every guest, every time, including the friend of a member who showed up once.
- Event participants sign for club-owned races and events.
- Minors need a parent or guardian signature.
The guest rule is the one clubs break, for a very human reason. It feels unwelcoming to hand a stranger a legal document ten seconds after they introduce themselves. But the guest is precisely the person with no relationship to the club and the least reason to give you the benefit of the doubt if something goes wrong.
The annual renewal is worth more than it looks. It is the one moment each year when your roster and your waiver file get re-synced, so the people you think are members and the people who have signed something recent become the same list.
Why the file matters more than the template
RRCA advises clubs to keep a file of waivers based on their state's statute of limitations for a civil lawsuit, with access to waivers going back at least two to three years or more.
Now hold that guidance up against how your club actually stores things. The waiver lives in a Google Form export. The roster is a spreadsheet one volunteer updates when they remember. Attendance is a thumbs-up emoji in GroupMe. Dues are in Venmo. Photos are on somebody's phone. None of those systems know that the others exist, and none of them were designed to produce a specific document about a specific person on demand.
That is the honest weakness of the default club stack. No single tool is bad. A signed waiver simply has nowhere to live where it stays attached to the person who signed it.
Here is the test, and it takes ten seconds to fail. Pick one member who joined about fourteen months ago. Could you produce their signed waiver right now, by yourself, in under ten minutes, without texting another volunteer? Most club founders cannot, and they usually discover this on the worst possible day.
The Saturday morning problem
Picture the parking lot. Forty runners, six of them brand new. The run starts in ninety seconds. Somebody is holding a clipboard.
What happens next is always the same. The run leader says "grab a form from me after," the group goes out, and afterward half of it turns social and nobody grabs anything. Even when it works, you have six pieces of paper in a tote bag in a trunk, unsearchable forever. Paper does not scale past about a dozen people, and it fails the retrieval test on day one.
What good looks like is boring and structural: the signing happens at RSVP time, before anyone is standing in a parking lot, and the signed record attaches to that person's member record rather than living on its own. Once it is attached, your roster and your waiver file stop being two different lists that drift apart.
That is a system-of-record question, and it is the piece most clubs are missing. RunLink puts the club roster, the event RSVPs, and the member record in one place, so a club's records about a person sit together instead of scattering across five apps. You still need a lawyer to write your waiver and a policy about who signs and when. You also need somewhere for that policy to live.
Where to get a template you can start from
Start with RRCA rather than a random PDF from a search result. RRCA publishes waiver templates for member clubs and event directors, written with running in mind, which puts them ahead of most of what is floating around.
One nuance is worth knowing before you copy anything. For events on federal land, such as National Park Service or Forest Service property, you may not be permitted to use a liability waiver at all. Federal land managers generally allow an acknowledgement of risk, which describes the inherent risks and lets the participant assume responsibility for their own safety, while a release of liability or indemnification agreement is not permitted. If your club runs trails in a national park, that form may need to be a different one.
Either way, treat anything you download as a draft. It is a starting structure, not a finished legal document, and the parts that matter most are the parts you customize to your actual runs. If you are earlier in the process and still setting up the club itself, the paperwork sequence makes a lot more sense in the context of starting a running club, and we covered the insurance side of this in more detail in our post on running club insurance requirements.
Questions clubs actually ask about waivers
Do guests really need to sign? Yes. RRCA is explicit that all guests to club training runs or programs must sign a waiver, not only dues-paying members.
Does a digital signature count? Electronically signed records are generally valid, and a timestamped digital record is usually easier to produce later than paper. Confirm the specifics with counsel in your state.
How long do we keep them? At least two to three years per RRCA guidance, and longer where your state's civil statute of limitations runs longer.
We are not an RRCA club and we have no insurance. Do we still need waivers? Your exposure in that situation is higher, not lower. Collecting waivers is also a requirement for using the RRCA Insurance Program, so if you ever want that coverage, the habit needs to already exist.
Does a waiver mean we cannot be sued? No. Anyone can file. A waiver is one layer, alongside insurance, sane run-leader practices, and route choices that do not send forty people through an unlit intersection at 5:45 a.m.
The part worth remembering
The template is the easy half. You can have a good one by the end of today.
The half that takes actual work is the process around it: every guest signs before they run, members re-sign at renewal, and every signature lands somewhere you can retrieve it in under ten minutes, two years from now, without help.
If your club records currently live in six places, that process cannot exist, no matter how good the document is. RunLink gives your roster, your events, and your member records one home, so the operational habits you build around them have something to hold on to. Club setup is free.
Related Posts
Running Club Payment Processing Without the Mess
Running club payment processing, explained: when to start charging dues, how to collect them, and the reconciliation work nobody warns you about.
How to Manage a Run Club That Got Too Big
Your run club outgrew its systems. How to manage a run club that got too big, split the run, hand off work, and keep the culture that made it grow.