Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Digital Marketing › Planning & Budgeting

Building a Campaign Calendar

How to lay campaigns, content and promotions on one timeline: the layers a calendar needs, planning around peaks, protecting always-on work, keeping it honest.
Guidebeginner8 min readUpdated

Why a calendar, and why it fails

Most marketing teams have a calendar. Most of them are a list of launch dates in a spreadsheet, out of date within weeks, consulted only when something collides. The collisions are the symptom: two campaigns targeting the same audience in the same fortnight, a product launch landing in the middle of a seasonal peak, a promotion that nobody told the email team about, a content piece published the week the audience is looking at something else.

The calendar fails because it tries to be one list. A working calendar is several layers on one timeline, each owned by someone, each with its own rhythm.

The layers

Always-on. Activity that runs continuously: brand and non-brand search, retargeting, evergreen content, the welcome and lifecycle emails, organic social cadence. It rarely appears on calendars because it has no start date, which is why it gets starved when budgets move to campaigns. Put it on the calendar as a baseline band, with its budget, so that every decision to fund a peak is visibly a decision about always-on too.

Seasonal peaks. The periods when demand rises for reasons outside the business's control: festivals and holidays, back-to-school, weather, end of financial year, industry events. Each market has its own; the annual planning guide covers how to identify them from historical data. Peaks are planned backwards from the date: media booked, creative ready and budget reserved weeks before demand starts, because auction prices rise with everyone else's spend.

Launches. Products, features, markets, partnerships. Launches have their own sequence (teaser, launch, sustain) and their own brief (see writing a campaign brief). They are the layer most likely to move, so they are placed with a confidence level and reviewed often. For product releases, the tutorial on running launch intake feeds this layer from one launch calendar agreed with product management, with each release's tier and milestones.

Content. Articles, videos, guides, email newsletters, social series. Content has a production lead time and a shelf life; the calendar shows both so that evergreen content is published before the search demand it serves rises, and timely content is not produced after its moment has passed.

Promotions. Discounts, bundles, events. Promotions interact with everything else: they lift conversion rate while live and depress it afterwards, they pull demand forward, and they train customers to wait. The calendar shows them so the lift and the dip are both expected. If the promotions layer looks crowded, the full-price protection test is a design for checking whether personal coded offers at a few planned events earn more gross profit per customer than the current rhythm.

Fixed external dates. Platform policy changes, tracking or privacy deadlines, regulatory dates, trade shows. Not marketing activity, but dates the activity must respect. Limits on what the business can serve, such as stock arrivals, staff holidays and weeks already fully booked, are dates of the same kind, and the guide to planning marketing around capacity and stock shows how to add them as a layer so that demand is shifted to the weeks with room. A trade show the business exhibits at brings its own sequence of invitations before it and follow-up after it, which the tutorial on exhibiting at a trade show sets out step by step.

Building the calendar

  1. Choose the unit. Weeks for most teams; days inside peak periods; months for the annual overview. The calendar should be readable at all three zoom levels.
  2. Place the fixed dates first. Seasonal peaks and external dates do not move; everything else fits around them.
  3. Lay down always-on as a band. With its budget per period, so the baseline is visible.
  4. Add launches and promotions. With their full sequence, not just the live date: teaser, launch, sustain, and the production milestones that precede them.
  5. Add content against demand. Evergreen pieces scheduled ahead of their search season; campaign content aligned with the campaigns it supports.
  6. Attach channels and audiences. For each item, which channels and which audience segment. This is what exposes collisions — the same segment hit by three things at once — and gaps where a segment hears nothing for months.
  7. Attach budget. Per item, per period. The calendar then doubles as the phasing of the annual budget, and moving an item moves its money visibly.

When the calendar has to cover several countries, the tutorial on building a marketing calendar for several markets adds each market's own moments, localisation lead times and release times in local and account clocks.

Reading the calendar for problems

Collisions. The same audience targeted by overlapping campaigns competes with itself in the auction and confuses the message. Fix by sequencing, by splitting audiences, or by merging campaigns under one brief.

