Statutory consultation
Proposal summary as a section, agreement matrix on the specific changes, free text for objections, then a demographic block at the end.
Matrix · Long text · Address · Conditional logic
Build this survey →Templates
Thirty surveys,
sketched out.
Each entry below is a structure rather than a file: what to ask, in what order, and which of the 16 question types and which logic rules it needs. There is no in-app template library yet, so nothing here is applied with one click — you open the builder and put the structure together yourself.
That is deliberate on our side and, honestly, better on yours. Almost every real survey needs its own wording, its own branching and its own demographic block. A template you have to unpick is slower than a structure you follow.
Local government
Consultation and resident-facing surveys, where the awkward parts are usually the address question, the demographic block and proving afterwards that you asked fairly.
Resident satisfaction
Recommend score on the council overall, linear scales per service, and a ranked list of spending priorities.
Recommend score · Linear scale · Ranking
Build this survey →Travel and transport
Journey purpose branching into mode-specific questions, so a cyclist never sees the parking section.
Multiple choice · Conditional logic · Number
Build this survey →Report a problem
Location by address with a checked postcode, a photo upload as evidence, and a contact block that only appears if they want a reply.
Address · File upload · Conditional logic
Build this survey →Grant application
Long, staged and worth saving halfway through — a resume link matters more here than anywhere else.
Paged layout · Save & continue · File upload
Build this survey →Education
Module evaluation, student voice and parent surveys. High volume, short windows, and results that go straight into a committee paper.
Surveys for schools, trusts and universities
Module or course evaluation
One agreement matrix across teaching, assessment and materials, then two open questions: keep, and change.
Matrix · Long text · Embed mode
Build this survey →Student voice
Short, conversational, one question at a time so it works on a phone between lessons.
Conversational layout · Rating · Checkboxes
Build this survey →Parent survey
Year group first, then only the questions relevant to that year group. Add the school badge as a per-survey logo.
Dropdown · Conditional logic · Partner logo
Build this survey →Trip consent and information
Contact details, dietary and medical notes shown only when needed, and a document upload for anything signed on paper.
Short text · Conditional logic · File upload
Build this survey →Staff wellbeing
Anonymous by design: no name field, no hidden identifier, one matrix and one open box.
Matrix · Long text · Linear scale
Build this survey →HR and people teams
Engagement, onboarding and exit. The recurring problem is asking a sensitive question in a way people answer honestly, then reporting it without identifying anyone.
Employee engagement
Standard engagement matrix, a recommend score, and department taken from a hidden field so nobody has to pick it from a list.
Matrix · Recommend score · Hidden fields
Build this survey →Onboarding check-in
Same short survey at 30, 60 and 90 days, with the stage passed in through the link.
Hidden fields · Rating · Long text
Build this survey →Exit interview
Reason for leaving branches into a different follow-up set for each reason. Nobody answers all of it.
Multiple choice · Conditional logic · Long text
Build this survey →Manager self-assessment
Scored answers, weighted questions, and a band shown on the thank-you screen the moment they finish.
Scoring · Weights · Bands
Build this survey →Training needs analysis
Rank the skills gaps, rate current confidence, and let people add one they think you have missed.
Ranking · Linear scale · Other (please specify)
Build this survey →Research and insight
Where question order effects, panel identifiers and a clean export matter more than how the survey looks.
Concept test
Image per concept, rated on the same scale, with the concept order randomised on a seed so going back does not reshuffle.
Question images · Rating · Seeded randomisation
Build this survey →Brand tracker
Unprompted awareness first as free text, prompted awareness after, so the prompt cannot contaminate the earlier answer.
Long text · Checkboxes · Paged layout
Build this survey →Screener
Quotas by branching: disqualifying answers skip straight to a custom closed message rather than wasting anyone’s time.
Conditional logic · Number · Custom closed message
Build this survey →Panel study with IDs
Respondent ID and wave number arrive as hidden fields in the query string and are stored with the response.
Hidden fields · CSV export · Response cap
Build this survey →Pricing sensitivity
Four number questions in sequence, each with a validated range, and a matrix for feature trade-offs.
Number · Validation · Matrix
Build this survey →Events
Registration before, feedback after, and a hard stop when the room is full — enforced by the database rather than by hoping.
How response caps and close dates work
Event registration
Capped at the room size and closed automatically on the date, with your own wording on the closed screen.
Response cap · Close date · Custom closed message
Build this survey →Session selection
Bento option tiles with an image and a description line per session, so choosing feels like picking, not reading a list.
Option tiles · Option images · Checkboxes
Build this survey →Post-event feedback
A recommend score, one rating per session they said they attended, and one open question.
Recommend score · Conditional logic · Rating
Build this survey →Speaker or abstract submission
Biography, session outline and a slide deck or paper uploaded into a private bucket.
Long text · File upload · Email
Build this survey →Accessibility and dietary needs
Asked once, shown only to people who say they have a requirement, and phrased so it is not a checkbox of assumptions.
Conditional logic · Checkboxes · Other (please specify)
Build this survey →Customer and service feedback
Short surveys that live at the end of something else — a visit, a purchase, a support ticket. The whole job is keeping them short.
Embed mode and per-survey branding
Recommend score follow-up
One 0–10 question, then a different follow-up depending on whether the score was low, middling or high.
Recommend score · Conditional logic · Long text
Build this survey →Website or service feedback
Embedded in the page it is about, with the page URL passed in as a hidden field so you know what they meant.
Embed mode · Hidden fields · Rating
Build this survey →Support ticket follow-up
Ticket reference in a hidden field, resolution rated, and one box for what would have been better.
Hidden fields · Linear scale · Long text
Build this survey →Complaint form
Contact details, a full account, supporting documents, and an address block with a checked postcode.
Address · File upload · Validation
Build this survey →Product or service quiz
Scored answers that land the respondent in a band, shown to them immediately with your own wording.
Scoring · Bands · Multiple choice
Build this survey →How to turn one of these into a real survey
The structures above assume five things about how you will build, and they are the five that make the difference between a survey people finish and one they close.
Branch early, not late
Put the question that determines what the rest of the survey looks like near the top — journey mode, year group, reason for leaving, whether they attended. Everything downstream then hangs off it with conditional logic, matching either any or all of your conditions. Scoring only counts questions a respondent actually saw, so branching never penalises someone for a section that did not apply to them.
Use a matrix instead of eight questions
Anywhere the same scale repeats — agreement statements, service ratings, confidence levels — ask it once as a matrix. It is faster to answer, and it exports as one column per row rather than as one cell of mush you spend an hour splitting apart.
Choose the layout to match the length
Classic works for a short form on one scrolling page. Conversational suits phone-first surveys, since one-tap questions advance themselves. Paged is the right answer for anything long or sectioned — a consultation, a grant application, a staged assessment.
Add save and continue to anything over ten minutes
A resume link keyed on a 24-character token means a half-finished answer
is not a lost one. Partial answers sit in a table with no row-level
security policies at all, reachable only through
SECURITY DEFINER functions —
the mechanics are here.
Set the ending before you send the link
A close date, a response cap and a custom closed message take a minute and save an awkward email. Both the cap and the date are enforced by a database trigger rather than by the interface, because responses insert straight from the browser.
When will there be real templates?
An in-app library — pick a template, get a survey — is planned but not built, and nothing on this page should be read as promising it. Until it ships, these pages exist to save you the design work rather than the typing. If there is a structure you want written up that is missing here, say so on the contact page; the list grows from requests.
If you are working out whether the product fits at all, the product overview is the quickest read, and the solutions pages map these structures onto the sector you are in. Pricing is not set yet, and building is free in the meantime.
Pick a structure and build it.
Start with the shortest one that answers your question, then add branching, scoring and a partner logo without rebuilding. Or describe the survey in a sentence and let the builder draft the first version for you to edit.
- Every structure above uses question types that exist today
- No in-app library yet — you build it, so the wording is yours
- Clear the test responses, uploads and all, before the link goes out
