Skip to content

What is a content calendar, and what goes in one?

A content calendar is a shared schedule of what you're publishing, when, and where. Here's what fields it needs and how to build one that holds up.

9 min read
A content calendar board view in Work Studio, showing posts grouped into stage columns from Idea to Posted

TL;DR

Explains what a content calendar is, the fields it needs (date, title, platform, status, owner, plus optional ones), status stages, spreadsheet vs. tool tradeoffs, and a sample entry. Shows how to build one with fields and three views in Probe's Work Studio.

A content calendar is a schedule that lists every piece of content you plan to publish, with the date, the platform, who's making it, and where it stands. It's the one place you and your team can look to see what's coming and what's stuck.

Key takeaways

A content calendar needs five core fields at minimum: date, title, platform, status, and owner.
It's different from an editorial calendar, which covers strategy and topics rather than day-to-day scheduling.
A spreadsheet works fine for one person; a team of three or more usually outgrows it fast.
The status field (idea, in progress, scheduled, published) is what turns a list into something you can actually manage.
You can build a working calendar, with fields and three views, through a written request to an AI agent.

What is a content calendar?

A simple example: a table with one row per blog post, a column for the publish date, and a column for who's writing it. A more complete one adds platform, status, and a link to the finished piece (source (opens another site)).

How is a content calendar different from an editorial calendar?

The two terms get used loosely, but they aren't quite the same thing. As Content Pen (opens another site) distinguishes them, an editorial calendar is the bigger-picture plan: themes, topics, campaigns, what you want to say over a quarter. A content calendar is the execution layer underneath it: the specific dates and posts that carry that plan out.

In practice, many teams run both in one tool, with a notes field or a separate view for the strategic side. If you're a one- or two-person operation, you may not need the split at all.

Why does a content calendar matter?

Three things a calendar gives you that a mental list doesn't:

Consistency. You can see the gaps before they happen, instead of noticing on Thursday that nothing's scheduled for Friday.
Collaboration. Everyone involved in production, writing, editing, or publishing looks at the same dates and statuses, rather than asking in chat.
Overview. You can step back and see a week or a month at once, which is hard to do scrolling through a feed of drafts.

What fields does a content calendar need?

At minimum, five fields:

FieldWhat it holds
DateWhen the post goes live, or when it's due
TitleThe working title or headline
PlatformWhere it's published (blog, YouTube, Instagram, etc.)
StatusWhere it stands (idea, in progress, scheduled, posted)
OwnerWho's responsible for it

Without status and owner, a calendar is just a list of dates. Those two fields are what let someone ask "where's this at" and get an answer without a meeting.

As a calendar grows past one person, a few more fields tend to earn their place:

Keywords: the target search term, if the post is meant to rank
URL: the live link, once published
Assets: a file field for drafts, images, or video cuts
Notes: anything that doesn't fit elsewhere: approvals needed, a client note, a reminder

Add these only when you actually use them. A field nobody fills in is just clutter.

Different formats need slightly different fields layered onto the same core five:

Blog posts: add keyword, word count target, and a link to the published URL.
Podcast episodes: add guest name, recording date (separate from publish date), and a file field for the raw audio.
Video: add script status, filming date, and editing status as their own fields or stages, since those are usually done by different people on different days.

Keep the base fields the same across all three so you can still see everything on one calendar. Layer the extras as fields that only matter for that content type.

How do you track status from idea to published?

A typical status progression looks like this:

Idea: a topic worth considering, not yet assigned
In progress: being written, filmed, or designed
In review: drafted, waiting on edits or approval
Scheduled: finished and queued with a publish date
Published: live, with a link filled in

Some teams split "in progress" further by format. A video calendar might use scripting, filming, and editing as separate stages instead of one lump "in progress" status, since those are done by different people at different times.

Should you use a spreadsheet or dedicated software?

A spreadsheet (Google Sheets or Excel) is the lowest-friction option. It costs nothing, everyone already knows how to use it, and for one person managing a handful of posts a month, it's enough.

