Editorial Calendar Planner

What This Skill Does

Generates a structured editorial calendar for a publication — mapping content across weeks or months, balancing evergreen and timely pieces, tracking production stages, and aligning coverage with external events.

When To Use This Skill

• You are planning the next quarter's coverage and need a skeleton calendar before assigning stories
• Your publication has a seasonal peak (awards season, festival coverage, holiday gift guides) and you need to reverse-engineer the production timeline from the publish dates
• You have recently expanded or shrunk your team and need to redistribute workload across writers
• An editor-in-chief is onboarding and wants to see the full pipeline visualised in one document
• You are launching a new publication or section and need to build the first production schedule from scratch
• You need to coordinate coverage across multiple beats that share the same production bottleneck (a single photographer, one copy editor, a shared designer)
• You want to stress-test an existing rough plan: you have a list of stories you want to run but have not mapped them against the calendar to check for bottlenecks, workload peaks, or deadline conflicts
• You are preparing a planning document for a stakeholder meeting (editorial board, publisher, funder) and need to show what the team will produce over the next period

What You Need To Provide

Required:

• Publication type and frequency (weekly, biweekly, monthly, daily digital)
• Team size — how many writers, editors, and other production staff
• Beat coverage — which subjects your publication covers
• Planning period — the timespan you want the calendar to cover (4–12 weeks)

Optional:

• Upcoming external events relevant to your beats (festivals, elections, legislative sessions, industry conferences, awareness weeks, holidays)
• Existing recurring content (regular columns, series, reviews sections)
• Any hard editorial commitments already on the schedule (commissioned features, pre-sold advertorial adjacencies, special issues)
• Preferred content mix (e.g., "we want more long-form features and fewer news recaps")
• Historical patterns — which types of content perform best, which weeks are slow for readership
• Production bottleneck information — does photography take longer than writing? Is the copy desk a single person?
• Writer availability notes — part-time schedules, planned leave, other commitments
• Whether you want the calendar to include web/digital slots alongside print, or print only

How the Assistant Approaches This

1. Establishes the production rhythm. Identifies the issue dates or digital publishing cadence and works backward from each publish date to set production stage deadlines: when pitches must be approved, when drafts are due, when editing is complete, when final copy goes to layout or CMS. For publications with overlapping production cycles (where Issue N is in layout while Issue N+1 is in draft), the calendar explicitly maps the overlap so the editor can see which days the team is serving two issues at once.

2. Maps external events. Places known external events on the calendar weeks and classifies each: does it warrant a planned feature, a short news slot, or nothing? Events that drive cover features get assigned early and locked; events that are relevant but secondary get noted as potential Opener or sidebar material. Weeks with no event hooks are flagged as evergreen slots.

3. Fills the content grid. Slots recurring content first (columns, reviews, roundups) since these are non-negotiable. Then places event-driven features in the weeks they must run. Then fills remaining feature slots with evergreen content, placing the strongest evergreen pieces in the quietest weeks where they will carry the issue without competition from timely coverage.

4. Distributes workload. Assigns each piece to a specific writer, ensuring no writer carries more than two pieces in active production simultaneously (unless the team size forces it). Identifies each writer's peak load week so the editor knows in advance which weeks are fragile. Flags any imbalances: a writer carrying significantly more than their share, or a writer with capacity that could absorb overflow.

5. Adds buffer mechanics. Reserves at least one open slot per issue or per week for unplanned coverage. Marks which planned pieces are "hold-able" (evergreen features that can shift one issue later without losing relevance) versus "locked" (event-driven coverage that must run on time or not at all). This gives the editor a clear decision framework when breaking news forces a schedule change.

6. Builds deadline cascades. Shows the critical path for each issue: the sequence of dates by which each stage must be complete, working backward from the publish date. Makes it immediately visible when a slipped draft deadline cascades into an editing bottleneck. For issues with a shared bottleneck (a single photographer, a single copy editor), the cascade highlights the dependency.

7. Identifies the pitch pipeline. Looks beyond the planning period to flag stories that need pitching or early reporting now in order to be ready for the quarter after. Prevents the common problem where a team finishes one quarter's calendar and has nothing in development for the next.

