A first-delivery brief for an event programme and later materials

A brief should explain what can usefully be delivered now and what still requires a decision. It should not hide unfinished publication work inside a broad request for an event page.

Use the fictional E-19 example below to prepare your own brief. It concerns the public programme for an organisational workshop, not registration software or the organisation of the event itself.

Starting material

The organiser has approved the event title, date, practical information and session programme. Three speakers have supplied slides. Two decks are cleared for later publication; the third includes a photograph whose publication permission has not been resolved.

The reader's immediate task is to find the programme and understand the practical arrangements. Access to all speaker slides is a separate later task. The page should not delay the approved programme or imply that every deck will be available.

The brief identifies who approved each item and where the supporting record is kept. The website developer does not resolve the photograph's rights by removing its credit or assuming that receiving the file permits publication.

Selected first delivery

The first delivery is one event page with the approved programme, the organiser's contact route and a clear description of the event's public purpose. The page includes the sentence: “Materials approved for public release will be added here after the event.” It does not promise every presentation or give an unapproved release date.

The scope includes an editing route for adding a cleared resource later, with its title, speaker, language and file destination. It excludes a participant account system, automated registration and a new slide-hosting service. Those functions are not needed to complete the selected reading task.

Acceptance questions

A reviewer starts at the event URL and checks the title, date and session sequence against the approved programme. They can find the practical information and the responsible organiser without being sent to an unrelated general contact.

The page has no active link to Speaker C's file and no text claiming that all slides are available. The ordinary editor can prepare a later resource entry using a harmless sample, then leave it unpublished until its release condition is met. The test does not require uploading the uncleared photograph to a public preview.

The approved programme remains readable if no slides are added. That is important: the first delivery must be useful on its own, not merely a shell waiting for every later dependency.

Remaining ownership and follow-up

The organiser assigns the Speaker C permission question to the person responsible for the event materials. A deadline for reviewing that question is recorded internally. If permission remains unresolved, the file stays outside the public collection; a different approved resource can be considered separately.

After the event, the editor checks the actual release decisions for Speakers A and B before publishing their files. Any changed practical information or event status remains the organiser's responsibility to approve.

Adapt the brief

Replace the fictional materials with your own approved programme, attachments and unresolved questions. Keep the first reader task narrow, identify what evidence supports each item and state a concrete result for material that is not ready.

The event-publishing service covers the technical page and editorial route. The edition map helps when the programme and later materials also have different language scopes. Send your outline when the useful first delivery is clear enough to discuss.