Build a codebook another person can follow.
Define the boundary of each code, add an example, and check the structure before coding drifts.
The check finds missing definitions, examples, near-duplicate names, and overlapping wording. It does not read your data or decide whether the codes are analytically right. Nothing is uploaded.
No account · no upload · nothing leaves your browser. Export saves a file to your device.
What makes a code usable
A name is not enough. Define what the code means, when it applies, when it does not, and show at least one example from the data. A near-miss is often the fastest way to make the boundary clear.
This checks structure only. It cannot tell whether a code fits the transcripts or whether the themes are analytically convincing. Those judgments remain with the research team.
New to the method? Read deductive, inductive, and abductive reasoning or build a qualitative codebook in Obsidian.
From codebook to methods record
The Sample Defence Pack keeps the codebook alongside sampling, stopping, and reporting decisions, so the method can be reviewed as one argument.
See the Sample Defence Pack · €49 Check findings wording