Do THIS before you import Anything to NVIVO - so that it doesn't crash
Based on Qualitative Researcher Dr Kriukow's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Remove any Microsoft Word table formatting from transcripts before importing into NVivo, especially when time stamps are stored in table columns.
Briefing
NVivo projects can crash when transcripts are imported with table-based formatting—especially when time stamps and speaker text are stored in Microsoft Word tables. The practical fix is to remove tables before import, because NVivo struggles to handle them during coding and can end up loading the entire transcript table for each coded quote, slowing work to a crawl and eventually breaking the project.
Before getting to that “project-breaker,” the transcript preparation checklist is mostly about reducing friction during long coding sessions. Since qualitative analysis often means spending dozens of hours reading, coding, and revisiting text, the file should be optimized for visual comfort and consistency. That starts with tidying up transcripts: correcting spelling errors, filling gaps, and standardizing formatting that commonly appears when transcripts come from outsourcing, automatic transcription tools, or copy-paste across multiple audio files. Consistency matters for fonts, colors, and general layout—small inconsistencies add up when someone is repeatedly scanning lines for meaning.
Readability is treated as a core workflow issue. The guidance emphasizes using a reasonably large, consistent font (roughly 11–13 rather than tiny sizes), avoiding distracting novelty fonts, and—most importantly—setting generous spacing between lines. Tight line spacing makes coding more exhausting because it forces closer, slower reading of every line. The same logic applies to paragraph structure: extra whitespace is preferred over cramped text. Distinct paragraphs, clear separation between speaker turns, and clean formatting help the eyes track where one idea ends and the next begins.
Heading styles in Microsoft Word are recommended both for clarity and for compatibility with NVivo’s Auto coding feature. Auto coding isn’t “automatic analysis”; it’s a formatting-driven tool that can separate questions and answers (or distinguish speakers in focus group transcripts) when the transcript uses consistent paragraph styles. For Auto coding to work as intended, questions and answers must be placed in different heading styles, and focus group speaker contributions should follow a consistent structure.
Time stamps are addressed with a pragmatic rule: they’re usually unnecessary unless a method specifically requires knowing when something was said (for example, discourse analysis). Many transcription tools insert time stamps by default, and they can typically be imported without harm. The real danger appears when time stamps are embedded inside tables—turning a transcript into a table layout that NVivo handles poorly.
The bottom line is straightforward: clean and standardize transcripts for comfort, use Word styles to support any NVivo Auto coding workflow, and—crucially—remove table formatting (especially time-stamp tables) before import to avoid severe performance problems and crashes.
Cornell Notes
The transcript’s central warning is that NVivo can crash or become unusably slow when transcripts are imported with table formatting, particularly when time stamps and text are stored in Microsoft Word tables. NVivo struggles to interpret coded content inside tables, often forcing it to load the entire table for each coded quote, which can eventually break the project.
To prevent day-to-day fatigue and errors, the guidance recommends tidying transcripts (spelling, missing text, inconsistent formatting) and standardizing readability: consistent font, larger font sizes, and especially comfortable line spacing (about 1.5–2). It also recommends using Word heading styles to keep speaker names, questions, and answers clearly separated—particularly if Auto coding is planned.
Time stamps are usually optional unless the research method requires them; default time stamps from transcription tools are generally fine unless they’re embedded in tables.
Why does table formatting in a transcript create such a serious problem in NVivo?
What “readability” settings are recommended before importing transcripts?
What should be done to transcripts that come from outsourcing or automatic transcription tools?
How do Microsoft Word heading styles relate to NVivo Auto coding?
When are time stamps worth worrying about, and when are they usually fine?
Review Questions
- What specific transcript formatting choice is most likely to cause NVivo to crash, and why?
- How do line spacing and paragraph spacing affect the coding workflow described in the transcript?
- What formatting requirements must be met in Microsoft Word if you plan to use NVivo Auto coding?
Key Points
- 1
Remove any Microsoft Word table formatting from transcripts before importing into NVivo, especially when time stamps are stored in table columns.
- 2
Standardize transcript formatting (font, spacing, and layout) to avoid inconsistencies caused by outsourcing, automatic transcription, or copy-paste across files.
- 3
Use a consistent, readable font size (around 11–13) and avoid tiny or distracting fonts to reduce fatigue during long coding sessions.
- 4
Set comfortable line spacing (about 1.5–2) because tight spacing increases exhaustion when coding line-by-line.
- 5
Prefer clear paragraph structure and extra whitespace over cramped text; distinct paragraphs make the transcript easier to scan.
- 6
If using NVivo Auto coding, apply Microsoft Word heading styles so questions and answers (and/or speaker turns) sit in separate, consistent paragraph styles.
- 7
Treat time stamps as optional unless the research method requires timing; keep them only if they are not embedded in tables.