What this template is for
Use the calendar to plan broadcast email: newsletters, promotions, announcements, seasonal sends and re-engagement campaigns, anything a person schedules for a list or segment on a date. It is usually built a quarter ahead, reviewed weekly and filled in more detail as each send approaches. Teams that send rarely can plan a month at a time; teams that send several times a week need the quarter view to see the build-up around peaks.
The calendar does not replace three neighbouring documents. The campaign calendar guide places whole campaigns across all channels and shows where email meets paid media and promotions; the email calendar takes its email rows and breaks them into sends. The social content calendar guide does the same job post by post for social, and the content calendar template plans the editorial pipeline that newsletters often draw on. The lifecycle email programme playbook inventories the automated journeys, such as the Welcome SeriesThe automated sequence of emails sent to a new subscriber in the days after sign-up., that run continuously; the email calendar refers to that inventory so broadcasts and flows do not collide.
A calendar is also a DeliverabilityWhether sent email reaches the inbox rather than spam or rejection, decided by sender reputation. tool. Mailbox providers judge a sender partly on how its recipients engage, so a schedule that keeps irrelevant or excessive mail away from people protects the inbox placement of every send. Google's email sender guidelines document the technical requirements for reaching Gmail users; a calendar is where the sending behaviour that sits on top of those requirements is planned.
The template
One row per broadcast send. Rules that apply to the whole calendar, such as the frequency limit and the consent basis of each segment, can sit in a header above the rows, as in the filled example.
| Field | What to write |
|---|---|
| Send date and time | The planned date and local send time for each broadcast, and the time zone |
| Segment | Who receives the send and who is suppressed from it |
| Objective and offer | What the send is for and the offer or content it carries |
| Subject line and preview | The draft subject line and preview text, and any test planned on them |
| Automated flows in play | Which automated flows reach the same people that week and whether they pause |
| Frequency limit | The maximum sends per contact per week, and how this row keeps within it |
| Consent basis | The permission the segment was collected under |
| Owner, status and QA | Writer, approver, build status and the reference for the completed QA check |
Keep the calendar in the same place as the rest of the team's work, so a send's status is visible without logging in to the email platform. A shared sheet or a board in the work management tool both work.
How to fill each section
Send date and time
Start with the fixed dates: seasonal peaks, holidays, product launches and promotions already on the campaign calendar. Plan backwards from each, so the send that announces an offer leaves time for the reminder and the last-chance send. Then place the regular newsletter on its usual day, and fill gaps last. Record the time zone, and note sends that must go at a particular hour, such as a delivery cut-off reminder.
Segment
Name the segment exactly as it exists in the email platform, and name who is suppressed. The email segmentation guide explains lifecycle, behaviour, preference and engagement segments; most calendars need at least an engagement-based suppression, so that inactive subscribers stop receiving regular sends. A row that says "whole list" should be rare and deliberate, because it is usually the row that drives unsubscribes.
Objective and offer
State what the send is for in a phrase: sell a seasonal product, announce a change, keep the newsletter habit, win back lapsed buyers. Then record the offer or content it carries. A send with two objectives usually achieves neither. The newsletter design and copy guide explains the difference between the newsletter, which earns attention by being regular and useful, and promotional sends, which arrive when there is something to sell. Where a row belongs to a larger campaign, link to the campaign brief rather than restating it.
Subject line and preview
Draft the subject line and the preview textThe short line of text an inbox shows after or below an email's subject line, taken from the start of the message. when the row is created, even if they change later; writing them early shows whether the send has a clear point. Note any test, such as two subject lines on a sample before the main send. The email metrics and testing guide explains why Open RateShare of delivered emails recorded as opened. is now a weak signal for judging subject lines, because of privacy changes in mail clients, and how to test with enough volume to read a result.
Automated flows in play
For each send, list the automated flows that could reach the same people that week, from the journey inventory in the lifecycle email playbook. Decide whether the flow continues, pauses or excludes the broadcast's recipients. A new subscriber in the middle of a welcome series does not usually need a promotion as well; a customer in a post-purchase flow does not need a discount on what they just bought.
Frequency limit
Set one maximum number of emails per contact per week, covering broadcasts and flows together, and write it in the calendar header. Then check each week's rows against it. The deliverability guide explains how engagement affects inbox placement, and why a sudden rise in volume can cost reputation. If the right frequency is uncertain, an email frequency test answers it better than adding sends and watching the totals. Watch Unsubscribe RateShare of delivered emails that led the recipient to opt out. by week alongside the calendar: a rise that follows a busy week is the calendar's own feedback.
Consent basis
Record the permission each segment was collected under: consent at sign-up, an existing-customer basis where the law allows it, or a specific preference choice. This determines what each segment may be sent. The list building and consent guide covers consent records and preference centres, and the UK Information Commissioner's Office publishes direct marketing guidance on when consent is needed for electronic mail and when existing customers can be contacted about similar products. This page is not legal advice; check the rules for each market mailed.
Owner, status and QA
Name the writer and the approver, and keep a status that moves from planned to drafted, approved, built, tested and scheduled. Record where the QA check was completed. The pre-send checks in the newsletter design and copy guide and the email campaign QA checklist are ready starting points. A send with no completed check should not reach the scheduled status.
Filled example
Below, the calendar is completed for one quarter of an invented business. The figures, dates and names are illustrative.
Marrowick Seafood: January to March broadcast calendar
| Header | Marrowick's rules for the quarter |
|---|---|
| List and segments | 48,000 subscribers. Customers (bought in the last 12 months): 14,500. Prospects (signed up, not bought): 21,000. Lapsed (no purchase in 12 months): 9,500. Inactive (no click in 180 days, any group): suppressed from all broadcasts after a two-send re-permission sequence in January |
| Frequency limit | No more than two broadcasts per contact per week, and no more than three emails a week including flows. New subscribers in the welcome series receive no broadcasts for its first ten days |
| Consent basis | Prospects and lapsed: consent at sign-up, recorded with form and timestamp. Customers: existing-customer basis for similar products, with an opt-out in every send; recipe-only subscribers receive the newsletter, not promotions |
| Automated flows | Welcome series (5 emails, 14 days), post-purchase (2 emails), abandoned basket (2 emails), win-back (3 emails, paused during the March promotion) |
| Date and time | Segment | Objective and offer | Subject line and preview | Flows | Owner and status |
|---|---|---|---|---|---|
| Thu 8 Jan, 07:30 | All engaged, excluding welcome days 1–10 | Newsletter: winter mussels and a recipe | "Mussels are at their best this month" / "A 20-minute supper and where ours come from" | Welcome excluded | Writer: content lead; approver: founder; scheduled, QA ref Q-014 |
| Tue 20 Jan, 18:00 | Customers and prospects in Scotland and northern England postcodes | Burns Night smoked salmon box, order by 22 Jan for delivery on the 24th | "Smoked salmon for Burns Night" / "Order by Thursday for Saturday delivery" | Abandoned basket continues | Writer: promotions manager; built, QA ref Q-015 |
| Thu 5 Feb, 07:30 | All engaged | Newsletter: what the boats landed in January | "What came in on the boats" / "Plus a hake recipe for a weeknight" | Welcome excluded | Content lead; drafted |
| Tue 10 Feb, 12:00 | Customers, prospects who clicked a shellfish link in 90 days | Valentine's oyster and lobster box, delivery 13 Feb | Test: "Oysters for two" vs "A shellfish supper for Friday" on 10% of the segment | Win-back recipients excluded | Promotions manager; planned |
| Thu 5 Mar, 07:30 | All engaged | Newsletter: Lent and simple fish suppers | "Six fish suppers for Lent" / "Each under 30 minutes" | Welcome excluded | Content lead; planned |
| Tue 10 Mar, 18:00 | Customers and lapsed | Mothering Sunday dressed crab, order by 12 Mar | "Dressed crab for Mothering Sunday" / "Delivered Saturday 14 March" | Win-back paused 9–16 Mar | Promotions manager; planned |
| Tue 24 Mar, 18:00 | Customers and prospects | Good Friday pre-order opens, delivery 2 April | "Pre-order for Good Friday" / "Choose your delivery slot now" | Post-purchase continues | Promotions manager; planned |
Review in the weekly marketing meeting: each week's rows checked against the frequency limit, the unsubscribe rate after each send recorded next to its row, and the April calendar drafted by 13 March.
Common mistakes
- Planning sends without the flows. A broadcast calendar that ignores automated journeys double-mails the newest and most valuable subscribers. Check the journey inventory for every week.
- A frequency limit nobody checks. A limit written in a policy and not in the calendar is not enforced. Put it in the header and count each week against it.
- Whole-list sends by default. Mailing everyone, including subscribers who have not engaged in months, weakens engagement signals for the whole domain. Suppress the inactive tier.
- Consent treated as one bucket. Subscribers collected under different permissions may be sent different things. Record the basis per segment before planning promotions.
- Subject lines written at the last minute. A send that cannot be summarised in a subject line when it is planned usually has no clear point. Draft the line with the row.
- Two objectives in one send. A newsletter that also runs a sale and announces a policy change does none of them well. Split the objectives across sends.
- No feedback loop. A calendar that never records results repeats its mistakes. Note the unsubscribe rate and the main result beside each row after it goes.
- Status without QA. A send marked scheduled without a completed check is how broken links and wrong segments reach customers.
The campaign brief that an email promotion belongs to, and the content calendar that feeds the newsletter, are in the templates library.
