What to say when asking for event feedback

Most event organisers do not have a survey problem. They have an ask problem.

They show a QR code, say "please fill this in if you have time," and then wonder why hardly anyone responds.

A lot of event survey and post-event survey advice tells you to keep the survey short, ask better questions, and send it quickly. That advice is not wrong. It is just incomplete. The moment that usually decides whether people respond is much simpler: what you actually say when you ask.

At Yush, we have seen the same pattern again and again in live pilots and account work. Passive QR on its own can underperform badly. A clear prompt with a visible response moment performs much better. In stronger setups, actively prompted feedback has landed in the 40–80% range. Passive QR can drop below 5%.

You don't have a QR problem. You have an ask problem.

A weak ask usually sounds like this: "Please fill in our survey if you have time."

That line underperforms for four reasons:

• It sounds optional in the wrong way.
• It gives no time estimate.
• It gives no real reason.
• It says nothing about what happens with the result.

Busy attendees are not going to stop for a vague admin task. They are much more likely to respond when they understand four things straight away.

The four things people need to hear before they respond

1. What this is

Do not make people decode the task.

Weak: "We'd love your feedback."

Better:

• "We've got one quick event feedback question."
• "We're collecting a few reactions before everyone heads off."
• "We're doing a quick check on what landed today."

2. Why it matters

Weak: "Your feedback is important to us."

Better:

• "This helps us improve the next event."
• "This helps us understand what actually landed."
• "This helps us report back properly to sponsors and partners."

3. How quick it is

If attendees do not know whether this is one tap or ten questions, many will postpone it and never do it.

• "It takes 10 seconds."
• "It's one quick question."
• "It takes about 10–30 seconds."
• "Two taps and you're done."

4. What happens next

People respond more when the outcome is visible.

• "We'll use this to shape the next event."
• "We'll use it to improve the format."
• "You can also see the live reactions after you respond."

Scripts by event format

On-stage or MC ask

This is the strongest setup for quick live feedback because attention is already shared.

Short version: "Before you head off, we've got one quick question about today. It takes about 10 seconds and helps us improve the next one. Please scan the QR now and share your reaction."

Stronger version: "We're collecting a quick reaction before everyone leaves. It's one short question, about 10–30 seconds. This helps us understand what landed and what to improve for next time, so please get your phones out now and scan the QR on screen."

Speaker closing-slide ask

Slide headline: One quick question before you go

Slide subhead: Takes 10–30 seconds. Helps us improve future sessions.

Speaker line: "If you've got 10 seconds before the next break, scan the QR and tell us what landed for you today."

Roaming, community, or festival ask

Staff or volunteer version: "Hey, we're collecting quick reactions from today. It's literally one question and takes about 10 seconds. Would you mind scanning this and telling us what stood out to you?"

Bad asks vs better asks

Common mistakes that kill response

• Leading with the QR code
• Hiding the time cost
• Asking too late
• Sounding too formal
• Asking for too much
• Never saying what the feedback influences

Final takeaway

If you want help writing an ask that sounds natural, not corporate, Yush can generate event feedback scripts for different formats and goals.