Five handoffs, one operating brief
This is the planning sequence for a scoped engagement. Each stage produces a record the next person can use; the proposal assigns the actual work and access.
| Stage | Campaign supplies | Planning output | Decision owner |
|---|---|---|---|
| 1 · Brief | Committee, office, jurisdiction, objective | An agreed campaign brief | Authorized campaign contact |
| 2 · Scope | Volume estimates, formats, team responsibilities | Written quote with inclusions and dependencies | Campaign purchaser and Ananasi |
| 3 · Prepare | Identity records, audience evidence, final text and media | Sender packet and creative version | Assigned preparation owners |
| 4 · Review | Approved copy, timing zone, reply coverage | Launch decision with unresolved items | Named campaign approver |
| 5 · Learn | Available status and response records | Report with sources, denominators, and unknowns | Report owner defined in the proposal |
Example brief: a local campaign event
Illustrative brief, not a customer engagement: the fictional Meadowbrook council campaign wants to invite its existing authorized audience to a neighborhood meeting. The objective is attendance information; the essential text includes the venue, time, sender identity, and opt-out instruction. The campaign confirms its seat and audience boundaries before discussing a sender.
- Objective: make the event details easy to find.
- Audience record: source and permission evidence reviewed separately from the electoral district.
- Creative record: version label, text fallback, and approved destination.
- Response record: a named owner for venue questions and revocation requests.
A launch decision that survives a change
Retain the exact message version, approver, intended sender, audience record reference, schedule and zone, suppression check, test result, and open dependencies. If the venue changes after approval, the revised creative returns to review. Approval of one version does not silently authorize another.
What moves the launch
An incomplete sender packet, a missing campaign authorization, an unresolved audience question, or absent reply coverage can change the plan. Record the dependency and its owner rather than filling the gap with a promised turnaround. The launch planner explores your own calendar-day assumptions; it does not predict provider approval.
Interactive planning example
An event changes. What needs review?
Fictional Meadowbrook council campaign. This working example stays in your browser and sends no messages. It illustrates version control; it is not a Pantheon integration or a customer result.
- BriefMeeting at the community hall
- CreativeVersion 1
- ReviewApproved in this example
- Response ownerUse community hall directions
Illustrative SMS · Version 1
Meadowbrook Council Committee: Join our neighborhood meeting at the community hall, 6 PM. Reply STOP to opt out.
Version 1 is approved in this example. A revision needs a new decision.
A real release also requires the actual sender, audience evidence, suppression check, timing zone, and controlled test. Review the launch checklist.