Waivers
Writing waivers, the version history every save creates, and what a family can sign or decline.
A waiver in Dojo Tiger is a document, not a signature record. You write the text once; families sign it during registration; and the app keeps a numbered version history so you can always answer "what exactly did this parent agree to, and when".
Studio then Waivers is the screen. Write your waivers before you hand out your registration link — a family who registers before a waiver exists is never asked to sign it.
Creating a waiver
Add Waiver
Studio then Waivers → Add Waiver.
Title and body text
- Title — what the family sees as the heading, e.g. "Liability Waiver", "Photo and Media Release". Up to 200 characters.
- Waiver Body Text — the full text, up to 50,000 characters. Plain text: paste it straight out of the document you use today. Line breaks are preserved exactly as you type them; there is no bold, no headings and no formatting.
Create Waiver
It appears in the list marked Active, at v1.
Add as many as you need. Most studios have one or two; a liability waiver and a photo-release are the common pair.
The list
Each row shows the title, an Active or Inactive badge, and the current version number.
| Control | What it does |
|---|---|
| Up / Down | The order families sign them in. Saved immediately. |
| Edit | Opens the waiver's own page — text, version history, and the save that creates a new version. |
| Deactivate / Activate | Takes the waiver out of, or back into, the registration flow. |
Deactivating does not delete anything. The waiver stops being presented to new registrations; signatures already collected against it stay on file and stay visible on the registration and student detail pages. It is the right way to retire a waiver you no longer use.
There is no delete button for a waiver.
Versioning: every save is a new version
This is the part that surprises people, so it is worth being precise.
Saving always creates a new version
Pressing Save New Version on a waiver creates version n+1 and makes it the current one — every time, whether you rewrote three paragraphs, fixed a typo, or only changed the title and left the body untouched. The app does not compare the old text to the new text.
The editor says as much before you save: "Saving will create a new version. Existing signatures are tied to previous versions."
What that means in practice:
- Signatures never move. A parent who signed v1 has signed v1 for ever. The record on their registration reads "Liability Waiver (v1) — signed by …" with a timestamp and the IP address it came from.
- New registrations sign the current version. From the moment you save, everyone signing is signing v2.
- Nobody is asked to re-sign. There is no bulk "everyone must re-sign the new version" action, and no report of who is on an old version. If a legal change genuinely requires existing families to re-sign, you have to ask them directly.
The Version History list at the bottom of the waiver's page shows every version with its date, and marks which one is current.
Draft outside, paste in
Because there is no way to save a work-in-progress without publishing it as the live version, write and edit long waiver text in a document, and paste the finished version in. One save, one version.
What a family actually does
During registration, after the intake form, the family is shown each active waiver in your display order, one at a time:
- the full text in a scrollable box;
- a Type Your Legal Name to Sign field;
- I Agree & Sign, and Decline.
Decline is a real option. Choosing it asks "Are you sure? You can still proceed without signing this waiver" and needs a second press to confirm. A declined waiver is recorded as declined, with the same timestamp treatment as a signature — it is not the same as an unanswered waiver.
A family that declines still completes registration. Nothing in the app blocks a student with an unsigned or declined waiver from being enrolled, appearing on the attendance sheet, or checking in at the kiosk. Enforcing a waiver is a front-desk policy, not a software gate.
Where signatures show up
| Screen | What it shows |
|---|---|
| Students then Registrations | The row's status — Waivers Partial when some are done, Waivers Complete when all are. |
| A registration's detail page | The Waiver Signatures card: each waiver, its version number, signed or declined, the typed name, the date and the IP address. |
| A student's detail page | The same signature list, gathered from all of that student's registrations. |
A studio with no active waivers skips the signing step entirely, and registrations arrive already at Waivers Complete.
Recording a paper waiver
If a family signed on paper — most of your existing roster, most likely — the manual student form can record it. On Students then Students → Add student, the Record paper waiver card lets you tick which waivers were signed, and enter the date, the signer's name, their relationship and a note.
Those go on file as signatures against the version that is current now, marked as recorded in person rather than online. See Adding students by hand and in bulk.
Common questions
| Question | Answer |
|---|---|
| Can I see everyone who has signed a given waiver? | No. Signatures are viewed per registration or per student, not per waiver. |
| Can I upload a PDF? | No. Waivers are plain text typed or pasted into the app. |
| Can I require a waiver before someone trains? | Not in software. Nothing is blocked by an unsigned waiver. |
| Does changing a waiver notify anyone? | No. |
| Can a family re-sign later? | Only by going through your registration link again, which creates a second registration. |
Last reviewed