Open-End Coding Studio
The Open-End Coding Studio helps you turn unstructured text responses into structured, analyzable themes.
Use this workflow when your survey includes Short Text or Long Text questions and you want faster, more consistent coding.
Note
Open-end coding (this article) runs after collection. AI probing on Long Text questions nudges respondents for richer answers during the interview — see Long Text (Open-end). They are separate features.
Before you start
- Your package must include AI Open-End Coding.
- Your survey should already have responses.
- Open-end coding works on open text responses (for example, short text and long text answers).
Where to find it
Open your survey from the dashboard.
Go to Open-ends (Intelligence), then open the Coding (themes) tab. From Analytics you can also use Code open-ends / themes.
The Open-End Coding Studio opens in the dedicated coding workspace.
Workflow overview
The coding studio uses a researcher-friendly flow:
- Pick a question and review sample answers
- Build themes — Suggest themes, Use my list, or Reuse saved themes, then edit in the visual theme editor
- Set coding options — single vs multi-theme, confidence threshold, model, include tests
- Review & code — confirm the pre-run summary, then start the job
- Needs attention — fix uncertain answers with theme chips, Apply to similar, Mark reviewed
- Approve for analysis — lock the codeframe version and activate for analytics charts
- Optional Research tools — emerging themes, drift/QA, audit CSV, compare, rerun
Advanced JSON / codeframe version controls stay available for power users; day-to-day work stays in the visual theme editor.
Step 1: Questions
Select the open-ended question you want to code.
- Only eligible open-text question types are listed.
- If no eligible question appears, add open-text questions in the survey builder first.
Step 2: Themes / codeframes
Themes are your codebook structure.
What you can do
- Suggest themes from real responses
- Use my list to paste or enter your own theme set
- Reuse saved themes from an existing organization codeframe
- Edit themes visually (labels, chips) before you run coding
- Keep reusable codeframes and versions for your organization
Version status
Each version can be:
- Draft: editable, good for testing
- Locked: stable for production use (required before Approve for analysis)
- Deprecated: cannot be used for new jobs
Step 3: Run coding
Configure options, review the pre-run summary (and estimate when available), then start the job.
Progress appears in the studio while coding runs.
Step 4: Review
Focus on Needs attention items first.
Review features
- Default focus on items that need attention
- Confidence and multi-theme controls
- Theme chip pickers for quick edits
- Search and filters for status / review state
Manual correction tools
- Override themes on one response
- Apply to similar responses in bulk
- Mark reviewed / clear themes
- Bulk assign a shared theme set
Step 5: Approve for analysis
When review is solid, Approve for analysis locks the codeframe version (when needed) and activates coding for survey analytics / theme charts.
Step 6: Research tools and audit
Use the research tools panel for emerging themes, drift/QA checks, compare/rerun, and audit history (including CSV export).
Best practices
- Start with a small sample run before coding the full set.
- Prefer clear, mutually exclusive theme labels unless you intentionally allow multi-theme.
- Lock and approve only after human review of Needs attention items.
- Keep probing (during the interview) and coding (after collection) separate in your study design.