Golf day entries arrive as texts, emails and phone calls, each with a different detail missing. I would rather every captain answer the same questions once, so the tee sheet starts from a clean list.
Before the form opens
I decide how many groups the course can host and which tee waves I can offer. Then I set max_responses to that number of groups and close_at to the entry deadline. I share one link in the invitation email, on the club page and at the front desk.
While it is open
A captain registers a whole group of up to four golfers. They add names, a rough handicap, a preferred tee wave, a cart plan and any side contests they want to join. They also say how many will stay for dinner, with dietary needs, and tick a box if their company would like to sponsor a hole. A captain's AI could ask "Who is playing in your group?" Then "Which tee wave do you prefer?" Then "How many stay for dinner?" It shows the answers and sends only after a yes. Learn about agent-fillable forms.
After the deadline
Download the CSV, build the tee sheet by wave and handicap, send the caterer the dinner total and call the sponsors. This form does not book tee times or email captains, so confirm times by message yourself. Planning other events? Browse forms for sports clubs and teams and forms for events. A general tournament registration form suits team sports, and a plain RSVP form suits the prize dinner.
Questions
Can I limit the number of groups?
Yes. Set max_responses to the number of groups the course can host. Each captain submits once for the whole group, so the cap counts groups, not golfers.
How do I plan dinner numbers?
Download the CSV and add up the dinner_count column. The dinner_dietary_needs column lists every dietary request for the caterer.
Does the form take payment for entries or sponsors?
No. It does not handle payments or card details. Send invoices or collect fees your usual way, and use the hole sponsor box to see who to call.