Practical guide
Define One Survey Question Before You Choose the Interface
A workshop ends with one unanswered question: which topic should the follow-up session cover? By Monday, that question has acquired a visual builder, response dashboard, integration plan, and account decision.
The research job is still one controlled answer. Define that interaction first. You will know whether the surrounding software changes the result or merely surrounds it.
Give the question five lines
Write the prompt, answer type, required consent version, completion rule, and export column. These lines create a stopping point that a person can inspect before any interface choice takes over.
The demonstrated interaction recognizes five answer types:
- short text;
- email;
- single select;
- a rating from one through five;
- yes or no.
Choose the single type that matches the decision. This job ends after one question, so an answer-dependent path adds no value to its result.
For a fictional workshop, the facilitator asks, “Which topic should the follow-up session cover?” The definition lists the choices. A supplied answer must match one of them before the interaction can finish.
Make completion mean something exact
The interaction begins after affirmative consent matches the version named in the definition. A valid answer then satisfies the required field and reaches the stated end.
Opening the question is activity, not completion. A value outside the allowed choices is an error, not a usable response. Closing the interaction halfway through leaves no finished row to review.
This distinction protects the research decision. The completed file contains answers that reached the same declared stopping point, rather than a mixture of views, partial entries, and finished responses.
Compare the definition with the completed row
The bounded file job writes completed responses to CSV with columns in definition order. It quotes cells and neutralizes formula-like spreadsheet values before a reviewer opens the file.
Use this four-step check:
- Read the question and choices from the definition.
- Compare the supplied answer with the allowed rule.
- Confirm that the CSV column names the question answered.
- Keep interpretation notes separate from the response value.
The proof sits in that comparison. The definition states what can count. The completed row shows what did count. A reviewer can inspect both without reconstructing settings from a screen.
Decide whether the surrounding service changes the result
Typeform documents answer-dependent logic, response exports from its Results area, and webhooks that send response data to an HTTPS destination. Those functions belong to a wider authoring, collection, and connection experience.
The file-defined job covers one supplied interaction and one completed CSV record. Choose the wider service when visual authoring, public response collection, richer logic, file uploads, shared workspace access, analysis, or live connections affect success.
Choose the smaller boundary when one person controls the definition, one supported answer resolves the immediate question, and a completed row is enough for review.
Take away the five-line test
One question needs a precise prompt, one answer rule, a consent version, a completion condition, and a review column. If five lines cannot describe the job, name the missing requirement before comparing interfaces.
Write the definition on one page
Put the five lines beside the decision the answer will inform. Then ask whether anything outside that page must happen for the research job to finish.