Run a content-queue health check
Reads the master calendar and current pipeline state and produces a health report — date conflicts, topic clusters colliding, channel gaps, and missing Produce handoffs — flagging issues without rescheduling.
In / outMaster calendar + pipeline state (drafts / ready / scheduled) → structured health report with flagged issues
You might say…
“I haven't looked at the calendar in two weeks. Tell me what's broken before I find out the hard way.”
What it does
Reads the master calendar plus the current pipeline state (drafts, ready-to-ship assets, scheduled items) and produces a structured health report — date conflicts, topic clusters shipping too close together, channels with empty schedule windows, and missing handoffs from Produce. Used as a periodic pass to surface what needs attention before sequencing decisions are made; flags issues but does not reschedule.
Trigger: Use as a periodic pass to surface scheduling risks and pipeline gaps before committing to the next window's schedule.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation