ع
Start Topics Teams Reference What's new Saved
playbook

The quarterly editorial calendar

Go from a messy list of topic ideas to a balanced, themed 12-week calendar with draft headlines — and a weekly rhythm you can actually keep.

medium ~1 hour
when to reach for this

Planning content one week at a time means you're always reacting, repeating yourself, and over-indexing on whatever's top of mind. A quarterly calendar fixes the altitude problem: you decide the themes once, balance the formats, and then each week is just execution. This system turns a pile of half-formed ideas into a structured quarter you can defend to your boss and hand to a freelancer.

gather this first
  • A raw dump of ideas — topics.csv, a Notion export, or just a pasted list. Messy is fine; that's the point.
  • Your content pillars / themes if you have them (e.g. how-to, customer story, industry take, product). If you don't, Claude can propose them.
  • Cadence and constraints: how many posts a week, which channels, any fixed dates (launches, events, holidays).
the workflow

  1. Cluster the chaos into themes

    Save your idea dump into a folder, open it in Claude Desktop, and ask in the chat — no terminal needed. Before scheduling anything, find the structure already hiding in your ideas. This stops the calendar from being a random list and makes gaps obvious.

    you ask
    Here are 40 raw content ideas in topics.csv. Group them into 4–6 themes, name each theme, and tell me which themes are overloaded and which are thin. Flag any ideas that are actually the same topic twice.

    what you get back Your ideas sorted into named buckets, with a read on balance — e.g. "12 how-tos, but only 2 customer stories" — so you know what to commission before you schedule.

    This is the strategic step. The calendar is downstream of getting the themes right.

  2. Fill the obvious gaps

    Now that the thin themes are visible, have Claude generate candidates to balance the quarter — grounded in your actual product and audience.

    you ask
    We're light on customer stories and industry takes. Suggest 8 new topic ideas in those two themes that fit a [your audience] reader and our product. One-line angle each — no fluff.

    what you get back Eight specific, on-theme ideas with a clear angle apiece, enough to balance the quarter.

  3. Schedule it across 12 weeks

    Now lay it on a calendar with real rules: cadence, theme rotation, and any fixed dates. Ask for a single table so it drops into your tool.

    you ask
    Build a 12-week calendar, 2 posts per week, alternating themes so we never run the same theme twice in a row. Work around these fixed dates: [launch on week 5, holiday on week 9]. One table: week, date, theme, working headline.

    what you get back A 24-row table — every slot has a date, a theme, and a draft headline, with your fixed dates respected and themes rotating cleanly.

  4. Pressure-test the plan

    Have Claude critique its own calendar. A second pass catches clustering, repetition, and seasonal mismatches you'd otherwise discover in week 8.

    you ask
    Critique this calendar as if you were my skeptical CMO. Where is it repetitive, where does it sag, and which 3 weeks are weakest? Suggest a fix for each.

    what you get back A short, honest critique with three concrete fixes — the review you'd otherwise only get after publishing.

make it your own
  • Tie it to campaigns: add align posts to these 3 campaigns and Claude will theme weeks around launches instead of evenly rotating.
  • Multi-channel: ask for a channel column and per-channel adaptation notes so one theme ships as a blog + a thread + an email.
  • Living doc: keep the calendar in a file and each Monday ask what's due this week and what still needs a draft? to turn the plan into a checklist.
watch out for
  • A calendar is a hypothesis, not a contract. Revisit it monthly — don't let a plan from January quietly run your June.
  • A shared calendar has more owners than you think. At enterprise scale it collides with demand-gen campaigns, PR embargoes, events, and regional holidays across markets. Sync the fixed dates with those teams before you lock it — a plan built in a silo gets steamrolled by the launch nobody told you about.
  • Don't let Claude over-produce on themes that are easy to write but don't convert. Balance for your audience, not for what's easy to draft.
  • Working headlines are drafts, not final. They're there to make the slot concrete, not to ship as-is.

you'll end up with A themed, balanced 12-week calendar with draft headlines and a weekly rhythm — strategy decided once, so each week is execution instead of improvisation.

Questions people ask

What do I need to bring to build the calendar?
A raw dump of topic ideas (a CSV, a Notion export, or just a pasted list — messy is fine), your content pillars if you have them, and your constraints: posts per week, channels, and any fixed dates like launches or holidays.
What if I don't have content themes or pillars defined yet?
Claude can propose them. The first step clusters your raw ideas into 4–6 named themes and flags which are overloaded and which are thin — so the structure is discovered from your ideas rather than imposed up front.
Are the working headlines final?
No. Working headlines are drafts whose only job is to make each calendar slot concrete. Treat them as placeholders to sharpen later, not copy to ship as-is.
Is the calendar locked once it's built?
No — a calendar is a hypothesis, not a contract. Keep it in a file and revisit it monthly; each Monday you can ask Claude what's due this week and what still needs a draft, so the plan stays a living checklist.