A content calendar that starts from one weekly recording

// In this article+

Most content calendars fail because nothing feeds them; plan one backwards from a weekly recording and every cell has something in it. Ghost defines the tool this way: "In simplest terms, a content calendar helps you know what to publish and when to publish it." Most guides hand you a blank grid and leave you to invent the content, while the calendar below starts from one recording each week and gives each channel a dated cut of it.

What is a content calendar, and why start from one recording?

Ghost's step-by-step guide ↗︎ names the minimum fields a calendar needs: a title, a keyword, an audience, a target date, and a distribution plan. A blank content calendar template gives you those columns and nothing to put under them. The usual result is a calendar that fills in week one and goes empty by week three.

A weekly recording fixes the supply problem. A 45-minute conversation, interview, or solo session is the raw material. Every channel gets a cut of it, and the calendar only has to say which cut, on which day, and who owns it.

Here are the columns I would use:

• Recording ID. The week and the one argument the recording makes.
• Channel. Site article, newsletter, LinkedIn, short video, podcast feed.
• Cut. The specific piece: a 900-word article, a 60-second clip, a 200-word newsletter section.
• Owner. One named person per cut.
• Review deadline. The date the cut must clear review, covered below.
• Publish date. The date the platform schedules it for.
• Repurposed from. The recording ID, so nobody posts the same cut twice.

Content calendar vs editorial calendar

The two terms overlap. In practice, an editorial calendar plans the owned site: topics, briefs, and the article queue. A content calendar spans every channel the recording feeds. If you also run a site publishing plan, the editorial calendar covers that side, and this one sits across it.

The Content Marketing Institute's strategic editorial calendar article ↗︎ treats the calendar as the working plan for a documented strategy, which is the right order. Strategy first, then the calendar that carries it out. The full range of what an agency produces from that plan is in what a content marketing agency actually produces.

Which channel gets which cut, and on which day?

Plan from Day 0, the recording day, and date every cut from there. MillionPodcasts' five-day repurposing workflow ↗︎ gives a usable five-day skeleton. Its Day 1 step reads "Review transcript 1 hr: highlight key moments".

The table carries the sequence turned into a calendar for one weekly recording. Look at the time budget and the owner on each row. The Day 0 row and the owners are a suggested split, not a sourced one.

Source: MillionPodcasts' five-day workflow ↗︎, with the Day 0 row and the owner column added as suggestions.

One argument, rewritten per channel

Each cut is rewritten, not pasted. Brafton's multichannel calendar guide ↗︎ states the rule plainly: "The same audiences shouldn't see a piece of content twice unless you've adjusted it." Podglomerate's repurposing playbook ↗︎ makes the same point about written formats, warning against copying one text across formats with no changes. A newsletter deepens the relationship with listeners already on your list, while the article is there to be found by search.

Clearwater Agency's cross-channel calendar post ↗︎ gives the question to ask for every cut: "Does this content, or any other content created previously, have the potential to be repurposed across other platforms?" Answer it per row. If the answer is yes, write the new cut for that platform's reader.

Podglomerate's playbook also advises a shared template with "due dates tied to the episode drop". That is the Day 0 anchor in this table. Move the recording and every date moves with it.

Two production notes. A recording built around three to five clear arguments cuts far better than a wandering one, so the content briefs for the week should name them in advance. And the recording itself has its own pipeline, covered in the podcast production process post. If the cuts, not the recording, are your bottleneck, that is the work content production exists to take on.

How far ahead should each channel be scheduled?

Lead time differs by platform, and the platform's own documentation beats a template's guess. This section is a checklist per channel.

Social posts. Buffer's social calendar guide ↗︎ recommends planning ahead by a margin: "Try to plan at least two to four weeks ahead". That is a vendor recommendation, not a measured rule, and Buffer sells scheduling software. It is still a sensible default: start at two weeks and move toward four once review clears on time. Buffer's own reasoning is that the range leaves room to swap in something timely.

Video. YouTube supports scheduled publishing natively, so the cut can sit finished and dated. Its scheduling help page ↗︎ carries a caveat worth building into your checklist: "If your account has a Community Guidelines strike, your scheduled video won't publish during the penalty period." A scheduled video can drop back to private and need rescheduling, so check the queue the day before.

Podcast. Spotify for Creators lets you queue an episode for a later date. Its publishing guide ↗︎ says "Click Publish, or find Publish date to select a future time and date." The episode is the Day 0 anchor, so it can be scheduled first and everything else dated against it.

