What should a youth sports registration form collect?

The player

• Full legal name, and the name they actually go by if those differ. The scoreboard and the roster want different things.
• Date of birth. Not the age. Age changes; a birthday does not, and age group eligibility is a birthday window.
• Grade or school, if you place by grade rather than age, and only then.

The adults

• One parent or guardian with a phone number and an email address. This is who you contact.
• A second emergency contact who is not that person, with a phone number. This is the one that matters at 7pm on a Tuesday when a child is hurt and the first number rings out.
• Who is allowed to collect the child, for younger age groups. Some leagues need this and some do not. Know which you are.

Medical

• Allergies and conditions a coach must know about, in a free text box. Asthma, diabetes, epilepsy, severe allergies.
• Permission to seek emergency treatment.
• Physical exam date, only if your league or insurer requires one and you will actually check it.

Keep medical questions narrow. You are asking what a coach needs in order to keep a child safe for ninety minutes, not taking a medical history. The more you collect, the more you are responsible for storing properly.

Practical

• Shirt or uniform size, as a dropdown, never free text. The bulk order is the single most common reason a season starts badly.
• Returning player or new, if it changes how you place them.
• Preferred division or level, where families genuinely choose.

Agreements

• A code of conduct acknowledgment for the player and, more usefully, for the parent.
• Photo permission, with a real way to say no that you then honor.
• The liability waiver. This is a signature, not a checkbox, and is worth treating separately.

Anything your system already holds. If a family account already carries the parent's phone number, asking again gets you two versions that disagree and no way to know which is current.

Height and weight, unless your sport genuinely places by them. For most sports it is a number nobody uses and a question that makes a self conscious eleven year old's parent uncomfortable.

Card numbers. Never. Payment goes through a payment processor so the card never touches your form, your inbox or your spreadsheet.

Social security numbers, full addresses you will not mail anything to, employer details, and anything else you are collecting out of habit. Every field you store about a child is one you are responsible for.

Open ended questions you will not read. "Is there anything else we should know?" is a good question only if somebody is going to read all four hundred answers.

The difference between a form you can work with and one you cannot is usually the answer type, not the question.

Use a fixed list wherever the answers are knowable. Shirt sizes, divisions, practice night preferences. Free text answers cannot be counted, sorted or filtered, so a shirt size question asked as free text turns into an afternoon of cleaning up Medium, med, M and Mens M before you can place the order.

Keep options consistent across programs. If your fall and spring forms offer different size labels, you cannot compare seasons.

Give every question a short column name for export. "Shirt" beats "What size shirt does your player wear?" as a spreadsheet heading, and you will be looking at that spreadsheet more than at the form.

For a typical youth league, this is close to the minimum that works, and most organizations would do well to stop here:

1. Player legal name and preferred name
2. Date of birth
3. Parent or guardian name, phone, email
4. Second emergency contact and phone
5. Allergies or medical conditions a coach must know
6. Permission to seek emergency treatment
7. Shirt size, from a list
8. Returning player, yes or no
9. Code of conduct acknowledgment
10. Photo permission
11. Liability waiver signature

Eleven items, of which the family already knows ten without looking anything up. That is a form that gets finished on a phone.

The player's name and date of birth sit on the player profile, and the parent's contact details on the family account, so neither is asked twice. The profile also has optional height and weight fields, which is where those belong if your sport needs them. Everything else is a question you add to the program's own form, choosing from short text, long text, a date, a dropdown, radio buttons, checkboxes or an agreement checkbox.

See how to build your registration form for the mechanics, and the free player registration form template if you would rather start from paper.