Frequency spikes. When several layers reach the same people in the same weeks, each may be at a sensible Frequency while the combined exposure is not. The reach and frequency calculator helps size what a budget will deliver per item; the calendar shows what adds up. For email, the email marketing calendar template breaks this layer into individual sends with a weekly limit per contact.

Starved baselines. Always-on budget cut to fund a peak, then not restored. The band makes this a visible decision rather than a quiet drift.

Production crunches. Several launches needing assets in the same fortnight. Visible once production milestones are on the calendar, invisible when only live dates are.

Silent periods. Weeks where a segment is reached by nothing. Sometimes correct (no demand); often a gap that always-on activity should fill.

Illustrative example — not a real result

A retailer's third quarter

The quarter contains a festival peak in its second month. The calendar places the peak first, with media booked and creative due four weeks before demand starts. A new product launch originally planned for the same month is moved to the first month so it has its own attention and its own budget rather than competing with the peak. Always-on search and retargeting keep their budget throughout, with the testing reserve paused during the peak to reduce noise. Content for the peak is published in the first month so it has time to rank; a post-peak re-engagement email flow is scheduled for the third month, when past buyers are most likely to return. The calendar shows a two-week production crunch before the peak and spreads the launch asset deadlines to avoid it.

Keeping it honest

A calendar is only useful if it is true. Three habits keep it that way:

  • One owner, one source. One person maintains it, in one place, and everyone else reads from there. Copies in slide decks go stale within days.
  • A weekly review. Fifteen minutes to move what has moved, confirm what is next, and surface collisions early. The annual planning guide describes how this fits a longer cycle.
  • A record of changes. When a launch slips, note why. Patterns in the reasons (approvals, production, dependencies on other teams) are the information needed to plan better next time.

Calendar and budget

Because every item carries a budget and a period, the calendar is also the phasing of the year's spend. Reading the budget by month off the calendar, rather than dividing the annual total by twelve, is what keeps peaks funded and quiet months lean. The budgeting methods guide covers how the total is set; the budget allocation guide covers how it is split across channels. The calendar is where both become dates. Before a sale or seasonal peak on the calendar goes live, the sale promotion readiness checklist checks the offer, site, stock, media and owned channels together.

Columns a calendar needs

Whatever the tool, each item on the calendar carries the same fields, because those fields are what the problem checks read.

FieldWhy it is there
LayerAlways-on, seasonal, launch, content, promotion, external
Item and brief linkOne line, pointing at the brief that holds the detail
Audience segmentCollisions are found by segment, not by campaign name
ChannelsWhich channels carry it; frequency checks need this
Live datesStart and end
Production milestonesConcepts, approvals, assets due, tracking verified
Budget by periodThe phasing of the year's spend
OwnerOne name
Status and confidenceConfirmed, likely, provisional; drives the weekly review

Set-up checklist

0/7

Calendars for small teams

A one-person marketing team does not need a planning tool; it needs the same layers in a spreadsheet with weeks as columns and the fields above as rows. The discipline that matters at small scale is the always-on band: a solo marketer's time is the budget, and a launch that absorbs every hour for a month switches off the search content, the email and the social cadence that were producing most of the results. Blocking a fixed share of each week for always-on work, and planning launches around what is left, is the small-team version of the budget band.

Common mistakes

  • Only live dates. Without production milestones, every launch is a surprise to the people building it.
  • No always-on band. The baseline that generates most of the year's results becomes invisible and is cut first.
  • Planning peaks forward instead of backward. Starting at the peak and asking what is needed by when, not starting now and hoping.
  • Treating promotions as free. The post-promotion dip and the training effect are predictable; plan for them.
  • A calendar nobody reads. If it is not the single source, it is decoration.

For the sequence of documents around a campaign — brief, calendar, budget — see the planning section; for how the author runs calendars across a brand portfolio, see campaign management.

Terms used on this page

Tools to try

Frameworks

Where this page is used

Also related

Related