Plan Data Quality Before Launch
Data quality is part of survey design. In academic survey software, quality checks should be built into the instrument, flow, publishing process, and export review before live collection begins.
Preview: Respondent View
Preview
Walk through respondent-facing behavior in the same preview surface.
Run The Quality Pass
Step 1: Review Block Builder. Check wording, required questions, validation rules, attention checks, and any respondent-facing instructions.
Step 1: Review Block Builder
Survey Editor
No-persist demo using the real builder shell.
Step 2: Review Flow. Confirm screeners, experimental paths, quota-full routes, and end screens work as intended.
Step 2: Review Flow
Block BuilderPreviewDeployFlow Canvas
Interactive routing surface from the app, running in no-persist help mode.
Step 3: Review Deploy. Check public link settings, quotas, reCAPTCHA, and launch readiness.
Step 3: Review Deploy
Block BuilderPreviewDeployDeploy
Configure publishing, links, quotas, and theme from the Deploy tab.
Step 4: Use Preview. Complete the survey with realistic answers for every major path using the pilot testing workflow.
Step 4: Use Preview
Block BuilderPreviewDeployPreview
Walk through respondent-facing behavior in the same preview surface.
Step 5: Inspect Export. Submit test responses and confirm variables and recodes, conditions, and randomized order fields are present.
Step 5: Inspect Export
Block BuilderPreviewDeployExport
Download analysis-ready response data from the Export tab.
Step 6: Fix and repeat. Re-run the quality pass after any change to wording, Flow, quotas, validation, or response options.
Step 6: Fix and Repeat
Survey Editor
No-persist demo using the real builder shell.
Common Quality Checks
- Eligibility screeners: keep the target population clear.
- Required questions: prevent missing values where an answer is essential.
- Validation rules: keep numeric and text answers in the expected format.
- Attention checks: identify careless responses when your protocol allows them.
- reCAPTCHA: reduce automated responses on public survey links.
- Pilot testing: catch confusing wording and broken paths before launch.
For experimental studies, add manipulation checks and comprehension checks that match the treatment design. See Attention and Manipulation Checks.
Block Builder: Required Toggle
Block Builder: Required Questions
Toggle Required on any question to make it mandatory before the respondent can continue.
Use Flow And Quotas Carefully
Broken routing can damage data quality as much as bad wording. Preview every path, especially eligibility exits, experimental conditions, and quota-full screens. If quotas affect routing, confirm the quota status variable behaves as expected.
Flow: Conditions and Routing
Flow Canvas
Interactive routing surface from the app, running in no-persist help mode.
Review Exported Data
Submit test responses and inspect the export before publishing. Confirm that variables, recodes, condition assignments, and randomized order fields are present when needed.
Export: Data Output
Export
Download analysis-ready response data from the Export tab.