It’s two weeks before opening day, and the director has a spreadsheet open with a column of names highlighted yellow. These are the families whose waivers never came back. The registration form was filled out months ago — names, birth dates, sessions, payment. But the liability waiver and the medical-treatment authorization went out as a PDF packet in a separate email, with instructions to print, sign, scan, and return. Most families did. The highlighted ones didn’t, and now the director is sending the third reminder, fielding replies about broken printers, and matching the scanned pages that do arrive to the right camper by hand. The registration looked done in the fall. The paperwork is still being chased in June.
That gap — between a registration that’s submitted and one where the required forms are actually signed and on file — is the subject of this piece. It’s a normal part of camp registration software, and it’s where a lot of pre-season work hides. The fix is to stop treating the documents as a separate errand and collect them inside the registration itself.
The paper trail that lives outside the registration
The duct-taped version has a recognizable shape. The registration form collects the answers. Then a PDF packet — waiver, medical authorization, photo release, a page of policies to initial — goes out by email. The parent prints it, signs it, scans or photographs it, and emails it back, or faxes it if the camp still has a fax line for exactly this reason. Someone at the camp opens each returned file, figures out which camper it belongs to, files it in a folder, and crosses the family off a list maintained by hand.
Every step in that chain is a place the process leaks. A family that means well forgets. A scan comes back rotated, or missing the second page, or signed in the wrong spot. A returned waiver gets filed under the parent’s name when the camper has a different last name. And the list of who’s outstanding is only as accurate as the last time someone reconciled it against the inbox. None of this is anyone’s fault — it’s the structure. The signature lives in one place, the registration in another, and the director is the connective tissue holding the two together by hand.
Waivers signed inside the registration flow
The alternative is to make the documents part of registration rather than a thing that happens after it. In Camp Runner the registration includes a documents-and-waivers step. The parent reaches it as one screen in the same multi-step flow that collected the camper’s details — the same flow described in online camp registration forms that don’t fall apart at scale — and works through the camp’s waivers in line.
Each waiver is its own item with its full text shown for the parent to read. The liability waiver, the medical-treatment authorization, the photo or media release, the policy acknowledgment — each appears as a document to review and sign. The parent reads the terms, enters their legal name, signs by drawing or typing a signature, and confirms agreement to the terms. The signature is recorded against that camper’s record as part of the registration. There’s no second email, no print step, no scan to match later. The document that used to come back as an attachment in June is signed on the spot in the fall.
Each waiver also carries a required-or-optional flag. A required waiver is one the camp won’t run without; an optional one — a photo release a family can decline — is offered but not forced. The step shows the parent which is which, and marks each waiver signed or not signed as they go, so nobody is guessing what’s left.
A registration that isn’t finished until the required forms are signed
Here’s the part that retires the yellow spreadsheet. Because the required waivers are a step inside the registration, the registration carries them forward as part of being complete. In Camp Runner the documents-and-waivers step won’t advance to review and payment until every required waiver has been signed. The parent can’t sign the easy ones and skip the medical authorization; the step holds until the required set is done.
The effect, from the director’s chair, is that “registered but missing a waiver” stops being a state you have to police. The families who reach the end of registration reached it by signing what the camp requires along the way. You’re not building a list of who’s outstanding, because the flow doesn’t leave required waivers outstanding to begin with. The signatures arrive attached to the campers they belong to, in the same submission that created the registration — which is the difference between the documents living on the record and the documents living in your inbox waiting to be filed.
This is the same principle that makes returning-family and sibling registration less work: when a thing is captured once, in line, on the record, it isn’t something you reassemble by hand later.
Required uploads and documents that expire
Not every required document is a signature. Some are files the family already has — an immunization record from the pediatrician, an insurance card, a completed physician’s form. These belong on the camper record too, attached rather than emailed, so a health coordinator opening a camper’s file finds the immunization record where they’d expect it instead of searching a shared drive for a photo a parent texted in March.
And some of those documents go stale, which is its own quiet problem. An immunization record or an insurance card is only good until it isn’t. Camp Runner’s document library stores an expiration date on a document and tracks where it stands: valid, expiring soon when it’s within thirty days of lapsing, or expired once the date passes. A document also carries a category — medical, legal, form, policy — and keeps its version history when a newer file replaces an older one. The practical payoff is timing. Instead of discovering on day one that a camper’s record lapsed over the winter, the camp sees the expiring-soon warning ahead of the season and asks the family for the current copy while there’s still time to get it.
The director stops being the filing system
Pull the threads together and the shift is the one that runs through all of this. The waivers and required documents shouldn’t be a separate errand bolted onto the side of registration — they should be part of the registration, signed and uploaded in line, attached to the camper record, and visible where the rest of the system already reads. The liability waiver is signed during the flow that created the registration. The immunization record is uploaded to the camper instead of emailed to you. The expiring insurance card raises its hand before camp starts rather than during it.
That’s the version where the director runs the season instead of running the filing. The two weeks before opening day go to coaching counselors and confirming logistics, not to a third reminder email about a printer. The paperwork was never separate from the registration, so there’s nothing left to chase.
Join the waitlist to build next season’s registration with waivers and required documents collected in line — and if you’d rather see the flow first, the registration features walk through it end to end.
Common questions
- Why collect waivers during camp registration instead of mailing a packet?
- A mailed packet separates the signature from the registration, and that gap is where the work lives. Some families never print, sign, scan, and return the pages, so you spend the weeks before camp chasing them. The ones who do return them arrive as loose attachments you match to campers by hand. Collecting the waivers inside the registration flow removes both problems — the signature happens in line and attaches to the camper as part of the same submission.
- Which documents can a camp collect during registration?
- Two kinds. Documents a parent signs — the liability waiver, a medical-treatment authorization, a photo or media release, and policy acknowledgments — are presented as a signing step in the registration flow. Documents a parent uploads — an immunization record, an insurance card, a physician's form — are files attached to the record rather than emailed separately. Both end up on the camper instead of in your inbox.
- Can a parent finish registration without signing the required waivers?
- In Camp Runner the documents-and-waivers step marks each waiver as required or optional, and the step won't advance to review and payment until every required waiver is signed. A parent reads each document, signs it, and the signature is recorded against the camper record before they move on. That means 'registered but missing a waiver' stops being a state you have to track down after the fact.
- How does a camp track documents that expire, like immunization records?
- Some required documents carry an expiration date — an immunization record, a certification, an insurance card. Camp Runner's document library stores an expiration date on a document and flags it as expiring soon within thirty days of that date, or expired once it passes. Instead of finding out mid-season that a record lapsed, you see the warning ahead of time and ask the family for the current one.
- Where do signed waivers and uploaded documents end up?
- On the camper record and in the camp's document library, not in an email folder or a shared drive. A signed waiver attaches to the camper it was signed for. An uploaded document lives in the library with its category, version, and expiration. Because they're stored where the rest of the system reads, a missing or expired document surfaces on its own instead of being something you reconstruct from a spreadsheet.
