Event feedback questionnaire builder
The event is over, a feedback form is due, and the team wants questions that produce evidence rather than compliments.
…
The short answer
The builder takes your event objectives, the evidence each would need and your draft questions, and gives you an editable questionnaire with a measure map from objective to question. It flags leading wording, questions that collect a personal detail, two questions in one, questions linked to no objective and objectives with no question.
It also counts response burden against the limit you set. It holds no responses and produces no results, scores or averages: it builds the instrument only.
What to enter
- The most questions a respondent should face. Leave it blank if you have not set one.
- Event objectives, one per row, with the evidence that would show each: for example, whether attendees found sessions relevant to their work.
- Draft questions, each with an answer type, the objective it serves (written as in the objectives list) and whether an answer is required.
The checks
- Leading wording: phrases that push the answer, such as "how excellent was" or "do you agree that". Rewrite them so a respondent can answer either way.
- Personal details: questions that ask for a name, contact detail, age, gender or similar. Keep one only if an objective cannot be met without it, and make it optional.
- Two questions in one: a rating, yes or no, or choice question joined by "and". Each answer should mean one thing.
- No linked objective: a question that serves nothing you listed. Link it or remove it.
The measure map
For each objective the map lists the questions that serve it. An objective with no question is marked, because the feedback cannot give you evidence on it.
Use it before sending: every objective should have a question, and every question should have an objective. See feedback objectives and survey question selection.
Response burden
The tool counts questions, required answers and open-text questions, and compares the number of questions with the limit you set. A required open-text question is flagged because it adds burden and may push people to leave. The tool does not know how long a question takes to answer.
Anonymity is a design decision of its own; see anonymous feedback boundaries.
Limits
The checks are simple word checks, so read every question yourself. A question that is not flagged is not therefore good, and a flagged one may be fine with a reason. Once responses arrive, use feedback action prioritisation to decide what to act on.
Worked example · Fictional example
A fictional conference
Fictional objectives and questions, to show the flags.
A fictional conference sets three objectives and a limit of eight questions, and drafts six. One asks "How excellent was the keynote?", one asks whether the venue was easy to find and whether registration was quick, one asks for age, and one required open-text question asks what to change.
The result flags one leading question, one double question, one personal-detail question that serves no objective, and one required open-text question. Every objective has at least one question and the six questions are within the limit.
| Question | Check |
|---|---|
| How excellent was the keynote? | Leading wording |
| Was the venue easy to find and was the registration quick? | May ask two things |
| What is your age? | Personal detail, no linked objective |
| What would you change about the day? | Required open text |
Use this yourself
Feedback questionnaire and measure map
List objectives first, then write questions that each serve one. Remove any question that has no objective.
| Objective | Evidence that would show it | Question | Answer type | Required (yes or no) |
|---|---|---|---|---|
| Check: does every objective have a question? | ||||
| Check: is any question leading, double or asking for a personal detail it does not need? |
Handle it in-house, or bring in help?
Your team can usually handle this when
- One event, a few clear objectives and a short form that one person can draft and review.
- You already know what decision the feedback will inform.
Outside planning help earns its fee when
- Several stakeholders each want their own questions and the form keeps growing.
- The questionnaire must work in more than one language or for both in-person and online attendees.
- Feedback needs to be tied to programme decisions, and someone must coordinate the review and the follow-up.
Need the feedback process coordinated?
An outsourced conference project lead can agree the objectives with your committee, consolidate the questions, keep the questionnaire short and make sure the findings reach the decisions they are meant to inform. Wording sign-off and what to do with the findings stay with you.
Questions organisers ask
Does the tool analyse survey results?
No. It builds the questionnaire and a measure map only. It holds no responses and produces no scores or averages.
How are leading questions found?
By simple word checks for phrases that push the answer. Read every question yourself, because the check cannot judge meaning.
Should I ask for age or gender?
Only if an objective cannot be met without it. The tool flags these questions so you decide, and an optional answer adds less burden.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.