Free content calendar template

A content calendar is useful when it tells you what is going out, what is missing and who needs to act next. A grid of publication dates does only the first of those jobs. The other two are why a full week can still end with nothing ready to publish.

This free content calendar template has four parts, all described below: a blank calendar with twelve columns, a filled example, suggested status values and a review sheet. Set the columns up as tabs in Excel or Google Sheets, or in the planning tool you already use.

If you want the calendar beside the copy and images, download Plexii free. It is free forever for personal use on Mac and Windows. You can use the template independently, or arrange the work on a Plexii desk as shown in the marketing and content workspace.

Plan the reader's next step before the publishing date

Begin with one audience and a practical question they need answered. A date creates a deadline; a reader question gives the piece a reason to exist.

The template's fictional example is a community repair workshop. The first article answers, “Can I bring a broken lamp?” A newsletter then explains three checks before booking. A social post shows the table setup so people know what happens when they arrive.

Those pieces are related, but they are not copies of the same announcement. Each removes a different obstacle between interest and attending. That is a better starting point than deciding to fill five channels because five channels are available.

The Calendar tab: one row per publishable item

The blank Calendar tab has twelve columns. You can add rows, but keep one row for each item that has its own approval and publication state. If a blog article and a newsletter need different approvals, they should not share a single status cell.

ID and working title. Give each piece a stable reference, such as C01. A title may change several times, while the ID keeps comments and file references intelligible. Write a working title specific enough that another person can distinguish it from the rest of the month's work.

Reader question. Put the actual question here, not a broad category such as awareness. For C01, the question is whether a broken lamp is an acceptable item. That makes the necessary safety and eligibility information obvious before anyone writes the introduction.

Channel and publish date. Choose the intended destination and an achievable date. Use the brief for a precise publishing time and time zone if timing matters. Do not make a date look committed while a necessary interview or approval has not been arranged.

Owner role and status. The owner moves the work forward; the status describes where it is now. Replace role names with the actual responsible people in your private copy. Avoid assigning a piece to “everyone”, because that usually means nobody knows who is meant to chase it.

Source or asset and approver. Link the current brief, copy, image folder or source material. Name the person who can approve the relevant subject. A workshop lead may approve safety wording; a communications lead may approve style. Decide which approval is required before the piece is marked Ready.

Next action, success measure and live URL. The next action should tell you how the piece moves forward. The success measure records the response you care about. The live URL is evidence that it actually went out, not merely that somebody scheduled it.

Follow the filled example from question to publication

The filled example contains three items. C01, “What to bring to a first repair session”, is a blog article in Drafting. It points to Safety checklist v2, names the workshop lead as approver and has “Check electrical safety wording” as the next action.

That next action matters. The writer cannot responsibly answer the lamp question by assuming every electrical item is accepted. The calendar exposes the need for an authoritative answer before polishing the copy.

C02 is the newsletter, “Three checks before booking a repair”. It uses C01 as its source and is still at Idea. Its next action is to write a short introduction. This piece should send readers to booking information, not repeat the entire article in an inbox.

C03 is a social post showing the repair table setup. It is Awaiting approval, and its source is a consent-cleared photo folder. Its next action is to confirm image permissions. The example illustrates a separate publication dependency: an image being available does not mean it is appropriate to publish.

All three rows are fictional planning examples. Replace their dates, approval routes and measures with your own. What is reusable is the chain from question to evidence to action.

Use statuses that mean something observable

The Lists tab suggests Idea, Brief ready, Drafting, Awaiting approval, Ready, Scheduled, Live and Hold. It also lists channel options and date guidance.

Agree the transition between each status. Brief ready means the writer has the question, sources, intended reader action and constraints. Awaiting approval means there is a complete item for an identified person to assess. Ready means the required approvals are complete and the assets are available.

Scheduled is not Live. A publishing tool can fail, a link can be wrong or a scheduled item can be paused. Mark Live only after checking the published result and recording its URL.

Hold is a useful decision, not a failure. If a service is not ready to accept bookings, pausing the announcement is better than pushing people towards a broken next step. Include the reason and the condition for restarting in the next-action field.

Build the brief beside the calendar

The spreadsheet should point to the work, not contain every version of it. The interactive demo lets you explore a desk before installing the workspace. Give a substantial article a short brief with the reader's problem, the answer, the evidence, the intended next step and the person who can settle factual questions.

For the repair article, the brief could require an accepted-items list, a plain description of what volunteers can assess and a link to booking details. It should not promise that every object will be repaired.

Keep the current image and copy locations beside the row. In Plexii, a desk holds notes, files, tables and browser material around one piece of work. The content calendar desk template offers a starting layout, while organising by project explains how to avoid scattering the brief across applications.

To keep the calendar beside the copy and assets on one desk, download Plexii free.

Make conversion a helpful next action

A content calendar supports conversion by making the reader's next step specific and appropriate. That need not be a purchase. It may be checking eligibility, downloading a checklist, booking a visit or comparing options.

For the workshop example, the article's next step is to check accepted items and then view the booking information. Asking for a booking before explaining the safety limits would make the page less useful and could produce unsuitable enquiries.

Put the next step where it resolves a question. Link the accepted-items list beside the explanation of what to bring. Use a clear booking invitation after the practical details. Do not repeat a generic button after every paragraph.

In the success-measure column, record a response that connects to the item's job. C01 uses workshop enquiries; C02 uses clicks to booking information. A page view alone cannot show that readers found the answer or took the intended next step.

The Review tab: change the next cycle

The Review tab asks for period, published IDs, reader response, what to change and an owner role. Its example records that readers asked about electrical items, then proposes adding an accepted-items link before the booking button.

That is a useful editorial observation without pretending to prove causation from a small sample. Keep direct questions, corrections and recurring confusion alongside any numerical measures. They can explain what a number on its own cannot.

At the end of the month, decide which pieces deserve updating, which deserve a related follow-up and which should stop. Do not simply copy every unfinished item into the next month. A date that slipped may have exposed a weak idea or a dependency worth resolving first.

For shared production, design feedback rounds can help keep approvals bounded. The by-role collection has more practical desk arrangements for work with several moving parts.

Common questions

Can I use the calendar outside a spreadsheet? Yes. The twelve columns work as a table in most planning tools. Keep the status values and the review questions with it, because they are what make the calendar useful after publication.

Should every social variation get a separate row? Use a separate row when it has its own approval, date or publication state. Keep minor copy variations together in the linked working document if they move through the same process.

How far ahead should I plan? Plan far enough to obtain evidence, assets and approvals. Keep near-term commitments detailed and later ideas provisional. The right horizon depends on how much preparation your content needs.

What should I do with a missed publication date? Record why it slipped, decide whether the piece still matters and choose a real new date or put it on Hold. Do not silently roll dates forward while the same dependency remains unresolved.

Can this template schedule posts automatically? No. It is a planning and tracking sheet, not a connection to a publishing service. Scheduled means you have arranged publication separately; verify the live result afterwards.

What is a sensible success measure for a helpful article? Choose the response that fits the reader's task, such as a relevant enquiry, a template download or a visit to booking information. Include reader questions and corrections rather than relying only on traffic totals.