WHY ENGLISH?
NVivo can organise thousands of passages, but the quality of the analysis still depends on how clearly the researcher defines a code, distinguishes a case and explains an inference.
This guide helps students, parents and early researchers turn NVivo features into a transparent qualitative-analysis workflow rather than a collection of colourful outputs.
NVivo is qualitative data-analysis software for organising, coding, annotating, querying and visualising material such as interviews, documents, surveys, images and media. People searching for an NVivo tutorial, qualitative coding, thematic analysis software or matrix coding query often want the fastest route to a word cloud. The practical value of English appears earlier: deciding what a code means, which person or place counts as a case and what question a query actually asks.
Software can retrieve every passage assigned to a label. It cannot decide by itself whether the label is conceptually coherent, whether an interview was interpreted fairly or whether a frequent word matters. Codes represent topics or analytical ideas; cases represent units of analysis such as people, organisations or locations. Memos retain the development of reasoning. Queries explore patterns, but results must return to the underlying context.
The official NVivo 15 Windows getting-started guidance, checked on 5 November 2026, describes a back-and-forth workflow of importing, coding, note-taking, querying and visualising. The official key-concepts guide distinguishes codes from cases. This article uses the current Windows documentation while acknowledging that interfaces and features can differ across versions and platforms.
Start With a Research Question and Analysis Plan
A new NVivo project should begin with the phenomenon, units of analysis and evidence needed to answer the question.
The plan names data sources, coding approach, comparison dimensions and decision points. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Start With a Research Question and Analysis Plan
A project asks how students experience useful feedback and plans interviews, school cases and reflexive memos. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Opening menus before defining the question encourages tool-led analysis.
Audit move: Start With a Research Question and Analysis Plan
Write the question and planned analytical products on the project front page. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Define the Project Boundary
A project boundary states which data, period, population and purpose belong.
Clear scope keeps unrelated files and attractive side questions from quietly changing the study. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Define the Project Boundary
Only interviews from the current transition study enter the main analysis; pilot interviews remain labelled separately. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
A large project is not automatically a coherent project.
Audit move: Define the Project Boundary
Record inclusion, exclusion and version rules. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Import Data With Provenance
Every imported file should retain source, date, version, consent status and transformation history.
A transcript is not merely text; it is a research object linked to recording and participant context. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Import Data With Provenance
The team names transcripts by participant ID and logs transcription and correction dates. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Renaming or cleaning without a log can detach quotations from their source.
Audit move: Import Data With Provenance
Keep a data register outside and inside the project. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Check Transcripts Before Coding
Coding unreliable transcripts produces precise organisation of wrong text.
Compare a sample with audio, mark inaudible sections and distinguish speaker turns. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Check Transcripts Before Coding
A key phrase is corrected after audio review before it becomes an in-vivo code. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Automated transcription errors can cluster around accents and technical terms.
Audit move: Check Transcripts Before Coding
Record who checked each transcript and how uncertainty is marked. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Separate Codes From Cases
Official NVivo guidance says codes represent topics or analytical ideas while cases represent units of analysis.
The distinction allows a theme to be compared across people, places or organisations. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Separate Codes From Cases
Feedback anxiety is a code; Student P07 is a case. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Coding a person’s name as a topic can break later comparisons.
Audit move: Separate Codes From Cases
Write one sentence defining every case type and code family. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Use Descriptive Codes for What Is Said
Descriptive codes identify topics, activities or events close to the data.
They support retrieval before deeper interpretation. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Use Descriptive Codes for What Is Said
Passages about waiting for comments receive a timing code even when participants disagree about its meaning. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Descriptive coding can become an endless index if not connected to the question.
Audit move: Use Descriptive Codes for What Is Said
Review whether each code helps retrieval or analysis. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Use Analytical Codes for Why It Matters
Analytical codes express an interpretation or mechanism rather than only a subject.
Their descriptions need evidence, boundaries and revision history. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Use Analytical Codes for Why It Matters
Several passages are coded feedback as social risk because judgement affects whether students ask for help. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
An elegant phrase can outrun the data.
Audit move: Use Analytical Codes for Why It Matters
Link analytical codes to supporting and contradictory passages. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Use In-Vivo Codes Carefully
NVivo can create a code from selected participant language.
In-vivo codes preserve emic wording and can reveal concepts researchers did not anticipate. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Use In-Vivo Codes Carefully
The phrase saving face becomes a temporary code and is later examined across cases. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
A memorable phrase may belong to one speaker and should not be universalised.
Audit move: Use In-Vivo Codes Carefully
Retain speaker context and decide whether the phrase remains a code or evidence. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Write Code Descriptions and Boundaries
A useful codebook explains what belongs, what does not and how overlapping cases are handled.
Definitions keep collaborators from using the same label for different ideas. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Write Code Descriptions and Boundaries
The code delayed feedback includes time-related usability but excludes general dislike without timing. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Code names alone invite drift.
Audit move: Write Code Descriptions and Boundaries
Add inclusion, exclusion and example text to important codes. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Build a Hierarchy Only When It Helps
Parent and child codes can organise related ideas, but hierarchy should represent a reasoned relationship.
Some projects work better with flatter structures and later synthesis. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Build a Hierarchy Only When It Helps
Access barriers contains time, technology and language subcodes because they answer one analytical question. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Deep trees can hide duplication and make coding inconsistent.
Audit move: Build a Hierarchy Only When It Helps
Explain what the parent-child relation means. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Keep Overlapping Coding When Meaning Overlaps
One passage may legitimately support several analytical ideas.
Qualitative meaning is not forced into mutually exclusive bins unless the method requires it. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Keep Overlapping Coding When Meaning Overlaps
A comment about late feedback and fear of embarrassment receives timing and social-risk codes. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Multiple coding can inflate counts if interpreted as independent evidence.
Audit move: Keep Overlapping Coding When Meaning Overlaps
Return to passages before comparing frequencies. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Create Cases as Units of Analysis
Cases may be people, organisations, locations or other entities relevant to comparison.
Official guidance calls them units of analysis or observation. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Create Cases as Units of Analysis
Each student interview is coded to a student case, while each school can also be represented as an organisational case. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Cases should not be created merely because the software permits them.
Audit move: Create Cases as Units of Analysis
Define the unit and its relationship to files. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Use Case Classifications and Attributes
Classifications store descriptive attributes for cases so patterns can be compared.
Age, role or site should use consistent values and ethically appropriate detail. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Use Case Classifications and Attributes
Student cases receive school level and programme attributes without names. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Small combinations can re-identify participants.
Audit move: Use Case Classifications and Attributes
Minimise attributes and document value definitions. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Use File Classifications for Source Context
File classifications store descriptive or bibliographic information about sources.
They help distinguish interviews, focus groups, policies and articles in queries. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Use File Classifications for Source Context
A document source records organisation, year and document type. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
File metadata does not replace reading the file.
Audit move: Use File Classifications for Source Context
Check imported attributes against authoritative records. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Write Analytical Memos Throughout
NVivo’s official guidance describes memos as documents that can tell the story of a project’s ideas and findings.
Analytical memos capture emerging interpretations, evidence and alternatives. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Write Analytical Memos Throughout
A memo explains why two descriptive codes may form one theme and cites contrary cases. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Writing memos only at the end creates a retrospective story.
Audit move: Write Analytical Memos Throughout
Date memos and link them to codes or cases. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Keep Procedural Memos Separate
Procedural memos document methodological decisions, software steps and changes.
Separating them from analytical claims makes the audit trail clearer. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Keep Procedural Memos Separate
A memo records why a code was split after calibration and which files were recoded. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
A technical note cannot justify an interpretation by itself.
Audit move: Keep Procedural Memos Separate
Use distinct memo prefixes and purposes. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Use Annotations for Local Notes
Official NVivo guidance says annotations attach notes to selected content.
They suit transcription issues, follow-up questions or local context that should remain beside a passage. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Use Annotations for Local Notes
An annotation marks uncertain speaker identity without turning it into a theme. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Annotations are not coded in the same way as source content.
Audit move: Use Annotations for Local Notes
Use them for local reminders and promote major ideas to memos. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Use See-Also Links to Preserve Connections
See-also links connect a selected passage with another project item or passage.
They can retain relationships that a shared code would oversimplify. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Use See-Also Links to Preserve Connections
A participant’s statement links to a policy clause that shaped the experience. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
A web of links becomes unusable without a clear purpose.
Audit move: Use See-Also Links to Preserve Connections
Name the relationship in a memo or log. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Calibrate Collaborative Coding
Teams need a shared interpretation of code definitions before dividing the dataset.
Independent practice, discussion and codebook revision can reveal ambiguity. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Calibrate Collaborative Coding
Two coders compare the same three transcripts and revise the boundary between confusion and disagreement. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Agreement statistics cannot prove conceptual validity.
Audit move: Calibrate Collaborative Coding
Save disagreements and the reasoning that resolved them. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Use Coding Comparison as a Diagnostic
Coding comparison can show where collaborators applied codes differently.
The result should lead back to passages and definitions. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Use Coding Comparison as a Diagnostic
Low agreement for social risk reveals that one coder included general anxiety and the other required peer judgement. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
High agreement can reflect a shared narrow mistake.
Audit move: Use Coding Comparison as a Diagnostic
Review both matched and mismatched examples. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Run Text Search as Discovery
Text search can locate words or phrases across selected data.
Search terms, stemming and scope determine what is found. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Run Text Search as Discovery
The team searches feedback and comments but also reads context where the words mean different things. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Words absent from transcripts can still be represented through synonyms or implicit meaning.
Audit move: Run Text Search as Discovery
Treat hits as candidates for reading, not themes. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Use Word Frequency With Context
Official guidance says word-frequency queries list common words and can support early theme discovery.
Stop words, stems, language and source scope affect counts. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Use Word Frequency With Context
The word late is common, but the researcher reads passages before linking it to timing. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Frequency is not importance, sentiment or causation.
Audit move: Use Word Frequency With Context
Save query settings and inspect concordance context. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Remember Scanned PDFs May Be Images
NVivo’s word-frequency guidance notes that image-only scanned PDFs are not searched as text without OCR.
File appearance can therefore hide a retrieval limit. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Remember Scanned PDFs May Be Images
A scanned policy is OCR-checked before text queries are run. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
OCR introduces its own errors, especially in tables and poor scans.
Audit move: Remember Scanned PDFs May Be Images
Record OCR method and verify important quotations. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Use Coding Queries to Test Retrieval Questions
Coding queries gather material based on codes, cases and attributes.
The verbal question should be written before the query is configured. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Use Coding Queries to Test Retrieval Questions
The researcher asks for social-risk passages among lower-secondary cases rather than clicking filters until a pattern appears. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Query logic can exclude relevant material silently.
Audit move: Use Coding Queries to Test Retrieval Questions
Save the question, scope and operators. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Use Matrix Coding for Comparisons
Matrix coding queries display intersections between row and column criteria.
Official guidance says each cell represents content coded to the intersection. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Use Matrix Coding for Comparisons
Rows contain feedback themes and columns contain school-level cases, allowing passage-level comparison. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Cell counts are not automatically prevalence rates and may reflect coding density.
Audit move: Use Matrix Coding for Comparisons
Open cells and read the contributing content. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Distinguish Co-Occurrence From Connection
Two codes in the same passage or case may co-occur without one causing the other.
Window, unit and coding practices shape the result. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Distinguish Co-Occurrence From Connection
Timing and anxiety often overlap, prompting a memo about possible mechanism rather than a causal claim. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Frequent co-occurrence can reflect broad codes.
Audit move: Distinguish Co-Occurrence From Connection
Check definitions and negative cases. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Use Visualisations as Questions
Charts, maps and word clouds can reveal patterns worth investigating.
They compress project structure and should link back to data. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Use Visualisations as Questions
A chart suggests one theme appears more in focus groups, so the researcher checks file numbers and passages. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Colour and size create rhetorical emphasis that may exceed evidence.
Audit move: Use Visualisations as Questions
Caption every visual with scope, unit and limitation. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Preserve Negative and Deviant Cases
Cases that contradict an emerging pattern help refine analysis.
Code or memo them visibly instead of forcing them into the dominant theme. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Preserve Negative and Deviant Cases
Two students welcome public feedback while most avoid it, revealing a condition about group trust. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
A deviant case is not a nuisance or automatic refutation.
Audit move: Preserve Negative and Deviant Cases
Explain how it changed the theme boundary. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Move From Codes to Themes Transparently
Themes require an organising idea that answers the research question.
Memos, code maps and passage comparison should show how codes were combined or separated. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Move From Codes to Themes Transparently
Timing, access and social risk become a theme about feedback usability only after their relationships are evidenced. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Renaming a parent code as a theme is not enough.
Audit move: Move From Codes to Themes Transparently
Write the theme claim, evidence, exclusions and alternatives. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Use Counts Without Pretending They Are Survey Estimates
NVivo can count files, references and coded passages.
These counts describe the project and coding, not population prevalence unless the design supports that inference. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Use Counts Without Pretending They Are Survey Estimates
A theme appears in 18 of 24 interviews, reported as sample context rather than a national percentage. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
One participant can generate many passages.
Audit move: Use Counts Without Pretending They Are Survey Estimates
Choose the unit of counting and state it. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Protect Participant Privacy
Qualitative projects often contain identifiable stories, audio, locations and sensitive attributes.
Access control, pseudonyms, minimisation and secure exports belong in the analysis plan. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Protect Participant Privacy
A shared project removes direct identifiers and restricts raw audio. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Removing names may not prevent identification in a small setting.
Audit move: Protect Participant Privacy
Audit quotations and attribute combinations before sharing. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Version the Project and Codebook
Qualitative analysis evolves, so major changes need recoverable checkpoints.
Project copies, codebook versions and change memos preserve decision history. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Version the Project and Codebook
Before merging codes, the team saves a dated version and records the rationale. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Uncontrolled copies create competing truths.
Audit move: Version the Project and Codebook
Name the canonical file and archive milestones. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Report the Method, Not the Brand
A research report should explain sampling, data generation, coding, reflexivity and analysis rather than saying only NVivo was used.
Software supports but does not constitute a methodology. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Report the Method, Not the Brand
The methods describe reflexive thematic analysis and how NVivo organised passages and memos. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Brand names can create false authority.
Audit move: Report the Method, Not the Brand
Write the analytic logic independently of menu steps. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
A Parent and Student Coding Routine
Students can learn qualitative reasoning with a small, non-sensitive text set.
They define two codes, code passages, write one memo and test a contrasting case. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: A Parent and Student Coding Routine
A parent asks why a passage fits the code and what would not fit. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
The exercise should not use private peer disclosures without consent.
Audit move: A Parent and Student Coding Routine
Reward definitions and evidence, not the number of codes. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Transfer NVivo Habits to Education and Work
Clear coding, case definitions and decision memos improve user research, interviews and document review.
Teams should preserve context and alternative explanations even when software differs. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Transfer NVivo Habits to Education and Work
A workplace review links customer themes to cases and retains dissenting accounts. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
Tool skill is not a licence to overclaim.
Audit move: Transfer NVivo Habits to Education and Work
Transfer the audit trail and evidence habit. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Finish With a Data-to-Theme Audit
A final audit traces each theme through codes, passages, cases, memos, queries and contrary evidence.
It also verifies privacy, versions and wording strength. English does analytical work here: names define the object, descriptions preserve inclusion boundaries, memos retain reasoning and queries turn a verbal question into an inspectable operation.
Project example: Finish With a Data-to-Theme Audit
A second researcher can open the project and reconstruct why a theme exists. The researcher returns from the result to the underlying passages before making a theme or comparison claim.
A beautiful model is not enough if the path to data is broken.
Audit move: Finish With a Data-to-Theme Audit
Audit the strongest claim and the weakest-supported claim first. Save the decision in a dated memo or project log so a collaborator can see how the interpretation developed rather than only the final colourful display.
Frequently Asked Questions
What is the difference between a code and a case in NVivo?
Codes represent topics or analytical ideas; cases represent units of analysis such as people, organisations or locations.
Does NVivo do thematic analysis automatically?
It can organise and query material, but researchers remain responsible for definitions, interpretation, reflexivity and theme development.
What is an in-vivo code?
It is a code created from selected participant language, useful for preserving an emic phrase while retaining context.
What are memos for?
Memos record analytical ideas, procedural decisions and the development of reasoning across the project.
How are annotations different from memos?
Annotations attach a local note to selected content; memos are fuller project documents that can develop an analysis.
Does word frequency show the most important theme?
No. Frequency depends on language, scope and settings and does not establish meaning or importance.
What does a matrix-coding cell mean?
It contains material coded to the intersection of the row and column criteria; counts require careful interpretation.
Can code counts be reported?
Yes, with a clear unit and design-aware caveat; passage counts are not automatically population prevalence.
Can students use NVivo?
Yes for appropriately scoped, ethical projects with explicit code definitions and supervision.
What is the final quality check?
Trace every theme back to source passages, cases, code definitions, memos, query settings and contradictory evidence.
Useful Next Reading
- Official NVivo 15 getting-started tutorials — verify the current workflow.
- NVivo key concepts — distinguish codes, cases and classifications.
- NVivo guidance on memos and annotations — preserve the analytical trail.
- Use the CASP qualitative checklist — appraise a completed qualitative study without competing with this analysis-workflow owner.
Closing thought: NVivo becomes educationally valuable when every code has a boundary, every case has a meaning, every query has a question and every theme can find its way home to the data.