Campaign Operations · What's In Build

Department Inputs

What's being built, where it's at, and where your voice shapes it. This is not a finished system. Every entry below has a place where the department it touches gives input — in a meeting, async over email, or 1:1.

The Promise

Campaign Ops drafts the system. Your department shapes it. Every deliverable here has an open input window with a named contact and a closing date. If something on this list affects your team and you don't see your department named, that's a bug — tell us.

How to read this: Each row = one deliverable. Stage shows where it sits today. Input window tells you when feedback is being gathered. How to give input names the path — meeting, email, or 1:1. After the window closes, the deliverable goes live and starts iterating in production.

Scoping defining the work

In Build drafting

Open for Input your voice goes here

Locked shipped, in iteration

Shipped live in production

Deliverable	Stage	Departments	How to give input	Input window
[Deliverable name] [1 sentence explaining what this is]	Locked	[Dept A] [Dept B]	Closed — locked at [working session date]	[Status] [Note]
[Deliverable name] [1 sentence explaining what this is]	In Build	[Dept]	Async review — draft to [SVP name] [date]	Through [date] [Sprint #]
[Deliverable name] [1 sentence explaining what this is]	Open for Input	[Dept A] [Dept B] [Dept C]	Live in [Meeting name, day] — feedback in meeting or to [contact] after	Through [date] [Sprint #]
[Deliverable name] [1 sentence explaining what this is]	Scoping	[Dept]	1:1 with [SVP name] — [working session approach]	[Sprint #] scope-out first
[Deliverable name] [1 sentence explaining what this is]	Shipped	All	In production — flag issues to Campaign Ops as they come up	Live v1, iterating

Don't see your department? Or want to add a deliverable to this list? → reach out to Campaign Ops directly.

Framework reference: /phases.html · Full language framework: /docs/language-framework.html