Design it to be anonymous
Leave out the name and email questions entirely. Questionful does not require respondents to sign in, so an anonymous form is genuinely anonymous.
An employee feedback form gives people a structured, low-stakes way to say something they would not raise in a meeting. Anonymity is usually what makes it work, and the design has to earn that: no name field, no email capture, and nothing in the questions that identifies a team of three.
Not a stock template. Build it in a few minutes from a blank form, or describe it and let AI draft the questions on a paid plan.
What you do with it matters more than the form. A pulse survey that produces no visible change trains people to stop answering it, and the second round is always worse than the first.
A starting point, not a rulebook: every question below is a real Questionful question type, and all of them are editable once the form is in your account.
| Question | Question type |
|---|---|
| How are you feeling about work this month? | Linear scale |
| Rate each of these Workload, clarity, support, tooling | Rating grid |
| Which area would you most like to talk about? The branching question | Dropdown |
| What is working well? | Paragraph |
| What is getting in your way? | Paragraph |
| Do you have what you need to do your job? | Multiple choice |
| How should we split effort across these next quarter? | Budget allocator |
| Would you like someone to follow up with you? Routes to an optional contact section | Multiple choice |
Leave out the name and email questions entirely. Questionful does not require respondents to sign in, so an anonymous form is genuinely anonymous.
A final "would you like a follow-up?" choice question can route to a section that asks for contact details, so people who want a conversation can have one without everyone being identified.
Fix the scale and the grid, and let the open questions change. Duplicate the form each cycle rather than editing a live one.
Use the public response summary or export the aggregate to show what people said and what is changing because of it. That is what keeps round two honest.
They are if you do not ask for identifying information. Respondents never sign in, so with no name or email question there is nothing linking a response to a person.
Yes, end with a choice question that routes people who opt in to a section asking for their name or email. Everyone else finishes without giving one.
Yes. The opt-in public response summary aggregates closed-set questions; open text is never published, so nobody is quoted by accident.
Yes. The usual pattern is a short form sent after the last day, with branching on the reason for leaving so each path asks a different follow-up.
Scales, grids and summaries, questions built to aggregate.
Feature19 types, including specialist ones most builders skip.
FeatureRoute each answer choice to its own section, so people only see what applies.
TemplateCSAT and NPS with the follow-up question matched to the score.
TemplateDates, type of leave, cover arrangements, and a record of the approval.
TemplateStructured intake for internal or client work, routed by request type.
TemplateMeasure how people feel about the work, the manager and the load, anonymously.
Use caseTurn recurring internal requests (time off, IT tickets, purchase approvals) into structured forms with a real audit trail.
Use caseReplace the CV inbox with a structured application form: same questions for everyone, CV attached, and every submission comparable.
Unlimited forms and 100 responses a month, free. Paid plans from €19.
No credit card required.
Choose which cookies you allow. Strictly necessary cookies are always on because the site cannot function without them.
Required for core features such as security, load balancing and remembering this cookie choice. These set no tracking cookies.
Google Analytics, used to understand traffic and improve the site. Loaded only if you allow it.