An editorial calendar is a capacity plan, not a list of keywords assigned to dates. It connects audience needs and business priorities to real owners, review time, source requirements, and publishing destinations.

The framework below produces a 12-month view without pretending every title is final. Near-term work should be specific. Later work should remain flexible enough to absorb product changes, new evidence, and lessons from published content.

Start with a source inventory

Collect inputs before drafting titles:

  • Questions from customers, support, sales, and product onboarding.
  • Existing pages that are outdated, duplicated, incomplete, or unsupported.
  • Product releases and operational dates that are genuinely scheduled.
  • Primary documentation, internal subject-matter knowledge, and original data available to support a page.
  • Business goals that content can reasonably assist, without treating ranking as a guaranteed outcome.

Use one row per publishable outcome

A spreadsheet, project board, or database is enough. Include these fields:

  • Reader and task: who needs the page and what they should accomplish.
  • Working title: descriptive, provisional, and free of unsupported promises.
  • Content type: guide, release note, comparison, reference, case study, or update.
  • Source owner: the person responsible for evidence and factual review.
  • Editorial owner: the person responsible for structure, clarity, and completion.
  • Primary sources: links or records that support material claims.
  • Destination: WordPress site, category, language, and intended status.
  • Dates: brief ready, draft due, review due, and publish window.
  • Dependencies and risk: launch timing, legal review, localization, media, or unavailable data.
  • Lifecycle: planned, drafting, review, approved, scheduled, published, update, or retired.

Calculate capacity before assigning dates

Use the team's own history. For each content type, estimate research, drafting, technical review, editorial review, media, and publishing time. Include rework and leave. Do not borrow a universal “posts per writer” benchmark.

A simple capacity formula is:

monthly publishable capacity =
  available editorial hours
  / median reviewed hours per item
  × reliability buffer

The reliability buffer is a planning choice, not an industry standard. Use it to leave room for corrections and urgent work. If the calendar only works when every draft is approved on the first pass, it is already overloaded.

Prioritize with explicit criteria

Score proposals with criteria the team can explain. Possible inputs include reader need, evidence readiness, business relevance, freshness risk, effort, and dependency risk. Choose weights openly and keep the raw inputs beside the score.

A high search-volume estimate should not override weak evidence or poor site fit. A narrow page that resolves a recurring customer problem may deserve priority even when its public search demand is modest.

Plan at three levels of certainty

  • Next 4–6 weeks: named owner, approved brief, sources, and review date.
  • Following quarter: validated task, provisional title, likely owner, and dependency notes.
  • Remaining year: themes, campaigns, recurring maintenance, and capacity reservations.

This prevents a January plan from pretending to know every title needed in November. It also keeps longer-term themes visible without locking the team into stale assumptions.

Add recurring maintenance

A calendar should reserve time for existing pages. Track pages with changing versions, prices, policies, screenshots, external links, or product behavior. Set review triggers based on the source: a product release, policy update, reported error, broken link, or measured decline that warrants investigation.

Do not change a displayed “updated” date unless the page was materially reviewed or revised. Retire a page when it cannot meet current evidence standards and return an appropriate 404 or 410 response if it has been removed.

Map the plan into AutoPress

AutoPress can hold titles, generation instructions, WordPress destinations, content status, and publishing queues. The calendar remains the planning source; AutoPress becomes the execution surface for approved work.

  1. Create only titles whose brief and destination are ready.
  2. Carry source requirements and exclusions into the generation instructions.
  3. Generate a small batch and publish as drafts while the template is being calibrated.
  4. Record review outcomes in the planning system.
  5. Increase batch size only after accuracy and failure handling are predictable.

Weekly operating review

Review blocked items, overdue evidence, draft quality, publishing failures, corrections, and next-week capacity. Move or remove work instead of silently letting dates become fiction. The calendar is useful when it exposes tradeoffs early, not when every cell stays green.