Write a conference report from the sessions you actually attended
Write a conference report that distinguishes attended sessions, checked programme information and proposed follow-up work.
About 6 min read · Allow extra time for the practical checks
Choose a useful thread from the academic sessions you attended and explain what those contributions brought to it. A conference report should help someone who was absent understand the event’s intellectual work. Copying the programme in chronological order gives that reader a timetable, while broad claims about the whole conference may exceed what you observed.
Check the intended destination first. A public report, a departmental account and a required participation form can ask for different things. Follow the actual brief and distinguish your own attendance from information checked in the programme or supplied by the organisers.
Select a thread for the intended reader
The Royal Musical Association’s conference-report guidance, checked on 3 November 2026, presents the report as a record and an overview for people who could not attend. It recommends selecting contributions, connecting themes and giving academic activity the main emphasis. Its audience, lengths and contributor-format requirements concern its own website; they are not requirements for every conference report.
Ask what your reader needs to understand about the sessions you can discuss. You may organise the report around a recurring question, a disagreement or different approaches to a shared problem. Explain that connection rather than assuming that a common subject makes the papers interchangeable.
Identify the event accurately using the final programme or other confirmed organiser information. Keep that event identity separate from the scope of your account. If you attended one day of a longer conference, make that boundary clear. A title in the programme establishes that a session was scheduled; it does not establish what happened in the room.
Work through an original fictional attendance record
The conference, sessions and documents below are invented teaching material. They describe no real event, speaker, research finding or attendee.
Imagine a fictional conference on describing local collections. The writer attended a session demonstrating how a teaching catalogue marks uncertain dates, followed by a discussion of how explanatory notes communicate uncertainty. A parallel session on catalogue search was listed in the programme, but the writer did not attend it. Their notes record a proposal to compare two note formats; no comparison has yet been carried out.
| Material available in the exercise | Defensible use in the report |
|---|---|
| Final programme | Verify the event identity and identify scheduled sessions |
| Notes from the date-marking demonstration | Describe the approach demonstrated, without claiming it improves users’ understanding |
| Notes from the explanatory-note discussion | Explain the question raised about communicating uncertainty |
| Parallel search-session title only | Do not describe its discussion as something the writer observed |
| Proposed comparison of two note formats | Present it as a possible follow-up, not a completed result |
An overreaching account says:
The conference proved that clearer catalogue notes improve search success, and participants agreed on the best format.
Neither outcome appears in the fictional record. A narrower passage could read:
In the two sessions I attended, a recurring question was how catalogue descriptions make uncertainty visible. A date-marking demonstration showed one way to represent uncertain dates, while the later discussion considered what accompanying notes need to explain. These contributions suggested a question for my own work: how might readers interpret two alternative note formats? A comparison remains to be planned; the sessions did not establish which format works better.
This passage connects contributions without turning a demonstration into an effectiveness study or a discussion into consensus. It also makes the writer’s own proposed inquiry distinguishable from the content of the event.
Repair attribution when attendance notes are incomplete
Check speakers’ names, affiliations and presentation titles against reliable event material, then follow the destination’s style. A programme identifies scheduled contributors. It cannot establish which person made an unrecorded comment during a discussion.
Consider a second version of the fictional exercise. The writer’s notebook contains the fragment “compare two note formats?” but no speaker’s name or clear indication of whether this was an audience comment or the writer’s own idea. The earlier date-marking demonstration and explanatory-note discussion are still established by the exercise. Only the origin of the comparison proposal is uncertain.
Three possible sentences handle that uncertainty differently:
| Proposed wording | What goes wrong or remains defensible |
|---|---|
| Participants agreed to compare two note formats | Turns an unattributed fragment into collective agreement and an agreed action |
| The discussion speaker proposed a comparison | Assigns the idea to a contributor whom the notes do not identify |
| I would like to explore a comparison of two note formats | States a present idea for the writer’s own work, without claiming who originated it at the event |
The third sentence is appropriate only if it truthfully describes the writer’s current intention. It does not recover the fragment’s missing attribution. Do not use first-person wording to claim ownership of someone else’s identifiable idea; if that relationship matters, check it through an appropriate source before making the claim.
A report paragraph for this variant could read:
The date-marking demonstration and explanatory-note discussion both raised questions about how catalogue descriptions present uncertainty. My notes do not establish who suggested comparing two note formats, so I cannot attribute that proposal to a particular contributor or describe it as an agreed action. For my own work, I would like to explore whether such a comparison would be useful. That remains an idea to develop, rather than an outcome delivered by the conference.
This version gives the absent reader the supported connection and the status of the possible follow-up. It does not fill the missing attribution with an invented speaker or consensus. In a shorter public report, the notebook uncertainty may be unnecessary detail: retain the supported account and omit the disputed origin claim altogether.
Where a particular argument is important, verify its attribution using the relevant recording, supplied paper or an appropriate clarification. Keep that basis clear rather than pretending the check was a firsthand observation. Do not reconstruct an exact quotation from memory. When discussing a limitation or disagreement, explain the idea and the basis of the assessment; a dismissive description of a person does not do that work.
Distinguish a useful next step from a completed outcome
Anna University’s conference-after-participation form, also checked on 3 November 2026, separates attended sessions from a way-forward section about applying insights and follow-up actions. Use that distinction while following your own brief. Its other requested information is specific to that form, not a universal public-report template.
State whether a next step is an idea, a proposal, an agreed arrangement or work already completed. An interesting conversation does not by itself establish a collaboration. A possible future publication should not become an announced publication without confirmation.
Before submitting, compare the finished report with your attendance record and checked event information. The seminar-announcement guide concerns what an organiser plans before an event; this report concerns what you can substantiate afterwards. Use the recommendation guide when you need to explain why a proposed next action follows from the account. The reader should be able to separate the event, the sessions you observed and the work you may do next.
