Content calendar template: the columns that matter and how to keep one

A content calendar is one table where every row is a single piece of content and the columns answer who it is for, which question it answers, who is writing it, when it goes live, where it will be promoted, and the one number you will judge it by. Twelve columns is enough. The structure below can be pasted straight into a Google Sheet, and the habit that keeps it working is a thirty minute review on the same day every week.

This page gives the copyable column set, explains why each column earns its place, shows the Google Sheets setup that stops it decaying, and covers the weekly routine. It is built for a marketing team of one to ten people.

The copyable structure

Paste this as row one of a new sheet, then widen the columns and freeze the row.

Status | Publish date | Owner | Working title | Audience | Question it answers | Format | Primary query | Channels | Internal links | Success metric | Live URL

If you prefer to import it, save this as a CSV and open it in Sheets:

Status,Publish date,Owner,Working title,Audience,Question it answers,Format,Primary query,Channels,Internal links,Success metric,Live URL
Idea,2026-11-04,,How much does X cost,Buyer comparing three vendors,What will this actually cost me,Pricing explainer,x pricing,"Blog, newsletter","/services, /contact",Enquiries from the page,
Drafting,2026-11-11,,X vs Y,Buyer who has shortlisted two,Which one fits my case,Comparison,x vs y,"Blog, LinkedIn","/x, /y",Clicks to the product page,

Why each column is there

Column	What it does	What goes wrong without it
Status	Idea, Briefed, Drafting, In review, Scheduled, Live, Needs update	Nobody can see where the queue is blocked
Publish date	The date it goes live, not the date you hope to start	Everything slides and nothing is late
Owner	One named person per row, never a team	Shared ownership becomes no ownership
Working title	A plain sentence, rewritten before publishing	Clever titles get written before the point is clear
Audience	The one person it is for, described by their situation	Pieces drift into writing for everybody
Question it answers	The actual question, in the reader's words	Topics with no reader behind them
Format	Guide, comparison, template, case write up, video, email	Every idea becomes another blog post
Primary query	One search phrase, used once per calendar	Three pages compete for the same phrase
Channels	Where it will be promoted, decided before writing	Publishing is treated as distribution
Internal links	The existing pages this one will link to	New pages sit unlinked and unvisited
Success metric	One number, chosen in advance	Reporting becomes a hunt for a flattering chart
Live URL	Filled in at publish	No one can find what was published last quarter

Two columns people add that rarely survive: word count, which the subject decides for you, and a long notes field, which turns into a chat log. Keep notes in the brief instead and link to it.

The Google Sheets setup

Five minutes of setup is the difference between a calendar you read and a grid you ignore.

• Freeze row one and set it bold, so the headers stay visible as the sheet grows.
• Data validation on Status, from a fixed list. Typing free text into a status column is how filters stop working.
• Conditional formatting on Publish date. One rule for dates in the past where Status is not Live, one for dates in the next seven days. Two colours, no more.
• Filter views, not filters. A filter view lets you look at your own rows without changing what everyone else sees.
• Three tabs only: Calendar for the next eight weeks, Backlog for everything unscheduled, and Published for the archive with its metric.
• A days to go helper. Put =IF(L2<>"","live",B2-TODAY()) in a spare column to see slippage without reading dates.

How to fill it the first time

1. Write twenty questions your buyers actually ask, taken from sales calls, support tickets and your Search Console queries. Not topics. Questions.
2. Drop all twenty into Backlog with the audience and question columns filled.
3. Pull the six that sit closest to a purchase decision into Calendar and give them dates across the next eight weeks.
4. For each one, name the owner and the single metric before any drafting starts.
5. Leave the rest in Backlog. A calendar planned twelve months ahead is a document, not a plan.

The habit that keeps it alive

Most calendars die in week six, and the cause is almost always that nobody owns the file. Fix it with three rules.

• One standing slot. Thirty minutes, same day each week, one person driving. Move overdue rows, confirm next week's dates, pull one item up from Backlog.
• Anything undated goes to Backlog. The Calendar tab holds only work with a date and an owner. This keeps the view honest.
• Review published work once a month. Open the Published tab, look at the metric column, and mark anything worth improving as Needs update. Refreshing a page that already gets traffic usually beats writing a new one.

A useful discipline for planning volume: decide what you can finish, not what you can start. Two finished pieces a month with real distribution beats eight drafts.

Adapting it for social and for email

A social calendar needs two extra columns, Asset and Scheduled time, because the asset is the work. An email calendar needs Segment and Send time, and benefits from a rule that no two sends hit the same segment in one week. Keep these as separate tabs with the same Status vocabulary rather than one giant grid, so each view stays readable.

This page covers the structure of a content calendar and the routine for running it. For choosing what to write in the first place, work from a buyer question list. For publishing workflow inside a CMS, mirror the Status column here in your editorial tool so the two never disagree.

Where people get stuck on content calendar template

How far ahead should a content calendar be planned?

Eight weeks dated, with a backlog behind it. Dated rows past two months get moved so often that maintaining them costs more than the planning is worth. Quarterly themes can live above the calendar as a single line of text.

Is a spreadsheet enough, or do I need a tool?

A sheet is enough up to roughly ten pieces a month and a handful of people. Move to a project tool when you need per task comments, file attachments and notifications in one place. The column set stays the same either way, which makes the migration simple.

What is the right publishing frequency?

Pick the number you can hold every week for six months. One strong piece a week that gets promoted properly outperforms a burst of daily posts followed by three quiet months, because the compounding comes from pages that stay useful.

Who should own the calendar?

One person, and it works best when that person also runs the weekly review. Rotating ownership is the most common reason a calendar drifts out of date.

How do I handle reactive content?

Keep one empty slot a fortnight. Reactive work then has somewhere to go without pushing planned work aside, and if nothing comes up you pull an item forward from Backlog.

A question column for the calendar

Add a column to the calendar titled asked. For each planned piece, write the exact question it answers. A month after publishing, once the page has had time to be found, put that question to an assistant and record whether your page is named. The calendar then shows which topics earn a place and which need rework, and it stops being a list of intentions. AI Knows Us can fill the column for you.