Swell

Audience mapping begins with structured interviews and existing material read in silence before a workshop. We chart segments by need, not demographics alone, and mark where current messages fail to reach a segment without rewriting the whole hierarchy. The chart stays on the wall for two weeks so stakeholders can annotate with a pen rather than a slide comment.

Message architecture turns research into a ordered stack: promise, proof, permission, and channel-specific variants that still read as one voice. Each layer is tested by reading aloud in the studio; if a sentence cannot be spoken clearly, it is rewritten before it enters the document. The architecture feeds every later table row — calendar, channel, launch — without duplicate drafting.

The editorial calendar is a quarter grid with owners, formats, and dependencies visible at once. We do not colour-code for decoration; colour marks approval state only. Weekly re-reads compare live posts to the grid and log amendments in the tidebook rather than editing the grid silently.

Channel planning aligns paid, owned, and earned work to the same hierarchy document. Each channel brief states audience slice, message layer, and success criteria described qualitatively — clarity of sign-up path, consistency of narrative — never numeric targets on this site. Briefs are dated so media teams know when copy freezes.

Launch sequencing orders touchpoints across a bounded window, usually six weeks, with explicit dependencies drawn on the waterline rail. We name who publishes, who approves, and what happens if a date slips. The sequence is shared as a folded sheet summary for leadership and a full table for operators.

Governance read-through is a standing review of live communications against the approved hierarchy. We mark drift, suggest realignment, and record decisions in the amendment log. For regulated sectors, the read-through produces a plain-language memo suitable for compliance files without promising regulatory outcomes.