Choose a starting point

Choose the path that fits the work. Each one ends with a small questionnaire you can check against an explicit expectation. The same five steps take a reviewed script into hosted fieldwork:

  1. Install the QubeSurvey extension. See installation.
  2. Write or paste a script and test it locally. Use invented answers.
  3. Upload to app.qubesurvey.com for team testing and tickets.
  4. Run fieldwork. Use an open link or personal invitations when enabled.
  5. Export and download the data. Use an available Run export.

The first-survey guide explains each step and current beta limits.

Before you start

  • Use invented study details, participant identities and answers throughout.
  • Local authoring and interview testing with QubeSurvey extension need no hosted account or sign-in.
  • Hosted sign-in options depend on the environment. A configured identity provider can allow registration without an invitation; email sign-in links are limited to existing accounts and current project invitees. A signed-in user can create a billing Account and a Script. Uploading to an existing Script requires Account access and permission to edit it; see People, access and billing.
  • Hosted MCP is limited to an evaluation and is not generally enabled. None of these paths depends on it.

I work in market research or script surveys for NIPO

Start with one study specification and its existing instrument.

  1. Keep the specification beside the source. Pick one representative route whose wording, answer domain or routing matters to the study.
  2. Use the source as your reference. For QubeScript, see the quickstart; for an existing Odin file, keep its .odin extension and test the behavior you need.
  3. Open the file in the QubeSurvey extension. Resolve errors and review warnings.
  4. Run the selected route locally, compare its questions and outcomes with the specification, and test a correction with Back if it is relevant.

Result: one route checked locally against its written requirement. This is a bounded route check; it does not establish that a whole NIPO questionnaire has been migrated.

I need a more explicit route than my current survey tool provides

Start with one known constraint and one branch that is difficult to check.

  1. Write the condition and expected behavior in plain language: which answer leads where, and what should happen when it does not match.
  2. Adapt the small example in the QubeScript quickstart to express that branch.
  3. Save it as .qube and open it in QubeSurvey extension. Resolve errors.
  4. Run both the matching and non-matching paths. Compare the result with your written expectation and check a correction with Back.

Result: a constrained branch expressed in source and checked against both expected paths.

I am exploring a basic research question for a startup

Start with one decision and the group whose views would inform it.

  1. Write down the decision, the target group, and what you still need to learn.
  2. Use the tiny QubeScript sample as a prototype. Change only what is needed to ask your first questions.
  3. Run the prototype locally in QubeSurvey extension with invented answers.
  4. Review the wording for leading questions. Check that the target group is appropriate and decide how you would recruit them; the prototype does not establish either.

If you use an assistant you already have, under your own model and data settings, you can give it this brief:

I am deciding [decision] for [product or service]. The people whose views matter are [target group]. I need to learn [one or two unknowns]. Suggest three to five neutral draft questions for a short prototype, based on the QubeScript sample or study I provide. Mark assumptions and flag wording that could lead an answer. Do not claim the questions are validated or choose who to recruit. Return suggested wording only; I will review it and write or adapt the QubeScript source.

Treat generated wording as a draft, not proof of research validity. Review the wording, target group and recruitment plan yourself.

Result: a small question set and a human-reviewed plan for what to check next.

Continue with a Run

When you have a version to test in hosted fieldwork, follow Prepare your first survey. It covers hosted version testing, creating and activating a Run, submitting an invented response, and exporting the result.