
Holiday Email Planning: A Week-by-Week Production Timeline
For many email programmes the holiday season is the most valuable stretch of the year, and it is also the one most often planned in a rush. Creative is approved in the final week, segments are built the night before, and the first sends go out into a crowded inbox with no plan for what happens next. The teams that do well are rarely the ones with the most inventive ideas. They are the ones that finished the work before the first email was sent.
This guide sets out a week-by-week production timeline from mid-November through the end of the holiday period. It covers the work that has to happen before anything is sent: goals, segments, creative, testing and a dry run. It then covers how to watch the season once it begins. The frequency and volume side of the plan is covered in the holiday email sending schedule.
Holiday email planning works best as a production timeline. Start in mid-November, finish segments and creative before the first send, test every template in advance, run a dry send to an internal list and agree the measures you will watch before the volume arrives.
Why planning starts in mid-November
Much of the holiday calendar is fixed. Thanksgiving falls on the fourth Thursday of November, and the main shopping events follow in quick succession across the weeks that come after it. Working backwards from those dates, mid-November gives you six to eight weeks before the first large send. That is enough time for goal-setting, creative production, list work and proper testing, but only if the work begins at that point. Teams that start in early December find that the calendar is already full and that every decision is being made under pressure.
The week-by-week timeline
The timeline below is built backwards from the first send. Adjust the weeks to fit your own calendar, but keep the order, because the sequence matters more than the exact dates.
In the first two weeks of the plan, set the goals and the calendar. The revenue target should use last year's holiday results as the baseline, plus the growth you have planned, and it should be paired with a target for the list, so you can see whether volume is buying revenue or only buying complaints. The calendar is drafted at the same time, with each send assigned to a segment, an offer, a send window and an owner.
Between weeks five and three, the segments and the list come first. Define each segment as a clear rule, and run the suppression list before anything else, so that you are not discovering on launch day that a large group should have been excluded. Offers and the creative brief come next, and they are approved before production starts. Production and build take the middle weeks, and the templates are built inside the email platform, not in a separate design tool that has to be rebuilt later.
The final two weeks are for testing and a dry run. Each template is tested across the client matrix, every link is checked, and personalisation fields are checked against records that are missing data, since those are the cases that break. The dry run is a full send to an internal seed list, which exposes problems that only show up when the whole sequence runs together. A common example is two sends that trigger the same automation at the same time. Once the dry run is clean, the plan moves to launch and monitoring, and after the peak it moves to review.
Set goals before the calendar
The calendar should follow from the goals, not the other way round. Begin with the revenue target for the season and the list-growth target that sits alongside it. Break the revenue target down by send, so that each campaign has a job to do. This makes the eventual review much easier, because you can see which sends delivered and which did not against an expectation you wrote down in advance.
Segment for the season, not the whole list
A holiday send to the full list is the quickest route to fatigue, and the quickest route to a spike in complaints. Segmentation lets you send more to the people who want to hear from you and less to those who do not. Three segment types do most of the work. Engagement segments decide how often a subscriber receives sends, so that engaged readers hear more and dormant ones hear less. Purchase-history segments decide what offers a subscriber sees, so that past buyers receive related products rather than a generic promotion. Lifecycle segments decide the message itself, so that a new subscriber receives an introduction to the season rather than the peak offer on their first day.
Every holiday segment should answer one question: which subscribers should get which message, and why? If you cannot answer that in a sentence, the segment is too complicated to manage under pressure.
Keep the number of segments small enough that someone can check each one before it sends. A few well-defined groups that everyone understands are more useful than a complicated set that only one person can maintain.
Design for the phone first
Most holiday emails are opened on mobile devices, which should shape every design decision. Lead with the offer and the main call to action in the first screen, since that is all many readers will see before deciding whether to keep going. Keep the layout to a single column, with buttons large enough to tap comfortably. The subject line and preheader should carry the most important words, because phones display less of both than desktop clients do.
The technical side of this is covered in the email client rendering guide, and it is worth reading before the templates are built rather than after. Rendering problems discovered during the peak are the most expensive kind, because they are found by readers rather than by the team.
Build a calendar that prevents collisions
A shared calendar is one of the cheapest protections a holiday programme can have. Every send should appear in it with its segment, its offer, its send window and its owner. Leave at least a day between major sends to the same segment, and mark the days when a send would clash with a known automation. Two teams sending to the same list on the same afternoon is one of the most common holiday errors, and it is almost always preventable with a calendar that everyone checks before approving a send.
Test before the peak, not during it
Testing is the stage that protects everything before it. Each template should pass the client matrix, each link should be checked, and each personalisation field should be tested with missing data. The dry run then ties the sequence together, which is the only way to see how the sends interact. Treat a failed dry run as a reason to delay, not as a list of problems to fix during the first send.
Set the measures before launch
Decide what you will watch and what you will do about it before the first email goes out. Unsubscribe rate needs a baseline, so that a spike is visible against normal performance, and a rule for pausing the next send when it rises. Spam complaints need the same treatment, with a stop rule for any segment that approaches the 0.1 percent threshold. Hard bounces should trigger a check of the list source if they rise unexpectedly. Revenue per recipient should be reviewed after each send, because a fall across several sends suggests that the offer or the timing needs changing.
These decisions are much easier to make in advance than during a busy week. The metric definitions behind these measures are covered in the engagement KPI guide.
Measure the season properly
After the peak, compare the results with the goals you set in week six. Report revenue per recipient, unsubscribes and complaints by segment, and the performance of each send against its own expectation. The most useful part of the review is the note on what you would change next time, written while the details are still fresh. Holiday programmes improve quickly when each season's lessons become the starting point for the next one.
The holiday season rewards preparation. A programme that finishes its segments, creative and testing before the first send can spend the peak watching the results rather than fixing the problems. For the work that comes before the season, see the Q4 readiness checks.
Key Takeaways
- Plan the holiday calendar by mid-November so creative, testing and segmentation are ready.
- Segment by engagement and purchase history to protect deliverability.
- Design for mobile first, since most holiday emails are opened there.
- Watch unsubscribes and complaints as the early signs of fatigue.
- Set revenue targets from last year's results plus planned growth.
Related Reading
- Holiday Email Sending Schedule: How to Plan Frequency and Volume From Halloween to New Year
- Black Friday Email Sequence: What to Send, When to Send It and How to Measure It
- Thanksgiving Week Email Campaigns: What to Send (and Not Send) on 26 November
- Cyber Monday Email Campaigns: How to Plan a Strong 30 November Send
- Q4 Email Readiness: Six Checks Before Peak Volume
Frequently Asked Questions
Start in mid-November for a campaign that begins in late November. Start earlier if your creative needs external approval.
There is no universal number. Increase volume only for engaged segments, and stop increasing when unsubscribes or complaints rise above your baseline.
Rarely. Use the same core offer, but vary the segment, the framing and the timing so each group receives a message that fits them.
Increase frequency only where engagement holds. Map the calendar, cap promotional sends per week and give engaged subscribers more sends than dormant ones.
Suppress them or move them to a lighter sequence after a clear period without engagement. Sending the peak offer to inactive contacts raises complaints and hurts placement for the whole send.
Was this useful?