Qualitative Coding Plan
Plan transparent coding of interviews or texts.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Plan qualitative coding. Data (interviews, open responses, documents) and sample size: [DATA_SAMPLE]. Research question: [RESEARCH_QUESTION]. Approach I am leaning towards (thematic, content, grounded): [APPROACH]. Tools: [TOOLS]. Outline the steps: familiarisation, initial coding, building a codebook, applying codes, reviewing themes, and writing up. Provide a codebook template with definition, inclusion and exclusion criteria, and an example quote (from my data when I supply it). Suggest a method for checking consistency, such as a second coder on a sample, and a way to document decisions in a memo log. Include guidance on reflexivity and on handling sensitive data securely. Mark ethics and data protection requirements as items to verify [VERIFY]. Do not invent data or quotes. Also add a short worked example codebook entry for an invented interview about commuting, labelled as an illustration, and a procedure for writing analytic memos after each interview to capture emerging ideas. Add a short section on quality: keeping an audit trail of decisions, checking interpretations with participants where appropriate, and presenting negative cases honestly in the findings.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.
See an example result (fictional data)
Codebook entry (invented, interviews about commuting) Code: Time pressure. Definition: statements about lack of time shaping travel choices. Include: 'I leave at 7 or I'm late.' Exclude: general complaints about traffic. Example quote: 'I choose the bus because it's predictable.' [from data when supplied] Memo after interview 3: Several participants link time pressure to childcare; consider a parent theme. Consistency: second coder codes 10 percent of transcripts; discuss differences. Audit trail: keep a dated log of codebook changes, such as merging 'Cost' and 'Money worries' into one code on 3 June, with the reason.
Illustrative only, made-up data. Your results will differ and must be reviewed.