Free guide, nothing to fill in

The DirectToParents School Year Guide

How to set up school-to-parent communication so that every message lands with the people it concerns. Written for the person who will actually build the audiences, grant the coordinators and send the 5:30 a.m. message: a principal, an office manager, a communications lead or a technology coordinator.

For a public, private, charter or independent K-12 school, or a small district running more than one campus.

1. Start from what your school already knows

Before anything technical, write down the messages your school sent last year and who each one actually concerned. You will find four or five shapes and almost nothing else: the whole school, a division or grade, a route, a team or activity, and news somebody might want. That list is your audience plan. The Hub does not work it out for you and does not need to, because you already have it.

2. What belongs in DirectToParents, and what does not

It is for the thing that changed today and the thing that closes this week: closures and delayed openings, dismissal and pickup changes, a route running late or changing its stop order, a trip returning behind schedule, a cancelled practice, a moved rehearsal, a chaperone call, a form or fee deadline, and the notice families need now.

It is not for the handbook, the newsletter, the report card, the long explanation or the archive. Those stay in email and your portal, where people can go back and find them. And it is not for anything that has to be the official record: attendance letters, required notices and anything retained belong where they already are.

3. The whole-school audience, and why it should be rare

All Parents & Guardians reaches every adult connected to or subscribed with your school. Grant it only to the people who should use it, usually the principal and the office. A school that sends everything to everyone teaches families to skim, and then the one message that mattered gets skimmed too. Use it for closures, early dismissals, and the handful of notices that genuinely concern every family.

4. Structural audiences: the ones your office assigns

These are your school's own shape, so you create them by name and you fill them.

  • One per division, and one per grade. Name them the way families say them: Lower School, Grade 5.
  • One per classroom you actually message, not all of them, just the ones that send.
  • One per bus route, from the route list transportation already keeps.
  • One per team and per activity that communicates with families.
  • One for the after-school programme, from the enrolment list the office holds.
  • One for Staff, which you create yourself and set to the school assigns so it is never offered to a parent.
  • One for any combination you genuinely send to, such as Grade 5 Soccer, because a single send cannot combine two audiences.

5. One send, one audience

Every message goes to exactly one audience. There is no combining audiences, no excluding one and no rule that works out who fits. A parent of a Grade 5 student who plays soccer is in Grade 5 and in the soccer team's audience, and receives each of those messages separately. When a message genuinely concerns the combination, create Grade 5 Soccer as its own audience and fill it.

Inside audience files one audience under an open audience, one level deep, to keep a long list tidy. It is organization, not delivery: when you add people to the inner audience yourself only people already in the outer one are accepted, but people can join audiences in other ways too, so always send to the audience you mean.

6. Open interests: the ones a parent picks

Onboarding offers four that any school has: Athletics News, Arts & Activities News, School Events and Volunteer Opportunities. They appear on each person's preferences page and in Blasts, and people opt in themselves.

Keep them distinct from your structural groups. Athletics News is for anyone who wants to know how the season is going; the parents and guardians of the varsity roster are a different list, which you build and assign. Conflating the two is the most common way a school ends up sending a practice cancellation to four hundred people.

7. Who may send, and to what

The decision that matters is which audiences each person may send to and read replies from. Owner holds billing and the Blasts account, and should be a mailbox on the school's own domain so it survives a staffing change. Admins reach everything and manage the team. Coordinators (the transportation office, the athletic director, activity and arts leads, grade and campus leads) are granted specific audiences, ticked one at a time. Viewers read along.

Leave leader approval off unless you need it. A new school Hub starts that way on purpose: the person who learns the away game is cancelled should be able to say so at one o'clock. Turn it on where several coordinators share the channel and you want the tone held.

8. Rolling out by email first