8. Surfaces scheduling risks. Reviews the full calendar for structural problems: weeks where multiple high-effort pieces converge on the same editor, personnel concentration risks (too much riding on one writer), external dependencies (photographer availability, source access windows), and holiday timing conflicts. Each risk includes a specific mitigation.

Output Format

A week-by-week editorial calendar covering the requested period. Each week includes: the publication date (if applicable), planned content with working titles and assigned beat/writer slot, the current production stage for each piece (pitch > assigned > draft > edit > final > publish), and any external events that week.

Followed by five summary sections:

1. Deadline Cascade — the production timeline for each issue, showing every stage deadline in calendar-date form
2. Content Mix — the ratio of news, features, investigations, evergreen, and recurring content across the full period
3. Workload Distribution — pieces per writer across the period, with peak load weeks flagged
4. Pitch Pipeline — which story ideas need to be developed now for future issues, so the editor can see what is in the queue beyond the current planning window
5. Scheduling Risks — weeks that are overloaded, under-planned, or dependent on a single writer, with mitigation suggestions

Additional sections when applicable: 6. Photographer/Freelancer Booking Summary — consolidated dates for external contractors who need advance notice 7. Editor's Action Checklist — time-sequenced list of decisions and bookings the editor must make in the first two weeks of the planning period

Total length: 800–1,500 words depending on the planning period. Plain editorial language throughout — readable by an editor who has never used a project management tool. Tables are used for the issue-by-issue calendar and for summary data; prose is used for risk assessments and editorial strategy notes.

Quality Criteria

• Every week in the planning period has at least one content slot filled and at least one buffer or open slot identified
• Production stage deadlines are internally consistent — a piece cannot be in "edit" after its publish date
• External events are mapped to the correct calendar weeks and connected to specific planned content
• Workload distribution is explicit — each piece is assigned to a writer slot (by name, beat, or number) and no writer is silently overloaded
• The content mix includes at least three distinct content types (not all features, not all news)
• At least one scheduling risk or bottleneck is identified and flagged with a specific mitigation
• Buffer slots for breaking news are present and marked as movable
• Recurring content (columns, series, reviews) appears on a consistent schedule
• Hold-able vs. locked pieces are distinguished so the editor knows what can move
• The deadline cascade is internally consistent across overlapping production cycles
• Output is free of generic AI-template phrasing — no "delve into," "navigate the complexities of," Latinate filler verbs ("utilize," "facilitate," "leverage" where a plainer verb fits), restate-the-question intros, summary-of-the-summary closes, or em-dash overuse

Example

Input

Publication: A biweekly arts and culture magazine, print with a companion website. Six issues in the planning period.

Team: 4 writers (W1 covers film, W2 covers music, W3 covers visual arts and theatre, W4 is a generalist/features writer) plus 1 editor-in-chief who also copy-edits.

Beats: Film, music, visual arts, theatre, books, food/drink (occasional).

Planning period: 12 weeks, September 1 through November 23.

External events:

• Regional film festival (October 7–13)
• National book awards longlist announced September 18
• Major modern art retrospective opens October 25 at a city gallery
• Holiday book and gift guide needed for the November 23 issue

Recurring content:

• "The Opener" — a 400-word front-of-book opinion column, rotating between writers
• "Sound Check" — a music review slot, every issue
• "What We're Reading" — a 600-word books roundup, every issue

Existing commitments: A commissioned two-part profile of a theatre director, Part 1 to run in Issue 2 (September 29), Part 2 in Issue 3 (October 13).

Bottleneck: Photography. The magazine uses one freelance photographer who needs two weeks' notice for portrait shoots.

Output

Editorial Calendar: September–November

Publication: Biweekly arts and culture magazine (print + web) Period: 12 weeks, 6 issues Team: W1 (film), W2 (music), W3 (visual arts/theatre), W4 (generalist), Editor-in-chief

