Start with the dates families need to decide
Before publishing a season schedule, map the dates that affect a family’s decision: school breaks, holidays, likely conflicts with other activities, the first and last program days, and any planned closures. You may not be able to avoid every conflict, but identifying them early helps families decide whether the commitment is workable.
Set a registration window with a clear opening date, a decision deadline, and a date when you will confirm the season plan. For example, a community program might open registration six weeks before the first session, send a reminder midway through the window, and tell families when they can expect a final confirmation. Those are planning choices, not universal rules: choose timing that gives your team enough time to prepare and families enough time to compare schedules.
State what families are committing to: recurring days and times, the location, the season’s start and end dates, and which dates will not have sessions. If details are still tentative, label them as such and say when you expect to confirm them. Keep the information in one place, such as a season page or message linked from your program resources, rather than making families assemble it from multiple announcements.
Make transportation part of the schedule
A session time is only useful if families can get there. When selecting a time, consider the full trip: school dismissal, pickup, travel, parking or drop-off, and the return journey. Ask a few families about likely constraints before finalizing the schedule, and make it easy to reply without sharing unnecessary details about a child.
Be precise about arrival and departure expectations. Instead of writing “after school,” give the start time and explain when participants should arrive. If pickup happens at a different time from the activity’s end, spell that out. Identify the correct entrance or meeting point and name a contact route for day-of questions. Do not promise transportation support unless it is actually arranged.
A practical decision is to publish a transportation note with the schedule: “Please arrive between 3:45 and 3:55 p.m. at the east entrance; pickup is at 5 p.m. from the same location.” Adjust the example to match real arrangements. Share only information families need. Avoid placing children’s personal details, travel routines, or contact information in public posts.
Set a reminder rhythm families can rely on
Reminders work best when they answer a question or prompt a useful action. Decide what families need to know at registration, before the season starts, and during the season. A simple rhythm could include a registration confirmation, a pre-season message with the schedule and arrival instructions, and a reminder before each session if your team can maintain it.
Use consistent timing and wording. A reminder should include the date, start and end times, location, what to bring if anything, and the right way to report a change or ask a question. If there is nothing new, avoid sending messages just to fill a schedule. Families can miss important updates when routine messages become noisy.
Choose a communication process your team can reliably carry out. The ONWARD Playbook is a youth program operating system and family program discovery concept; this planning approach does not assume that any particular reminder, messaging, or registration feature is available. For operational planning ideas, see program operations. Keep child information private: limit access to family contact details, use appropriate channels, and do not expose participant lists in group messages or public updates.
Agree on a weather plan before the forecast changes
Weather decisions are easier when families know the rule in advance. Decide who assesses conditions, when the decision will be made, how families will hear about it, and what happens if a session is canceled or moved. The right approach depends on the activity, setting, and local conditions; do not rely on a vague promise to “update everyone if needed.”
For example, a program might tell families that it will post a cancellation decision by a stated time using its usual communication channel. If sessions can move indoors, name the alternate location and explain when that option applies. If there is no suitable alternate, say whether the session will be canceled and how families will receive the revised calendar. Avoid guaranteeing that every weather disruption can be rescheduled.
Keep the contingency message short and direct: what changed, which session is affected, what families should do, and when they can expect another update. Make sure staff know who is responsible for sending it and that the chosen channel reaches the enrolled families. Do not ask families to monitor several channels for the same decision.
Use a short season-readiness check
Before opening registration, review the plan from a caregiver’s point of view. Can someone quickly find the dates, commitment, location, arrival and pickup instructions, contact route, and weather policy? Is it clear what is confirmed and what remains subject to change? Can staff deliver every reminder and update promised?
**Checklist:** • Publish the full season calendar, including known breaks and closures. • Set registration opening, deadline, and confirmation dates. • Confirm the schedule works with realistic arrival and pickup needs. • Name one reliable route for routine messages and urgent changes. • Write the weather decision process before the season begins. • Remove unnecessary child or family details from shared materials.
Then ask one caregiver who was not involved in planning to review the information and point out anything unclear. Make the corrections before registration opens. For more planning context, browse program insights. Your next action: draft a one-page season calendar and have your team verify every date, instruction, and contingency against the arrangements you can actually support.
COMMON QUESTIONS
Frequently asked questions.
GO FURTHER
