Event briefing: a template and how to update it with AI
A briefing template covering objectives, scope and outstanding items, with EVA Brain using project agreements to update it.
An event briefing should explain what you need to achieve, for whom, what the work includes and what remains outstanding. This template brings those points together so you can use it with your team and ask EVA Brain for a version based on project agreements.
The document needs to help with production. If a sentence such as “we want a memorable experience” does not change a content, format or build decision, it needs to be more specific.
An event briefing template to copy and adapt
Use these sections as a model. Complete what you know and retain anything not yet agreed as outstanding. Do not fill a gap with an assumption to make the document look finished.
1. Objective and expected outcome
What the event should achieve: explain its purpose and how you would recognise a useful result.
For example, introduce a product to the sales team and give them arguments to use with clients. That intention guides demonstrations and questions; a brand presentation would have different needs.
2. Audience and participation arrangements
Who takes part and what they need: profiles, groups with different experiences and conditions affecting their participation.
Where relevant, include tickets, languages and accessibility needs. Distinguish confirmed information from an estimate that might still change.
3. Scope and deliverables
What the project includes: activities, services and material to prepare. Add exclusions where confusion is possible.
Presentation design and stage production are different jobs, for example. Specify which is included and who is responsible for each part.
4. Brand and content criteria
How the event should communicate: the brand to use, approved material, tone and messages confirmed by the client.
Include available references. “Use our brand” needs to connect to the right identity and material so the team can apply it.
5. Programme and operational arrangements
What happens and in which order: key moments, access, build, rehearsals and breakdown.
If the running order lives in another document, identify its current version and owner. Avoid copying a time that might later change without the briefing reflecting it.
6. Constraints and dependencies
What limits decisions: approved budget, venue conditions, loading times, technical requirements or external approvals.
A constraint should retain its source. If the venue only allows loading during a particular window, link or identify the confirmation so production can check it.
7. Responsibilities and coordination
Who decides and who does the work: project lead, client approval and the people coordinating each task.
For relevant items, add the next step and who needs to take it. Being copied into an email does not confirm that someone has accepted a task.
8. Agreements, approvals and outstanding items
What is confirmed and what remains: briefing review date, approved decisions and open questions with their owners.
You can divide this section into “confirmed”, “proposed” and “awaiting a reply”. These statuses help prevent a client’s idea becoming a production instruction.
How to ask EVA Brain for a briefing with this structure
Brain uses knowledge received about the project: meetings the assistant has been invited to, documents provided and emails arriving through configured routes. From that shared memory, you can request a document adapted to your brand.
A useful instruction would be:
Prepare the event briefing using these eight sections. Use the project’s available agreements and sources. Separate confirmed decisions from proposals and outstanding items. Identify missing information, retain references for constraints and adapt the document to our brand.
The template organises the request. Agreements provide its content. If Brain has not received the approved budget, it should not infer one; you need to provide the figure or leave it outstanding.
A client change and its effect on the briefing
Suppose the client proposes extending the Q&A session. Production has a confirmed deadline for leaving the venue. The proposal may affect the programme and rehearsals, but it is not yet an approved time.
Once the meeting is incorporated, you can ask Brain to identify affected sections and prepare a revision. The programme records the proposal as pending; the constraints section retains the departure deadline; coordination identifies who must confirm whether the change fits.
When approval arrives, incorporate that confirmation and request the updated version. Before sending it, check that the document distinguishes the new decision from the original proposal.
Updated memory does not itself replace every external file or the copies suppliers already have. The team must share the new version and withdraw or identify earlier ones within its process. Read more about keeping the team informed when a client changes the event.
Frequently asked questions
Is this template for a client or production briefing?
You can adapt it to both. For the client, specify objectives, scope and approvals. For production, develop programme details, constraints and responsibilities sufficiently to carry out the work.
Do I have to document every meeting again to update it?
EVA Brain incorporates what it receives from sources prepared for the project. You need to give it access to that information and add anything outside those sources, but not rewrite every conversation manually. Always review agreements affecting delivery.
Can it be generated using my agency’s brand?
Yes, you can request documentation adapted to your brand using project context. With EVA Brain, we start from the team’s sources to prepare that work and its revisions.
