Fictional studies: introduction and methodology

This collection demonstrates how professional market research instruments are specified and implemented in both Odin (NIPO-compatible) and QubeScript.

Unlike trivial single-question examples, these five studies illustrate substantial, real-world research workflows:

  • Multi-stage eligibility screeners with demographic and category quotas
  • Complex brand funnels (unaided recall, aided awareness, recent purchase, most-often purchase, consideration)
  • Dynamic loops over carried brand and category selections
  • Independent evaluation of satisfaction, repeat intent, and perceived value
  • Numeric gating (e.g. asking whether an estimate can be provided before capturing currency or counts)
  • Clean separation between substantive negative answers and missing/unapplicable codes (Cannot judge, Don't know, Prefer not to say)

Real-world specifications (.docx)

In commercial market research agencies, questionnaires typically originate as Microsoft Word documents created by research executives and passed to survey scripters. These specifications include:

  • Project metadata: Project name, client sponsor, methodology (CAWI), sample universe, target completes, and estimated length of interview (LOI).
  • Scripter instructions: Explicit programming annotations such as [PROGRAMMING NOTE: ...], [SINGLE CODE], [MULTI CODE], [ROTATE], [RANDOMIZE], [PIPE ...], and [ANCHOR AT BOTTOM].
  • Screener and termination rules: Directives such as [TERMINATE IF ...], [FILTER / ROUTING: ASK IF ...], and quota cell assignments.
  • Structured option tables: Precise code assignments and respondent labels.

Each study in this collection includes a downloadable .docx file formatted in this real-world agency style.

Paired language implementations

Every study is provided with two independent, fully working scripts:

  1. Odin: Written in standard Odin syntax for teams with existing NIPO workflows or legacy scripting assets.
  2. QubeScript: Written in QubeScript, QubeSurvey’s modern, typed survey language with native expression handling and domain selectors.

Both scripts satisfy the exact same research contract and produce identical collected question flows.

Testing and scenario verification

Each study is accompanied by a suite of synthetic scenarios (fixtures.json or scenarios.json). These test suites exercise:

  • Complete eligible respondent journeys
  • Screener terminations (underage, non-purchasers, non-decision makers, non-visitors)
  • Exclusive option enforcement (e.g. verifying that selecting “None of these” alongside a brand is rejected)
  • Range and format boundary checks
  • Carried selection integrity across repeated loops

You can verify all test scenarios locally from the repository root:

node tools/test_fictional_consumer_studies.mjs
node tools/test_fictional_professional_studies.mjs

Exploring the studies

Select any study from the sidebar to inspect its research scenario, download the Word specification and source files, and toggle between the Odin and QubeScript implementations:

Collection notes and shared test contract · File checksums