Rhythm: Biweekly print, 6 issues. The companion website publishes daily news briefs independently; this calendar covers print features and the three recurring slots only. Web-only content is not scheduled here unless a print piece has a web companion.

---

Production Stages and Lead Times

Each piece moves through six stages. The standard lead time for a biweekly cycle is:

Stage	Abbreviation	Lead time before publish
Pitch approved	P	4 weeks
Assigned + reporting	A	3 weeks
Draft due	D	10 days
Edit complete	E	5 days
Final to layout	F	3 days
Publish	PUB	Day 0

Photography note: Portrait and location shoots require booking the freelance photographer 2 weeks before the shoot date. Since shoots happen during the reporting phase, the photographer must be booked at least 4 weeks before publish. For Issue 1, that means bookings should already be confirmed before September 1.

Overlap note: On a biweekly cycle, Issue N is in layout while Issue N+1 is in draft. The editor is copy-editing two issues in parallel during the five days before each publish date. This overlap is manageable with four writers but tight when combined with fast-turnaround event coverage.

---

Issue 1 — Publish September 15

Event context: No major events this issue. September album releases begin. The fall arts season is starting but no single event dominates.

Editorial strategy: Use this issue to set the season. The cover feature surveys the full September–November landscape, giving readers a reason to stay with the magazine through the quarter. Feature 2 is forward-looking — a filmmaker profile timed to generate interest before the October festival.

Slot	Content	Writer	Stage (Sep 1)	Hold-able?	Notes
Cover feature	Fall arts season preview: what to see, hear, and read September through November	W4	Draft due Sep 5	No — time-sensitive; must run in the first fall issue	Anchors the issue. References the film festival, book awards, and retrospective. Establishes the season for readers and creates forward hooks for Issues 3, 4, and 6.
Feature 2	Profile of an emerging filmmaker screening at the regional festival	W1	Assigned, reporting	Yes — could move to Issue 3 as a festival companion	Photo shoot needed. Book photographer by Sep 1 at the latest. If the photographer is unavailable, consider a phone interview portrait or a supplied publicity still.
The Opener	Opinion: why arts coverage still matters in a shrinking local media landscape	W3	Draft due Sep 5	N/A — column	Tone-setter for the quarter. Should reference specific local closures or cutbacks, not abstract industry trends.
Sound Check	Review: pick from September album releases	W2	Awaiting release	N/A — review	Draft due Sep 8. W2 should have the album shortlist by Aug 25.
What We're Reading	Books roundup — three fall titles	W4	Assigned	N/A — recurring	Short turnaround; W4 handles since the cover feature draft is already filed.
Buffer slot	Open — hold for breaking arts news in the first two weeks of September	—	—	—	If unused by Sep 10, pull forward a short evergreen piece (a restaurant review or a gallery opening brief from W3) to fill the page.

Deadline cascade for Issue 1:

Date	Milestone
Aug 18	Pitches approved for cover feature and Feature 2
Aug 25	W1 begins reporting on filmmaker profile; photographer booked
Sep 1	W4 cover feature draft in progress; W1 photo shoot window opens
Sep 5	Cover feature draft due; Opener draft due
Sep 8	Sound Check draft due; What We're Reading draft due
Sep 10	All drafts in edit; editor begins copy-edit pass
Sep 12	Final copy to layout
Sep 15	Publish

---

Issue 2 — Publish September 29

Event context: National book awards longlist announced September 18. This drives Feature 2 and The Opener.

Editorial strategy: The commissioned theatre director profile is the cover. The book awards longlist gives Feature 2 and the books roundup a strong hook, but the turnaround is tight — only 11 days from longlist to publish. Keep the awards reaction piece short (1,200 words max) and have W4 combine research for both the feature and the roundup.

