Pre · phase 2
Phase 2 of 10
Setup
Build hub, brand, plan, roles, and kick off playbook.
Family PreToken #5FB55ADuration Normal
A
The intent
Why this phase exists
Concept becomes plan. We confirm the schedule, lock who's responsible for what, set up the tracking and the campaign, and stand the event up in WDS. This is the phase that makes everything after it possible.
Exit gate
Roles and approvals are agreed, the event is configured in WDS with the right access and permissions, and the campaign plan has owners against every line.
B
The work, by actor
Our people
Craft & judgement
Craft, judgement and client-facing approval.
- Event Manager — Confirm schedule, stakeholders, approvals, responsibilities and decision deadlines.
- Event Manager — Set roles and RACI, change control and comms cadence.
- Marketeer — Set tracking, segments, messaging and the campaign plan with owners assigned.
- Producer — Lock the speaker outreach plan, prep materials and programme structure drafts.
- Technical Production — Define signal flow, staffing, equipment, comms and rehearsal requirements.
- Technical Production — Set venue AV requirements, bandwidth plan, local AV scope and responsibilities.
- Event Manager — Capture speaker releases, recording consent, privacy and sponsor usage rights.
Our agents
Scale & speed
AI drafts; a named human owns and approves.
No agent tasks in this phase.
Our platform
Reliability
Deterministic WDS behaviour, no actor required.
- Producer — Migrate speakers to users with tasks and contact management.
- Technical Support — Configure the event in WDS: access, pages, permissions baseline.
C
What the client gets
Delivered
A fully configured event in WDS. A campaign plan with named owners. Their team clear on who does what and by when.
D
The safeguard
What could go wrong
The event runs and we discover we never got recording consent or sponsor usage rights.
Why it won't
Compliance, releases and consent are a Setup task with an owner, not something we chase during Live.
E
The thread continues
Wavecast Phase Playbook · internal conceptual reference
Phase tokens bound to the Colour Registry · wheel engine v1.3 · multi-actor delivery model.
Phase tokens bound to the Colour Registry · wheel engine v1.3 · multi-actor delivery model.