Most event email templates are designed for a single event announcement. If you send a regular newsletter covering multiple upcoming events, the structure is different — and the decisions about what to include, what to leave out, and how to keep it maintainable over time are what determine whether it gets read.
Most guides to event email templates assume you are promoting a single event – a conference, a product launch, a ticketed show. The advice is good for that context: compelling hero image, clear date and venue, strong CTA button, social proof.
But a lot of organisations run recurring newsletters covering multiple upcoming events. A school sends a weekly digest of term activities. A community venue sends a monthly programme of classes and concerts. An NPO keeps its mailing list informed about upcoming drop-in sessions and workshops. For these organisations, the single-event template is the wrong model.
A recurring events digest has different goals, a different structure, and different sustainability requirements – because it has to be produced consistently, often by one person without a marketing background, week after week or month after month.
This guide covers the structure that works for that format: what to include in each section, what to leave out, and how to keep the newsletter maintainable when events are frequently added, changed, or cancelled.
The goal of a recurring events digest
Before deciding what to include, it is worth being clear about what the newsletter is trying to do – because the goal shapes the structure.
A single-event promotional email is trying to drive registrations or ticket sales for one specific event. Every element exists to move the reader toward that action.
A recurring events digest is trying to do something more modest but equally valuable: keep your audience aware of what is happening so they can choose what to attend. The goal is discovery and habit, not conversion. Readers who open the newsletter regularly, scan the upcoming events, and occasionally attend something are exactly the right outcome – even if they do not click through every time.
This distinction changes what belongs in the email. Heavy promotional copy, urgency tactics, and countdown timers are appropriate for a single-event campaign. For a digest, clarity and scannability matter more than persuasion. The reader should be able to understand what is happening, when, and where in ten seconds.
The structure that works
1. Subject line – be specific, not clever
For a recurring newsletter, the subject line is a navigation signal, not a hook. Subscribers who open the email regularly are not being persuaded – they are checking what is on. A subject line that tells them exactly that performs better than one that teases.
Effective patterns: ‘What’s on this week at [Organisation]’, ‘Upcoming events – [Month]’, ‘[Organisation] events: [Date range]’. Including a specific event name works well if there is one that will stand out to your audience: ‘Open day this Saturday + upcoming events’.
Avoid: clever wordplay that obscures what is inside, generic phrases like ‘newsletter’ or ‘update’, or subject lines that could apply to any send regardless of content.
2. Brief opening – one or two sentences, no more
A recurring digest does not need a long introduction. Subscribers know what the newsletter is. A single sentence that sets the context for this particular send is sufficient: ‘Here is what is happening this month’, or ‘A busy few weeks ahead – here is the full programme’.
If there is something genuinely notable – a new event series launching, an unusual one-off occasion, a venue change – mention it in the opening. Otherwise, keep it short and get to the events. Subscribers who open for the events list do not want to scroll past three paragraphs of editorial before reaching it.
3. Events section – the main content
This is the core of the newsletter. How you structure it depends on your event volume, but the principle is consistent: every event entry should answer three questions immediately – what is it, when is it, and what should I do if I want to come.
For each event, include:
- Title – clear and specific. ‘Photography workshop’ tells the reader more than ‘Creative session’.
- Date and time – in a format that is immediately scannable. ‘Saturday 12 April, 2pm’ is clearer than ’12/04 14:00′.
- Location – even for regular events at a fixed venue. Subscribers may forward the email to someone unfamiliar with your organisation.
- One-line description – what the event is and who it is for. This does not need to be a full paragraph. ‘A hands-on session for beginners – no experience needed’ is enough.
- A link – to your website events page, a booking page, or more details. One clear link per event, not multiple competing options.
What to leave out: lengthy descriptions, speaker biographies, full terms and conditions, multiple CTAs per event. The email is a discovery tool, not an event brochure. If someone wants more detail, the link takes them there.
4. Number of events to include
Three to six events is the practical range for most organisations. Fewer than three risks the digest feeling sparse or not worth opening. More than six makes it hard to scan and may train readers to skim rather than read.
If you run more events than this, consider whether all of them belong in the same newsletter or whether segmenting by audience or category would serve subscribers better. A school might send separate digests for parents and for staff. A venue might send separate newsletters for music events and for workshops.
For weeks or months where event volume is genuinely low, it is better to send a shorter digest than to pad it with non-event content. Subscribers who sign up for event news are not asking for general updates.
5. CTA – one, at the end, pointing to your events page
A recurring digest benefits from a single consistent call to action at the bottom of the events section: a link to your full events page on your website. This serves readers who want to see everything, bookmark the page, or share it with someone else.
Linking all events to your website – rather than to individual hosted event pages or directly to booking systems – concentrates traffic on your own domain and keeps readers in your digital environment rather than sending them to third-party platforms. It also means the link is always current: your events page updates automatically when events change.
6. Footer – unsubscribe, contact, and nothing else
The footer of a regular newsletter needs an unsubscribe link (required by email regulations in most jurisdictions), a physical or contact address, and optionally a link to manage preferences. Nothing else. Footer bloat – social media icon rows, multiple navigation links, lengthy legal disclaimers – reduces the overall cleanliness of the email and is ignored by most readers.
What makes a recurring digest sustainable
The structural decisions above affect readability. The decisions below affect whether the newsletter actually gets sent consistently over the long term.
Keep the events section dynamic, not manually rebuilt
The most common reason recurring newsletters lapse is the effort required to update them. If every send requires opening Mailchimp, removing last month’s events, finding this month’s events, formatting them correctly, and checking for consistency – someone will eventually skip a send, then another, and the newsletter gradually stops.
The sustainable alternative: use an events embed that pulls from Google Calendar automatically. Revisual’s Mailchimp embed reads your current events at send time. The template stays the same; only the calendar changes. The newsletter coordinator’s job becomes adding events to Google Calendar – which they are likely doing anyway – rather than maintaining a separate Mailchimp template each cycle.
Separate static from dynamic content in the template
A well-structured template has two kinds of content: static elements that stay the same every send (header, branding, footer, unsubscribe link) and dynamic elements that change (the events). Keeping these clearly separated in your Mailchimp template makes the update process – to the extent there is one – faster and less error-prone.
If you include a brief editorial opening, treat it as the one thing you write fresh each send. It should be short enough that writing it takes two minutes. Everything else in the template should either update automatically or not need touching.
Plan for gaps and cancellations
Events get cancelled. Schedules go quiet over holidays. A recurring digest needs to account for this without creating a crisis each time it happens.
If you use an evergreen events embed, cancelled events simply disappear from the next send automatically when removed from Google Calendar. A quiet period shows fewer events. You can extend the evergreen window – showing the next eight weeks rather than the next four, for example – to ensure the newsletter always has something to show even during slower periods.
If you maintain the events section manually, build a habit of checking the template contents a day before the scheduled send. This is the maintenance cost of the manual approach and why the dynamic embed is worth setting up for any organisation sending more than monthly.
A sample structure at a glance
Subject: What’s on this week at [Organisation Name]
Opening: One or two sentences about this week’s programme.
Events section: Three to five events, each with title, date/time, location, one-line description, and link.
CTA: ‘See the full events calendar’ → link to website events page.
Footer: Unsubscribe link, contact address.
Total reading time: under ninety seconds. Total production time with a dynamic embed: under five minutes.
For a recurring events digest, the core content is an events section with three to six upcoming events, each showing the title, date and time, location, a one-line description, and a link. Surround this with a brief one or two sentence introduction, a single CTA at the end linking to your full events page, and a standard footer with unsubscribe and contact details. Keep it short and scannable – the goal is discovery, not conversion.
Three to six events is the practical range for most organisations. Fewer risks the digest feeling sparse; more makes it difficult to scan. If you consistently have more than six events worth featuring, consider whether your audience would be better served by segmenting the newsletter by event type or audience rather than including everything in one send.
Use an events embed that pulls live data from your calendar rather than static event listings you write manually. Revisual’s Mailchimp embed connects to Google Calendar and shows your current upcoming events at send time – when you add, change, or cancel an event in Google Calendar, the next newsletter send reflects that automatically without any changes to the Mailchimp template.
For a recurring digest, clarity outperforms cleverness. Subject lines that tell subscribers exactly what is inside – ‘What’s on this week’, ‘Upcoming events – April’, or ‘[Organisation] events: 14–28 March’ – perform consistently well because subscribers who open regularly are navigating, not being persuaded. Including a specific event name works when there is something genuinely notable that week.
Short. A recurring events digest should be readable in under two minutes. The events section is the content; everything else is navigation. Subscribers who have to scroll past lengthy introductions, multiple sections of non-event content, or detailed descriptions for each event are less likely to read consistently. Keep the opening to one or two sentences, keep event descriptions to one line each, and end with a single CTA.
Linking to your website events page – rather than to individual event pages or third-party booking platforms – is the more sustainable choice for a recurring digest. It keeps traffic on your own domain, ensures the link remains valid even if individual event details change, and gives subscribers access to your full programme rather than a single event. Include a booking or registration link in the event’s one-line description only when registration is required and the event has a fixed capacity.
About the author
Piotr Pozniak
Piotr’s is the cofounder of Revisual, a dedicated tool for seamlessly sharing events. With over six years of experience developing the platform, he brings extensive expertise in streamlining business processes through technology solutions. Work with partners across industries has honed his ability to optimize event workflows and enhance data accessibility.
