Introduction
Reflexive thematic analysis (RTA) does not use a codebook. Coding develops through deep engagement with the data, and themes are constructed through interpretive work rather than applied from a predefined framework .
By contrast, many qualitative projects require structured, systematic coding. When research involves team-based analysis, predefined analytic domains, large datasets, or the need for cross-case comparison, a codebook-led approach is often the appropriate design choice.
If your analysis depends on applying a defined set of codes consistently across participants, you are working within a codebook-led analytic approach.
This post explains:
- What a codebook actually is,
- The main qualitative approaches that use them,
- How to construct one,
- How to manage it rigorously,
- And how to write it up clearly.
1. What Is a Codebook?
A codebook is a structured analytic document that:
- Lists codes (and sometimes categories or themes),
- Defines each code,
- Clarifies inclusion and exclusion criteria,
- Provides examples,
- And guides consistent coding across a dataset.
Within thematic analysis, Braun and Clarke (2021, 2022) describe codebook thematic analysis as a cluster of structured approaches that includes:
- Framework Analysis
- Template Analysis
- Thematic Network Analysis
- Matrix analysis
Codebook TA shares a structured logic with coding reliability approaches: a detailed coding framework is developed to specify what should be coded and how. Codes are typically generated early in the analytic process — often informed by research questions, data collection tools, and initial familiarisation with the data. These codes are then systematically applied across the dataset.
In this approach, coding involves allocating segments of data to predefined codes or categories. Themes are often scaffolded early and may function as topic summaries that organise the analysis.
Codebook TA sits between coding reliability and reflexive thematic analysis . Like coding reliability, it uses structured coding and early theme development. However, the purpose differs. In coding reliability approaches, the codebook functions to measure consistency or accuracy of coding. In codebook TA, the framework functions to organise, chart, and map the analysis.
Unlike reflexive TA — where themes are constructed through ongoing interpretive engagement and no codebook directs analysis — codebook TA uses a structured framework to guide coding from an early stage .
A codebook, then, is not simply a list of labels. It is a formal analytic framework that structures how data are categorised, compared, and organised across a study.
2. Four Common Codebook Approaches in Thematic Analysis
Let’s look at these four approaches in more detail.
1️⃣ Framework Analysis
Originally developed for applied policy research, Framework Analysis involves:
- Developing a thematic framework,
- Indexing data according to that framework,
- Charting data into matrices,
- Comparing across cases and themes .
It is particularly suited to:
- Health research,
- Evaluation studies,
- Policy-driven projects,
- Team-based research.
The framework structures the analysis from early in the process.
2️⃣ Template Analysis
Template Analysis uses a hierarchical coding template that can incorporate:
- A priori themes,
- Data-driven codes,
- Iterative refinement .
The template evolves during analysis but still functions as a structured guide.
It is flexible but not fully open-ended in the way reflexive TA is.
3️⃣ Matrix Analysis
Matrix approaches organise coded data into case-by-theme tables to support systematic comparison .
Matrices:
- Make cross-case comparison visible,
- Support transparency,
- Help manage large datasets,
- Aid team coordination.
They are analytic tools, not merely presentation devices .
4️⃣ Thematic Network Analysis
Thematic Networks structure data into:
- Basic themes,
- Organising themes,
- Global themes .
This hierarchical mapping supports conceptual organisation while retaining structure.
3. When a Codebook Approach Makes Sense
A codebook approach is typically appropriate when:
- Your research has predefined information needs.
- You are working within applied or evaluation contexts.
- You need structured comparison across participants.
- You are analysing large datasets.
- Multiple researchers are coding data.
- Transparency and auditability are priorities.
It is less appropriate when:
- The methodology requires fully emergent, evolving coding (e.g. reflexive TA ).
- The analysis prioritises idiographic depth (e.g. IPA).
- The focus is discursive or narrative rather than categorical.
The decision should always be driven by the research question and project design, not personal preference.
4. How Codebooks Are Developed
Codebooks are constructed, not imported.
They typically develop from:
- Research questions,
- Theoretical frameworks,
- Policy or stakeholder priorities,
- Early familiarisation with data,
- Pilot coding,
- Team discussion.
In applied research, they often combine deductive and inductive elements.
Good codebook development is deliberate and documented.
At minimum, a codebook should:
- Define each code precisely enough that another researcher could apply it consistently.
- State clear inclusion and exclusion criteria to prevent overlap and ambiguity.
- Include illustrative data extracts.
- Clarify how codes relate hierarchically (e.g. parent and sub-codes).
- Maintain a revision log that records when and why codes were added, merged, or redefined.
Without this level of clarity, structured coding risks becoming inconsistent or opaque; particularly in team-based research.
In the codebook tradition of thematic analysis — as distinct from coding reliability approaches — the codebook functions to organise and map analysis, not to measure coding “accuracy.”
Unlike coding reliability approaches, where the codebook is intended to remain stable so consistency can be assessed, codebook TA allows the framework to evolve. As researchers work more deeply with the data, codes may be refined, merged, expanded, or reorganised. This evolution reflects analytic development rather than inconsistency.
Structured does not mean fixed. In codebook TA, structure provides organisation, while revision reflects ongoing analytic judgement.
5. Writing Up a Codebook Approach
When reporting a codebook-led analysis, clarity begins with naming the specific approach you have used (e.g., Framework Analysis, Template Analysis, Thematic Network Analysis) .
However, the approach should not be chosen retrospectively to fit what you have done. It should reflect the analytic structure you actually implemented.
How to Decide Which Approach You Used
Ask yourself:
🔹 Did you develop a structured framework early and chart data into matrices for cross-case comparison?
→ You are likely working within Framework Analysis.
🔹 Did you construct and iteratively refine a hierarchical coding template?
→ You are likely using Template Analysis.
🔹 Did you organise coded data primarily through case-by-theme matrices to support systematic comparison?
→ You are drawing on Matrix Analysis.
🔹 Did you structure your findings into basic, organising, and global themes?
→ You are using Thematic Network Analysis.
The name should reflect the analytic architecture of your study, not simply the fact that you used codes.
What to Include in the Methods Section
When writing up a codebook approach:
- Name the specific approach.
- Explain why it suited your research question and project design.
- Describe how the codebook or framework was developed.
- Clarify whether codes were derived deductively, inductively, or both.
- Explain how the framework evolved.
- Describe how coding was conducted (individual or team-based).
- Demonstrate how analysis moved beyond categorisation into interpretation.
Avoid vague statements such as:
“We conducted thematic analysis using a coding framework.”
Be specific about the analytic structure.
Precision strengthens credibility.
Closing Reflection
A codebook is not a compromise. It is a deliberate analytic choice suited to particular research designs.
Reflexive thematic analysis does not use a codebook.
But many qualitative approaches do — appropriately and rigorously.
The key question is not whether a codebook is “better” or “worse.”
The key question is:
Does this analytic structure align with my research question, aims, and project conditions?
When chosen deliberately and managed carefully, a codebook can support clarity, comparability, and transparency in qualitative research.
References
Attride-Stirling, J. (2001). Thematic networks: an analytic tool for qualitative research. Qualitative Research, 1(3), 385-405.
Braun, V., & Clarke, V. (2022). Conceptual and design thinking for thematic analysis. Qualitative Psychology, 9(1), 3–26.
Brooks J, McCluskey S, Turley E, King N. The Utility of Template Analysis in Qualitative Psychology Research. Qual Res Psychol. 2015 Apr 3;12(2):202-222.
Nadin, S., & Cassell, C. (2004). Using data matrices. In C. Cassell, G. Symon (Eds.) Using data matrices (pp. 271-287). SAGE Publications Ltd
Ritchie, J. and Spencer, L. (1994) Qualitative Data Analysis for Applied Policy Research. In: Bryman, A. and Burgess, R., Eds., Anal. Qual. Data, Routledge, London, 173-194.
