Analyze Qualitative Data with Structured Coding
Analyze qualitative data using a structured coding framework that combines deductive codes from your theory of change with inductive codes emerging from the data, culminating in thematic analysis.
Your Prompt
- What You Need
- Provide the research questions, de-identified texts or dataset description, any theory of change, respondent metadata, and quote permissions.
- Choose This Prompt When
- Choose this to code and analyze supplied qualitative material; choose interview-transcript analysis for a concise cross-interview synthesis.
Describe your goal, audience, available information and constraints. Your words are added to the prompt as supplied. You can also use the guided fields below.
Kept in this tab while you work. Copy and Start includes this description.
Copy this prompt and paste it into your AI chat to start. If it needs source material, the AI will ask for it.
Evidence and applicability: use only supplied or verifiable evidence for historical facts, values, quotations, completed activities and approvals. Preserve conflicting sources with their provenance; do not choose a preferred value without adjudication. Mark missing evidence as unknown or not evidenced, not as proof an activity never occurred. Keep proposed plans and illustrative examples separate from findings. Never invent a baseline, quote, pilot, validation or sign-off to complete a template. Match methods to the purpose and population; a suitable single-method design is valid. Distinguish descriptive change from causal attribution. Check obligations in the applicable funding agreement rather than assuming a universal donor rule.
Develop and, when source texts are supplied, apply a qualitative coding and thematic analysis framework for the stated evaluation questions. Ask for the material and question if neither is given.
Separate a proposed codebook from completed analysis. Start with a source inventory, unit of coding, consent or quote limits, and analytic stance. From questions and any theory of change, propose a modest deductive codebook with code ID, definition, inclusion and exclusion rule, and boundary example; add inductive codes from actual text during familiarization. Do not invent participant quotes or force 15 to 20 codes. Show a documented process for reading, first-cycle coding, memoing, revising codes, comparing cases, developing candidate themes, checking contradictory material, defining themes, and reporting with traceable excerpts. Provide a matrix template by case or respondent group only if metadata and privacy permit. Coding agreement statistics are optional and require multiple coders, a stable codebook, and a suitable coding approach; never impose a universal kappa threshold. Do not claim saturation from a predetermined count. Include reflexivity, versioning, access controls, and how quantitative findings may be integrated when supplied. If only a description exists, return a draft codebook and analysis protocol, not results.