Fundraising Event Team Signup template
Collect a team's interest in a fundraising event through one captain. This form records the team name, expected size, participation approach and support needed from the organizer. It avoids collecting everyone else's personal details and does not accept payments or confirm individual registrations.
8 questions · Free plan: 500 responses/month · fully customizable
- Editable cover artwork
What’s inside
The questions this template ships with — rename, reorder, or delete any of them in the builder.
When to use this template
- Organizing teams for a community fundraising challenge
- Collecting team plans before confirming event participation
- Coordinating approved materials and instructions through a captain
Tips to get more from it
- Count the captain in expected team size so organizers use one convention.
- Request one response per team and explain how a captain should report changes.
- Keep team interest separate from individual registration, attendance and money raised.
Use one captain as the coordination contact
Ask the captain to supply their own contact details and describe the expected group size. If the event later needs each participant to register, let the organizer provide the appropriate individual process. A captain's entry should not be treated as consent or acceptance on behalf of every member.
The integer field prevents fractional team sizes and requires at least one person. It does not enforce event capacity or reserve places. Review the expected size against the event's actual arrangements before confirming participation.
Confirm the team's plan before sharing materials
Review how the team wants to take part and what support it requests. The organizer can then provide current instructions and approved fundraising materials. If the approach involves something outside the planned event, clarify responsibilities and suitability before encouraging the activity.
Track team registration, individual participation and funds received in separate records. This form does not create a fundraising page, collect pledges or verify the amount raised. If the captain changes the team size or plan, reconcile the update rather than counting the team twice.
Example response and next steps
Illustrative example, not a real customer submission.
A neighborhood team wants to take part in a community walking event.
- Team name
- Riverside Walkers
- Expected team size including the captain
- 6
- What organizer support would help?
- Event instructions and approved fundraising materials.
How to use the response
Confirm the event arrangements with the captain and explain any individual signup steps. Record six expected participants, not six confirmed attendees or a verified fundraising total.
Before publishing your version
Replace event instructions, test rejection of zero and fractional team sizes, and confirm how updates will be handled. Keep the ending clear that participation still requires organizer confirmation.
Questions people ask
Does this register every team member individually?
No. It records team interest through the captain. Individual registration or other participation steps are separate.
Can teams collect donations through this form?
No. It has no payment field or fundraising total. Use an appropriately configured donation flow for payments.
Does expected team size reserve places?
No. It is a planning number for the organizer to review. Capacity and participation confirmation happen separately.
Go deeper
Related templates
Shifts, preferred roles, t-shirt size, and prior experience.
Record an intended donation amount, currency, timing and designation without collecting a payment.
Explore a sponsorship that makes sense for your organization and the event community.
Better forms.
Better data.
Start with a conversation, a document or a single page. Unlimited forms and 500 responses per month on Free. No card required.