Turning a conference into a report people will use

A conference report should help people act on what was discussed. That means organising it around ideas and recommendations, not around the programme.

Conferences generate a great deal of discussion in a short time. Without a good report, most of it is lost within weeks. With one, the event becomes a reference point that informs decisions, funding and the next event.

Agree the purpose before the event

A report for funders reads differently from a report for delegates or for a policy audience. Before the conference, agree who the report is for, how long it should be and what it must cover. This shapes what the documentation team listens for on the day.

Organise by theme, not by timetable

Session-by-session summaries are easy to write but hard to use. Readers want to know what the conference concluded about each issue. Grouping insights by theme, while noting which sessions they came from, makes the report far more useful.

Separate what was said from what was agreed

Clearly distinguish between points raised by individual speakers, views shared by many participants, and formal recommendations or resolutions. This protects speakers and gives readers an honest picture of where consensus lies.

A structure that works for most conferences

• An executive summary that a busy reader can take in on one page.
• Background: the purpose of the conference, who attended and the format.
• Key themes, each with the main points, debates and examples raised.
• Recommendations and agreed actions, with responsibility where it was assigned.
• Appendices for the programme, speaker list and any presentations.

Deliver while it still matters

A report that arrives months after the event has lost most of its value. Agree a delivery date upfront, and plan the documentation so that drafting starts while sessions are still running.