Format and programme worksheet

For product launches, conferences and awards. Adapt the relevant sections; these are not timing or capacity prescriptions.

Event: [name] | Programme owner: [name] | Version: [version] | Client approver: [name]

Common agenda test

Session or momentPurposeAudience actionContent ownerFormatDependenciesOutput recipient
[session][why][listen/discuss/try/decide][name][format][needs][name]

For every addition: what moves, what is removed, and who approves that trade-off? [answer]

Product launch message and demonstration

Primary announcement: [approved wording or owner]

Asset / momentProduct or message approvalGuest question answeredDemonstration readiness ownerTruthful alternativeRelease status
[reveal/demo/media brief][name/version][question][name][approved alternative][status]

• [ ] Launch objective distinguished from activation/participation objective.

• [ ] Reveal continues into an explanation and next step.

• [ ] Media access, message and release timing approved.

• [ ] Product claims remain with authorised client owner.

• [ ] Alternative demonstration is accurately described.

Conference sessions and speakers

SessionSpeaker/moderatorBrief sentContent approvedChecked versionArrival/holding ownerOutput/follow-up
[session][name][date][status][version][name][action]

Breakouts: [allocation method / approved rooms / hosts / close signal / output recipient]

Panel questions: [collection owner / moderator / selection explanation / unanswered route]

Awards cycle and register

CategoryApproved result sourcePresenterCitation/name approvalTrophy ID and checkRecipient readinessCue version
[category][restricted source][name][version][ID/status][owner/status][version]

Representative cycle rehearsal: [introduction → recipient movement → handover → photograph if planned → exit]

Observed constraints: [notes]. Agreed programme revision: [decision/approver]. Do not convert an observation into a universal award timing promise.

Final programme gate

• [ ] Purpose and sequence approved.

• [ ] Content and technical readiness recorded separately.

• [ ] Releasing and receiving owners named for transitions.

• [ ] Exceptions have an approved alternative or decision checkpoint.

• [ ] Host and operating teams receive the same released sequence.

ThreeSixZero · Event planning worksheet. Adapt to your agreed scope and responsibilities.