Let members choose what deserves their attention.

Relevance depends on the person and the moment

Membership of the same association does not imply identical information needs. Responsibilities differ within a member organisation, and a person’s priorities can change when a policy file becomes active or a new colleague joins.

A notification that is essential to one working group may be background information to everyone else. When those distinctions are unclear, members have to open messages just to decide whether they are relevant.

Start by considering the main roles in your membership. For a European association, these might include policy specialists, national federation leads and communications teams. Use these perspectives to test your communication structure, without assuming that a job title tells you everything someone wants to receive.

Separate the subject from the delivery rhythm

Two choices need to be understandable: what a member follows and how often they receive updates. A member may care deeply about a topic while preferring a weekly overview to daily messages.

Keep newsletter subscriptions distinct from automated digests. An editorial newsletter provides a selected overview; a digest collects eligible recent content. Members should understand what each option does before choosing it.

• Describe topics with familiar names and a short explanation where needed.
• Make email frequency choices explicit: daily, weekly or monthly.
• Explain whether frequencies are alternatives or can be enabled together.
• Make it clear how to stop a type of email or change a followed topic.
• Distinguish following a topic from having permission to access its content.

In Members Cloud, daily, weekly and monthly digests can be enabled independently. A member who wants only a weekly digest should be able to understand that the other frequencies need to be disabled.

Make preferences part of the member welcome

A preferences page is useful only if members know it exists. Introduce it when a new representative receives access, and explain how to revisit it when their role changes.

Provide a few realistic examples without deciding for everyone. A specialist might follow an active technical file closely; a senior representative might choose a broader selection and a less frequent digest. Both can remain informed in a way that fits their responsibilities.

Avoid creating so many overlapping topics that the choice becomes another administrative task. Review topic names with members and merge or clarify categories that people cannot distinguish. The secretariat should be able to explain the structure in a short conversation.

Keep essential requests recognisable

Preference controls do not remove the need for careful communication. A consultation request, a governance notice and an ordinary update serve different purposes. Your association should define how each is handled and explain any essential communication arrangements clearly.

Use a subject line and opening sentence that identify the action required. Do not mark routine updates as urgent to compensate for poor engagement. Review the relevance of the message and the audience first.

Finally, ask members whether they are receiving information they can use. Reducing unwanted notifications is about respecting attention, not simply reducing the number of emails. A well-chosen update can be more valuable than a quieter inbox with important information missing.