Draft a Qualitative Coding Frame

You are an expert qualitative analyst with experience building and applying codebooks across thematic, framework, and grounded-theory approaches. Draft a qualitative coding frame for your study and target population, working from the qualitative data sources you will be coding. Your codebook must adhere to the following requirements: 1. **Code definition clarity.** For each code, write a precise definition such that two independent coders applying it to the same passage would agree. Include inclusion rules (what the code covers) and exclusion rules (what the code does not cover, especially against near-miss codes). Use operational language, not theoretical jargon alone. 2. **Hierarchy structure.** Organize codes in a parent-child hierarchy where it adds value. Codes at the same level should not overlap in meaning (mutually exclusive at each level). Set depth appropriate to the data volume. 3. **Exemplar coverage.** For each code, include at least one anchor example that the code applies to and one near-miss example that it does not, with a one-sentence explanation of the boundary. 4. **Inductive-deductive balance.** Mark which codes are pre-specified from the evaluation questions or theoretical framework and which are reserved for emergent codes from the data. Build in a clear process for adding emergent codes during analysis. 5. **Reliability plan.** Include a reliability check plan: what share of transcripts will be double-coded, which agreement metric will be used (Cohen's kappa, percent agreement, Krippendorff's alpha), what threshold counts as acceptable, and how disagreements will be reconciled. **Output Format:** Produce: 1. A short framing paragraph stating the evaluation questions the codebook supports and the analytic approach (thematic, framework, grounded theory). 2. A code table with columns: code ID, parent code, code name, definition, inclusion rules, exclusion rules, positive example, near-miss example, deductive/inductive flag. 3. An emergent-code protocol (one paragraph). 4. A reliability check plan (one short section with the parameters above). 5. A note on software (e.g., NVivo, Dedoose, Atlas.ti, MAXQDA, Excel) and how codes will be exported and version-controlled.