Plainly

We begin with a planning intensive or a document read, depending on what you already hold. The first deliverable is always written: a hierarchy draft or an annotated review of your current plan. Meetings follow the document, not the reverse. Within two weeks you should see a quarter grid or a clear list of gaps before any channel work is scheduled.

Month one establishes the grid, names owners, and runs four Monday re-reads. Our planner attends the first two re-reads in person or by video; the editor joins for message architecture weeks. By week four the amendment log should contain at least one dated entry even if the plan is stable — we use the log to practice the ritual.

Yes. Most quarter programmes include video re-reads and photographed wall grids. We align to SGT for standing meetings and ship printed tidebooks when postal service is practical. Time zones beyond APAC are accepted case by case if the re-read ritual can be kept.

You receive a PDF tidebook archive: hierarchy document, final grid, amendment log, and read-through memos. Source files for the grid are included when your IT policy allows. We do not withhold editable files as a default; we ask that amendments continue in the log format so history stays visible.

Owned web, email, social, events, partner comms, and internal leadership notes are common. Paid media appears as briefs tied to the hierarchy, not as separate creative universes. We describe platforms generically in plans — major social networks, search, display — without certification badges or policy claims on this site.

Two initials on the amendment form: your communications lead and a named executive delegate. Verbal approvals stand for one business day only. We record slippage on the grid with strikethroughs rather than silent deletes. Emergency copy still enters the log so auditors see timing, not just text.

When leadership already runs a weekly forum and needs a planner to annotate agendas and message drift without building a full grid. Advisory seats are monthly or quarterly; they do not include calendar ownership unless added as a retainer crossing.

Send one planning artefact — last quarter grid, message doc, or launch sequence — and three sentences on your forum rhythm. We reply within two business days with suggested crossing and who from our studio would join. No questionnaire and no automated scheduling link.

Harbour is our static contact page; maps on other pages orient visitors to Tanjong Katong Road. Google may collect data when the embed loads; see Cookies for categories and toggles. Maps remain optional via the cookie panel.