Waiver & Risk Management Tracking

Most colleges require every club sports athlete to sign a liability waiver before their first practice (an assumption-of-risk form, sometimes an emergency medical consent, occasionally a separate one per sport if someone plays on more than one team). The waiver itself usually isn't the hard part; your university's risk management or student affairs office has a form. The hard part is knowing, in week twelve, whether the new walk-on from week five actually has one on file, and finding it in about ten seconds when someone official asks.

One thing up front: this is about tracking waivers, not creating them. Nothing here drafts legal language, provides legal advice, or replaces whatever signature process your university or club already requires. What it solves is the part that has nothing to do with the law and everything to do with organization: knowing who signed what, when, and whether it's still current.

What actually needs to be on record

A usable waiver record needs four things, and a folder of scanned PDFs usually has none of them attached to each other:

1. Who: tied to the person, not just sitting in a folder named after them.
2. What type: a general liability waiver and an emergency medical consent are different documents; don't collapse them into one "on file" checkbox.
3. When it was signed, and if it expires, when.
4. The document itself, or at minimum a reference to it, so "on file" means something you can actually pull up.

Two kinds of waiver types: what your school requires, what your club requires

Not every waiver is club-specific. Some are the kind every club at your school needs (a general assumption-of-risk form from the university), and some are specific to your sport (a form for a contact sport that a non-contact club wouldn't need). A workable system should let you use the common ones without recreating them for every club, and add your own on top when your sport genuinely needs something else: set up once by an officer, available to the whole roster after that.

Not every waiver needs an expiration date. A one-time liability waiver signed at the start of someone's time on the team is often good indefinitely. A medical consent tied to a specific season might not be. Decide this per waiver type, not per person: consistency here is what makes the "who's expiring soon" view actually mean something.

Recording a waiver, including the ones you collected on paper

The realistic workflow is rarely "everyone digitally signs through the app." It's more often: a captain collects paper forms at the first team meeting, or a link to the university's own e-signature system, and then someone has to go log that it happened. A good system should let a manager record a signature on a teammate's behalf, not just their own, because that's how it actually happens in practice, and it should visibly mark those entries as staff-recorded so it's clear who actually filled it in.

Attach the document itself when you have a scan or a photo of it. A signed form that exists but isn't attached to the record is a form someone has to go dig up later; a PDF or photo attached directly to the waiver record is one that answers "can I see it" immediately, held privately rather than sitting in an inbox or a shared drive folder anyone can browse.

Knowing who's covered and who isn't, at a glance

The view that actually matters to an officer isn't "here are all our waiver records," it's the roster, cross-referenced against what's missing or expiring. Every active member, every waiver type they should have, and a clear status for each: current, expiring soon, expired, or nothing on file. That last one, nothing on file, is the state that matters most and is the easiest to lose track of in a spreadsheet, because a spreadsheet only shows you rows that exist.

Be clear-eyed about what a status badge does and doesn't do: it's information for an officer to act on, not an automated gate that blocks someone from practicing. If your club's policy is that an unwaived player doesn't participate, that's still a human decision your staff has to make and enforce: the system's job is making sure nobody has to guess who's missing one.

A related but separate thing: certifications

Waivers aren't the only compliance document a club sports team tracks. Coaching certifications, CPR/first-aid cards, officiating certifications: these track differently (they usually have an issuing organization and a reference number, and they usually do expire) but the underlying idea is the same: who has it, is it current, and can you prove it. If your club has certified coaches or safety officers, it's worth tracking those the same way you track waivers, as a related but distinct record.

What this replaces, and what it doesn't

It replaces the shared drive folder nobody can search, the "I think I have it somewhere" text message, and the officer transition where the new treasurer inherits a Google Drive link that half-works. It does not replace your university's actual waiver requirements, insurance coordination, or legal counsel on what your waiver language should say. Talk to your risk management office about that part. This is the part after the form exists: making sure it's signed, current, and findable.

How TeamBasin handles this

TeamBasin tracks waivers as roster-scoped compliance records, the same pattern it uses for certifications, not as a document generator or e-signature tool.

• Two-tier waiver types. Common types are available to every team out of the box; a club can add its own sport-specific ones on top, with expiry tracking turned on or off per type.
• Staff can record on a teammate's behalf. A captain who collected paper forms can log them for the whole roster, and each entry is marked when it was staff-recorded rather than self-reported.
• Real document attachment. A signed PDF or a photo of a paper form attaches directly to the record, held privately and viewable only through a short-lived, access-controlled link, never a public file.
• A team compliance view, not a spreadsheet. Every active roster member, every waiver type, with a status of current, expiring within 30 days, expired, or nothing on file, so the gap is visible before someone asks about it.
• No e-signature, no drafting, and we're upfront about that. This is a tracking log for something that was signed somewhere else: through your university's process, on paper, however your club actually handles it.

If your club's waiver records currently live across three people's inboxes and one shared drive folder, request access and we'll show you what a real compliance view looks like.