What is a post-event survey?

A post-event survey evaluates the event as a whole. It is a different instrument from session feedback, which evaluates one talk, and the two should be run differently.

In practice at an event

Send once, within twenty-four hours of the event closing. Response rates fall steeply after the first day and a reminder rarely recovers them.

Keep it to eight to twelve questions, and put the completion time in the first line and honour it. Every question beyond twelve trades completion rate for data, and the trade gets worse as you go.

The test for each question is whether it names a decision it will change. A question producing a number nobody acts on has a real cost, because it spends the attention you needed for the question that mattered.

The single most effective way to raise next year’s response rate is to publish what you changed because of this year’s answers, from the stage, at the opening.

What to look for

Never use a matrix grid; most responses arrive on a phone and grids are close to unusable there. Never make a question required except the first one, because a required question mid-form turns a partial response into no response at all.

Read every free-text answer yourself, all of them, once. The most useful sentence in a survey is almost always in a free-text box and almost never in the summary.

How event67 handles it

The console has a forms builder: build and publish an attendee form, and responses land in the console. It is a general form tool rather than a survey product, so it will not compute a score or draw you a chart. Forms collect responses and not money — there is no payment on a form. Session-level feedback is a separate, in-app instrument and is usually the more actionable one.