For leagues that schedule teams against each other
When a field closes, a game time moves or an officials policy changes, the league makes the call, and it lands on players and families on different teams, their coaches, and the officials who belong to none of them. LeagueBlasts gives the league its own line to each of them, so the call doesn't have to travel coach by coach.
Starts with the registration contacts, coaches and officials you already have, with nothing for anyone to install. Setting up a Hub is free, credits are prepaid and never expire, and there's no subscription and no connector to your league system.
League decision for today: all U12 games at North Park are cancelled; the fields are unplayable. Please don't travel to North Park. Makeups will be posted on the league schedule.
ToU12 DivisionOfficials: the league has cancelled all U12 games at North Park this morning. You're not needed there today. Check the assigning system for any change to your later games.
ToOfficialsThe relay
In most leagues, the people who decide aren't the people who talk to the teams. A decision made at league level goes to each coach or team contact, then into each team's own chat, then to that team's players and families. The path runs once per team, through a volunteer who may be coaching, driving or asleep.
How a league decision usually travels
The same decision often also needs
Each hop waits for someone who is busy with something else.
One decision, retold by each coach in their own words.
A team whose contact didn't see it in time, and officials outside every team chat.
Replies go to the coach, who asks the league, who answers the coach.
Coaches spend the morning forwarding the league's messages instead of coaching.
The problem isn't coaches. It's structural: the league made the decision, but a volunteer on each team is the person delivering it.
This describes how league communication commonly works. It isn't a statistic or a customer story.
Game morning
Illustrative scenario, not a customer story
A Saturday in a made-up league. Nothing here happened to a real organization.
Without the league's own line
With LeagueBlasts
League decision for today: all U12 games at North Park are cancelled; the fields are unplayable. Please don't travel to North Park. Makeups will be posted on the league schedule.
ToU12 DivisionOfficials: the league has cancelled all U12 games at North Park this morning. You're not needed there today. Check the assigning system for any change to your later games.
ToOfficialsTwo sends, each to one audience the league keeps: the U12 Division and Officials. If the affected teams had been in different divisions, the league would send the same words to each team's audience. The Hub never works out which games were at North Park: the league picks the audiences.
Each send goes to exactly one audience. People who connected on Blasts get it there; everyone else gets it as an email from the league's address. Replies come back to the league, not to eight coaches.
The league's call
A league's call is a decision made at league level: not a phone call, and not something the Hub detects. It's what the league decides about fields, times, officials, rules, deadlines and the postseason, and it usually lands on more than one team.
If the league decided it, and it crosses team lines or reaches a neutral league role, it's a call.
U14: Saturday's games at Cedar Field move to the Eastside turf, 400 Mill Road. Game times are unchanged. The updated schedule is on the league site.
ToU14 DivisionThursday's 7:00 game, Red Line vs Night Owls, now starts at 8:15 on Court 2. The updated schedule is on the league site.
ToAdult Coed ThursdayOfficials: the league's heat policy is in effect from Saturday, with a water break each quarter. Details are in the officials' handbook. Your assignments stay in the assigning system.
ToOfficialsCoaches and team contacts: rosters and certifications are due to the league by the 20th, in the league system. Reply here if something is blocking you.
ToCoaches & Team ContactsU10: from this weekend the league is using the new substitution rule for every U10 team. The one-page summary is on the league site.
ToU10 DivisionPostseason games are on the 8th and 9th at North Park. Matchups and times are posted on the league site as the league sets them. Check-in opens 45 minutes before each game.
ToPlayoff TeamsEvery example goes to one audience the league keeps. Templates for these calls, and for weather decisions, registration windows, volunteer needs, safety notices and the season close, are ready in the Hub.
League and team
Teams already talk among themselves, in whatever app or chat each team chose. LeagueBlasts doesn't need to replace any of it. It carries a different kind of message.
Stays with the team
Comes from the league
A coach can still send a team note from the Hub if the league grants it. But the reason a league needs its own line is the second column.
LeagueBlasts isn't a team app, a scheduling system or a results service, and nothing here says team apps or league systems can't send messages.
Across the teams
That's what makes league communication different. The teams compete, so none of them speaks for the others. The officials serve every team and belong to none. The fields, gyms and courts are shared. Only the league stands across all of it.
Each team has its own coach or captain and its own way of talking. None of them reaches the other side of the game.
Officials, and often the field and volunteer crews, work for the league, not for a team.
One field problem can touch several games, and both teams in each of them.
Who the league needs to reach
A new league Hub starts with two audiences
Whole League reaches everyone on your league's list in the Hub, and sending to it asks for a passkey confirmation. Volunteer Opportunities is a list people choose for themselves. Setup puts nobody on it.
Structure the league fills itself, never offered on anyone's preferences page.
Lists people pick for themselves on their preferences page.
The league places people, and they can add more. It suits a division: a family with players in two divisions can add the second.
One send, one audience
Send to the U12 Division and Coaches & Team Contacts, but only the people in both
Create U12 Coaches as its own audience, and send to that.
Filing a team inside its division keeps your audiences organized, and a team you fill by hand only takes people already in the division. A send to the division reaches the people in the division; it doesn't add each team's list to it.
The Hub never knows your schedule, so it never works out who a call affects. The league picks the audience.
Who sends
Everyone who works in the Hub signs in as themselves, and every send is signed with their name.
Leader approval is on by default for leagues. A Leader's message goes out as the league, so an administrator approves it first. Owners and administrators always send directly, so the morning call never waits. A league can turn approval off in Settings.
A Leader reaches only the audiences the league grants them. Sending to Whole League asks for a passkey confirmation.
Email first
Import the registration contacts, coaches and officials who agreed to hear from the league, and they receive its messages by email from the first send.
A communication-only export, the inbound webhook or Zapier makes each person an email subscriber. Adding one address by hand sends an invitation instead.
From the league's own sending address once Settings shows it verified, with nothing to install.
When someone connects on Blasts with the same email address the league has for them, their messages move there on their own.
If a parent connects on Blasts with a different address, that's a separate person in the Hub. Nothing matches the two addresses for you or moves their audiences across.
An attached file, like a field map, reaches people on Blasts only. People receiving by email need a link, so put the map on the league site and link to it.
LeagueBlasts doesn't show you who read a message, and doesn't promise that a call reaches people who aren't on the list. When you need an answer, ask for a reply.
Your league system
Your league system keeps the schedule. LeagueBlasts carries the league's call to both sides of it.
Registration, scheduling and league-management systems stay the authority. There's no connector and nothing is synchronized: the Hub holds only what the league puts into it.
| System | Keeps | LeagueBlasts |
|---|---|---|
| Registration system | Registrations, payments, waivers, eligibility | A communication-only export of contacts, or a webhook for each new registrant |
| Scheduling or league management | Teams, rosters, fixtures, venues, standings, scores, brackets | The league's messages link to it |
| Assigning system | Official assignments and availability | An Officials audience for the league's policies and instructions |
| Facility or permit system | Field and gym reservations | Nothing; the league tells people when a venue changes |
| Team apps and chats | The team's own week | Nothing; they stay the team's |
What the Hub holds
A public calendar link can show up to twelve upcoming items from the next two weeks on the Hub's Home screen, ready to announce. It notices no change, knows no team and sends nothing on its own.
The Hub doesn't know a player's team, a game's time, a field's status or anyone's registration, payment or eligibility, and it sends nothing when the weather or the schedule changes: a person at the league makes the call.
Participant data
In a youth league, the person in the Hub is usually the registration contact: a parent or guardian. In an adult league, it's the player. Either way, the Hub needs only what communication needs.
Leave these in the system that owns them
A communication-only export
Name both the division and the team in the audiences column. An import doesn't add the division for you.
Email, name, household and the named audiences. Every other column is discarded before anything is saved, and the import preview marks it as not stored.
That's how the league import works. It isn't a scan for sensitive data and makes no compliance claim; what the league exports is still the league's decision.
If your export's plain First Name and Last Name columns hold the player's name, the Hub can't know that. Set those columns to not stored in the preview, or export the contact's own name instead.
A division or team the league wants to reach becomes a named audience: the Hub keeps the audience, not the column it came from. The preferences page doesn't ask for birthdays or anniversaries.
LeagueBlasts has no player record, no parent-to-player link, and no medical, waiver or payment field.
Season to season
Every season, teams are rebuilt, coaches change and new team chats start. The league goes on. The audiences and templates the league keeps in the Hub carry over because the league maintains them, not because the Hub knows a season ended.
Rebuilt each season
Kept by the league
Send the thank-you and the next registration date. Archive the team audiences you'll rebuild; the people stay.
Create the new teams, update Coaches & Team Contacts, and move each coach's grant to their new team.
Returning players and families who haven't opted out are already on the list, by email or on Blasts.
The Hub doesn't know when a season starts or ends, or who came back. Those steps are the league's.
Hub Pro
Journeys and Event Campaigns are Hub Pro, which unlocks at $500 in cumulative qualifying Blast Credit purchases.
Starts when someone is added to Coaches & Team Contacts
Coaches change every season, and they're the people who used to pass the league's calls on. The welcome tells each new one what the league now sends directly, and what stays with the team.
It never starts because a coach registered, was assigned a team or a season began. Adding the person to the audience starts it.
Timed around the date the league sets
Opening day is the one date every team, official and volunteer starts from. The campaign sets up how the league's calls will reach them before the first game.
Move the date and the unsent messages move with it. The Hub never detects the start of a season.
A registration window or championship weekend can use the same shape. Matchups and results stay in your league system; the messages link to them.
Pricing
Credits are prepaid, never expire and can come from any legitimate source. There's no subscription and no special league price: LeagueBlasts uses standard pricing.
One typed Blast to one person is one Blasts credit.
One email to one person is one email credit. Every new Hub starts with 50.
A call to one division costs a fraction of the same call to the Whole League.
Journeys and Event Campaigns unlock at $500 in cumulative qualifying Blast Credit purchases.
Illustrative example, not real data
Registration contacts, adult players, coaches and officials in an invented multisport league with youth and adult divisions. The messages are the kind a league sends in an ordinary month; none of it comes from a real league.
if the same 15 messages had each gone to all 1,200 people on the list
| Message | Audience | People × sends | Credits |
|---|---|---|---|
| Weather decision, U12 Division (two Saturdays) | Division | 190 × 2 | 380 |
| Weather decision, U10 Division (two Saturdays) | Division | 170 × 2 | 340 |
| Field change, U14 Hawks and U14 Kestrels (one send to each team) | Team | 15 × 2 | 30 |
| Officials: heat policy, then two field changes | Officials | 40 × 3 | 120 |
| Coaches & Team Contacts: roster and certification deadlines | Coaches | 80 × 2 | 160 |
| Postseason logistics, Adult Coed Thursday | Division | 120 × 1 | 120 |
| Volunteer Opportunities: field-prep crew | Chosen list | 90 × 1 | 90 |
| Whole League: the league note on heat policy and makeups | Whole League | 1,200 × 1 | 1,200 |
| Whole League: next season's registration window | Whole League | 1,200 × 1 | 1,200 |
| Sent to the audiences each call concerns | 3,640 | ||
Counted as typed Blasts, the $100 Plus package covers about 16 months at that invented pace.
Recipients are people. Anyone receiving by email is a recipient too, and uses an email credit instead of a Blasts credit. Package figures come from the current BlastCredits packages.
Getting started
The setup follows the league's own structure. The implementation guide walks through each step.
Sign in, set the timezone, and put the account on a mailbox on the league's own domain, so it survives board turnover.
Divisions first, then the teams inside them, then Coaches & Team Contacts and Officials, set to league assigns.
The contacts, coaches and officials who agreed to hear from the league, with an audiences column naming each division and team.
Administrators for the people who make the league's calls; Leaders for coaches, coordinators and the assignor.
Save the field change and weather decision templates with your schedule link in them.
Implementation guide
How to set up the league's own line: what belongs in LeagueBlasts and what stays with the teams, building divisions, teams and officials, a communication-only export, email first, Leaders and approval, and the first season. It's a page, not a download, and it's open to read now.
No form and no sign-up: the guide is a page, and nothing here asks for your name or email address.
Questions leagues ask
LeagueBlasts is the Blasts Hub for leagues: organizations that schedule teams against each other. It gives the league its own line to the people its decisions touch across every team: players and families, coaches and team contacts, and the officials who belong to no team. The league sends each call, like a field change, a weather decision, a game time or an officials instruction, to the one audience it concerns, by email from the first send and on Blasts for people who connect with the same email address. Your league system keeps the schedule, registrations and results; there is no connector and nothing is synchronized.
No. Teams keep talking in whatever app or chat they already use. LeagueBlasts is the league's own line for the decisions the league makes: fields, weather, game times, officials, rules, deadlines and the postseason. A coach can send to their own team from the Hub if the league grants it, but that's a courtesy, not the point.
No. Your league system keeps registration, rosters, teams, fixtures, venues, official assignments, standings, scores, payments, waivers and eligibility. There's no connector and nothing is synchronized. The Hub holds only the people, audiences and messages the league puts into it.
No. You can add a public calendar link, and the Hub's Home screen then shows up to twelve upcoming items from the next two weeks, ready to announce. That's a display. The schedule itself stays in your league system.
No. The Hub doesn't know your fixtures, so it can't tell that a game changed or who it affects. A person at the league makes the call and sends it to the audience it concerns: a division, each team, or Officials.
No. It doesn't monitor weather or field conditions and never cancels anything on its own. The league decides, and the Hub carries the decision.
No. The Hub has no venue or fixture information. If the same people are always at one venue, the league can keep an audience for it; otherwise the league sends to the division or to each team affected.
Yes, if the league invites them as a Leader and grants them an audience, usually their own team. A Leader sends only to the audiences granted to them and reads only those replies.
By default, yes. Leader approval is on for leagues because a Leader's message goes out as the league, so an administrator approves it first. Owners and administrators always send directly. A league can turn approval off in Settings.
Yes. Create Officials, set it to league assigns and fill it yourself. Grant it to the referee assignor as a Leader if they should send to it. Officials never see it offered on a preferences page, and nobody else can add themselves to it.
Yes. A division set to Either can hold the teams filed inside it. When you add people to a team yourself, only people already in the division can be added. Filing is organization: each audience is still its own list.
It reaches the people in the division. Filing a team inside a division doesn't add the team's list to the division. An import can place someone on a team without the division, so name both in the audiences column.
No, and they shouldn't. Teams are set to league assigns, so they never appear on anyone's preferences page. People choose only lists the league offers as a choice, like Volunteer Opportunities or a division set to Either.
Yes, when the league sets divisions to Either: the league places the family in one, and the parent can add the other on their preferences page. Unticking removes only a division they chose themselves; a placement the league made stays until the league removes it.
A communication-only export: each contact's email address, their own name, a household name if two guardians registered the same player, and an audiences column naming the divisions and teams you already created. Every other column is discarded before anything is saved.
No. Leave medical information, allergies, medications, emergency contacts, waivers, payment status, eligibility, dates of birth, school, grade and IDs in the system that owns them. The league import discards those columns anyway, but don't send them in the first place.
No. The person in the Hub is the communication contact: in a youth league usually a parent or guardian, in an adult league the player. There's no player record and no parent-to-player link.
The Hub can't tell that it's the player's name, so it would keep it as the contact's name. Set that column to not stored in the import preview, or export the contact's own name instead.
No. Everyone on the league's list receives by email from the first send. People who choose to connect on Blasts with the same email address receive there instead.
That's a separate person in the Hub. The audiences the first address is in don't move to the second, and the first address keeps receiving by email. Nothing matches the two addresses for you.
No. An attached file reaches people on Blasts only. For people receiving by email, put the field map or policy on the league site and link to it.
No. LeagueBlasts doesn't give the league a list of who read a message. When the league needs an answer, it asks for a reply; replies come back to the league in Conversations.
No. A YES or NO reply is counted against the league's most recent YES/NO message from the last three days, so two questions in the same weekend mix their answers. Availability belongs in the team's app, official assignments in your assigning system, and volunteers are confirmed by a person replying.
STOP stops everything and removes the person from every audience, including the teams, Coaches & Team Contacts and Officials the league placed them in. START turns messages back on, but it doesn't put them back in those audiences; the league adds them again.
A Journey sends a short sequence to each person from the day they enter one audience. The league starter is the Coach & Team Contact Welcome, on days 0, 2, 5 and 10 after someone is added to Coaches & Team Contacts. It never starts because a coach registered or a season began.
The league's Event Campaign starter: messages timed around the opening-day date the league sets, two weeks before, a week before, two days before, the morning of, and the day after. Move the date and the unsent messages move with it.
Hub Pro, which adds Journeys and Event Campaigns, unlocks at $500 in cumulative qualifying Blast Credit purchases. Sending, audiences, roles, replies, Content Series and email are there from the start.
No. LeagueBlasts uses standard pricing. Setting up a Hub is free, and one typed Blast to one person is one Blasts credit; one email is one email credit.
No. LeagueBlasts uses standard pricing. BlastCredits reviews nonprofit verification separately, on its own criteria, and this site makes no claim that a league is eligible. Verification never affects access to the Hub or Hub Pro.
Set up your league's Hub, build your divisions, teams and officials, and send the next call from the league.
Already have a Hub? Sign in