Product
Overview
The Survey Design Support System is a platform that handles designing, reviewing, versioning, and reusing questionnaires in a single set of screens, and pushes the finished questionnaire automatically into the delivery tool Creative Survey (CS).
A survey designer starts by entering a "theme" โ client, research objective, delivery area, and category โ then builds sections (major groups) and questions, and finally configures branch logic that reacts to respondents' answers. The finished questionnaire is exported as JSON and pushed into CS through a Chrome extension.
Problems (Why)
| Problem | How the system solves it |
|---|---|
| Questionnaires are designed in spreadsheets, so versions cannot be managed and differences cannot be tracked | Every save creates a version, and any version can be rolled back to or duplicated |
| Questions from past projects are found and copied by hand | Questions of exported surveys are accumulated automatically in a question library that can be searched and reused with one click |
| Pushing a designed questionnaire into CS by hand takes time and introduces transcription errors | The Chrome extension reads the questionnaire JSON and uses the CS API to create questions, choices, and branches in bulk |
| Whether a branch setting is possible depends on CS, and cannot be judged at design time | The policy is "everything CS can do must be possible here", so condition operators, AND/OR, and visibility logic follow the same semantics as CS |
| It is unclear who may edit which survey | View / edit permissions are set per survey, making the sharing relationship explicit |
Target Users
| User group | Description |
|---|---|
| Survey designer | Designs, edits, and exports questionnaires. Holds edit permission on a survey |
| Reviewer | Reviews authored questionnaires. Holds view permission on a survey |
| Administrator | Can access every survey and delete surveys and past question data |
Out of Scope
- Collecting and tabulating responses (delivery and tabulation are Creative Survey's responsibility)
- Score logic (branching on score groups)
- Randomized branch destinations (exists in CS but is not used)
- Survival-format questions (exists in CS but is not used)
- Branch destinations across sections (only within the same section, plus section complete / survey complete / screen out)
- Step and choice randomization, piped text
Current Phase
The project is in the development phase ahead of an internal rollout. Survey management, questionnaire design, versioning, permissions, the question library, and CS integration are all implemented, and work is ongoing to reach parity with CS on branching (full coverage of condition operators, visibility logic, and additional question types).
See branch-logic-current-state-and-cs-diff.md and branch-cs-parity-implementation-plan.md at the workspace root for details on the policy and the gaps.