A repeatable newsletter process starts with three decisions: who the message is for, what readers should get from it and who will check it before sending. Use the workflow below for your first newsletter and for each issue that follows.
Our example is the fictional Workshop Collective. It wants members to book a place at an autumn repair evening and find its updated opening hours. The organisation and example are invented; no customer results are implied.
Define the task before writing
Prepare a short brief before collecting content:
| Question | Example |
|---|---|
| Who should read it? | Members who want to receive the newsletter. |
| What matters most? | Being able to register for the repair evening. |
| What else do readers need? | Updated opening hours and a contact option. |
| What should happen next? | Readers decide whether to register. |
| Who checks the final message? | An editor other than the person who built it. |
Check the list’s purpose and recipients’ subscription status before selecting an audience. A record in a membership database does not, by itself, determine which messages someone should receive.
Choose content around the reader
The raw material includes lengthy meeting notes, six photographs, opening hours and details of the repair evening. It does not all need to go into the email. Lead with registration, follow with opening hours and link to the meeting notes for anyone who wants more detail.
Here is an original example:
Subject: Book your place at the repair evening on 12 November
Opening: Have a flickering lamp or a chair that needs fixing? At our repair evening, we help each other work out the next step. Find out what to bring and register by 5 November.
Button: View the programme and register
The subject describes the content. The opening explains the benefit, and the button tells readers where the link leads. Meeting notes no longer compete with the main task.
Build the newsletter in IdRelay
Start with a template and add text, images and links in the editor. IdRelay supports templates, content blocks and personalised content. Use recipient fields only where they help, and check what appears when a value is missing.
If AI helps shorten a paragraph, you still need to verify dates, names and claims. Review link text and image alternatives too. A venue photo can add context, but time and location must also appear as ordinary text.
Check the email that actually arrives
Send a test and follow the reader’s route all the way to the destination page. The editor preview is useful, but it does not replace testing in email clients that matter to your audience.
- Are the sender and reply address correct?
- Do links reach the right pages, with matching dates?
- Can people read and use the message on mobile and with images blocked?
- Is personalised text understandable when data is missing?
- Is there a working unsubscribe option where required?
- Have you selected the correct list, audience and sending time?
Before sending from a new domain, review its sender settings with your administrator or IdRelay support. Approve the content and audience together. A successful test to your own address does not prove that the full recipient selection is correct.
Send and learn from the result
IdRelay lets you send immediately or schedule a later time. Afterwards, read the report against the newsletter’s purpose. For the repair evening, registrations matter more than a high open count. A recorded open is not reliable proof that someone read the content. Privacy features can limit what the sender can observe; see Apple’s description of Mail Privacy Protection.
Keep three brief notes: what you sent, what you observed and what you will change next time. Reuse the brief and checklist, while checking dates, links and recipients afresh.
Explore IdRelay Campaigns, recipient lists and unsubscribes and accessible newsletters. For help with a particular campaign, contact IdRelay support.