Campaign Plan

---
name: campaign-plan
description: Turns event or campaign inputs (contract, brief, previous plan format, RACI) into a first-draft campaign plan for Notion with objectives, owners, budget and timeline. Use at kick-off of a new event or campaign, before the Notion page is built.
---

# Campaign Plan in Notion

## When to use

At the start of a new event or campaign, once the brief and previous-plan
reference are ready, and before the Notion page is built.

## You need

- The event contract or brief specifying deliverables
- The event URL or key info source
- A previous project plan to use as the format reference
- The RACI for key responsibilities

## Steps

1. State what the input covers and what it doesn't.
2. Confirm responsibilities, key deliverables and required resources from the
   kick-off.
3. Define event objectives, both internal and external-facing.
4. Set success measures: benchmark targets and stretch goals for this event.
5. Assign a clear action owner for each piece of work, and flag where dependents
   sit and where leadership is involved.
6. Define the post-event follow-up process and its accompanying comms plan.
7. Set the priority order: what must happen, and when.
8. List anything you were unsure about.

## Decisions and defaults

- Objectives differ by event type (own event vs external sponsorship). Default:
  ask before proceeding.
- Timeline expectations. Default: ask before proceeding.
- Order tasks are performed. Default: ask before proceeding.
- Format and frequency of updates and communications. Default: ask before
  proceeding.

## Output

Text, in this order: coverage note; objectives (internal and external-facing);
action owner and dependencies; budget with clear totals; project plan linking out
to the comms draft doc; event timeline with key deliverable dates; uncertainties.

## Never do this

- Do not set budgets or timelines that ignore production lead times, or that make
  the whole plan late by default.
- Do not assume stakeholders will follow the plan without flagging what happens if
  a step is ignored or a deadline is missed.
- Do not skip approval paths, especially where pushback mid-process is likely.
- Do not leave the objective vague. This is where scope drifts and unrelated work
  starts attaching itself to the plan.
- Do not invent numbers, names, quotes or trends. If the input doesn't support it,
  say so and leave a placeholder.
- Never output anything that identifies an individual by name in a shared plan
  beyond the RACI itself; aggregates and role-level findings only elsewhere.

## Before it goes out

- Every action owner and dependent checked against the RACI by hand.
- Objectives still match what was agreed in the kick-off, not an earlier draft.
- Budget totals read against the contract.
- Metrics checked against comparable previous events.
- Risks and limitations for each deliverable understood.
- Approval paths (who, what and when) confirmed for each deliverable.

This output is a draft. A person signs it.