Prepare a Community Event Speaker Brief
How to prepare a speaker brief for a community event: agree the contribution, timing, arrival, equipment, introduction and material-sharing terms, then issue one reviewed, dated version.
Contents
A speaker brief is a single dated document that you and the speaker have both reviewed. It records who the audience is, what the speaker has agreed to contribute, how the time slot is divided, where and when to arrive, what equipment is confirmed, how they will be introduced, and what may happen to their materials or recordings afterward. The brief's job is to turn verbal agreements into confirmed arrangements, so that the speaker, host and technical helpers all work from the same plan. It works the same way for a guest talk at a community gathering, a short address before a tournament awards session or a briefing for volunteers.
What to include in the brief
- Audience: who will be in the room and what they already know about the topic
- Contribution: what the speaker has agreed to cover, and any boundaries on scope or subject
- Format: talk, demonstration, panel segment, workshop or similar
- Host or facilitator: the name and contact of the person running the session
- Arrival: which entrance to use, what time to arrive and who will receive the speaker
- Equipment check: what is confirmed, who will run it and when the speaker can test it
- Introduction: the agreed wording and who will deliver it
- Speaking period: the length of the speaker's own contribution
- Questions: the time allocated and who manages them
- Finish: how the session closes and who closes it
- Materials: the format required and the deadline for sending slides, handouts or files
- Sharing permissions: whether materials or recordings may be shared or reused later, and how
- Change contact: one person to contact if anything changes before the event
Agree the contribution before the logistics
Start with the substance. Describe the audience and their starting knowledge, then write down what the speaker will contribute and what falls outside the brief. This prevents a mismatch, such as a beginner-level crowd receiving an advanced talk, and it gives the speaker a clear boundary to prepare against. Any public description of the speaker or their session should be approved by the speaker before it goes out. That includes program listings, social posts and the introduction the host will read aloud.
Divide the time slot into separate parts
A common scheduling mistake is to treat the whole slot as speaking time. Split it into the introduction, the speaker's contribution, questions and the close, so that everyone knows how long the speaker actually has. The breakdown below is a hypothetical 40-minute slot, shown for illustration only.
| Segment | Minutes | Who leads |
| Introduction | 3 | Host |
| Speaker's contribution | 25 | Speaker |
| Audience questions | 8 | Named question owner |
| Close | 4 | Host |
| Total | 40 | — |
Ask both the speaker and the host to approve these allocations, and agree on a time signal, such as a card or hand cue, that tells the speaker when to wrap up. Name the person responsible for handling audience questions. An eight-minute question allowance is not the same as a complete Q&A plan. If you have a separate process for collecting, screening or relaying questions, reference it in the brief instead of assuming the time allocation covers it.
Give every practical arrangement an owner and a status
For each arrangement, record who is confirming it and where it stands. Keep two distinctions clear. Equipment the speaker has requested is not the same as equipment that has been confirmed. An arrangement you have pencilled in is not the same as one the speaker has agreed to. The person who will actually operate the room's equipment should review the speaker's real presentation requirements rather than a summary of them. Send accessibility arrangements, technical requirements, formal agreements and content permissions to the people responsible for each, and don't settle them informally between the host and the speaker.
| Arrangement | Confirmer | Status |
| Arrival entrance and receiving person | Volunteer lead | Confirmed |
| Projector and laptop connection | Venue technical contact | Requested, not yet confirmed |
| Microphone type | Venue technical contact | Confirmed |
| Accessibility needs | Accessibility contact | Provisional, awaiting speaker reply |
| Introduction wording | Speaker | Approved |
| Recording permission | Program owner | Under discussion |
The table above is an illustrative example of a tracking layout, not a fixed list of roles. Swap in the people who actually hold each responsibility at your event.
Make material sharing and recording terms explicit
State the format you need for slides or handouts and the date you need them by. Then agree in writing whether the materials may be shared with attendees, posted afterward or reused, and whether the session will be recorded and how any recording may be used. Don't assume that agreeing to speak means agreeing to be recorded or to have slides redistributed. Settling this ahead of time avoids awkward requests after the event.
Finalize and issue the brief
- Draft the brief using the checklist above, with a confirmer and status for each practical item.
- Have the speaker review the contribution, public description, introduction and time allocations.
- Have the equipment operator review the actual presentation requirements.
- Resolve or clearly mark anything still provisional or only requested.
- Issue one dated version that both the speaker and the program owner have reviewed.
- Name a single change contact, and reissue a new dated version if anything material changes.
Related articles
Plan a Community Event Information Desk Enquiry Workflow
Build an information desk enquiry workflow for a community event or tournament: desk reference sheet, enquiry log template, referral steps and a printable desk copy.
Plan and Maintain a Community Event Attendee FAQ
Build an attendee FAQ from approved event information, with a named owner for each answer, publication approval and clear triggers for rechecking.
Prepare a Community Event Committee Handover
A practical handover template for community event and tournament committees: what to record, how to transfer each work area, and how successors confirm ownership.
Define Roles and Responsibilities for a Community Event Committee
A practical way to assign committee roles for a community event or amateur tournament: name an owner for every deliverable, set approval authority, map dependencies and agree when changes get reviewed.
Specify the Information and Presentation for an Event Ticket
Build a ticket design brief for your tournament or community event: confirm the required details, set a clear visual hierarchy and lock down print or digital output needs before design starts.
Compare Volunteer Management Software Against Event Requirements
Compare volunteer management software against your event's real needs with a requirements worksheet, scripted demo tests, like-for-like pricing and fair scoring.
Plan a Community Cleanup Event
A practical guide to planning a community cleanup: define the purpose and area, assign named owners, confirm collection arrangements and send participants a clear, final plan.
Plan Waste Collection and Cleanup for a Community Event
A step-by-step plan for community events and amateur tournaments: reduce materials, map collection points, assign volunteers and close out cleanup with confirmed collection.
Coordinate Community Event Accessibility Requests
A practical template for collecting, answering and confirming accessibility requests at community events and amateur tournaments, with restricted tracking and clear delivery owners.
Plan Accessibility Across a Community Event
An event accessibility checklist for community events and amateur tournaments: build an accessibility plan from publicity to arrival, venue, activities, vendors and emergencies.