Magazine editorial calendars and issue planning: a guide

What to take away

An editorial calendar answers what will be published, where, when, and by whom. An issue plan answers how the selected work forms one coherent edition. A print flatplan maps that edition to pages. These records should agree, but each has a separate job.

Begin with an issue statement

Define the audience, central question, publication date, shelf or access period, geographic scope, tone, and exclusions. State what the reader should understand, feel, or be able to do after the issue. Then choose stories that perform different jobs within that promise.

The image illustrates dated planning. It does not represent a current production schedule.

Use a mix table to expose repetition:

The mix then goes onto a flatplan, which maps the issue to a fixed number of pages. A 96 page example:

Build the dated calendar

Plan fixed dates and resource-heavy work far enough ahead to make access, rights, and production possible. Keep some capacity flexible.

West Virginia University's explanation of managing a content calendar describes a schedule that can include platform, purpose, timing, responsibility, and deadline.

Each row carries one gate for one issue. Typical lead times for a monthly, counted back from copy lock:

Swap the offset for a calendar date once the issue is scheduled. A weekly or a quarterly shifts every row.

Work backward from immutable dates. Printing, mailing, embargoes, travel, events, seasonal access, and contributor availability may create real constraints. Add decision dates before costs become unrecoverable.

The UK government's guidance on planning new content asks whether the content belongs on the site, then separates readers meeting the subject for the first time from specialists who already understand it.

A magazine calendar benefits from the same two questions. Decide whether an idea belongs in this publication, then decide which reader it is written for, before a date is attached to it.

Connect content to capacity

Count the editor, writer, design, photography, fact-checking, rights, and production hours available. A full calendar can still be impossible if every feature enters structural editing during the same three days. Limit simultaneous work and reserve capacity for expected revisions.

Maintain a backup item only when it is genuinely ready for the slot. A title without reporting, rights, or a willing contributor is not contingency coverage.

Review and roll forward

After release, compare planned and actual dates, page counts, costs, dropped items, rushed proofs, corrections, and reader response. Keep conclusions specific. "Start earlier" is weak. "Move photo commissioning seven days before the reporting check" is a testable change.

Common questions

Should the public editorial calendar match the internal one?

No. A public calendar may summarize themes for contributors or advertisers; the internal record contains owners, risks, and changing status.

Does every issue need a theme?

No. It does need a clear editorial purpose and a balanced reader experience.

What belongs in the backlog?

Unscheduled ideas with enough context to evaluate later, not promises or hidden assignments.