Writing a press release after an event: how to gather facts from the recording
Choose a newsworthy result, verify facts and figures, find a useful quote and distinguish plans from what actually happened.
Holding the event isn’t always the main news
An event can feature many participants and dozens of talks. A press release needs an outcome that matters to readers: material presented, a decision made, a project demonstrated or a next stage announced. Listing the guests rarely explains why the event mattered.
Decide what you’re writing: a report after the event rather than an announcement beforehand. Check the date, venue, organiser and the outcome itself. If attendance figures are preliminary, say so or wait for confirmation before giving a definitive count.
Build the release around verified news
Find a concrete outcome
Use the recording and post-event material to determine what happened. Distinguish a proposal from a decision to act on it. Choose the main fact and explain why it matters to readers without adding unsupported superlatives.
Verify the basic details
Check the name, date, venue, participant roles and figures against available primary materials. For an online event, distinguish registrations, connections and unique participants. These counts may differ and aren’t interchangeable.
Choose a quote that adds information
Look for a remark that explains a decision, a reason or a next step. Check the words and speaker against the recording. Don’t invent an emotional quote for an organiser. If you need new wording, obtain it separately through the established process.
Give the release a short structure
Open with the news, then add details, significance, a quote and necessary background. End with a way to ask follow-up questions if that’s part of the release. Check that future actions are described as plans and that readers can understand the text without the programme.
Outcome of a team meeting in a training example
This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.
Today we presented a draft of our shared handbook. Participants can send comments over the next month. After that, we’ll prepare the final version.
The news in this example is that the draft was presented and feedback is opening. The final handbook hasn’t been released; that’s the next planned stage.
Put the confirmed outcome in the first paragraph and describe how to give feedback separately. Verify the project name, dates and way to submit comments before a real publication.
| Information | Status | Accurate wording |
|---|---|---|
| A draft was shown | Completed fact | A draft was presented |
| Feedback will be collected | Announced step | Feedback collection is planned |
| The final version will be released | Future outcome | Don’t say it’s already finished |
Template for an event release
Fill in the fields with confirmed facts. Leave a missing figure out instead of adding a rough estimate to fill space.
Headline with the main outcome: What happened / where / when: Organiser and participants: Why the result matters to readers: Confirmed details and figures: Useful quote / speaker / timestamp: What is complete: What is planned: Brief background: Contact for follow-up questions: Sources used for verification:
Check the release before distributing it
- The main news is stated as a specific fact.
- Each number has a clear unit and source.
- The quote is attributed to the right person.
- Future plans aren’t reported as completed work.
A closer look
Do I need to mention every speaker?
Only if that matters to the news or the assignment requires it. You can keep the full programme separate so the release stays focused.
What if the final figures aren’t available yet?
Say they’re preliminary and explain what they’re based on, or leave them out until confirmed. Don’t use registration totals as attendance figures.