Content calendar template that fills itself in from one topic
Paste a topic and a cadence, get a dated calendar with a working title, a format, the query each row targets and the one input that has to exist before writing.
- Works in
- Claude
- You need
- A topic or product, in one sentence · How many posts, how often, starting when
- Written for
- content calendar template
Scored by our own engine
This page, run through the audit we sell. Measured 16 August 2026.
Most content calendar templates are an empty grid. The grid was never the hard part. This one arrives filled in: a dated row per slot, a working title specific enough to brief from, the query the row exists to answer, and the one thing that has to exist before anybody can start writing.
What it gives you back
Run with the topic “project management software for construction subcontractors”, two posts a week for three weeks, starting Monday 1 September 2026:
| Date | Working title | Format | Query it targets | Must exist before writing |
|---|---|---|---|---|
| Mon 1 Sep | What a subcontractor actually needs from job scheduling, and what general PM tools miss | explainer | project management software for subcontractors | none |
| Thu 4 Sep | Tracking variations without a spreadsheet that only one person understands | how to | construction variation tracking | Screenshot of the variations view |
| Mon 8 Sep | Procore, Buildertrend and the three questions that separate them for a sub | comparison | procore vs buildertrend | Current pricing for both, checked this month |
| Thu 11 Sep | The daily site diary, and why the ones that get filled in are the short ones | teardown | construction daily site diary | Two real diary entries, anonymised |
| Mon 15 Sep | A subcontractor onboarding checklist you can hand a new foreman | template | subcontractor onboarding checklist | Sign off from ops on the current steps |
| Thu 18 Sep | Why your labour hours never match the invoice, in four places | list | construction labour cost tracking | A figure from finance on invoice disputes |
- Formats used: explainer: 1, how to: 1, comparison: 1, teardown: 1, template: 1, list: 1
- Rows needing an input: 5 of 6
- Cut: none
Five of six rows need something from somebody who is not the writer. That is the honest state of most content plans and it is invisible in a normal calendar template, which is why the fourth column exists.
The rule that does the work
One distinct query per row, enforced, with duplicates deleted rather than reworded. Two pages built for the same query is the most expensive mistake in content planning: they split whatever authority the topic earns, and eventually one of them gets filed as the redundant copy of the other. Catching it in the calendar costs nothing. Catching it after both are written costs two pieces.
You are producing a content calendar as a table. Output the table first, with
no preamble above it.
I will give you a topic and a cadence. Turn them into a calendar that covers
exactly the period I state, one row per publishing slot.
Columns, in this order, and no others:
| Date | Working title | Format | Query it targets | Must exist before writing |
Rules:
1. One row per slot. If I say two a week for six weeks, produce twelve rows
and stop. Never add a row because a topic seemed worth covering.
2. Dates are real calendar dates, weekdays only, starting from the date I
give you and spread evenly across each week.
3. A working title has to be specific enough to write from. "A guide to X" is
not a working title. Name the angle, the reader, or the constraint.
4. Format is one of: guide, comparison, how to, list, teardown, explainer,
template, case note. Vary them. If more than half the calendar is a single
format, the calendar is wrong and you should rebalance it before answering.
5. Query it targets is the phrase a person would plausibly type, lower case,
no brand names. One per row, and no two rows may target the same one. If
you cannot name a distinct query for a row, delete that row and list it
under Cut.
6. Must exist before writing names the specific input the piece needs before
anybody can start: a screenshot, a customer quote, a figure somebody has to
look up, a screen recording, or the word none. This column is what stops a
calendar being fiction.
7. Order the rows so anything another row refers to is published first.
8. Never estimate traffic, search volume, keyword difficulty, or how long
something will take to rank. You have no data on any of it, and a calendar
sequenced on a predicted result is sequenced on nothing.
After the table, exactly three lines:
- Formats used: <format: count, comma separated>
- Rows needing an input: <number> of <total>
- Cut: <any row removed under rule 5, or the word none>
Do not ask me anything first. If something is ambiguous, state the assumption
in one line under the three lines above and continue.
Topic: [TOPIC]
Cadence and dates: [HOW MANY, HOW OFTEN, STARTING WHEN]What to change
Everything in square brackets is yours to replace. Nothing else needs editing.
[TOPIC]- One sentence describing what you sell or what the site is about, in the words a customer would use rather than the words your team uses internally. This is the only thing generating the titles, so a vague sentence produces a vague calendar. "Project management software for construction subcontractors" produces a usable calendar; "B2B SaaS" does not.
[HOW MANY, HOW OFTEN, STARTING WHEN]- Your real capacity and a real start date, for example "two a week for six weeks, starting Monday 1 September". State what you can actually finish, not what you would like to publish. The rule that one row equals one slot means overstating capacity here produces a calendar you will abandon in week three.
How to run it
- 01State the cadence you can actually hold
The single decision that makes this work. The prompt produces exactly as many rows as you ask for, so the number you type is the number of pieces somebody has to write. Halve whatever you first thought of if the writing is not somebody full time job.
- 02Run it and read the last column first
The Must exist before writing column is the part with real information in it. Every row that needs a screenshot, a quote or a figure is a row with a dependency on somebody who is not the writer, and those are the rows that slip. If two thirds of the calendar needs an input nobody has, you do not have a calendar yet, you have a research list.
- 03Check the Cut line
Rule 5 forces one distinct query per row and deletes anything that duplicates another row. Whatever appears under Cut is a topic you probably thought was separate and is not. That is the single most useful line in the output, because two pages aimed at the same query is the failure mode this whole format exists to prevent.
- 04Fix the titles by hand before it goes anywhere
Working titles are working titles. They are specific enough to brief from and none of them are finished. Rewrite them when the piece is actually commissioned, not now, or you will spend an afternoon polishing titles for pieces that get cut in week two.
Questions people ask
What should a content calendar actually contain?
A date, something specific enough to write from, the format, the one query or question it exists to answer, and what has to be true before writing can start. Most calendar templates stop at the first three, which is why they read as complete and cannot be executed: nobody knows what the piece is for or what is blocking it.
How far ahead should a content calendar go?
Six to twelve weeks for most teams. Further ahead than that and you are scheduling pieces whose reason for existing will have changed by the time they are written, and you will rewrite the calendar anyway. A short calendar you finish beats a quarterly one you abandon.
How many posts a week is right?
Whatever you can finish. Cadence is a capacity question and not a strategy question, and the most common reason a content calendar dies is that it was built at the cadence somebody wished they had. This prompt takes the number from you deliberately rather than recommending one, because it knows nothing about your team.
Why does it refuse to estimate traffic or difficulty?
Because it has no data to estimate from, and a confident invented number is worse than no number. Sequencing a calendar on a predicted ranking means sequencing it on a guess dressed as a measurement. Order by dependency and by what a reader needs to understand first, then measure what actually happens after publishing.
Can I use this for a social media calendar?
Use the [social media calendar template](/prompts/social-media-calendar-template/) instead. The columns are genuinely different: a social calendar needs a channel, a hook written out in full and the asset that has to exist, and it does not need a target query at all.
I already have a content plan. Can I just get dates on it?
Then this is the wrong prompt, because it generates the plan as well. Use the [plan to calendar prompt](/prompts/content-calendar-from-a-plan-prompt/), which takes a settled plan and does only the sequencing, ordering by dependency and refusing to schedule anything whose evidence does not exist yet.
Unsubscribe in one click. We never pass your address on.