The fastest way to a working channel is not an app campaign. Upload the CSV export of the opted-in parent and guardian contacts your school already keeps, where email is the only required column and each row is one adult (leave every student column out, and never include a student's date of birth), confirm they agreed to hear from you, and everyone on it can receive from you by email from your first send, with nothing to install. Addresses added by hand get an invitation instead.

Then offer the connection where families already read: the enrolment confirmation, the back-to-school letter, the first-day folder, the office counter, the open-house table, the pickup-line sign. Print the connection kit from the Hub. People who use Blasts will connect over the following weeks, and when they connect with the same email address their delivery moves there on its own; you keep one list throughout.

9. Enrolment: the code, the request, and auto-accept

Entering your school's code in Blasts creates a connection request that you accept under People who want to connect. During enrolment season turn on auto-accept so requests connect as they arrive, and turn it off afterwards if you would rather look at each one.

Auto-accept and leader approval are different settings that happen to live near each other. One is about who may join; the other is about who may send. Changing one does not change the other.

10. Two guardians, one home

Each adult connects as themselves, so a home with two guardians is two people with two sets of preferences. Usually that is exactly right. Where one copy is genuinely enough (a fee notice, a fundraising note), group them as a household on the person page and tick One per household on that message. It applies to Blasts delivery; anyone on email still receives their own copy.

It is a delivery convenience and nothing else. It records no child, no custody arrangement and no decision about who may receive school information or collect a student. Those stay with your systems and your process.

11. New Family Welcome

Set the five-note sequence up once on an audience you keep for new parents and guardians: where school messages come from, arrival and dismissal, choosing what you hear about, where the calendar and answers live, and their own control. A Journey runs on one audience, and each person starts it when they enter that audience after you activate it; choose to start it only for people who join from now on. It never starts because a student enrolled, a record changed or the year began, because the Hub knows none of those, so nothing in the sequence names a grade, a child or a date.

12. Back-to-School Night, and the rest of the calendar

An Event Campaign carries six messages around one date: the save-the-date, how the evening runs, a short reminder, the evening before, the morning of, and resources and follow-up the next day, written for everyone whether or not they came. Set the date once and move it if you must; unsent messages move with it, and someone who connects halfway through gets only what has not happened yet.

For the rhythm rather than the event, use a Content Series: write a term of week-ahead notes in one sitting and let them go out on schedule. That one is included from the start.

13. Beside your systems, not on top of them

Keep enrolment, attendance, grades, assignments, lunch balances and payments where they are. There is no connector to a student information system, a learning platform or a parent portal and none is planned; contacts reach the Hub as a CSV export, through the inbound webhook or through Zapier, and none of those creates a grade, a route or a team or works out who belongs in one.

The bridge is a person. Somebody at your school reads one of those systems, or simply knows, and writes the message. That is the whole integration, and it is the one that has never broken.

14. The student-data line, in one paragraph

The Hub holds adults and the audiences they are in. It holds no student record, no parent-child relationship, no attendance, grade, assignment, timetable, class list, route membership, lunch balance or medical detail. Keep student-level facts out of message bodies where you can and out of the Hub entirely as data. Import adults only: never a student's name, grade or date of birth as a column, because a birthday column is read as the adult's own. No FERPA or COPPA claim is made for this channel and nothing here satisfies a statutory notice, records-retention or accessibility obligation, so check anything that touches student records or privacy with your own counsel and your district's policy.

15. Ask for an answer

Do not build a follow-up plan around whether people have seen a message: DirectToParents gives you no reader list to work from, and email has no read signal at all. A message is not an acknowledgement and not proof that anyone was notified.

When you need an answer, ask for a YES or NO reply; the Hub counts the replies people send themselves. Ask one question at a time: if two messages asking for YES or NO go out within a few days, a reply counts against the most recent one. For anything that must reach every family, keep the call tree you already have.

16. Measuring whether it is working

Not by open rates. By whether the front desk stops answering the same question forty times, whether the drop-off lane is empty on a delay morning, and whether a coordinator sends their own cancellation without asking anyone. Those are the things that change first.

A first year, in order

The first two are setup. The rest is the rhythm.

  1. A summer afternoon Build the structure

    Sign in, finish onboarding, and create your divisions, grades, classrooms, routes, teams and activities. Add any combination you really send to, such as Grade 5 Soccer, as its own audience. Create Staff and set it to the school assigns.

  2. Before enrolment opens Bring the adults in

    Upload the opted-in parent and guardian contacts (adults only, no student columns), then Bulk assign them into the audiences you built. Invite the office as admins and your coordinators with their own grants. Save the closure, dismissal-change and deadline messages as templates.

  3. Enrolment and back-to-school Publish the connection

    Code and QR into the enrolment confirmation, the back-to-school letter and the first-day folder; kit on the office counter and the open-house table. Turn on auto-accept. Send a short welcome to All Parents & Guardians explaining what will come this way and where to set preferences.

  4. The opening weeks Use the precise audiences first

    Resist the whole-school send. Let the first ten messages be a grade, a route, a team, because that is what teaches families these messages are worth opening. Start the week-ahead Content Series.

  5. Through the year Let the people who know send

    Coordinators run their own cancellations and changes. The office runs deadlines and dismissal changes. The principal keeps the whole-school sends. New families arrive through the webhook or a re-import each term.

  6. Spring and year end Deadlines, then the clean sweep

    Short runs of reminders to the grades a deadline applies to. Top up credits before winter weather. At year end, send the thank-you with next year's first day, then archive the grades you will rebuild. The connections stay, so returning families are reachable in August.

Messages worth writing before you need them

Save these as templates and fill the brackets. Ask for a YES or NO reply where noted; that reply is the family's own.

Closure or delayed opening, to All Parents & Guardians

[School] is [closed / opening [n] hours late] on [day] because of [reason]. Buses run on the same delay and breakfast is not served. [What happens to after-school care.] We will send the plan for [next day] by [time].

Early dismissal, to All Parents & Guardians (YES / NO)

[School] dismisses at [time] today because of [reason]. Buses run [n] hours early. Reply YES if your usual pickup plan still works, or NO if it changes, so the office can plan.

Bus route change, to one route

[Route]: starting [day], [what changes]. [New times or stop order]. Everything else on the route stays the same. Reply here if that creates a problem for you.

Division or grade notice, to one division or grade

[Division or grade] families: [what is happening] on [day]. [Details]. This one is just for [division or grade]; nothing changes for anyone else.

Trip or deadline, to one grade

[Grade]: [form, fee or trip] is due [day]. [How to complete it]. Reply here if you need help or more time and we will sort it out.

Team or activity change, to one team

[Team or group]: [what] on [day] is [cancelled or moved] because of [reason]. [New details]. Questions go to [role] on this thread.

Volunteer call, to Volunteer Opportunities (YES / NO)

We need [n] more [chaperones / helpers] for [what] on [day], [time] to [time]. Reply YES if you can come and [role] will follow up with what to bring.

School event, to School Events or one division

[Event] is on [day] at [time], [where]. [What to expect, parking, doors]. [How to be in touch with a question.]

What it does, and what it does not

  • Sends a typed message, with formatting, links and images, to the one audience a person picks. Files attached to a Blast reach people on Blasts only.
  • Sends that message by email, without attachments, to everyone in that audience who is still an email subscriber.
  • Lets a parent or guardian belong to as many audiences as apply, each one a separate list the school maintains.
  • Counts the YES or NO replies that parents, guardians and staff send themselves.
  • Limits a message to one copy per grouped household on Blasts delivery when you tick it on that send.
  • Lets each coordinator reach only the audiences you granted them, with every send attributed.
  • Hold any student record: no enrolment, attendance, grades, assignments, timetables, class lists, route membership or lunch balances.
  • Know a parent-child relationship, a custody arrangement or who is authorised to collect a student.
  • Connect to a student information system, a learning platform or a parent portal, or populate any audience for you.
  • Combine, intersect or exclude audiences in one send, or work out who belongs in any audience.
  • Replace your emergency procedures, your official notification or anything your district requires. There is no emergency badge, priority or routing.
  • Promise that a message is delivered or read, or give you a record of who was notified.
  • Translate what you write, or send SMS. This is Blasts plus email; there are no mobile numbers to collect.
  • Gate anything on this guide. Any school can sign in and set up a Hub today.

Hub Pro unlocks at $500 in cumulative purchases for any organization and adds Journeys and Event Campaigns. A nonprofit school can apply for bonus credits on BlastCredits; that only adds credits and never unlocks anything.

Ready when you are

DirectToParents is open today. Sign in to your Hub, or set one up through onboarding after signing in; setting up is free, and sending uses prepaid credits. The Hub documentation covers everything in this guide in more detail, in school terms.

See it in action at Asterfield Academy (a fictional example organization created to show the product, not a customer)

Product facts on this page reflect published Blasts.app information as of September 24, 2026.