# Conference Session Evaluation: Questions & a Comparison Template

Build a conference session evaluation with useful questions, clear response bases and a worked comparison to decide what to repeat or revise.

- Canonical URL: https://www.harmate.com/en/blog/conference-session-evaluation
- Author: Harmate Team
- Published: 2026-10-25
- Updated: 2026-10-25T22:44:24.522534+00:00
- Language: en

## Content

# Conference Session Evaluation: Questions & a Comparison Template

To decide which conference sessions to repeat, collect feedback tied to each session people actually attended. Preserve the portion they saw, the need that brought them there and the examples behind their assessment. Then compare explicit situations, with a response base for each question, rather than ranking average ratings from sessions serving different audiences.

This form supports program decisions: retain a worked case, clarify the advertised level, revise an explanation or change a format. A general [post-event survey](/en/blog/post-event-survey-questions-a-practical-guide-for-attendee-feedback) remains useful for the whole-day experience. Here, the unit being examined is one identifiable session.

## Make every answer traceable to the right session

Put the title, date and, where needed, time or room on the form. If respondents select the session themselves, use actual program titles. “Morning workshop” is ambiguous when several workshops run at the same time.

Next, ask what they followed: the whole session, part of it or none. Allow people with partial attendance to name the section. Do not require an exact percentage if they cannot reasonably estimate one. Someone who left before the worked case should not be asked to evaluate it.

If one form covers several sessions, repeat a clearly identified block for each. Avoid an option for “multiple sessions” followed by a single rating whose subject is unclear. Someone may contribute to several session evaluations while remaining one person in the conference participation count.

Explain how responses will be used and who will read them. In a small session, an account may identify its author. Do not promise anonymity merely because the form does not request a name.

## An adaptable session evaluation form

Let participants describe their expectations and experience first. Open questions can reveal matters that the organizer’s categories would have missed. A few closed questions then help locate those accounts; they do not replace the explanations.

| Field | Suggested wording | Intended use |
|---|---|---|
| Session | Which session does this response concern? | Connect the remaining answers to the correct content |
| Exposure | Which parts did you have a chance to follow? | Avoid evaluating material the person did not see |
| Expectation | What were you hoping to understand or do by choosing this session? | Distinguish different needs behind similar ratings |
| Useful point | Which part gave you something useful? Describe what it helped you understand. | Identify content worth retaining, with context |
| Difficulty | Which part, if any, left you with a question or was difficult to follow? | Locate an explanation need without assuming its cause |
| Level | For your needs, was the level too introductory, appropriate, too advanced or difficult to assess? | Describe perceived fit, rather than measure competence |
| Next step | What specific change would make this session more useful to someone in your situation? | Prepare a change to examine |

If you need a rating, define exactly what it concerns and use consistent response labels for the comparisons you intend. Separate explanation clarity, practical conditions and interest in the topic. A combined rating will not tell you which element to change.

[AAPOR’s best-practice guidance](https://aapor.org/standards-and-ethics/best-practices/) recommends simple questions focused on one concept and pretesting with people similar to the respondents. Check the form against two different sessions: can people identify the passage they are evaluating and indicate material they did not see?

## Define the response bases before comparing answers

For each session, distinguish known attendees, people invited to respond, respondents and usable answers to each question. Those counts may differ. An unanswered question does not mean satisfaction or dissatisfaction.

For a worked case, the relevant base consists of respondents who report seeing it and answer the question about it. An overall session assessment may use a different scope, provided you explain it. Do not silently change the base between rows of a report.

Also preserve context that may change the meaning of an answer: advertised level, stated need, duration, format and any reported incident. You do not need a detailed personal profile. Collect only what helps you understand the session and avoid unnecessary or sensitive categories.

## Worked comparison: the highest-rated session is not necessarily the only one to repeat

This example is entirely fictional. A conference offers an introduction and an advanced workshop on the same subject. The team wants to choose the next edition’s content.

| Item | Introduction A | Advanced workshop B |
|---|---|---|
| Known attendance from the available record | 60 | 25 |
| Respondents | 24 | 12 |
| Answered about the worked case after seeing it | 18 | 8 |
| Need described in several comments | Learn the steps and terminology | Address an exception encountered at work |
| Fictional positive excerpt | “The sequence of steps helps me see where to start.” | “The exception matched the problem I had brought.” |
| Fictional critical excerpt | “I already use the method; I wanted to understand its limits.” | “I lost the thread when the prerequisites were assumed.” |

Even if A has a better overall rating, the table does not establish that its content fits everyone better. People selected their sessions, their needs differ and some attendees did not respond. B’s positive experience is worth preserving alongside the difficulty other participants reported.

A reasonable decision to examine would be to retain both tracks, clarify their prerequisites and test a recap before the advanced case. The eight answers about B’s case may inform that change; they do not evaluate the experience of everyone in B, much less the entire conference.

Ask session owners to check the passages described. A difficulty may concern the materials, the advertised level or a specific example. The questionnaire alone cannot identify the speaker as its cause.

## Turn the feedback into a program decision

Write a short decision record for each session: content to keep, reported problem, supporting excerpts, disagreement, proposed change and planned check. Do not force a positive or negative summary when the same sequence helped one group and confused another.

The [pre-event survey on program choices](/en/blog/pre-event-survey-choose-topics-for-your-event-programme) can complement this review. Feedback describes a past experience, while a new consultation explores needs that remain unmet. A request for a topic does not establish that people will attend a future session.

If comments across several sessions become difficult to review, [Harmate helps you examine open answers alongside their source excerpts](/en/product/open-questions) and select useful material for a decision file. Keep session identifiers and relevant contexts with the material. Assessing comparison bases and choosing the program remain human responsibilities.

Then share the follow-up with the relevant speakers and participants: what will stay, what will change and what still needs checking. The aim is a better-supported program decision, not a league table of people.