Survey logic — the rule layer that decides which question shows next. Skip, branching, piping, display, scoring — what each one costs the analysis.
Survey logic is the skip and branching rules that show each respondent only the questions that apply to them, producing cleaner structured data. Sopact runs that logic against clean-at-source intake onto the Outcome Thread: one participant record under a persistent Contact ID, validated as it is entered so the structured answers are analyzable on arrival rather than repaired after export.
Branching is meant to make data cleaner, and often makes the export messier. Every path a respondent could take becomes a different set of populated columns, so a raw file is full of blanks that mean “not asked” and blanks that mean “skipped,” and untangling them is another cleanup pass. The logic saved the respondent time and cost the analyst a day.
Key takeaways
Logic in a form-centric tool controls what a respondent sees but still writes every path into one flat export. Blanks pile up with no marker for why, IDs across branches have to be reconciled, and a downstream analyst rebuilds the structure the logic already knew. Each send repeats the untangling on a fresh anonymous sheet.
Sopact is record-centric: logic runs against validated intake and each answer lands clean on a persistent Contact ID, so a branched survey is analyzable on arrival on the Outcome Thread rather than a file to reconstruct. See the wider discipline on survey methodology, or the act of gathering on survey data collection.
SurveyMonkey, Qualtrics, Google Forms, Typeform, and Microsoft Forms all support skip and branching logic, and each writes the results to an export you then clean in Excel. Each builds paths well, and each treats the output as a flat file, so the logic that shaped the interview is not preserved in a form the analysis can use directly.
The one test that separates them: ask the tool to deliver a branched wave already structured and validated, landing on the same records as the last wave. A form-centric tool answers with a flat export and ambiguous blanks. Sopact answers from the Outcome Thread, because intake was validated at the source and the record persists.
The move that makes branching pay off is validating each answer as it is entered, so a skipped question and an unanswered one are distinct and the structured data lands ready. Sopact enforces the rules at the source and reads any open-text on arrival, so a branched survey is analyzable the moment it closes rather than after a reconstruction pass.
Kept on the Outcome Thread, logic is durable across waves: the same respondent’s paths and answers on one persistent ID, so a follow-up survey branches from what is already known. Sopact keeps collecting after a wave, so the next send asks only what the record does not already hold.
A form-centric tool applies logic and returns a flat file to untangle; the Outcome Thread runs logic against validated intake and lands each answer clean on one record. The difference is whether branching saves work or moves it to the analyst.
| The question | Flat export | Outcome Thread |
|---|---|---|
| Show relevant questions? | Yes: by branching | Yes, on the participant record |
| Structured on arrival? | No: a flat file | Yes: validated at intake |
| Skipped vs unanswered clear? | Ambiguous blanks | Yes: marked at the source |
| Branch from prior waves? | No: a new sheet | Yes: one persistent ID |
See the wider discipline on survey methodology, or how to read the results on how to analyze survey data.
An export is a snapshot of what a batch answered by the time you opened the file. The value of a response is highest the moment it lands, when a low rating or a worrying open-text answer can still change what happens next, not in a report written after the survey closed. That is the premise of the Loop, Sopact’s method for continuous intelligence: collect clean at the source, so each response is validated at intake on a persistent Contact ID with no post-hoc cleanup; analyze on arrival, so the open-text is themed as it lands rather than set aside for later; improve in time, so a problem in the responses surfaces during the cycle instead of after it.
The Loop is also what keeps a survey finding defensible: every theme traces back to the exact sentence a respondent wrote and the number that respondent also gave, the standard detailed in Loop traceability, so a conclusion rests on the Outcome Thread rather than a cleaned-up spreadsheet no one can re-check.
One method, three moves that never stop
Then the next wave reads a little sharper on the same record. Read the method: the Loop methodology →
The fastest way to see validated logic is to run a branched wave on your own participants. Export a branched survey with its IDs and any open-text, then paste the prompts below into Sopact Sense’s Assistant, or reason through them with your team. The arrow above each links the Academy walkthrough with the expected output and tips.
Academy walkthrough → Analyze open-ended responses
Here is a batch of open-ended survey responses with each respondent’s ID and rating: [ATTACH]. Read each open-text answer against our codebook as it lands, tag the themes, quote the exact sentence behind each theme, and keep every answer tied to the respondent’s persistent ID and number, so the reason sits on one Outcome Thread rather than in a separate export I have to match later.
Academy walkthrough → Clean responses at the source
Here is a raw export of survey responses on their participant IDs: [ATTACH]. Flag blanks, duplicates, and off-topic answers, normalize the text and the structured fields, and keep each cleaned response tied to its persistent ID, so the data is analyzable the moment it lands on the Outcome Thread instead of after a round of hand-cleaning a fresh anonymous sheet.
Academy walkthrough → Connect the number and the reason
Here is our quantitative data and the open-ended responses on the same participant IDs: [ATTACH]. For each rating, pull the open-text the same respondent wrote that explains it, quote the sentence, and show the number and the reason on one record, so a low score carries its reason on the Outcome Thread rather than sitting in a column with no explanation.
Academy walkthrough → Read results by subgroup
Here are our survey results with each respondent’s subgroup and persistent ID: [ATTACH]. Break the scores and the themes out by subgroup, quote the sentence behind each subgroup’s pattern, and keep every row on its participant record, so a difference between groups is read from the Outcome Thread rather than re-sliced by hand from a new anonymous export each wave.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Watch: collecting clean at the source on a persistent record and reading the open-text on arrival, so the survey keeps collecting on one Outcome Thread.
It is the skip and branching rules that show each respondent only the questions that apply to them. Sopact runs that logic against clean-at-source intake on the Outcome Thread, so the structured answers are analyzable on arrival rather than repaired after export.
Because a form-centric tool writes every path into one flat export, filling it with blanks that mean different things. Sopact validates each answer at the source on the Outcome Thread, so a branched path lands structured and clear.
Those tools build paths well and return a flat file to clean. Sopact is record-centric: it runs logic against validated intake and keeps each answer on a persistent Contact ID on the Outcome Thread, so the structure survives into analysis.
Yes. Sopact marks the distinction at the source on the Outcome Thread, so an analyst is not left guessing whether a blank means not asked or not answered.
Yes. Because the Outcome Thread persists, a later wave branches from the same respondent’s prior answers rather than starting from a blank form.
Yes. Sopact reads any open-text on arrival and ties it to the branched structured answers on the Outcome Thread, so the reason behind a path is captured too.
Yes. Validated at intake and kept on a persistent ID, every answer traces to a clean record, so a finding from a branched survey rests on the Outcome Thread rather than a reconstructed file.
Sopact keeps every wave on one persistent ID, so a respondent’s branched answers across sends read as a trajectory. The Outcome Thread survives each cycle, which makes durable logic possible.
Next: see the wider discipline on survey methodology, or the act of gathering on survey data collection.