Slot	Content	Writer	Stage (Sep 1)	Hold-able?	Notes
Cover feature	Theatre director profile, Part 1 (commissioned)	W3	Assigned, reporting	No — pre-sold commitment	Contracted piece. Photo shoot needed. Book photographer by Sep 8 at the latest. W3 should have interview access confirmed by Sep 1. Two-part structure means Part 1 must stand alone as a complete read while leaving the narrative open for Part 2.
Feature 2	National book awards longlist reaction — surprises, snubs, and what the list says about the year in publishing	W4	Pitch approved	No — pegged to Sep 18 announcement	Longlist announced Sep 18. Draft due Sep 22. This is the tightest turnaround of the quarter: four days from announcement to draft. Keep the piece to 1,200 words. W4 should prepare a template and longlist context notes before Sep 18 so the writing time is spent on analysis, not background research.
The Opener	Opinion: the politics of prize lists	W2	Pitch stage	N/A — column	Ties to the book awards. W2 writes the opinion column this issue while W1 is in pre-reporting mode for the film festival. W2 should pitch the specific angle by Sep 8 — "prize lists are political" is a starting point, not a column.
Sound Check	Review: album or live concert review	W2	Awaiting event	N/A — review	W2 has both Sound Check and The Opener this issue. Manageable — Sound Check is a standard 500-word review, and The Opener is 400 words. Combined workload is under one feature's worth.
What We're Reading	Books roundup — longlist picks and fall reading	W4	Will draft after longlist	N/A — recurring	Combines with Feature 2 reporting. W4 can draft both pieces from the same research session.
Buffer slot	Open	—	—	—	Film festival starts Oct 7. W1 is in pre-reporting mode: arranging interviews, reviewing the festival programme, confirming press accreditation. Do not assign W1 any additional work this issue.

Deadline cascade for Issue 2:

Date	Milestone
Sep 1	W3 begins reporting on theatre director profile
Sep 8	Photographer booked for W3 portrait shoot; W2 Opener angle pitched
Sep 15	Issue 1 publishes; W3 profile draft due Sep 19
Sep 18	Book awards longlist announced — W4 begins awards reaction piece
Sep 19	W3 Part 1 draft due
Sep 22	W4 awards reaction draft due; What We're Reading draft due
Sep 23	W2 Opener draft due; Sound Check draft due
Sep 24	All drafts in edit
Sep 26	Final copy to layout
Sep 29	Publish

Production overlap: Between Sep 15 and Sep 19, the editor is simultaneously closing Issue 1 (final layout corrections, press check) and receiving drafts for Issue 2. This is standard for a biweekly cycle but worth noting: the editor should not schedule meetings on Sep 16–17. The same overlap occurs between every pair of consecutive issues — the three days after each publish date are always double-loaded. On a biweekly cycle, the editor effectively has 11 single-focus days and 3 double-focus days per cycle. Planning around this pattern is more effective than treating it as an exception each time.

---

Issue 3 — Publish October 13

Event context: Regional film festival runs October 7–13. Publish date falls on the festival's closing day.

Editorial strategy: This is the highest-pressure issue of the quarter. The cover is the commissioned Part 2 of the theatre profile (locked commitment). Feature 2 is the film festival dispatch, which must be filed mid-festival. The Opener can be a short festival-adjacent opinion from W1 since they are already on-site. The risk is concentrated: W1 and W3 are both on tight deadlines the same week, and the editor must fast-track editing for the festival piece.

Slot	Content	Writer	Stage (Sep 1)	Hold-able?	Notes
Cover feature	Theatre director profile, Part 2 (commissioned)	W3	Not yet started	No — pre-sold commitment, Part 1 runs in Issue 2	Part 1 must be finalised and approved before W3 begins Part 2. Earliest start date: Sep 25 (after Part 1 is in layout). Draft due Oct 3. If Part 1 edit runs long, Part 2 is at risk.
Feature 2	Film festival dispatch — highlights, standout screenings, audience trends, one breakout title	W1	Pre-reporting	No — pegged to Oct 7–13 festival dates	Festival runs Oct 7–13. Publish-week filing: W1 files draft Oct 8 (mid-festival, after the first weekend of screenings). Draft covers the first half of the programme. If a major story breaks in the festival's second half, W1 files a 300-word update by Oct 10 and the editor inserts it.
The Opener	Opinion: a festival-adjacent take (what audiences want vs. what programmers select, or similar)	W1	Pitch stage	N/A — column	W1 can write a 400-word column from the festival without adding heavy workload. The angle should come from something W1 observes on-site, not from pre-reporting. Pitch by Oct 5; draft by Oct 9.
Sound Check	Review	W2	Awaiting event	N/A — review	Standard slot. W2 has no feature this issue, so capacity is clear.
What We're Reading	Books roundup	W3	Assigned	N/A — recurring	W3 picks up this slot while W4 rotates to heavier feature work in Issues 4 and 5. W3 should draft this before Oct 1, before the Part 2 deadline crunch begins.
Buffer slot	Open — likely consumed by additional festival coverage	—	—	—	If the festival produces a breakout story that exceeds the dispatch (a controversy, a surprise premiere, a major acquisition), this slot absorbs it. W4 is available as backup: W4 can attend a screening and file a 600-word companion piece if W1 is overloaded.

