Plan a month of blog posts that don't let a product launch crowd out evergreen SEO

You are building a four-week blog content calendar for a small team that has a product launch landing in the middle of the window — the risk I need you to actively manage is the launch crowding out every evergreen SEO post that was already supposed to publish that month.

PHASE 1 — INPUTS
TEAM AND CAPACITY
Two writers: Priya (full-time, can handle 3 posts) and Dev (also doing launch comms, realistically 1 post max this month).

LAUNCH DATE AND CONTEXT
Launching a new integrations marketplace on the 15th, mid-month.

EVERGREEN TOPICS ALREADY QUEUED
1) 'How to migrate from spreadsheet tracking to a PM tool' (target keyword: spreadsheet to project management migration), 2) 'Async vs sync team communication' (no hard keyword target yet), 3) a customer case study draft that's 80% done.

PUBLISHING CADENCE
Twice a week, Tuesday and Thursday.

PHASE 2 — BUILD THE CALENDAR
Allocate slots across the four weeks first for the minimum viable launch coverage (an announcement post, and if capacity allows a follow-up post addressing likely objections or a comparison to what the launch replaces) — treat this as a fixed, non-negotiable block rather than something that expands to fill available time, since launch content has a habit of absorbing every slot around it once it starts getting attention. Then fill the remaining slots with the queued evergreen topics in the order that keeps the site publishing something every scheduled slot, never leaving a gap with the excuse that "the team was busy with launch." For each slot, assign: the topic, the target keyword if it's an SEO post, a one-line angle, and which team member from the capacity list is realistically positioned to own it based on what you were told about their bandwidth — do not assign two heavy pieces to the same person in the same week even if the calendar math would otherwise allow it.

PHASE 3 — RISK CHECK
Identify which evergreen topic is most likely to get bumped if the launch runs long, and propose in advance which specific slot it moves to rather than leaving "we'll fit it in later" as the plan — a displaced post with no assigned new slot reliably never gets published.

PHASE 4 — OUTPUT
Produce a week-by-week table: Week | Date | Topic | Type (launch/evergreen) | Target keyword | Owner | Status risk note (only where relevant). Follow the table with the one contingency slot identified in Phase 3.