Forms people have to sign

Seed article

The structure and the worked example below are settled. The product owner writes the rest. Anything marked TODO needs a real answer before this page ships.

Most leagues ask families to agree to something before a child plays — a statement about risk, a medical release, a code of conduct. Kordnate stores the wording, records who agreed and when, and shows you who has not.

If you are a parent

You were probably sent a link. Open it, read it, and agree at the bottom. That is the whole thing.

You are agreeing to your league’s own wording, not to Kordnate’s. If a line worries you, ask your league — they wrote it and they can explain it. We cannot, and we will not agree on your behalf.

Once you have agreed, you can see it again any time. Nothing expires part-way through a season.

The wording you agreed to is kept exactly as it was on the day you signed. If your league later changes the form, your record still shows the words you actually read — a change made after you sign never rewrites what you agreed to.

Each season is its own agreement. When the next season starts, you are asked to agree again, even if the wording has not changed a word. That is deliberate: a signature says what someone agreed to and when, and last year’s answer is not evidence about this year’s team, this year’s coach, or this year’s risks.

If you run a league

Write a form once, and use it everywhere

A form is one document that belongs to your organization, and you say where it applies. Write your liability wording once and put it on every league you run, every season, instead of keeping a near-identical copy per team and re-pasting it each year.

1. Open Waivers in the sidebar, choose New, and paste in your wording.
2. Open the form you just made and go to Assignments.
3. Choose Assign. Under Applies to, pick League for everyone in a league, or Team for one team.
4. Leave Season empty to mean every season, including ones you have not created yet. Pick a season to limit it to that one.

Repeat step 3 for each place the form applies. Every family who signs up for a team the form reaches has to agree before they can finish.

You do not attach a form to each registration window. A sign-up shows whatever forms reach that team for that season, so a form you assign at league level covers a team you add next month without anyone remembering to go back for it.

Who has not signed

The dashboard shows the count. For the names, open the form itself and go to Outstanding: that is every player the form reaches who has not agreed for the season shown at the top of the screen. Signed, next to it, is the other half of the same question.

Check the season before you chase anyone. The screen shows one season at a time, and because agreements are per season, a parent who is missing from this season’s list may well have signed last season.

TODO — product owner to confirm whether a reminder can be sent from that screen.

What a signed form is, and is not

It is a record: this person, this wording, this date and time.

It is not legal advice, and Kordnate does not check that your wording does what you think it does. Have a lawyer read it once. It is the cheapest hour your league will spend.

What happens when a league moves

This is the question that catches people out, so read it before you move.

A league can be transferred to a different organization. When that happens the signed forms move with it — the record of who agreed, to what, and when is not lost, and you do not have to ask families to sign again.

Worked example. The Riverside Youth Soccer League runs on its own. In June it joins the Riverside Parks Department, which already runs three other leagues on Kordnate.

• 240 families signed the 2026 form in March.
• The league moves in June.
• All 240 signatures come across. Nobody signs anything twice.
• The wording comes across too, exactly as it was in March. It is not replaced by the Parks Department’s wording, because those 240 people did not agree to that.

If the Parks Department wants everyone on its own wording, that is a new form and a new round of signatures. There is no way to make an old signature count for new wording, and there should not be.

TODO — product owner to confirm what admins see about the old wording after a move, and whether both versions stay visible.

Common mistakes

• Editing the wording after people have signed. This is safe now: saving a change publishes a new version and leaves every existing signature pointing at the exact words that person read. What matters is the one question Kordnate asks when you save — does this change what people are agreeing to? Say yes for a real change, and everyone who signed the old wording moves back to your outstanding list to sign again. Say no only for a genuine typo, and they stay signed. The old advice here was “never edit, make a new form”; you no longer have to.
• Assigning the form after sign-ups open. Everyone who signed up in the gap has no form on file, and you will have to chase them one at a time.