Build an editorial calendar that helps decisions

Plan decisions rather than filling dates

Begin with the publication’s promise and the kinds of questions readers return with. A calendar full of titles is not yet a plan if nobody knows why the items matter or who will make them ready. The calendar earns its place by helping the team say yes or no to material.

Use the rhythm you can maintain. Some material benefits from a regular pattern; other items depend on a source becoming available or an event occurring. Keep those dependencies visible so a planned edition does not quietly turn an uncertain item into an announced fact.

Keep the planning fields practical

For each proposed item, record the reader’s question, the angle, the underlying source, the destination, the owner and the remaining work. Add its role in the issue: a lead explanation, a practical resource, a short update or a commercial placement. A small team can maintain these fields in an ordinary document.

Separate an idea from a committed item. A promising topic without a checked source needs a different label from approved copy with a working destination. That distinction makes a plan more honest and reduces the pressure to publish weak material merely because a date is approaching.

A planning row you can copy

Use this specimen as a starting structure, then remove fields your team does not actually use. Its purpose is to expose the work needed before a title becomes a publishable item.

• Reader question: what exactly will this item help someone understand or do?
• Working angle: the answer or explanation the issue will develop.
• Evidence: the original source, its scope and any important limitation.
• Destination: the article or resource the invitation will open.
• Owner and next action: who checks or completes the item, and what remains?
• Readiness: idea, evidence checked, copy reviewed or ready for distribution.
• Placement: lead item, supporting explanation, practical resource or identified commercial material.
• Review note: what changed and what should inform the next edition.

Choose a working horizon and name the readiness states

Choose a planning horizon—a number of editions or a span of time—that the team can maintain. State it clearly and revisit it when dependencies or capacity change. Beyond it, material can remain an idea; for committed items, name an owner, a dependency and a readiness state.

A readiness state is useful only if it says what the item may and may not do. One workable set, which a team should adapt to its own process:

• Idea: may sit on the sheet; may not be promised to a contributor, a sponsor or readers.
• Evidence checked: the source has been read, its scope noted and its limits recorded; the copy may now be written.
• Copy reviewed: another person has read the text and opened the destination.
• Ready for distribution: links tested in the intended version, subject line reviewed, any commercial placement labelled.
• Dependency: each item names what it waits on, such as a source, a contributor, a resource page or an event, and cannot advance while that dependency is unresolved.

Worked example: a filled planning row (hypothetical)

Imagine Rota Notes, an invented monthly briefing for volunteer coordinators at small community venues. The team has fixed a planning horizon of four editions, and this is the sheet’s row for edition 3, the worked-method issue, at the moment its evidence is being checked. No real publication, reader reply or result lies behind it.

• Reader question: how can a coordinator write a shift handover note that the next person can use without a phone call?
• Working angle: a one-page note with five fixed headings (what happened, what is unfinished, whom to contact, what not to change, where things are kept), shown on an invented venue.
• Evidence: two parts. First, the editor’s own method, which the issue will label as the publication’s suggestion. Second, an invented volunteer-support guidance page, cited for one statement about why handovers fail. Scope: that page supports only that one statement.
• Destination: a printable handover template on the publication’s own resources page. Open question: whether it opens without sign-in on a phone.
• Owner and next action: the editor rereads the cited page and records the exact sentence relied on; the template contributor finishes the file and the access test.
• Readiness: copy drafted; evidence not yet marked as checked.
• Placement: lead explanation, with the template as the practical resource in the second slot.
• Review note: left empty until after sending.

Worked example: a source goes missing after the item looked ready

When the editor runs the evidence check, the cited guidance page no longer opens. The editor cannot tell whether it was removed, moved or restricted. The row is edited, while the edition’s promise stays as it was:

• Readiness: moved back from copy drafted to evidence pending, with the reason written in the row.
• Evidence field: now reads ‘cited page not reachable on the day of the check; the statement that relied on it is unsupported’.
• Options listed: find an equivalent source and read it in full; narrow the sentence to what the publication can show itself and label it as the publication’s method; or remove the sentence.
• Decision: no replacement is found before copy review, so the attributed statement is removed and the lead is reframed as a labelled method. The reader question and the angle are unchanged.
• Dependency check: the template access test is still open. If it also fails, the reserve item, edition 4’s reader-question piece, which is already at copy reviewed, is brought forward, and edition 3 moves within the horizon with the change recorded openly.

Keep commercial planning visible

A recovered former-form configuration points to an ESM Magazine features-list and rate-card route. That is evidence of a publishing-related resource in a signup journey. It does not tell us how that publisher made every editorial or commercial decision.

For your own publication, make placement commitments and editorial work visible to the people responsible for the issue. A commercial opportunity should not silently change the reader promise or become an unlabelled recommendation. The sponsorship guide considers that boundary in more detail.

Close the loop after each edition

After sending, note what was published, what changed from the plan and what the team learned. Include corrections, resource-access problems and useful reader questions as well as performance figures. The next planning discussion can then begin with evidence rather than a fresh guess about topics.

Use the issue-layout guide to turn the plan into a readable edition, and click analysis to avoid overstating its outcome. The calendar’s value is the quality of the decisions it supports, not the number of filled cells.

Worked example: a post-send note (hypothetical)

For the same invented edition, the post-send note might read as follows. Its observations are fictional; no real performance figures are reported.

• Published: the lead explanation of the handover note, labelled as the publication’s own method, and the template as the second item. The reader-question piece stayed with edition 4.
• Changed from plan: the attributed statement about why handovers fail was removed after the cited page could not be reached, and the lead was reframed accordingly.
• Corrections: none needed after sending in this specimen. A real note would list any.
• Access problem: a reader reply says the template downloads instead of opening in the browser on a phone.
• Reader questions: two replies ask how to hand over between venues; both are logged as candidates for a later edition.
• Measurement: click figures are reviewed separately and read with the caution described in the click-analysis guide; the specimen states none.
• Input for the next sheet: add ‘download or page?’ to the destination field, and keep a short extract and the reading date beside each cited source so a later disappearance is easier to handle.