How a programme runs

Wecountbackwardsfromthedate.

A runway with seven checkpoints, three gates that cannot be skipped, and a communication rhythm you can plan your own week around.

The runway

Sevencheckpoints,eachwithsomethingsigned

10 WKS OUTObjective brief

One sentence on what the programme must change, plus the internal approvers who have to agree it. Nothing else starts before this line exists.

8 WKS OUTSigned brief

Audience, agenda skeleton, faculty shortlist, compliance route and budget band — in one document, signed by both sides.

6 WKS OUTFaculty roster

Invitations out, contracts moving, honoraria and transfer-of-value records opened at the moment of agreement.

3 WKS OUTReview log

Decks, pre-reads and moderator guides in your reviewers' hands with enough runway for two honest revision rounds.

1 WK OUTRun-of-show

Minute-level schedule, AV plan, contingencies and a named contact per room. Changes after this point are logged, not absorbed.

EVENT DAYLive capture

We run the room. Your team attends its own programme instead of managing it.

5 DAYS AFTERInsight report

Meeting report, attendance and spend reconciliation, and the compliance file closed while memories are still accurate.

Gates

No date without a brief

Venues and faculty are not approached until the objective and budget band are agreed in writing.

No content without a reviewer

Every draft leaves with a named reviewer and a return date attached, so nothing waits in an inbox.

No spend without a line

If a cost is not on the approved budget grid, it is escalated the same day rather than reconciled later.

Cadence

Most delivery anxiety is an information problem, not a capability one. This is the rhythm that removes it.

Working to a date that is already fixed? Tell us the date and we'll tell you honestly whether the runway still works.