Survey testing and reporting / Survey guide

Survey methods · Decision workshop

Bridge an open-text survey codebook revision

Trace reclassification when a survey theme definition changes instead of presenting it as a new respondent trend.

Opens product registration. Example questions are not imported automatically.

Editable examplesPractical guidanceNo-code starting point

DESIGN THE ANSWER SPACE

PROMPT 01

What does the timing label suggest this comment concerns?

Optional short open textProbe the broad label’s meaning before choosing a split.
PROMPT 02

Which part of this fabricated comment distinguishes unclear information from a changed date?

Optional short open textIdentify the actual inclusion evidence for the narrower themes.
PROMPT 03

When would both proposed themes apply to the same comment?

Optional short open textTest multi-coding rather than forcing exclusive bins.

Suggested formats to adapt, not preconfigured product fields.

A worked interpretation example

From a comment to a practical next step.

Illustrative scenario. These are not customer results.

01 / OBSERVE

Keep the finding specific

Three unchanged fabricated snippets are redistributed by a definition change.

02 / INVESTIGATE

Choose an action to test

Define clarity as missing or unclear date information and changed dates as explicit movement of an announced date; keep mixed and uncertain cases reviewable.

03 / FOLLOW UP

Check the experience again

Use fresh fabricated snippets including both issues and neither; check inclusion, exclusion and uncertain treatment.

Read the answers carefully

Keep the interpretation within the evidence

Changed classification of unchanged text is not attitude change. Ambiguous or mixed snippets need their stated review and multi-coding rules.

The same three synthetic snippets move from one broad timing theme to two clarity cases and one changed-date case under revised definitions. This is reclassification, not respondent change.

From question to next step

Make the feedback useful.

01

Run the pilot

Before applying a revised codebook, ask reviewers to explain the proposed theme boundaries using synthetic snippets.

02

Choose a bounded action

Define clarity as missing or unclear date information and changed dates as explicit movement of an announced date; keep mixed and uncertain cases reviewable.

03

Check the revision

Use fresh fabricated snippets including both issues and neither; check inclusion, exclusion and uncertain treatment.

A useful starting point

Optional free-text pilot questions

A synthetic version-one codebook groups both schedule clarity and date changes as “timing.” Version two splits clarity from changed dates. Three unchanged snippets are recoded.

If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.

QUESTION 01

What does the timing label suggest this comment concerns?

Probe the broad label’s meaning before choosing a split.

QUESTION 02

Which part of this fabricated comment distinguishes unclear information from a changed date?

Identify the actual inclusion evidence for the narrower themes.

QUESTION 03

When would both proposed themes apply to the same comment?

Test multi-coding rather than forcing exclusive bins.

QUESTION 04

What case would you leave uncertain under these definitions?

Expose an unresolved boundary that should remain reviewable.

Download the questions as text ↓

Examples to adapt, rather than a validated research instrument.

Choose the response format

Make room for the explanation.

Suggested formats for this example questionnaire
QuestionSuggested formatWhat to preserve
What does the timing label suggest this comment concerns?Optional short open textProbe the broad label’s meaning before choosing a split.
Which part of this fabricated comment distinguishes unclear information from a changed date?Optional short open textIdentify the actual inclusion evidence for the narrower themes.
When would both proposed themes apply to the same comment?Optional short open textTest multi-coding rather than forcing exclusive bins.
What case would you leave uncertain under these definitions?Optional short open textExpose an unresolved boundary that should remain reviewable.

Make questions optional where appropriate. If you add a rating scale, label its endpoints, keep one idea per question, and retain a follow-up for reasons. These examples are not a validated measurement instrument.

Before you send it

Check what your wording assumes.

BEFORE / LEADING

Does this timing complaint prove the date was changed?

AFTER / CONTEXTUAL

Which part of this fabricated comment distinguishes unclear information from a changed date?

The reviewer must identify text evidence rather than infer a narrower theme from a broad label.

Build with SurveyTeams

Adapt these pilot questions in SurveyTeams

Use these examples to draft your questionnaire. Create a survey draft, add questions, and check the respondent preview in SurveyTeams. Additional features depend on your account and plan.

Create your survey in SurveyTeams

Opens product registration. Example questions are not imported automatically.

Learn about the product ↗

Run a focused feedback cycle

Plan the invitation, review and follow-up.

When and whom to ask

Before applying a revised codebook, ask reviewers to explain the proposed theme boundaries using synthetic snippets.

Who reviews the finding

The coding owner versions definitions; a second reviewer checks ambiguous and multi-theme cases.

What to check after a change

Use fresh fabricated snippets including both issues and neither; check inclusion, exclusion and uncertain treatment.

Handle responses carefully

Use invented text and avoid extracting identifiable comments into a public worksheet.

A practical decision workshop

Inspect the example before choosing a rule

Trace an invented case, preserve the evidence limits, then adapt the manual worksheet to your own decision.

Version comparison viewer

Keep the draft and its correction visible

Draft or earlier version · review its limits

Date-change concerns fell from three to one.

Revised example · limits retained

The same three synthetic snippets move from one broad timing theme to two clarity cases and one changed-date case under revised definitions. This is reclassification, not respondent change.

What the review changes
Review boundaryDraft to reviewRevised example
Theme ruleBroad timing labelSeparate inclusion rules
TrendReclassified records called a declineSame responses, changed codebook

Wide tables scroll sideways on small screens.

Synthetic example · not customer data

Inspect the records

Synthetic pilot and reporting records
Synthetic snippetTextCodebook v1Codebook v2
s1Date was not explainedTimingClarity
s2Date moved twiceTimingChanged dates
s3No date providedTimingClarity

Wide tables scroll sideways on small screens.

Download records (.csv) · Download complete decision kit (.json)

Decision explorer

Choose an evidence situation

This returns a written example explanation. It does not inspect your records or approve a real report.

Choose a situation to read its example explanation.
Read every situation without the interactive tool
Original text and both definitions are retained
Write a snippet-level bridge and disclose the coding-version break.
Earlier text or definitions are unavailable
Hold exact reclassification claims.
A later respondent wave is compared
Review both instrument and coding comparability before a trend claim.

Before you send it

Questions, answered.

What belongs in the new clarity theme?

Missing or unclear information about a date; an explicit date change alone is excluded. Mixed comments may receive both themes.

What if the snippet only says “timing bad”?

Its specific issue is uncertain. Retain it for review rather than guessing a narrow theme.

Can this show attitudes improved?

No. The response text is unchanged; the definition changed.

Will the example import or configure a results view?

No. Copy the optional text prompts into a manual draft. Tables, coding rules and comparisons are separate educational worksheets; check supported product features in your account.

Continue exploring

Related feedback guides.