1. Start with the right fundraising model
For standard ticketed launches, a normal event draft is enough. For a cause-led event where proceeds or positioning depend on a beneficiary organization, use the beneficiary-aware flow and complete the nonprofit details before publish.
Beneficiary events are stricter than ordinary launches because the beneficiary organization may need to approve the relationship before the event can be published.
2. Collect the beneficiary data early
In advanced event settings, add the beneficiary organization, contact details, estimated costs, and message while the event is still in draft. That avoids a late publish failure after the rest of the event is already ready.
If you are collaborating across multiple organizations, settle host ownership and revenue expectations before you invite outside collaborators or sponsors.
Checklist
- - Beneficiary organization selected
- - Contact email and message completed
- - Estimated costs reviewed before submit
3. Treat sponsorships like operational commitments
Sponsor reservations follow the same trust model as attendee reservations: for still-confirming events, payment is only captured if the launch reaches its goal by the deadline.
Once the event is confirmed, sponsor flows can advance into the normal charged state. Use /dashboard/sponsorships and related event views to monitor reserved, confirmed, and expired sponsor activity.