Methodology Guide
Template Analysis
Nigel King's iterative, hierarchical approach to qualitative coding — and how QualIntel OS supports structured template development and evolution.
What is Template Analysis?
Template Analysis was developed by Nigel King (King, 2012; King, Brooks & Weir, 2019). It involves creating an initial template — a hierarchical set of codes — derived partly from prior literature and research questions (a priori codes) and partly from an initial reading of data. The template is then applied to the full dataset and iteratively refined as analysis proceeds.
Template Analysis occupies a middle ground between more rigid, deductive approaches and fully inductive, emergent approaches. Codes can be a priori (defined before analysis) or emergent (arising from the data). The hierarchical structure supports complex, nuanced analysis across multiple levels of abstraction. It is commonly used in organisational, health, and applied social research.
Commonly used in: Organisational research, health psychology, clinical research, applied social research, management studies
Why rigour documentation matters
Template Analysis requires clear documentation of the initial template (what a priori codes were used and why), how it evolved during analysis (what codes were added, moved, or removed and the rationale), and the final template structure. Examiners expect to see this evolution documented — it demonstrates rigorous engagement with data rather than simply applying predetermined categories without revision.
How QualIntel OS supports Template Analysis
- Initial template built as the codebook at project setup — a priori codes extracted from your research design, immediately reviewable and editable before evidence review begins
- Full codebook evolution log: every code addition, rename, restructure, merge, or deletion is timestamped — documenting how the template evolved during analysis
- Hierarchical codebook structure directly mirrors Template Analysis's nested code structure, with parent and child codes at multiple levels
- Iterative evidence review cycle supports template refinement — evidence review informs codebook adjustments in a natural loop
- A priori vs emergent code distinction supported in the synthesis editor and exportable in the codebook
- Submission export includes complete codebook with version history, supporting a clear account of template evolution in your methods chapter
Frequently asked questions
What is Template Analysis?
Template Analysis (King, 2012; King et al., 2019) is a qualitative methodology that involves creating a hierarchical template of codes — some defined a priori from literature and research questions, others emerging from the data — and iteratively refining it throughout analysis. It offers structured, systematic coding with flexibility for emergent findings. It is commonly used in organisational, health, and applied social research.
How does QualIntel OS help with iterative template refinement?
The codebook editor supports iterative refinement at every stage. You can add codes, restructure the hierarchy, merge codes, or delete codes as your template evolves. Every change is logged with a timestamp. When you return to evidence review after modifying the template, QualIntel OS can surface candidate evidence for newly added codes. The full codebook evolution history is included in your submission export.
What is the difference between Template Analysis and Reflexive Thematic Analysis?
Reflexive Thematic Analysis (Braun & Clarke) is more interpretivist — themes are fluid researcher constructions, the methodology is epistemologically flexible, and researcher reflexivity is central. Template Analysis is more structured: it uses a predefined hierarchical template with some a priori codes, applies it systematically, and documents how it evolved. Template Analysis suits research with clear theoretical or empirical starting points; RTA suits exploratory work where the researcher's interpretive lens is foregrounded.