A paper sign-up sheet gets lost in a kit bag, and a group chat buries the dates under photos. Two families bring oranges, and nobody brings water. I would rather collect the dates in one place and read them as a list.
How it works
- A parent gives their name, email and their child's name.
- They choose a game day and, if they like, a backup date.
- They say what they will bring, and how many children it will feed.
- They tick that the snack has no nuts. They can add an allergy note for the team.
A short chat with a parent's AI
"Which game day suits you?" Then "What will you bring?" Then "Does your snack contain nuts?" The AI shows the answers, asks "Send it?" and submits only after a yes. Learn more about agent-fillable forms.
Good to know
The form takes sign-ups. It does not lock dates, so check the CSV once a week and reply to a second family on the same day. For a strict one family per date, create one form per game day and cap it with max_responses.
Coaches who run a whole season can pair this with a team registration form. A school class can use the same idea, and a parent consent form pairs well when parents must also give permission. Browse forms for sports clubs and teams and forms for schools and teachers.
Questions
How do I stop two families picking the same date?
The form does not lock a date once it is taken. Sort the CSV by the snack_date column and message the second family, or make one form per game day with max_responses set to 1.
How do families see the final schedule?
You read the responses as CSV, then send the final schedule to the team yourself, for example in your usual group message. The form does not email families.
Why is the nut free box required?
Every family sees the rule before they send. If your team has no allergy rule, remove that field, or change its label to match the rule you do have.