Push notifications for Canadian club members: what to send and what to leave out

Canada edition. This guide is written for volunteer-run clubs in Canada. Where rules differ — grants, tax, incorporation, safeguarding — follow the Canada-specific pointers below or check with your national body.

The first week a club switches on push notifications, everything goes out. The training venue has changed: push. The raffle closes on Friday: push. Someone in the parents' chat has posted a photo of a lost drink bottle: push. A sponsor's café has two-for-one coffee: push. By the third week a parent who never asked for most of it has found the switch in their phone's settings, turned notifications off for the club, and moved on. The next push sent to that phone is the one saying Saturday's game has moved grounds, and nothing happens.

Nobody did anything wrong here except treat push like a megaphone. A push notification lands on a lock screen beside messages from family and alerts from the bank. It is the most personal channel a club has, and the permission behind it can be withdrawn in one tap and is rarely given back. The clubs that keep that permission use push sparingly, for things that are about the person holding the phone, and they hand members the controls rather than making them choose between everything and nothing.

This guide is for whoever sends club messages — a secretary, a registrar, a comms volunteer — and for a committee deciding whether to point members at an installable club app at all. It covers a three-question test for what earns a push, what to send and what to leave out, when to ask members to switch notifications on, how per-category settings keep the channel alive, and what to tell members honestly about delivery. Which channel suits which kind of message is covered in our guide to choosing a channel for club updates, and how an installable web app compares with a store app is in native app vs web app for clubs. This one is about using push well once you have it.

Why push is the channel members switch off first

Email can be ignored politely. A newsletter nobody opens costs the reader nothing; it sits in a folder until they have a minute. A push notification can't be ignored politely. It lights up the screen, sometimes makes a sound, and asks for attention now. Each one spends a little of the goodwill that made the member say yes in the first place.

Three things make that goodwill expensive to lose:

• Refusal is sticky. Once someone blocks notifications for a site, the browser stops asking. Getting them back means the member finding the site's own settings in their browser or phone and changing it by hand, which almost nobody does.
• The worst message decides. Members don't average their experience. One irrelevant push at 10pm does more damage than ten useful ones do good.
• Muting is all or nothing unless you offer something better. If the only control a member has is the phone's own switch, the only way to stop the coffee offers is to stop the ground changes too.

Treat push as a budget, not a megaphone. Every push should be one the member would be glad to have received, even when the news is bad.

The three-question test

Before anything goes out as a push, run it past three questions:

1. Is it about this person? Their team, an event they are going to, a duty they signed up for, a channel they belong to. "The club" is not a person.
2. Does it change what they do in the next day or two? Where to be, when, whether to come at all, or something they need to act on.
3. Would they be annoyed to find out later? A cancelled session they drove to, a duty reminder they never saw, a monthly donation that quietly stopped.

Two yeses and it earns a push. One yes and it belongs in an email or on the website. None, and it belongs in the newsletter, if anywhere.

The test is deliberately strict because it gets applied by volunteers in a hurry. "Is this about them, does it change their plans, would they mind finding out late" is quick enough to ask on a Friday night, which is when most club messages get sent.

What to send, and what to leave out

Two patterns sit underneath the table. First, almost every "yes" row is something the member chose: an event they follow, a duty they took, a team they follow, a channel they joined. That's no coincidence. A push that follows a member's choice feels like a service; one that follows a committee decision feels like marketing.

Second, the "no" rows aren't unimportant, they're just not urgent. The newsletter matters. It doesn't matter at 7:42 on a Tuesday evening.

Ask at the moment it makes sense

Most clubs ask for notification permission in the least effective way available: a message to everyone saying "download our app and turn on notifications!" with no reason attached. The members most likely to act on it already read everything. The ones you most need to reach delete it.

Ask when the member has just done something that makes notifications obviously useful:

• They've just followed an event or a venue. "Want to hear if this changes?" is an easy yes.
• They've just signed up for a volunteer duty. A reminder beforehand is a favour, not an intrusion.
• They've just joined a team chat. The coach's "running ten minutes late" message is the reason they joined.
• They're standing in front of you. Registration day, the first training of the season, the club barbecue. Installing the app and switching on notifications takes a minute with someone showing how, and a great deal longer from written instructions.

Two practical details trip people up often enough to plan for:

• iPhones need the app installed first. On an iPhone or iPad, web push only works for a site that has been added to the home screen and opened from its icon. Switching notifications on from a Safari tab does nothing. Show members the order: Share, then Add to Home Screen, then open the app from the new icon, then switch notifications on.
• Each device is separate. Turning notifications on for a phone does nothing for the same member's tablet or laptop. A member who wants alerts in two places switches them on in both.

Say what members will get before they tap allow. "We'll only notify you about events you follow, your volunteer duties and your team chat, and you can change that any time" is a promise members can hold you to, and it's the sentence that earns the yes.

Let members choose, one category at a time

The biggest single thing a club can do to keep push alive is let members turn off one kind of notification without losing the rest. A parent who wants to know when the game moves, but not about every chat message, should be able to say exactly that.

That means settings organised by kind of notification, with a separate choice for each way of receiving it:

• By category. Event changes, event reminders, volunteer duties, chat, and so on. Members already think in these terms.
• By channel. The same category might suit a push for one member and an email for another. A grandparent may want event changes by email only; a team manager may want them by push as well.
• A very short always-on list. A few messages a member shouldn't be able to mute: a security alert, a change to their role, a failed payment, a scheduled account deletion. Keep that list short and say why each item is on it, because an "always on" category that turns out to be a raffle reminder is how members stop trusting the whole screen.

Then tell members where the settings are, in the same breath as telling them how to switch push on. People mute what they can't adjust.

