Link the stages
You add your studies to the project as stages. On each stage card you choose its source and write the condition for moving on: "everyone scoring above 70 on the pre-test", "everyone who chose this track". Pointing one source at two different targets is branching — you can run different second stages for different age groups.
Keep the data apart
Because every stage is its own study, every group gets its own clean table. The sparse table you end up with when you squeeze everything into one questionnaire and steer it with skip logic — the one where the branches a participant never saw stay empty — does not appear here. Your columns are full when you reach analysis.
Rehearse before a real participant sees it
Run the chain end to end in pilot mode: fill in the form, watch the filter select the right people, check that the invitation goes out and that entry to the second stage opens. Then take everything live in a single action. Pilot data is deleted, and the deletion is written to the destruction log.
See the silent mistakes first
If you wrote your age bands as "18-25" and "25-35", you are told that 25 goes down both branches; a band that goes down no branch is reported too. Closing dates, language coverage, participation quotas and a missing contact question all turn into the same kind of warning. Warnings do not block publication — the decision is yours.
Without touching your questionnaire
The chain lives in the project, not inside the questionnaire. You do not have to break your survey to build the flow: the same exam can be the second stage of one project and stand on its own somewhere else. The template version is pinned to the project, so you can run the same study again next year with the same instrument.
Setup steps
Linked stages, separate data.
Where it is used
Where it is used
Application and exam
Those who meet your criteria among the applicants are invited to the exam. When you run the filter you see, in a preview, how many people qualify and how many have no address on file, and then you approve.
A different instrument per segment
You ask for age in the first stage and run a separate second questionnaire for each age group, with its own wording and examples.
Tiering by score
The pre-test score sends the participant to the easier or the harder second exam.
Multi-stage selection
Pre-screening, the qualifying exam and the certification stage are linked to one another. A stage marked by a person →
Security & architectural discipline
Security & architectural discipline
Access to the second stage is enforced on the server; the invitee list is kept only in an area restricted to administrators. Partially completed answers are left out of the eligibility calculation. The same person is never invited twice through the same link. Questions holding personal data are marked in the interface while you build the chain. These mechanisms are not a compliance guarantee; they are tools that support the controller's decision and put it on record. The controller adds the project context to each stage's privacy notice.