All guides

The workshop feedback form that people actually finish

Updated August 2026 · 6 min read

Most workshop feedback forms are too long and ask the wrong things. Here's a six-question form you can copy, why each question is there, and what to cut.

Why long forms fail

The people most likely to complete a fifteen-question form are the ones at the extremes — delighted or annoyed. Everyone in the middle, which is most of the room, walks out. You end up with a bimodal dataset and a comfortable average that tells you nothing.

A form that takes under 60 seconds on a phone, handed out while people are still in their seats, routinely triples response rate. Fewer questions, more answers, better data.

The six-question form

  1. How useful was this workshop to your work? (1–5) Usefulness, not enjoyment. This is the number you trend over time.
  2. How clearly was it delivered? (1–5) Separates the content from the facilitator, so a weak score tells you which one to fix.
  3. What is one thing you'll do differently this week? The single best predictor of whether learning transfers. Vague answers are a finding.
  4. What should we have spent more time on? Gives you your next agenda for free.
  5. How likely are you to recommend this to a colleague? (0–10) One comparable benchmark across every session you run.
  6. Anything else — good or bad? Optional, open, and where the genuinely useful criticism shows up.

What to cut

  • Venue, catering and logistics questions — send those to the organiser, not the room.
  • 'Was the facilitator knowledgeable?' Almost nobody says no; it costs you a question slot.
  • Demographic fields you will never segment by.
  • Anything requiring a person to remember what happened three hours ago in detail.

Timing and delivery

  • Ask in the room, in the last three minutes, before people pack up. Emailed forms lose most of the room.
  • Put the QR code on the final slide and leave it up.
  • Keep it anonymous unless you have a specific reason not to.
  • If you want to send slides or templates afterwards, ask for the email as a separate optional step — never as a condition of giving feedback.

Reading the results without fooling yourself

Averages hide the story. Read every open text answer, count how often a theme repeats, and weight the answers to question three most heavily — a room full of 5s that cannot name one behaviour change is a room that enjoyed itself and learned nothing.

In PulseCheck you can build exactly this form as custom session questions, collect it from a QR code in the room, and have the read-out cluster the free-text answers into themes for you.

Try it in your next session

PulseCheck collects live reactions and post-session feedback from a join code or QR — then writes the read-out for you.

Start free