How ClubHelix handles it

In ClubHelix the club website is the app. Members install it from their account page (or, on an iPhone, through Share and Add to Home Screen) and it opens full screen with the club's name and colour. There is no app store listing, and it works on every plan.

Notification settings live under My account → Notifications: a table with a row for each kind of notification and three columns — Email, In-app and Push — with a tick box in every cell. At the top sits Enable push on this device, which a member taps once on each phone, tablet or computer they want notifications on, and the browser then asks for permission. Once a device is switched on, the Push box starts ticked for every category, so the member's job is to untick what they don't want rather than hunt for what they do. A handful of rows are ticked and locked: role changes, security alerts, payment failures, scheduled deletions and messages from your governing body.

Chat is shaped so it can't flood anyone. In-app chat notifications collapse to one per channel while it's unread, rather than one per message, and chat email goes out at most once an hour per person. Members who follow an event or a venue hear about changes, new events at that venue and a reminder beforehand, through whichever of the three columns they've left ticked. On a team page, Get live-score notifications lets a member follow that team's scores as they're entered.

What a member sees when they tap

A notification that opens the club's home page has wasted the member's tap. The link should take them to the thing the notification is about — the event, the duty, the chat channel — and, where possible, to the exact spot on that page.

In ClubHelix the push, the email and the in-app notification all carry the same link. A volunteer duty notification opens the volunteer page and scrolls to that duty in the member's upcoming duties, with a brief highlight so the eye lands on it. A failed monthly donation opens the member's account page at that donation. Other notifications open the page they're about.

Signed-in members also get a notification bell in the club site's header. Each notification shows an icon for its kind, and clicking anywhere on one marks it read and opens its page. The badge counts every unread notification, not just the ones on screen; the panel lists the newest twenty and says so ("Showing 20 of 45") when there are more. Members can mark one read or clear it, or use Mark all read and Clear all. Two honest limits: there is no full-page notification inbox beyond that panel, and the bell shows what had arrived when the page loaded, so a new notification appears on the next page load rather than live.

Be honest about delivery

Push is quick, but not instant and not guaranteed. Members who understand that won't treat it as the only place important news lives, and neither should the committee.

• It takes minutes, not seconds. Delivery runs through the phone platform's notification service and can be held back by battery saving or a focus mode. In ClubHelix, pushes are also gathered and sent in batches, so they arrive within minutes of being sent rather than the moment you press the button.
• There's no read receipt. You can know a notification was sent to a device, not that anyone looked at it.
• It only reaches members who installed and allowed it. However well the rollout goes, some members never will. They still need the email, and everyone needs a page that holds the detail.

So a push should always be the alert and never the record. "Saturday's game has moved to the other ground, details on the event page" works. A push that is the only place the new venue is written down does not. The club communication plan sets out the full ladder of channels, and the wet-weather communication plan walks through the morning it gets tested.

A first-season rollout

1. Write the push rule on one page. "We send push notifications for event changes and reminders, volunteer duties and team chat. We never send them for sponsor offers, newsletters or general club news." Publish it where members will see it, and put it in the committee handover pack.
2. Decide what the club will actually use. List the kinds of notification you expect members to receive, so the "what you'll get" promise is true on the day you make it.
3. Pick an install moment. Registration day or the first week of training, with one volunteer at a table showing people how, and a second pair of hands for iPhones.
4. Post the steps. A short news post with the Android and iPhone steps, and where the settings live, for everyone who wasn't there.
5. Hold the line for a month. The pressure to push "just this once" arrives in week two, usually about a fundraiser. Say no and email it instead.
6. Ask, then adjust. After four weeks, ask a handful of members what they've muted and why. If the same category keeps coming up, you're sending too much of it.
7. Review at the end of the season. Keep what worked, drop what didn't, and update the one-page rule before the next volunteer inherits it.

Frequently asked questions

Can a club website send push notifications?

Yes, once a member has allowed notifications for it. In most Android and desktop browsers a member can switch them on straight away; on an iPhone or iPad the site has to be added to the home screen and opened from its icon first. Nothing needs to be published to an app store, because the club's website is the app.

How many push notifications is too many?

There's no magic number, but there is a reliable warning sign: members receiving pushes about things that aren't theirs. If a member gets a push for a team they don't play in, an event they aren't going to or a sponsor promotion, the club is sending too many, whatever the count. Keep push to what a member chose to follow and the volume looks after itself.

Can we send a push notification to every member at once?

Not as a push-only blast in ClubHelix. Push rides on things the club already does, such as an event change, a chat message or a duty reminder, and reaches the members involved who have push switched on for that kind of notification. A message for the whole club belongs in an email and on the website, where every member can find it.

Why isn't a member getting notifications on their iPhone?

Almost always because they're using the site in Safari rather than from a home-screen icon. iPhones and iPads deliver web push only to a site that has been added to the home screen. Ask them to add it, open it from the new icon, and then switch notifications on from their notification settings.

Can a member turn off every notification?

Everything except a short list of messages that must always get through: security alerts, changes to their role, failed payments, scheduled deletions and messages from a governing body. Every other kind of notification can be switched off channel by channel, so a member can keep event changes as a push while taking everything else by email, or not at all.

Do push notifications replace email?

No. Push is the tap on the shoulder; email is the record. Keep formal notices, newsletters and anything members may need to find again in email and on the website, and use push to tell the right people that something about their plans has changed.

---

ClubHelix turns your club website into an installable app on every plan, with notifications for the events members follow, their volunteer duties and team chat, and a settings page where each member decides what reaches their phone. Team chat and volunteer rostering start on the Standard plan — see pricing.