Co-op newsletters, member messages and consent

A co-op may need to send members an administrative notice and also want to promote an event, product or campaign. Those messages should not automatically use the same audience or permission. Membership alone does not establish consent to receive all marketing.

Begin by classifying the message you are actually sending. The ICO's electronic-mail guidance distinguishes purely administrative service messages from marketing, and explains that promotional content can change the classification. Promotion of aims and ideals can count as marketing too.

Separate the message streams

An illustrative member-meeting notice that gives the date, papers and participation instructions serves a different purpose from an email advertising a paid public workshop. Keep the administrative notice focused. Adding unrelated product offers makes both the reader's expectations and the compliance analysis less clear.

Create a short mailing map with the stream name, purpose, intended recipients, responsible owner and sending system. Useful streams might include membership administration, requested application updates and an optional public newsletter. Your exact streams should follow your actual work.

Give editors a way to resolve uncertain cases before scheduling a send. A title such as “Member update” does not determine the rules; the content and circumstances matter. If classification or the applicable exception is unclear, seek appropriate advice using the current ICO guidance.

Record the permission for marketing

The ICO's PECR guidance says unsolicited electronic marketing to individual subscribers needs consent or all the conditions of an applicable soft opt-in. Different rules apply to corporate subscribers. Do not infer subscriber type simply from a work-looking email address.

When using consent, make the choice optional, specific and active; leave opt-in boxes unticked and keep evidence of what the person agreed to. Provide a working opt-out route and respect withdrawal. Record the address, date, method and wording version so future administrators can understand the permission.

The ICO updated its guidance in April 2026 to cover a charitable-purposes soft opt-in. This route only applies to contact details obtained on or after 5 February 2026, with all the relevant conditions met. Co-operative status does not automatically make an organisation a charity. Check eligibility and every condition before relying on this route; do not apply it retrospectively to an old list by assumption.

Design a manageable process

For a new optional newsletter, an illustrative form might identify the co-op, explain the kinds of email and offer a separate unticked choice. Show the privacy information at the point of collection. Ask a person unfamiliar with the form to explain what they believe will happen after submitting it.

Keep the newsletter audience separate from the full membership register. Use clear states that operators understand, such as subscribed, unsubscribed and awaiting review. Document how a preference change moves between your form, membership system and mailing platform.

Before importing an inherited spreadsheet, inspect its provenance and permission records. An old column labelled “contacts” is not enough to explain the intended use. Pause uncertain entries for review rather than filling gaps with an invented consent date.

Write instructions for manual requests too. Someone may ask to stop receiving marketing by replying to an email or contacting an officer. The person receiving that request needs a reliable route to the mailing owner.

Test before sending to real recipients

1. Create fictional test contacts representing the relevant subscription states.
2. Build the proposed audience and inspect who is included and excluded.
3. Send a test message and check sender identity, reply handling, links and mobile readability.
4. Use the unsubscribe route and verify the resulting state in connected systems.
5. Confirm a later import cannot silently overwrite that preference.
6. Check that the operational mailing process remains separately controlled.
7. Record the approving editor and final audience before the real send.

Use the member-data guide to reduce unnecessary copied fields and the shared-email guide to assign replies. Record mailing ownership and the tested process in the digital handover tool.