Generate Campaign Plans and Briefs

Overview

Campaign plan generation turns an approved communication strategy into a full editorial skeleton: week-by-week, workspace-by-workspace plan slots with exact `weekStart` and `plannedDate` values, each slot eventually materializing as a content brief in the target workspace calendar. This is a single user action that triggers durable orchestration—processed sequentially by week and workspace rather than as a fragile monolithic batch—so large campaigns can reach nominal volumes (up to sixteen briefs per workspace per week, split technically only on failure) without silent truncation.

During generation, CntX maintains cumulative editorial memory: titles, angles, keywords, and canonical channels already used earlier in the run inform later slots so the model avoids repeating itself. An anti-collision comparator flags overlapping topics; targeted repairs fix invalid or colliding slots without discarding valid briefs from the same batch. RAG retrieval from campaign source documents and company context is mandatory in the generation contract—briefs should cite evidence keys and coverage where the product surfaces provenance.

When generation completes and passes validation, briefs appear in needs review status in each workspace Calendar, tagged to the campaign. Campaign detail shows a paginated briefs summary (fifteen per page) with filters; Quick Review offers a focused validation queue. Editorial destinations attached during strategy setup inform where each brief intends to publish.

When to use

Run plan and brief generation when:

• Campaign strategy is saved and reflects approved objectives, key messages, channels, and destinations.
• Source documents are indexed if your workflow depends on document-grounded messaging.
• You are ready to review a full brief set—not a single trial slot.
• A previous plan is stale after strategy changes and stakeholders approved regeneration.

Do not generate repeatedly without review between runs—you risk duplicate slots, capacity noise, and reviewer fatigue. Fix strategy first; regenerate once.

Before you start

• Complete Generate and Edit a Campaign Strategy for all targets.
• Confirm campaign start and end dates cover the intended launch window.
• Verify weekly effort budget and channel frequencies on child strategies align with realistic output—see capacity guidance if evergreen calendars run in parallel.
• Ensure reviewers have access to each target workspace.
• Optional but recommended: skim Understand Campaign Capacity and Calendar Conflicts so you interpret overflow warnings correctly.

Steps

1. Open Campaigns → [campaign name] and locate the Plan or Generate step in the campaign progress rail.
2. Review pre-flight indicators: strategy freshness, document indexing status, target list, and any stale-plan warnings from earlier edits.
3. Choose Generate plan (wording may vary: Generate campaign plan, Generate briefs). Confirm if the UI asks about overwriting provisional slots from a prior run.
4. Wait for orchestration to finish. Progress may show week and workspace granularity; large multi-target campaigns take longer than single-workspace launches. Do not navigate away if your session warns about interruption—durable runs resume, but UX is smoother if you stay on the page.
5. When complete, open the Briefs tab or summary panel on campaign detail. Scan totals by workspace and channel.
6. Switch to Quick Review from campaign detail or Home if a priority card appears. Review briefs in validation order: title, angle, persona, funnel stage, pillar, planned date, and source evidence when shown.
7. Open a target workspace Calendar, enable the Campaign planning layer (and multi-select if you compare with evergreen strategy), and confirm dated items appear on expected weeks.
8. For spot checks, open individual briefs and verify channel and destination alignment with the child strategy tab you configured earlier.
9. Note any capacity or collision warnings surfaced post-generation; adjust strategy frequencies or remove conflicting evergreen items before mass approval.

Expected result

A CampaignPlan with slots covering the campaign window across all targets, and content briefs created in each workspace calendar in needs review (or equivalent draft review state). Campaign detail lists briefs with pagination and filters; Quick Review queues items awaiting human decision.

Editorial memory from the run reduces duplicate angles across weeks and brands. Source-backed briefs show traceability to uploaded documents where the product exposes evidence. The campaign remains hidden from business-as-usual views until you approve and publish content—generation staging avoids half-finished plans polluting live calendars, though brief rows may be visible in review states depending on your build.

Tips / common issues

• Generation stuck or slow — Large campaigns with many targets/weeks are expected to run longer. Check campaign status panel; durable orchestration should resume failed steps without restarting validated groups.
• Missing briefs in one workspace — Target may lack child strategy, enabled channels, or destinations. Revisit workspace strategy tab and regenerate.
• Duplicate topics — Rare after memory and anti-collision; reject duplicates in Quick Review and remove slots if regeneration keeps pairing the same angle—often signals weak pillar diversity or too few key messages.
• Briefs without evidence — Upload and index source documents before generation; verify document processing succeeded.
• Dates on wrong weeks — Check child strategy timezone and campaign dates; regenerate if strategy dates shifted after an earlier plan.
• Too many briefs — Lower channel frequencies or shorten campaign window before regenerating; capacity assessment may show overflow against evergreen work.
• Approved strategy but stale plan flag — Strategy fingerprint changed. Use Regenerate a Stale Campaign Plan instead of forcing partial edits slot by slot.

Next step

Review, Approve and Remove Campaign Briefs to validate the generated set before content production.