General research
AuraScore 79/100

Quantitative Survey Instrument Pre-Flight Checklist

Verify survey design, logic branching, and data integrity parameters before live fielding.

Use this template prior to launching primary quantitative research studies or customer panels. It delivers an operational verification checklist to avoid survey bias, logic breaks, and data quality flaws.

Template

Role: Quantitative Research Operations Lead with deep expertise in survey methodology and data validation pipelines.

Context

  • Survey Objective: {{survey_objective}}
  • Target Sample Size: {{target_sample_size}}
  • Demographic Strata: {{demographic_strata}}
  • Fielding Window: {{fielding_window}}
  • Data Collection Platform: {{data_collection_platform}}
  • Statistical Power Target: {{statistical_power_target}}

Task

Develop an operational pre-flight checklist to validate survey instrumentation, skip logic, sampling quotas, and data collection integrity before launching {{survey_objective}}.

Method

  1. Review question phrasing to eliminate double-barreled prompts, leading language, and framing bias.
  2. Verify response scale consistency (e.g., Likert alignment, balanced polarity, mutually exclusive options).
  3. Test complex branching logic, piping, and randomization rules on {{data_collection_platform}}.
  4. Validate quota balancing rules against {{demographic_strata}} requirements.
  5. Audit fraud prevention mechanisms (e.g., reCAPTCHA, honeypots, duplicate IP filters, speeders thresholds).
  6. Check data export schema compatibility with downstream statistical software.
  7. Run a soft-launch pilot verification protocol across a 5% sample sub-segment.
  8. Verify statistical adequacy against {{target_sample_size}} and {{statistical_power_target}} parameters.

Constraints

  • Every checklist item MUST state the specific technical or methodological risk it mitigates.
  • MUST NOT permit ambiguous survey logic without a manual dry-run verification step.
  • Structure items sequentially matching the respondent journey and data backend configuration.
  • Maximum length of 25 checklist items across all stages.

Output format

  • Section 1: Question Design & Construct Validity (5-7 checklist items with [ ])
  • Section 2: Technical Logic & Platform Integrity (5-7 checklist items with [ ])
  • Section 3: Quotas, Sampling & Fraud Prevention (4-6 checklist items with [ ])
  • Section 4: Data Pipeline & Export Validation (3-5 checklist items with [ ])
  • Launch Go/No-Go Decision Gate (3 mandatory sign-off criteria)

Self-review

  • Does the checklist account for quota controls specific to {{demographic_strata}}?
  • Are data pipeline checks fully compatible with {{data_collection_platform}}?
  • Will completing this checklist guarantee sample readiness for {{target_sample_size}}?
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering8/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

research-analysis
research-general
research-productivity-operations
survey-design
data-collection
research-ops