Deadline cascade for Issue 3:

Date	Milestone
Sep 25	W3 begins Part 2 of theatre profile (after Part 1 is in layout for Issue 2)
Sep 29	Issue 2 publishes
Oct 1	W3 files What We're Reading draft (early, before Part 2 crunch)
Oct 3	W3 Part 2 draft due
Oct 5	W1 pitches Opener angle from festival prep
Oct 7	Film festival opens — W1 on-site
Oct 8	W1 files festival dispatch draft (mid-festival)
Oct 9	W1 Opener draft due; editor begins fast-track edit of dispatch and Part 2
Oct 10	All drafts in edit; final copy to layout
Oct 13	Publish / Film festival closes

Scheduling risk — Week of Oct 7: This is the single highest-risk week of the quarter. W1 is filing from the festival and writing The Opener. W3 is finalising Part 2 of the theatre profile. The editor carries the full editing load for both pieces simultaneously, with only three working days before layout. Mitigation: pre-edit W3's Part 2 draft before Oct 7 if the draft comes in early; keep W4 on standby for a festival backup piece; the editor should block Oct 8–11 completely (no meetings, no admin, no web content).

---

Issue 4 — Publish October 27

Event context: Major modern art retrospective opens October 25 at the city gallery. Press preview likely October 23–24.

Editorial strategy: Pressure drops after the festival issue. The retrospective gives W3 a strong cover feature with a clear press-preview window. Feature 2 is W1's post-festival analysis — this piece is evergreen-adjacent and can be held to Issue 5 if something more urgent surfaces. A recovery week for the editor after the Issue 3 crunch.

Slot	Content	Writer	Stage (Sep 1)	Hold-able?	Notes
Cover feature	Modern art retrospective — review of the exhibition and interview with the lead curator	W3	Pitch approved	No — pegged to Oct 25 opening	Exhibition opens Oct 25. Press preview likely Oct 23–24. W3 attends the press preview and files the review with a 48-hour turnaround. Photo shoot at the gallery during the press preview — book the photographer by Oct 10 at the latest. The review should cover both the exhibition itself and the curatorial argument: what the retrospective claims about the artist's legacy and whether the work on the walls supports that claim.
Feature 2	Post-festival analysis: which films from the regional festival will find distribution, which will disappear	W1	Pitch approved	Yes — can move to Issue 5	Evergreen-adjacent. Based on W1's festival reporting and follow-up calls with distributors and sales agents. If a stronger timely piece appears (an award announcement, a controversy from the festival aftermath), swap this for Issue 5 and run the timely piece here.
The Opener	Opinion	W4	Pitch stage	N/A — column	W4's turn. Subject open — could be food/drink adjacent (fall restaurant openings), a reflection on arts funding, or a personal essay. Pitch by Oct 13.
Sound Check	Review	W2	Awaiting event	N/A — review	Standard slot.
What We're Reading	Books roundup	W4	Assigned	N/A — recurring	W4 handles both the Opener and the roundup. Combined word count is 1,000 words — manageable in a week where W4 has no feature.
Buffer slot	Open	—	—	—	Calendar is lighter this issue. Good week to commission a short freelance piece or to run an evergreen feature that has been in the drawer.

Deadline cascade for Issue 4: