Signal-to-Noise in 2026: How Sports Organisations Fight Information Overload

# Signal-to-Noise in 2026: How Sports Organisations Fight Information Overload

"I think it's a signal to noise problem, broadly speaking, in our world."

That observation—made during a conversation about why volunteers miss critical communications—cuts to the heart of the engagement crisis facing peak sporting bodies.

It's not that volunteers don't care. It's that they can't hear you over the noise.

The Noise Problem

Let's paint the picture of a typical volunteer administrator in 2026.

They're the secretary of their local football club. They work full-time. They've got kids. They volunteer roughly 14 hours a week across club duties.

Their communication channels include:

• Work email (200+ messages per day)
• Personal email (another 50+ per day)
• Club email (shared inbox, 20-30 per day)
• WhatsApp groups (multiple, constant notifications)
• Facebook groups (club-related and personal)
• Instagram (following club and personal accounts)
• LinkedIn (professional updates)
• SMS (family, friends, club urgent messages)
• Slack/Teams (if they work for a larger organisation)
• Various apps with push notifications

Every channel is screaming for attention. Every sender thinks their message is the most important.

Now add the peak body.

The peak body sends:

• Compliance reminders (insurance, registration, safeguarding)
• Policy updates (need-to-know information)
• Deadline notifications (financial reporting, grant applications)
• Opportunity announcements (workshops, funding, resources)
• General updates (season fixtures, rule changes, news)
• Surveys (feedback requests, data collection)
• Event invitations (conferences, meetings, networking)

All via email. All marked important. All competing for attention in an inbox already drowning in noise.

The volunteer doesn't see 90% of it. Of the 10% they see, they can't process it all. Of what they process, they can't remember what requires action versus what was FYI.

And then we're surprised when compliance rates are low.

Why "Send More Reminders" Makes It Worse

The natural response when volunteers miss communications: send more reminders.

Send the initial email. Send a follow-up a week later. Send a final warning three days before the deadline. Send a post-deadline escalation.

Four emails instead of one.

This doesn't improve signal-to-noise. It amplifies noise.

Now the volunteer sees:

• Four versions of the same message (which one is current?)
• Escalating urgency language (creating panic, not clarity)
• Competing priorities (are all four deadlines equally critical?)
• Guilt-inducing subject lines ("FINAL REMINDER" creates anxiety, not action)

Peak bodies track open rates, see they're low, and conclude: "We need more touchpoints."

That's treating the symptom, not the cause.

The cause is signal-to-noise ratio.

The Notification Fatigue Indicator

One feature in the new TidyConnect announcement system caught our attention during a demo: Notification Health.

It tracks how many communications a peak body is sending to clubs and flags fatigue risk.

Green: You're communicating at a sustainable level. Yellow: Watch for signs of fatigue—clubs may start tuning out. Red: You're overcommunicating. Expect declining engagement.

The formula accounts for:

• Total volume of communications
• Frequency over time
• Type of communications (tasks vs. announcements)
• Acknowledgement requirements (how many things demand action)

It's a forcing function.

Peak bodies can't just blast more emails and hope for the best. The system explicitly signals: you're creating noise, not signal.

"It's like the signal-to-noise ratio," as one team member explained. "It shows you if you're sending too many emails or notifications—watch out for fatigue signs."

Most organisations don't have this feedback loop. They send until someone complains (which volunteers rarely do—they just disengage).

TidyConnect makes fatigue visible.

The 20/80 Insight: Tasks vs. Announcements

PFL discovered something critical when they analysed their 100+ tasks from last season.

Only 20-30% actually required action.

The rest? Information that clubs should know but didn't need to do anything about.

Season fixture released. Policy updated. Workshop opportunity available. New resource published.

Important? Yes. Requiring action? No.

But when everything gets packaged as a "task," volunteers treat it all the same: overwhelming.

The breakthrough was taxonomic.

