Survey Variable Names and Recodes

Create readable variable names, stable answer labels, and recodes before the data reach analysis.

Why Variable Names And Recodes Matter

Analysis-ready survey data depends on readable variable names and stable coding. Before launching an academic research survey, decide how each key question should appear in exports and how answer options should be represented in analysis.

Variable naming is easiest while you are still in Block Builder. Name the question before using it in Flow, quotas, random assignment, codebooks, API pulls, or analysis scripts.

Changing a variable name or recode value after live data collection has started will break any analysis script, codebook, or API query that references the old name. Freeze names before publishing.

Block Builder: Variable Name

Name A Question In Block Builder

Step 1: Open the question card. In Block Builder, select the question that will appear in analysis, Flow, quotas, or a codebook.
Step 1: Open the question card
Step 2: Fill in Question Name. Use a short stable name, such as party_id, age, treatment_check, or trust_media.
Step 2: Fill in Question Name
Step 3: Add recodes where available. For closed options, enter stable numeric or text recodes before publishing.
Step 3: Add recodes where available
Step 4: Preview and submit a test response. Use Preview to make sure the respondent-facing label still reads naturally.
Step 4: Preview and submit a test response
Step 5: Open Export. Confirm the exported header and values match the codebook before live data collection.
Step 5: Open Export

Name Questions For Analysis

Use short, descriptive question names for variables that will appear in models, branching, quota logic, or codebooks. Names such as party_id, age, treatment_check, or trust_media are easier to analyze than long prompt text.

Prefer lowercase with underscores: policy_support is easier to use in scripts than a sentence-length prompt.
Include the construct, not the wording: trust_court can survive a wording edit better than agree_courts_are_fair.
Keep waves or arms explicit: use names such as w2_income or post_trust_media when timing matters.
Avoid vague labels: names like question_1, score, and response become hard to audit in exports.

Export: Variable Names in Output

Use Recodes For Stable Values

Recodes let researchers keep exported values stable even if display labels are longer or more participant-friendly. They are especially useful for Multiple Choice, Grid Matrix, Conjoint, and Ranking questions.

Ordered scales: use numeric recodes in the same direction across the battery.
Nominal categories: use stable text or numeric codes that will not change when labels are edited for readability.
Missing-like answers: document Prefer not to answer, Don't know, Other, and skipped values separately.
Experimental arms: choose condition codes that analysts can understand without seeing the full treatment text.

Block Builder: Multiple Choice (Recodes)

Best Practices

Use consistent naming conventions across related surveys, study waves, and library blocks.
Keep recodes stable after publishing, and document any mid-field change in the codebook.
Document missing values such as Prefer not to answer, skipped, invalid, screen-out, and quota-full paths.
Use numeric recodes for ordered scales when that helps analysis.
Review exports before collecting live data and again after any major edit.

Related Help