QubeSurveyQubeSurvey
Guides and references for writing survey scripts, testing them with a team, collecting responses and exporting data. In QubeScript, you write the questions, answer options and survey logic in a text file. Write and test locally with the QubeSurvey VS Code extension, then upload a version to the app for team review.
Getting started
- Getting started: the four-step path from local authoring through fieldwork and export.
- Choose a starting point: a route for an existing questionnaire, advanced routing, or a first small study.
- QubeScript basics: a short language introduction.
Write and test
- QubeSurvey extension: local editing, checks, interviews, uploads and field transforms.
- QubeSurvey MCP: local script tools and optional hosted fieldwork tools for your AI agent.
- Using existing Odin scripts: run supported Odin surveys on QubeSurvey or audit and test them before NIPO Fieldwork System.
- Testing a script: run routes and record a reproducible problem.
- Tickets and proposed fixes: review a reported issue and its candidate version.
- How the Assistant works: hosted ticket work, review and cost.
Run and manage
- Managing fieldwork: Participants, Groups, Runs, outcomes, quotas, responses and exports.
- Services: AI tasks called from your survey.
- People, access and billing: Accounts, Script roles, Run progress access and prepaid credit.
Language reference
- QubeScript reference: contracts, domains, routing, repeats, frames, ordering, validation, overlays, endings and the full standard library.
- Odin reference: command coverage, data positions, expressions, routing, presentation and the differences from NIPO Odin.
- Fictional survey examples, including the short commuter-travel study. Each full study pairs a brief and Word specification with QubeScript and Odin source.
Terms used in QubeSurvey
| Term | Meaning |
|---|---|
| Account | Owns your team’s Scripts, participants, Groups, Services and shared prepaid balance. Account membership and access to individual Scripts are managed separately. |
| Script | A questionnaire, its uploaded versions, collaborators and tickets. Edit the file locally, then upload it as a new version. |
| Version | A saved copy of an uploaded script. It stays unchanged; upload another version to revise it. |
| Run | A round of data collection using a selected Script version, with its own access settings and responses. It starts as a draft; activate it when ready to collect. |
| Attempt | One respondent interview session, whether completed, screened out, or abandoned. |
| Ticket | A reported issue tied to a Script or version. A ticket filed from a running test can also capture the interview history. |
| Participant | A person in your sample or contact list. Use Groups to organize cohorts for invitations or signed-in access. |
| Service | An AI task that your survey can call, such as interpreting an open-text answer. |