Role-Based Filtering: Why 'My Role' Should Be the Default View

# Role-Based Filtering: Why 'My Role' Should Be the Default View

"One of the biggest challenges I think at the moment we have is tasks being lost or missed with my role versus all tasks."

Mark Sanders from PFL said that during a product demo, and it's a problem every peak body managing multiple clubs recognises immediately.

The secretary doesn't need to see communications meant for the treasurer. The treasurer doesn't need compliance updates meant for the safety officer. The president probably needs to see most things, but even they don't need every single update cluttering their view.

Role-based filtering isn't a nice-to-have feature. It's the difference between a volunteer engaging with your communications or giving up entirely.

The Problem: Information Overload by Default

Here's what happens in most club management systems:

1. Peak body sends communication to a club
2. Communication goes to... everyone? The president? Whoever registered the account?
3. Volunteer either sees everything (overwhelming) or sees nothing (they're not the designated recipient)
4. Critical updates get lost in noise or never reach the right person

PFL experienced this firsthand. Tasks were getting missed not because volunteers were ignoring them, but because they couldn't find them.

"Some of the people don't realise the default view shows their role only," Mark explained. "On the mobile view here, this looks a bit more obvious at the top, with filters for 'all' and 'for my role'. It's right in the middle, front and centre. In the desktop view, I think that gets closer to the side there. It's not actually really obvious."

The interface defaulted to role-based filtering, but volunteers didn't notice. They thought they were seeing everything. They weren't.

The Fix: Make Role-Based Filtering Obvious

The solution isn't complicated. It's design.

Mobile does it right: The filter sits prominently at the top. "All" vs. "For My Role" is immediately visible. Nobody misses it.

Desktop needs work: When the filter lives off to the side, it becomes easy to overlook. Volunteers assume they're seeing everything when they're only seeing a subset.

Mark's feedback was clear: "Whether that could be sent by going towards the left or something like that, rather than off to the right? Because I think that is a common error that they don't understand that."

Small design change. Massive impact on usability.

How Role-Based Subscriptions Actually Work

Here's where it gets interesting. Role-based filtering isn't just about hiding irrelevant information. It's about intelligent routing from the moment a communication is created.

When a peak body creates an announcement in TidyConnect, they assign it to categories:

• Governance
• Finance
• Safety & Compliance
• Operations
• Events
• Membership
• Facilities

Each club then maps those categories to their own internal roles:

Example:

• Governance → Secretary
• Finance → Treasurer
• Safety & Compliance → Safety Officer + President (fallback)
• Operations → President
• Events → Events Coordinator
• Membership → Registrar
• Facilities → Facilities Manager

When the peak body sends a Finance category update, it doesn't blast everyone at the club. It goes to whoever that club has assigned to Finance communications—typically the treasurer.

The Fallback Person: Solving the Setup Problem

Here's the genius part: clubs don't always set up roles perfectly.

Maybe they haven't assigned anyone to the Finance category yet. Maybe they don't have a dedicated Safety Officer and forgot to route those comms elsewhere. Maybe their Events Coordinator just resigned and they haven't updated the system.

In traditional systems, those communications would go nowhere. Into the void.

TidyConnect handles it differently: fallback person.

Each club designates a fallback person (usually the president or secretary). If a communication doesn't have a role subscriber, it routes to the fallback.

This ensures nobody misses critical updates even when the club's setup is incomplete.

"It ensures there's at least one email to send to, because a role could be empty of admins," one team member explained during the PFL demo.

That's empowerment design: assume imperfect setup, plan for it, prevent failure.

AI-Powered Role Suggestions: Breaking the Setup Inertia

The biggest barrier to role-based filtering? Setup friction.

Clubs receive an invitation to join TidyConnect. They land on a configuration screen showing 8-12 communication categories and 6-10 internal roles. The mapping isn't immediately obvious.

Do Governance announcements go to the Secretary or President or both? Does Finance go to Treasurer only or also to President for oversight? What about categories that don't map cleanly to a single role?

Faced with that decision paralysis, clubs often abandon setup entirely.

TidyConnect solves this with AI-powered suggestions.

Hit "Apply Suggestions" and the system pre-fills likely mappings:

• Governance → Secretary
• Finance → Treasurer
• Safety & Compliance → President (fallback to cover gaps)
• Operations → President
• Events → Secretary (if no Events Coordinator exists)
• Membership → Secretary
• Facilities → President

Clubs can adjust from there, but the inertia is broken. The cognitive load drops from "Figure out 48 mapping decisions" to "Review and tweak 8 suggestions."

"It breaks the inertia of setting this up," as one team member put it.

Why This Matters for Engagement

Role-based filtering directly impacts whether volunteers engage with your communications.

Without it:

• Treasurers get bombarded with safety compliance updates they can't action
• Safety officers miss critical updates buried in finance noise
• Everyone develops learned helplessness: "There's too much, I'll just ignore it all"

With it:

• Treasurers see finance communications (and only finance communications)
• Safety officers see compliance updates (and only compliance updates)
• Signal-to-noise ratio improves dramatically
• Volunteers engage because the information is relevant to them

Mark summed it up perfectly: "I think the client has missed that they've just said they want to look for their own role, but can't find a task. It's in 'all' because you haven't met a saw on that one."

The task wasn't lost. The volunteer just couldn't find it in the noise.

The Mobile vs. Desktop Insight

One surprising finding from the PFL demo: the mobile interface handled role-based filtering better than desktop.

Why? Because mobile forces simplicity.

There's no room for cluttered navigation. The filter has to be prominent. The choice between "All" and "My Role" sits front and centre.

Desktop has more space, which paradoxically makes it easier to hide critical UI elements off to the side.

The lesson: just because you have screen real estate doesn't mean you should use it. Sometimes constraint forces better design.

Implementation Checklist

If you're building or evaluating a club communication system, here's what role-based filtering should include:

1. Category-based communications (governance, finance, safety, etc.)
2. Role-based subscriptions (clubs map categories to their internal roles)
3. Fallback person mechanism (ensures nobody misses comms if setup is incomplete)
4. AI-powered role suggestions (breaks setup inertia with smart defaults)
5. Prominent filtering UI (mobile-first design, not buried in a sidebar)
6. Default to "My Role" view (show volunteers what matters to them first)
7. Easy toggle to "All" (for presidents or multi-role volunteers who need full visibility)

Get those right, and you'll see engagement rates climb.

The Bigger Picture

Role-based filtering isn't just a feature. It's a fundamental rethink of how peak bodies communicate with clubs.

The old model: broadcast everything to everyone, hope it sticks.

The new model: intelligent routing based on responsibility, reducing noise, increasing relevance.

It respects volunteers' time. It acknowledges they're juggling multiple commitments. It meets them where they are instead of demanding they wade through irrelevant information to find what matters.

And when you make it easier for people to engage with the information they actually need?

They engage.

---

Key Takeaway: Volunteers don't have time to sort through everything. Role-based filtering does the sorting for them, routing communications based on responsibility. Make the filter prominent, provide smart defaults, and build in fallback mechanisms. Engagement will follow.