Owned site. Show real dates. Google Search Central's guidance on publication dates ↗︎ says to "Add a user-visible date to the page and feature it prominently." My rule on top of that is to publish the article on the date it carries and to update the date only when the page changes. A post stamped with a future date, or refreshed on a cosmetic change, does not serve the reader.

To turn this into a lookup, add a "Lead time" and a "Last check" column to the calendar. Social: two to four weeks, checked weekly. Video and podcast: scheduled once finished, checked the day before. Site: dated when it goes live.

What review step happens before anything goes out?

Nothing is scheduled until it clears review. Smartsheet defines the term: "A content approval workflow is the series of steps that content goes through before publication." In its guide to approval workflows ↗︎, it lists six steps: list your content types, map the review stages, assign roles, set timelines, choose tools, and test and adjust.

Scheduling tools make it easy to queue a post before anyone has read it. The gate has to come first, and it needs a name on it.

Map the stages and name the approver

For a weekly recording, three stages are enough. This is my adaptation of Smartsheet's longer list, not a sourced standard:

1. Edit. One person checks voice, length, and that the cut rewrites the argument for its channel.
2. Fact and compliance check. One person verifies every number, name, and claim against the recording, plus any legal or client constraints.
3. Approve. One named person says yes. Not a committee.

Smartsheet quotes Elaine Chen, founder of the marketing consultancy excogita, on the failure to avoid. She calls a single person approving everything common and a disaster, because everything stalls when that person is busy or out. Name a backup for every stage.

Set the deadline before the publish date

Put a review deadline in the calendar for every cut, ahead of its scheduled date. How long that gap is, you decide. Smartsheet sets no standard gap before publishing, only advice to build realistic timelines with room for revisions. Its quoted practitioner does recommend finishing approvals within a 24-hour period, which is one data point. A common-sense start: two working days before the earliest social post, and one day before the article. Adjust after a month of data.

If a cut misses its deadline, it does not go out. It moves to the next open slot. That rule is what keeps the gate real.

How do you review the calendar and keep it honest?

A calendar drifts unless someone reviews it. Podglomerate's playbook ↗︎ recommends reviewing performance monthly and retiring "formats that don't move the needle", which it measures by engagement, reach, or conversions. Batching also helps: pull all the clips for the month into one task, and write the month's newsletters in one sitting.

Here is a monthly review checklist, 30 minutes:

• Count what shipped. Cuts planned against cuts published, per channel.
• Count what was late. Which stage held things up, and who owns it.
• Check performance by format. Keep, change, or retire each format.
• Check cadence. Buffer's calendar templates guide ↗︎ offers a rule for this: "Three posts a week you can sustain beats seven you'll abandon by Thursday."
• Fix the next four weeks. Move dates, swap cuts, confirm owners.

Above the weekly rhythm, set themes by quarter. The Content Marketing Institute's strategic calendar article ↗︎ advises that you "Plan content in quarterly sprints so you can adapt topics to real-time changes in the industry." Quarterly themes give the weekly recordings a direction. The recording still decides the week's argument, so the calendar stays flexible.

What to do this week

1. Pick or record this week's source. One conversation or solo session of about 45 minutes, with three to five arguments named beforehand.
2. Build the columns. Use the seven above and nothing else.
3. Date each cut from Day 0. Copy the Day 0 to Day 5 table and put real dates on it.
4. Check native scheduling on each channel. Confirm you can queue the post, video, and episode, and note any caveats such as the YouTube strike rule.
5. Name the reviewer, a backup, and the deadline. Write the three stages into the calendar.
6. Book the first monthly review. Put it on the calendar now, 30 minutes, four weeks out.

FAQ

What should a content calendar include?

Ghost's guide lists a title, a keyword, an audience, a target date, and a distribution plan as the basics. For a recording-first calendar, add the recording ID, the cut, an owner, and a review deadline, so each row traces back to its source and has a named person.

How far ahead should I plan social posts?

Buffer's guide recommends at least two to four weeks ahead. That is a vendor recommendation, and Buffer sells scheduling tools. Treat it as a starting range. Start at two weeks, and move toward four once your review step reliably clears on time.

Should every channel get the same text?

No. Brafton says the same audiences shouldn't see a piece of content twice unless it has been adjusted, and Clearwater Agency suggests asking whether each piece can be repurposed across other platforms. Rewrite the one argument for each channel's reader, and mark the original in a repurposed-from column.