Tasks: Things clubs must do by a deadline. Compliance items. Sign-offs. Submissions. Things with consequences if missed.

Announcements: Things clubs should know. Updates. Resources. Opportunities. Information.

Same content. Different framing. Dramatically different cognitive load.

When volunteers open their portal and see:

• 5 tasks (clear deadlines, clear actions, clear consequences)
• 25 announcements (read when relevant, no action required)

They can process that.

When they see 30 tasks, all marked urgent, all demanding attention? They shut down.

"Roughly 20%, 30% deserve to be tasks and the rest deserve to be basically announcements," as one team member summarised.

That distinction—tasks vs. announcements—is a signal-to-noise intervention.

The ISO Standards Research

During the PFL conversation, there was a fascinating aside:

"We did some research on ISO standards, a bunch of research around delivery of urgent communications and how other organisations do this at scale."

Peak sporting bodies aren't the only organisations dealing with signal-to-noise at scale.

Emergency services do it. Hospitals do it. Logistics companies do it.

They've codified best practices:

1. Classify by urgency and consequence, not just "important"

- Critical: Immediate action required, significant consequences - Urgent: Action required within timeframe, moderate consequences - Standard: Routine communication, no immediate action - FYI: Informational only, no action expected

1. Limit critical/urgent classifications to maintain credibility

- If everything is urgent, nothing is urgent - Reserve highest priority for genuine crises

1. Use distinct channels for different urgency levels

- Critical: SMS + Phone + Email - Urgent: Email + Portal notification - Standard: Portal notification - FYI: Portal only, discoverable not pushed

1. Audit usage to prevent classification inflation

- Teams naturally escalate everything to "urgent" over time - Governance required to maintain signal integrity

"It allows your clubs to better triage things," as one team member explained when describing how ISO research informed the announcement redesign.

Triage. That's the right word.

Volunteers shouldn't have to triage 30 communications to figure out what actually matters. The system should triage for them.

The Role-Based Routing Solution

Signal-to-noise isn't just about volume. It's about relevance.

When the treasurer receives safety compliance updates meant for the safety officer, that's noise. When the events coordinator receives financial reporting reminders, that's noise. When everyone receives everything, it's all noise.

Role-based routing is signal-to-noise intervention at the distribution layer.

Instead of:

• Peak body sends communication to "club"
• Communication goes to... president? Whoever registered? Everyone?
• Treasurer sees safety updates, events coordinator sees finance deadlines, nobody knows what's relevant to them

You get:

• Peak body sends communication categorised by domain (Finance, Safety, Governance, Events, Membership)
• Club maps categories to internal roles (Finance → Treasurer, Safety → Safety Officer)
• Communications route intelligently to the right person
• Treasurer sees finance communications only, safety officer sees safety communications only

The treasurer's signal-to-noise ratio improves because irrelevant messages don't reach them.

Same total communication volume. Dramatically different individual experience.

The Filtering UX Challenge

PFL discovered something interesting during testing: clubs were missing tasks not because they weren't sent, but because the filter UI wasn't obvious.

"Some of the people don't realise the default view shows their role only. They can't find a task because it's in 'all' and they haven't toggled the filter."

The system was actually working—role-based filtering was reducing noise for each volunteer.

But the UI didn't make it clear that's what was happening.

"On the mobile view, this looks more obvious at the top—filters for 'all' and 'for my role' right in the middle, front and centre. In the desktop view, it gets closer to the side. It's not actually really obvious."

Small design detail. Massive impact on whether volunteers understand what they're seeing.

Signal-to-noise improvements fail if users don't understand the system is filtering for them.

The fix: make filtering prominent. Mobile-first design. Assume people won't read documentation—they'll just use the interface.

The Acknowledgement Paradox

Here's a tension PFL is navigating:

Acknowledgements add accountability (did the club actually see this?). But acknowledgements also add friction (now I have to click a button, not just read).

