A mailing that bounced to a firm she left in 2021
The journal goes out and a stack of copies come back marked not known at this address. The email newsletter bounces for a noticeable share of members, most of them work addresses at employers they have left. The regional branch secretary asks for a list of members in the area and gets one that includes people who moved away years ago.
Meanwhile, a member rings to complain that her renewal invoice went to her old employer's accounts department. She did tell you she had moved, in an email to a staff member who has since left. The database still shows her old job title, her old employer and her old work email.
Why member records drift
Members rarely think to tell their professional body when they move jobs, and when they do, the update often never reaches the database.
- Changes are sent by email to whoever the member knows, and not always entered.
- The member portal exists, but members do not log in unless they need something.
- Bounced emails are not processed, so the address stays on the record.
- Returned post is put in a tray and dealt with occasionally.
- Employer names are free text, so the same firm is spelled a dozen ways.
- There is no record of when details were last confirmed.
The underlying problem is that updating a record is left to the member's initiative, at no particular moment.
What stale records cost
Print and postage go on journals and letters that never arrive. Renewal invoices go to the wrong place, which delays payment and irritates members. Branch and regional activity is planned from lists that are wrong. Reports on where members work, which boards and funders sometimes ask for, are unreliable.
There is also a practical data protection point: holding details you know are out of date is not a good position, and your own policy will say what you should do about it.
How we keep member records current
- Update prompts appear at moments members already engage: renewal, event booking, CPD submission, and logging into the portal, with their current details shown for a quick confirm or edit.
- Email bounces from your email platform are read automatically, and a hard bounce marks the address as failed and triggers a request for an update through another channel.
- Returned post is logged by scanning the membership number on the label, which flags the address and prompts the member.
- Employer names are chosen from a maintained list as members type, so the same firm is recorded consistently, with new ones added after a quick check.
- Each detail carries the date it was last confirmed, so staff can see which records are stale.
- Changes made by staff after a phone call or email are entered on the same form, so there is one route in.
- Members who have not confirmed their details for a long period receive a short, friendly request with a one-click confirm.
| Signal | What happens |
|---|---|
| Hard email bounce | Address flagged, member asked by post or phone to update |
| Returned journal | Address flagged by scanning the label |
| Renewal | Details shown to confirm before paying |
| Event booking | Job title and employer confirmed in the booking form |
The approach relies on small, well-timed prompts rather than an annual data cleanse that members ignore.
Member records afterwards
Members confirm their details in seconds when they renew or book an event. Bounces and returned post are processed as they happen, not in a quarterly clear-out. Staff can see how current each record is, and branch lists reflect where members are now.
Reports on members by employer and sector become useful, because employer names are consistent.
Is your member data like this?
- Journals and letters come back undelivered.
- Emails bounce to former employers.
- Renewal invoices go to members' old jobs.
- Employer names are spelled many ways.
- You cannot tell when a record was last confirmed.