The tradeoff shows up with a team. A spreadsheet has one view: rows. If you want to see the same posts as a calendar grid or a status board, you're either building separate sheets by hand or giving up on one of those views. A dedicated tool keeps one set of records and shows it multiple ways at once, so a change in a cell shows up on the board and the calendar without re-entering anything.

The right call depends on team size and how often the calendar changes, as One.com (opens another site) notes. A solo creator posting twice a week doesn't need more than a sheet. A team coordinating across three platforms with different people handling each stage usually does. One.com also points to a regular review-and-adjust cycle: checking the calendar on a set schedule and moving things around as plans change, rather than treating the first version as final.

A calendar can show the same underlying records in different layouts:

Table: every post as a row, sortable by date. Good for seeing everything at once.
Board: posts grouped into columns by status, so you can drag a post from "Idea" to "Scheduled" as it moves along.
Calendar: posts placed on the days they publish, grouped by publish date. Good for spotting gaps or days with too much going out at once.

The useful part is that these aren't three separate lists you maintain, they're three views of one set of records. Change a post's status on the board, and it moves on the calendar and the table too.

How do you build a content calendar template?

Start with these columns, in this order: Date, Title, Platform, Status, Owner. Add Link once something is actually published. Add Keywords only if SEO is part of the plan. Resist adding more than that until you've used the calendar for a few weeks and know what's missing.

Here's what one filled-in row looks like with the core fields plus two optional ones:

FieldValue
DateTuesday, November 17, 2026
Title5 Tools That Changed How I Work
PlatformYouTube
StatusIdea
OwnerYou
KeywordsN/A
LinkN/A

As the post moves through production, only the Status and Link fields change. Everything else stays put, which is the point: one row, updated as it goes, instead of rewritten each time.

How does a content calendar help with SEO and keeping a team in sync?

If some of your content is meant to rank in search, a content calendar is where keyword targets live before the post is written. Mapping a target keyword to a planned date lets you see, at a glance, whether you're covering a topic cluster evenly or clustering every post around the same term. It also keeps you from publishing two pieces that compete for the same search months apart without realizing it.

The practical benefit of a shared calendar is fewer status-update conversations. If a writer, an editor, and whoever posts to social are all working off the same record, nobody has to ask "is this ready yet": the status field answers that. The calendar also makes handoffs visible: when a post moves from "In review" to "Scheduled," the next person in line sees it without being told.

How far in advance should you plan a content calendar?

There's no fixed rule, but most calendars work best planned two to four weeks out. Far enough ahead that you're not scrambling the day before, but not so far that half the entries get revised before they're due. Seasonal or campaign-driven content (a product launch, a holiday push) is the exception, and usually gets planned months ahead as its own block.

Questions people ask

Do I need software, or is a spreadsheet enough?

A spreadsheet is enough for one person or a small, steady volume of posts; once a team needs to see the same posts as a board and a calendar at the same time, a dedicated tool pays off.

What's the difference between a content calendar and a content plan?

A content plan covers strategy, like themes and goals, while a content calendar covers the specific dates and posts carrying that plan out.

How many fields should a content calendar have?

Start with five: date, title, platform, status, owner. Add more only once you know what's actually missing.

Can one content calendar cover multiple platforms?

Yes, that's one of its main uses: adding a platform field lets you see YouTube, TikTok, and Instagram posts on one shared calendar instead of three separate ones.

Do it on Probe

In Work Studio, open a Doc, choose Build with AI and describe your calendar, for example "A content calendar for my YouTube, TikTok and Instagram posts, with publish date, platform, and a stage from idea to posted". It proposes the fields and three views: a board by stage, a calendar by publish date and a table.

The proposal showed up as a Review required card, with Apply and Reject, and nothing changed until Apply was clicked. That step took 51 credits across four charges and was ready about 30 seconds after sending. Adding a handful of posts works the same way, as another card to review before applying.

Was this helpful?