Require acknowledgement on too many communications → fatigue, declining response rates. Require acknowledgement on too few → no visibility into whether critical updates landed.

The solution: be surgical about acknowledgement requirements.

Require acknowledgement for:

• Genuine compliance items with deadlines
• Policy changes that require understanding (not just awareness)
• Critical safety updates
• Things with legal or insurance consequences if missed

Don't require acknowledgement for:

• General announcements
• Resource notifications
• Opportunity alerts
• Updates that don't require action

PFL simplified their model: announcements either require acknowledgement or they don't. No more "urgent" vs. "critical" vs. "high priority." Just: does this need a response, yes or no?

That clarity helps peak bodies make better decisions about when to demand attention.

And it prevents acknowledgement inflation—where everything requires acknowledgement, so nothing gets acknowledged.

The Email Design Decisions

One surprisingly important detail from the PFL demo: whether to include an unsubscribe link in announcement emails.

"You have to have the unsubscribe option due to spam rules," one team member noted. "Gmail and Outlook now really require this."

But here's the tension:

These aren't marketing emails. They're operational communications between a peak body and its member clubs.

You could argue: "This is transactional, not promotional. Clubs need this information. Unsubscribe isn't appropriate."

But if you don't include unsubscribe, email deliverability suffers. Gmail and Outlook start treating your messages as spam. Now nobody sees them.

"We're walking the line," as one person put it. "This is a requirement of their role, but we could get in big trouble and really stuff up our deliverability of emails."

Signal-to-noise isn't just about content. It's about infrastructure decisions that affect whether your messages reach inboxes at all.

What Works: The Signal-Enhancement Playbook

Based on the conversations we've had across the sector, here's what actually improves signal-to-noise:

1. Taxonomic Discipline

• Reserve "task" for genuine action items (20-30% of communications)
• Use "announcements" for everything else (70-80%)
• Never mark something urgent that isn't
• Audit usage to prevent classification inflation

2. Role-Based Routing

• Route communications to specific roles, not "the club"
• Treasurer gets finance, safety officer gets compliance, etc.
• Dramatically reduces irrelevant noise for each volunteer

3. Notification Health Monitoring

• Track total communication volume over time
• Flag fatigue risk before engagement declines
• Create feedback loops that prevent overcommunication

4. Smart Defaults with Easy Override

• Default view: "My Role" (only what's relevant to me)
• Easy toggle to "All" (for presidents or multi-role volunteers)
• Make filtering prominent in UI (mobile-first design)

5. Acknowledgement Precision

• Require acknowledgement only when genuinely necessary
• Don't demand responses for FYI communications
• Preserve acknowledgement credibility by using it sparingly

6. Infrastructure Hygiene

• Include unsubscribe even for operational comms (deliverability)
• Monitor bounce rates and spam complaints
• Test across email clients (Gmail, Outlook, mobile)

The Bigger Picture

Signal-to-noise isn't a feature request. It's an existential challenge.

Every peak body, local government, and national federation is competing for volunteer attention in the most saturated information environment in human history.

You're competing with:

• Their job
• Their family
• Their 17 other communication channels
• Every other organisation demanding their time
• The siren call of "just ignore it all"

You cannot win that competition with more volume.

You win by being the signal that cuts through the noise.

That means:

• Ruthless clarity about what's actually important
• Intelligent routing to reduce irrelevant messages
• Interfaces that make filtering obvious
• Infrastructure that ensures messages actually reach inboxes
• Feedback loops that prevent communication inflation

The peak bodies that figure this out will retain volunteers longer, achieve higher compliance, and build stronger clubs.

The ones that keep hitting "send more reminders"?

They'll keep wondering why nobody's listening.

---

Key Takeaway: Volunteers aren't ignoring you—they can't hear you over the noise. Improve signal-to-noise by distinguishing tasks from announcements, routing communications by role, monitoring notification fatigue, and making filtering obvious. More reminders make it worse, not better.