A party book fundraiser offers sign-up parties that families can book to support their school. A good launch helps families answer three questions quickly: which event fits, what a ticket includes, and how to book. Work through this checklist before the announcement goes out, then keep it as the start of your coordinator handover.
Confirm each event
- The host has reviewed the final description and date.
- The intended audience or grades are clear.
- Start/end time and time zone are correct.
- The ticket unit, price, capacity, and inclusions agree.
- The public location description is sufficient for deciding whether to attend.
- Private addresses and contact details are shared only through the appropriate access process.
- Host responsibilities, supplies, expenses, and venue arrangements are agreed.
- Cancellation, date-change, and minimum-enrollment terms are settled where applicable.
- The host knows who handles attendee questions.
Use the ticket-unit examples to check ambiguous family or couple tickets.
Rehearse the family experience
- Open the exact school link from the planned announcement on a phone.
- Check any browsing-code instructions.
- Find an event appropriate for a specific audience.
- Explain what one ticket covers without asking the organizer.
- Complete the approved test booking flow and locate its confirmation.
- Check the sold-out/waitlist explanation.
- Verify the coordinator contact route.
- Confirm paid booking readiness with the financial owner before accepting money.
Treat a rehearsal as a chance to find confusing details. A test reservation and a real payment are different checks.
Prepare the launch day
- Confirm the sales opening date, time, and time zone.
- Choose the school’s approved announcement channels.
- Assign one coordinator to handle first-day questions.
- Check that the public catalog shows the intended parties.
- Make sure each sold-out event has a clear next step.
- Keep a simple question log so you can improve the explanation once for everyone.
Copy: launch announcement
Replace the bracketed fields before sending.
Subject: Explore [school]’s party fundraiser—signups open [date]
Our community’s new party collection is ready to explore. Families have offered [two or three actual examples] to support [approved purpose].
Browse the collection at [school catalog link]. Signups open [date, time, time zone]. [Include the school’s access-code instructions if needed.]
Each listing explains the audience, date, price, and what one ticket includes. Please check those details before booking. Questions? Contact [coordinator contact].
Thank you to the hosts and volunteers bringing this collection together.
Copy: available-spots reminder
Subject: A few ways to join the fun at [school]
There are still places available at [specific events with verified availability]. Browse the current collection at [school link] for the latest details.
If your preferred party is full, check its waitlist instructions. A waitlist request does not guarantee a place. For questions, contact [coordinator].
Check availability immediately before sending. Do not create urgency around a deadline or ticket count that has not been verified.
Leave a useful handover
At the end of the collection, save a short record for the next chair:
Collection and dates:
Organizer and financial owner:
Where authorized records and account access are managed:
Host recruitment timeline and templates used:
What families asked most often:
Changes to make next time:
Financial reconciliation and unresolved items:
Next collection’s first decision and owner:
Store account access through the school’s approved process; do not put passwords or private family records into a public handover guide.
Next: use the complete party book guide for your next collection, or the two-week fall planning guide for a seasonal schedule.