Free Dynamic QR Code for Event Feedback

Ask for feedback while the experience is fresh, with one code that can open a different survey for each session or day.

Dynamic: change where the code points after printing, and see how many people scan it.

Design

#000000
#ffffff
Dot style
Corner style
Frame with call to action
#000000

Say what people get: "SCAN FOR MENU" usually gets more scans than "SCAN ME".

Preview

Create the code to get your scannable dynamic QR.

Feedback collected by email days after an event tends to be thin, because people have moved on. The best responses come from asking in the moment: at the end of a session, on the way out, or while people are still at their tables. A QR code puts the survey in front of them at exactly that point, using the phone they already have in hand.

With a dynamic code, one set of printed table cards or exit signs can serve every survey you run. Point the code at the session one survey, then the session two survey, then the overall event survey at closing. If you rewrite the form halfway through, nothing printed needs to change. Live audience tools are covered further down for when you want reactions during a talk.

Why use a dynamic QR code for event feedback

Ask at the right moment

Switch the code to the survey for whichever session just ended. Attendees answer about what they just experienced instead of trying to remember a talk from hours earlier. One printed card covers them all.

Fix a broken survey fast

If a question is confusing or the form stops accepting responses, duplicate it, update the code's destination, and keep collecting answers without anyone noticing. Responses already collected stay in the original form, so nothing is lost.

See when people respond

The scans-per-day chart shows whether feedback came in at the event or trickled in later, helping you decide where and when to ask next time. Combine it with your form's response count to see how many scanners finished.

Close the loop afterward

Once the survey closes, redirect the code to a thank-you page with recordings or next year's dates, so lingering table cards still offer something worthwhile. The code keeps working for as long as cards are around.

How to set it up

  1. Write a short survey of three to five questions: one overall rating, one about the specific session, and one open question about what to improve. Test it on a phone.
  2. Paste the survey URL above and name the code clearly. Decide whether one code will rotate between surveys or each session gets its own.
  3. Download the code and add it to the last slide of every presentation, table cards, and exit signs, with a line telling people how long the survey takes.
  4. Save the manage link, schedule when to switch to each survey in your run sheet, and scan every printed placement before the event starts.

Where to place it

  • On the final slide of each session, shown while the speaker takes questions and wraps up, so people scan before leaving the room.
  • On table tent cards at meals and breakouts, where attendees sit for long enough to answer a few questions.
  • On exit signs and doors at the end of the venue, labeled "Two minutes? Tell us how it went."
  • On the back of the printed program, next to the closing session listing and the thank-you message.
  • On a large screen in the lobby during the closing reception, alongside sponsor slides.

Tips that improve scans

Size for the slide

A code on a projected slide needs to be large, at least a quarter of the slide's height, and shown long enough for people at the back to scan. Leave it up for a minute or more.

Promise a short survey

"Scan to rate this session - 3 questions" gets more responses than "Give feedback." Then keep the promise; long forms lose people halfway through. Three to five questions is plenty.

Ask before people leave

Build two minutes into the agenda for feedback at the end of key sessions. Responses drop sharply once people are walking to the next room.

Share what changed

Tell attendees, on the thank-you page or in the next event's invite, what you changed because of their feedback. It encourages them to answer next time.

A survey gets rewritten during the event

A product user group runs a one-day event with feedback table cards printed in advance. After the morning sessions, organizers notice that most people skip a long multiple-choice question and abandon the form. At lunch, they create a shorter version with three questions and redirect the code to it. The afternoon sessions use the same table cards and slide, and the closing session's code switches once more to an overall event survey.

Frequently asked questions

Does the code collect feedback itself?

No. It opens the survey you link to, such as an online form. Responses are stored by that form tool. The code makes it easy to reach and lets you change which survey it opens.

Can I use one code for every session?

Yes. Switch the destination to each session's survey as it ends. If sessions run at the same time in different rooms, create a separate code for each room. Label each room's code clearly.

Can I tell how many people scanned the feedback code?

Yes. You see total scans, a daily chart for 30 days, top countries, and device type. Compare scans with completed responses to see how many people dropped off. Repeat scans count too.

What about live reactions during a talk?

A survey link works for after-session feedback. For live polls, word clouds, or Q&A while someone is presenting, an interactive presentation tool is the better fit; see the suggestion on this page.

Related use cases