| Tool | Maker | Cost (approximate, 2026) | Where it stands |
|---|---|---|---|
| Taguette | Rémi Rampin and contributors; open source | Free; runs locally or on a server; a hosted version at taguette.org | The simplest tool: highlight and tag text; exports everything. The right first tool and enough for many projects |
| QualCoder | Colin Curtain and contributors; open source, Python | Free; desktop | Full-featured: text, PDF, image, audio and video coding; attributes; queries; coder comparison; REFI-QDA export |
| NVivo | Lumivero (formerly QSR International) | Student licences roughly US$100 a year; institutional site licences common at Indian universities | The most widely taught; strong queries and matrices; transcription and AI add-ons |
| MAXQDA | VERBI Software, Berlin | Similar student pricing; educational licences | Strong on mixed methods and visual tools; a Stats module; team cloud |
| ATLAS.ti | ATLAS.ti Scientific Software Development, Berlin | Similar; a web version by subscription | Quotation-based; networks; the earliest AI coding features |
| Also: Dedoose, Quirkos, Delve | Various | Monthly subscriptions | Web-based, simpler; Dedoose is built for mixed-methods teams |
| Situation | Software worth it? | Why |
|---|---|---|
| Six key-informant interviews, one analyst, a report in three weeks | Marginal | A framework matrix in Word or a spreadsheet does it; the software's setup costs a day |
| Forty interviews, two languages, two coders, a thesis | Yes | Retrieval, consistency, merging and the audit trail; hand methods fail at this scale |
| Two hundred open-ended survey responses | Yes, a simple tool | Taguette or the spreadsheet route (section 09); coding is fast, counting is the point |
| Focus groups with audio, needing time-stamped coding of who said what | Yes, a fuller tool | QualCoder, NVivo, MAXQDA and ATLAS.ti code audio directly |
| A multi-year programme with recurring qualitative monitoring | Yes, with a shared codebook | The codebook and the project persist across rounds and staff |
| Documents and policy texts, hundreds of pages | Yes | Search, auto-coding by structure, and document attributes |
| Photographs and video from participatory work | Yes, a fuller tool | Region coding of images; video time-stamps |
| Idea | NVivo | MAXQDA | ATLAS.ti | QualCoder | Taguette |
|---|---|---|---|---|---|
| A source file | File (formerly Source) | Document | Document | File | Document |
| A coded passage | Reference / coded content | Coded segment | Quotation | Coded segment | Highlight |
| A code | Code (formerly Node) | Code | Code | Code | Tag |
| A code hierarchy | Code tree; parent and child codes | Code system | Code groups; folders | Code categories | Nested by naming |
| Respondent characteristics | Case classification attributes | Document variables | Document groups; attributes | Attributes | — |
| A note to yourself | Memo; annotation | Memo | Memo; comment | Memo; journal | — |
| Cases by codes table | Matrix coding query; framework matrix | Code matrix browser; crosstab | Code-document table | Coding matrix | Export and count |
| Co-occurrence | Matrix coding query (code × code) | Code relations browser | Code co-occurrence table | Code co-occurrence | — |
| Project exchange | REFI-QDA export/import | Same | Same | Same | CSV / DOCX export |
| Level | What is captured | Cost | Suits |
|---|---|---|---|
| Intelligent verbatim | Every word, with fillers and false starts removed | About 4–6 hours per hour of audio by hand; minutes by machine plus checking | Thematic and framework analysis; most applied work |
| Full verbatim | Every word, filler, repetition and pause | 6–8 hours per hour | Discourse and conversation analysis; where the how matters |
| Jefferson-style | Timing, overlap, intonation marked | 10+ hours per hour | Conversation analysis only |
| Summary or notes | Content summarised by the interviewer | Under an hour | Rapid appraisal; not for coding |
| Material | Format to import | Notes |
|---|---|---|
| Transcripts | .docx or .txt, UTF-8; one file per interview | Speaker labels on their own line ('I:' and 'R:', or names); a header block with ID, date, place, language; consistent formatting lets NVivo and MAXQDA auto-code speakers |
| Audio | .mp3, .wav, .m4a | QualCoder, NVivo, MAXQDA and ATLAS.ti code audio with time-stamps and can link a transcript to it; Taguette does not take audio |
| Video | .mp4 | Large files; compress first; region and time coding |
| PDFs (policy documents, reports) | Text-based PDF, not scanned | Scanned PDFs need OCR first (Bodhan's IndicOCR or Tesseract for Indic scripts); ATLAS.ti and MAXQDA code PDFs in place |
| Images, photographs | .jpg, .png | Region coding in QualCoder, NVivo, MAXQDA, ATLAS.ti |
| Survey open-ends | A spreadsheet: one row per respondent, one column per question, plus attribute columns | Import as a dataset (NVivo), a survey (MAXQDA), or a table of documents; each cell becomes codeable |
| Field notes, diaries | .docx, .txt | Date each entry; the researcher's own notes are data too |
| Social media, web pages | Exported text; NCapture (NVivo) or copy | Terms of service and ethics apply |
| Element | Convention | Why |
|---|---|---|
| Project file | One per study; named with the study and date; on encrypted storage; backed up daily to a second place | Project files corrupt and laptops are stolen |
| Source folders | By type and site: Interviews/Bihar, Interviews/Bengal, FGDs, Documents, Field notes | Attributes do the fine sorting; folders do the coarse |
| File names | TYPE_SITE_ID_LANG (INT_WB_022_BN) | Sortable; language visible; ID matches the master sheet and the survey |
| Attribute sheet | One spreadsheet, imported; the master list | Section 02 |
| Codebook | Started from the protocol's a priori codes, with definitions; versioned | Section 03 |
| Memos | A project memo (decisions, dated), a methods memo, a memo per emerging theme, and coding memos as needed | The audit trail; section 10 |
| Versions | Save-as with a date at each milestone; never overwrite the only copy | Recovery and the trail |
| Team | One master project; coders work on copies and merge (section 08), or use a server or cloud version | Merging is where projects break |
| Check | Done |
|---|---|
| Consent for recording, transcription, storage, quotation and external processing recorded per participant | |
| Recordings and transcripts on encrypted storage with a backup | |
| Transcription level chosen and stated; language and script decided | |
| Every machine transcript checked by a native speaker; the check recorded | |
| Translation workflow chosen (A, B or C) and stated; translators named | |
| Files named by convention; one file per interview or group | |
| Speaker labels consistent; focus-group speakers identifiable | |
| Pseudonymised; key stored separately | |
| Attribute sheet complete and imported; codes match the survey's | |
| Project folders, first memo and a priori codebook in place | |
| Project file backed up and versioned |
| Codebook field | Example |
|---|---|
| Name | FEAR_FORMAL_FINANCE |
| Definition | Anxiety, avoidance or distrust toward banks, officers, forms |
| Use when | Respondent describes her own or others' fear or avoidance |
| Do not use when | Worry about money in general (MONEY_WORRY); anger at a specific officer (BANK_MISTREATMENT) |
| Example | 'I never went inside; they would ask for papers I don't have' (INT_BR_014) |
| Source | A priori, from the theory of change; revised 2026-03-04 after five transcripts |
| Code | Definition (abridged) | Origin | Segments | Files |
|---|---|---|---|---|
| SAVINGS | Parent: any talk of saving money, in group or otherwise | A priori | — | 36 |
| SAVINGS_PURPOSE | What the money is for: emergencies, school, ceremonies, business | A priori | 94 | 34 |
| SAVINGS_SHIELD | Savings described as protected from household demands by being 'in the group' | Inductive, transcript 6 | 41 | 22 |
| SAVINGS_BARRIER | What prevents saving: income, husband, group rules, distance | A priori | 67 | 31 |
| DECISIONS | Parent: who decides what, and how that is negotiated | A priori | — | 36 |
| DECISION_SMALL | Daily purchases, food, children's small needs | A priori | 58 | 33 |
| DECISION_LARGE | Assets, loans, ceremonies, migration | A priori | 72 | 35 |
| DECISION_STRATEGY | How women get a say: timing, allies, group backing, withholding | Inductive, transcript 9 | 53 | 27 |
| FORMAL_FINANCE | Parent: banks, officers, forms, phones | A priori | — | 30 |
| FEAR_FORMAL_FINANCE | Anxiety, avoidance, distrust | A priori, redefined | 38 | 21 |
| IN_VIVO | Respondents' own phrases kept as codes | Inductive | 29 | 19 |
| Practice | Done |
|---|---|
| Method and coding approach stated in the first memo | |
| A priori codes defined from the protocol before coding | |
| Every transcript read once before coding | |
| First five transcripts coded closely; codebook revised; the five recoded | |
| Every code has a definition, use and do-not-use rules, and an example | |
| Codebook versioned with dates and reasons | |
| Segment size decided and consistent | |
| Memos written at decisions, patterns and surprises; dated; linked | |
| Inductive codes flagged and reviewed by a second person | |
| Second-cycle grouping done deliberately, with theme memos | |
| Saturation, if claimed, evidenced by the code-creation curve | |
| Auto-coding and text search used to find, never to code |
pip install taguette, then taguette, and the browser opens at a local address; data stays on the machine. Windows and Mac installers exist. The hosted service at app.taguette.org needs an account and stores your documents on its server, which the consent form must allow; a self-hosted server (the same software on an institution's machine) gives the collaboration without the storage question.| Export | Format | Use |
|---|---|---|
| Codebook | .csv, .docx, .xlsx, .html | The appendix table of tags and definitions; the codebook for a fuller tool |
| Highlights for one tag | .docx, .html, .csv | The evidence for a theme, ready to quote; a document to read through when writing |
| All highlights | .csv (document, tag, text) | A spreadsheet for counting tags by document, for the agreement check, and for pivot tables by attribute if you add the attribute columns by hand |
| A document with its highlights | .docx, .html | A marked-up transcript for a supervisor or a participant check |
| The whole project | .sqlite3 | The backup; reimportable into another Taguette |
| REFI-QDA | Not supported | Move to a fuller tool via the CSV export and re-code, or via QualCoder's import of the CSV as a starting point |
| Need | Taguette | Move to |
|---|---|---|
| Coding audio or video directly | No | QualCoder (free), or the commercial three |
| Attributes (district, arm) and matrices by them | By hand in the CSV export | QualCoder or the commercial three |
| Memos linked to segments and codes | Tag descriptions only | Any fuller tool |
| Co-occurrence and proximity queries | No | QualCoder (basic), commercial (full) |
| A real hierarchy with aggregation | Naming convention only | Any fuller tool |
| Inter-coder agreement statistics | By hand from the export | QualCoder, NVivo, MAXQDA, ATLAS.ti |
| Hundreds of documents | Slows; the flat tag list becomes unwieldy | Any fuller tool |
| REFI-QDA exchange | No | QualCoder and the commercial three |
| Session | Activity | Output |
|---|---|---|
| 1 | Install; import three anonymised transcripts; create six a priori tags from a supplied codebook; tag one transcript each | A tagged transcript; a first argument about a definition |
| 2 | Two students tag the same transcript with prefixed tags; export; compare in a spreadsheet; revise the codebook together | An agreement table; codebook version 2 |
| 3 | Tag the rest; export highlights by tag; write one theme memo with three quotations | A one-page theme memo |
| Tag | Description (abridged) | Highlights | Documents |
|---|---|---|---|
| SAVINGS.purpose | What the savings are for | 31 | 12 |
| SAVINGS.shield | Savings protected from household demands by being in the group | 14 | 8 |
| SAVINGS.barrier | What prevents saving | 22 | 11 |
| DECISION.large | Assets, loans, ceremonies | 24 | 12 |
| DECISION.strategy | How a say is obtained | 18 | 9 |
| FINANCE.fear | Fear or avoidance of banks | 13 | 7 |
| INVIVO | Respondents' phrases | 11 | 8 |
pip install qualcoder. Recent versions add optional LLM-assisted features that call an external model with an API key you supply; they are off by default and section 11 says what to think about before turning them on.| Menu or tab | What it does | Used for |
|---|---|---|
| Project | New, open, close; import survey; project memo; settings (coder name, fonts, backups) | Setup; set the coder name before coding |
| Manage → Files | Import text, PDF, images, AV; edit file memos; assign attributes; bulk import from a folder | Section 02's data in |
| Manage → Cases | Create cases (a participant across several files); attach files or portions; case attributes | A woman interviewed twice; a focus-group speaker |
| Manage → Attributes | Define attributes for files and cases; import from CSV | District, arm, language, interviewer |
| Coding → Code text / image / AV | The coding workspace: file on the left, code tree on the right, memos and annotations | Sections 03's work |
| Coding → Codebook | Export the code tree with memos | The appendix |
| Reports | Coding reports by code, file, case, attribute; code frequencies; coder comparison; code relations; co-occurrence matrix; text mining | Section 07 and 08 |
| Action log; Journals | The record of what was done; free-text journals | The audit trail and the memos |
| Report | What it gives | Section 07 or 08 equivalent |
|---|---|---|
| Coding report | Every segment for chosen codes, filtered by file, case or attribute value; exported to HTML, ODT, CSV | Retrieval: 'SHIELD among Bengal members' |
| Code frequencies | Counts of segments per code, by coder | The code-summary table |
| Code relations | Which codes overlap or are adjacent, with counts | Co-occurrence |
| Co-occurrence matrix | Code by code counts of overlapping segments | The co-occurrence table |
| Case and attribute reports | Codes by case; codes by attribute value | The matrix of cases by codes |
| Coder comparison | Agreement between two coders on selected codes and files: percentage agreement and Cohen's kappa | Section 08 |
| Text mining | Word frequencies with a stop list | Orientation only |
| Charts | Bar and pie charts of code counts, hierarchy sunbursts | Report figures, with care |
| Step | QualCoder | Result |
|---|---|---|
| Import | 36 source-language transcripts and 36 English translations; 12 audio files linked; attributes from CSV (state, member, language, migrant husband, interviewer) | Project of 72 files, 36 cases |
| Codebook | Version 3 imported as a tree with memos | 46 codes in 9 categories |
| Coding | Coder A (Hindi) and coder B (Bangla) on their language; each also codes four of the other's English translations for comparison | Coded in three weeks |
| Agreement | Coder comparison on the eight shared files, twelve key codes | Kappa 0.61 to 0.84; SHIELD 0.58 before, 0.79 after redefinition |
| Retrieval | Coding reports by attribute: SHIELD by state, by migrant husband | SHIELD in 15/18 with migrant husbands, 7/18 without |
| Co-occurrence | SHIELD × HUSBAND_DEMANDS matrix | Overlap in 19 segments across 14 files |
| Memos | Theme memos for SHIELD, STRATEGY, FEAR; a methods journal | The findings' first drafts |
| Export | Codebook, coding reports for the appendix, .qdpx for the archive | Report and deposit |
| NVivo | MAXQDA | ATLAS.ti | |
|---|---|---|---|
| Maker; since | Lumivero (QSR International); 1999 | VERBI, Berlin; 1989 (as winMAX) | ATLAS.ti GmbH, Berlin; 1993 |
| Organising idea | Files, codes and cases in a database; queries as the analytic engine | Four windows: documents, codes, browser, retrieved segments; everything visible at once | Quotations as first-class objects; codes, memos and networks link to them |
| Strengths | Queries (matrix coding, coding comparison, crosstab); framework matrices; survey and social-media import; the most-taught | Mixed methods (crosstabs, joint displays, typology tables); visual tools (MAXMaps); paraphrasing and summary grids; a built-in Stats module | Networks; the query tool's operators (co-occurrence, proximity, embedding); PDF coding; the earliest and most developed AI features |
| Platforms | Windows and Mac (features differ); Collaboration Cloud | Windows and Mac; TeamCloud | Windows and Mac; a full Web version |
| Transcription | NVivo Transcription (paid, per hour); English-centred | Via partner services; a transcription mode with foot-pedal support | Via the Web version and partners |
| AI | AI Assistant: summaries, code suggestions | AI Assist: summaries, suggested codes, chat with data | Intentional AI coding, AI summaries, conversational AI |
| Learning curve | Steeper; many objects and windows | Gentlest of the three | Middle; the quotation model takes a day to click |
| Typical licence | Student around US$100 a year; institutional site licences common in India | Similar; educational licences; a free Reader | Similar; Web by subscription |
| If | Lean toward | Because |
|---|---|---|
| Your institution licenses one | That one | Support, training, and a supervisor who can open your project |
| Your team is on Mac | MAXQDA or ATLAS.ti | Feature parity across platforms |
| The study is mixed methods with a survey | MAXQDA | Variables, crosstabs, joint displays and the Stats module in one place |
| The study is framework analysis for a policy client | NVivo (framework matrices) or MAXQDA (Summary Grid) | The charting step is built in |
| The analysis links passages to each other and draws conceptual maps | ATLAS.ti | Quotations and networks |
| Large document corpora, PDFs, policy texts | ATLAS.ti or MAXQDA | PDF handling and document-level coding |
| A distributed team with no server | ATLAS.ti Web, or MAXQDA TeamCloud, or NVivo Collaboration Cloud | Simultaneous access; check data-residency terms |
| No budget | QualCoder, or Taguette | Sections 04 and 05; the coding is the same |
| A thesis to be examined | Whatever the examiners can open | REFI-QDA export covers the rest |
| Route | Languages | Cost | Notes |
|---|---|---|---|
| NVivo Transcription | English-centred; some other languages; weak on Indian languages | Per audio hour, paid | Convenient for English interviews; not the route for Hindi or Bangla |
| VaniScribe (ImpactMojo) | Hindi, Tamil, Bangla, Marathi, Telugu and others via Sarvam's models; native script or transliteration | A few rupees a minute with your own key | Built for this course's readers; output has timestamps and speaker turns |
| Bodhan AI Indic-Transcribe (open weights) | The scheduled languages | Free to run locally; hosted API by the minute | Data stays on the machine if run locally; needs a capable computer or a notebook |
| Whisper and its Indic fine-tunes | Hindi and major languages, variable quality on others | Free locally | Hallucinates in silence; check every transcript |
| Human transcription (in-house or agency) | Any | Rs 300–1,500 per audio hour depending on level and language | Still the standard for full verbatim and for dialects; quality varies with the agency |
| Interviewer's own transcription | Any | Their time: 4–8 hours per hour | Slow, and the best first analysis there is |
| Code | Bihar member (n = 12) | Bihar non-member (7) | Bengal member (12) | Bengal non-member (5) |
|---|---|---|---|---|
| SAVINGS_SHIELD | 10 files, 24 seg. | 1, 1 | 8, 14 | 0, 0 |
| SAVINGS_BARRIER | 9, 17 | 7, 22 | 10, 19 | 5, 9 |
| DECISION_STRATEGY | 9, 21 | 3, 5 | 10, 24 | 2, 3 |
| FEAR_FORMAL_FINANCE | 4, 6 | 6, 13 | 5, 8 | 5, 11 |
| HUSBAND_DEMANDS | 11, 26 | 6, 12 | 9, 18 | 4, 8 |
| Case | Savings purpose | Shield | Decision strategy | Formal finance |
|---|---|---|---|---|
| BR_003 (member, migrant husband) | School fees; a buffalo | Strong: 'the money is the group's until I take it'; husband's family cannot ask | Times requests for when remittance arrives; group president as ally | Never entered the bank; group leader deposits |
| BR_007 (member, husband present) | Emergencies | Weak: husband knows the schedule and asks | Concedes small, holds large | Fear of forms; went once with the group |
| BR_011 (non-member) | 'Nothing to save' | — | None described; husband decides | Distrust from a relative's experience |
| WB_015 (member, migrant husband) | Daughter's marriage; a phone | Strong; explicit comparison with pre-membership | Uses group meeting days as cover for market visits | Has an account; uses it with the group |
| Visual | Tool | Use when | Avoid when |
|---|---|---|---|
| Code tree (the codebook as a diagram) | All | Showing the structure of the analysis in the methods | It is decoration for a list that reads better as a table |
| Matrix heat map (codes by attributes) | NVivo, MAXQDA, ATLAS.ti | Showing where a theme concentrates, as a pointer | The reader will read cell shading as proportions of a population |
| Co-occurrence network | ATLAS.ti networks; MAXMaps; NVivo maps | Showing how themes relate, with the links labelled and argued | It is a hairball of every code linked to every other |
| Concept map from memos | MAXMaps, ATLAS.ti networks | The theory of change that emerged; a figure for the discussion | It restates the code tree |
| Comparison diagram (two cases) | NVivo | Showing what two contrasting cases share and do not | Rarely; it is a two-row framework matrix |
| Hierarchy chart, sunburst | NVivo, QualCoder | Showing coverage of codes as a diagnostic during coding | In a report; it is a pie chart of segment counts |
| Word cloud | All | Never in a report | Always |
| Joint display (qual and quant side by side) | MAXQDA; by hand | Mixed methods, section 09 | — |
| Practice | Done |
|---|---|
| Every retrieval read in full before any count is reported | |
| Matrices report files (cases) first, segments second, and the sample size per column | |
| No matrix cell presented as a population proportion | |
| Co-occurrence read as a pointer; the overlapping segments read | |
| Text search and word frequency used to find, not to code or to conclude | |
| Framework matrix or equivalent charted for the main themes | |
| Every claim traceable: memo, query, retrieval, segments | |
| Disconfirming cases searched for and reported | |
| Visuals limited to those that carry an argument |
| Code | % agreement | κ round 1 | Action | κ round 2 |
|---|---|---|---|---|
| SAVINGS_PURPOSE | 94 | 0.84 | None | — |
| SAVINGS_SHIELD | 86 | 0.58 | Redefined: requires explicit reference to the money being inaccessible to others; added two examples and a do-not-use | 0.79 |
| SAVINGS_BARRIER | 91 | 0.76 | None | — |
| DECISION_STRATEGY | 83 | 0.52 | Split into STRATEGY_TIMING, STRATEGY_ALLY, STRATEGY_WITHHOLD | 0.71, 0.77, 0.74 |
| FEAR_FORMAL_FINANCE | 92 | 0.74 | Boundary with BANK_MISTREATMENT clarified | 0.81 |
| HUSBAND_DEMANDS | 90 | 0.71 | None | — |
| Arrangement | How | Tools | Risks |
|---|---|---|---|
| Divide the files | Each coder codes different files in a copy of the master; the master imports each copy (NVivo import project; MAXQDA merge; ATLAS.ti merge; QualCoder import coding) | All four | Codebook drift between coders; new codes created in two places under different names; merge conflicts on files coded twice |
| Simultaneous on a shared project | A server or cloud project everyone opens (NVivo Collaboration Cloud, MAXQDA TeamCloud, ATLAS.ti Web, hosted Taguette) | Cloud versions; Taguette | Data residency and consent; subscription cost; connectivity |
| Sequential | One project file passed from coder to coder with a lock (only one person edits at a time) | Any | Slow; someone always has it; the lock is broken by email |
| What | When | How |
|---|---|---|
| Project file backup | Daily during coding; automatic where the tool offers it | A dated copy on a second drive or institutional storage; not only the laptop |
| Milestone version | After the codebook revision; after the merge; before second-cycle coding; at submission | Save-as with a date; keep them all |
| Codebook version | At every revision | Export the codebook with date and a change note; keep the sequence for the appendix |
| REFI-QDA export | At milestones | The tool-independent archive |
| Project log | Continuous | A dated memo of decisions: what changed, why, who decided; NVivo's event log and QualCoder's action log supplement it |
| Coder copies | Until the merge is verified | Each coder's project before merging, kept |
| Practice | Done |
|---|---|
| One codebook owner; coders propose, owner decides | |
| Coder names set in the software before coding | |
| Merging arrangement agreed and tested before coding starts | |
| Shared sample (10–20% of files) coded independently by two coders | |
| Agreement computed per code, acted on, and re-measured; reported in the appendix | |
| Weekly coding meeting with segments on screen; decisions logged | |
| Bilingual codebook with source-language anchors where languages differ | |
| Backups daily; milestone versions kept; coder copies kept until the merge is verified | |
| Cloud use consistent with consent and data policy |
| Survey result (n = 640) | Qualitative finding (36 interviews) | Integrated reading |
|---|---|---|
| Members score 0.9 points higher on decision-making (95% CI 0.4 to 1.3) | Members describe group savings as a protected fund; decisions over large purchases are timed to its availability | The effect is concentrated in large-purchase decisions and works through control over a lump sum |
| Effect larger where husband is a migrant (interaction, p = .03) | SHIELD theme present in 15 of 18 migrant-husband cases, 7 of 18 others; remittance lumps attract relatives' claims, the group's fund does not | The mechanism is protection from claims, which matters most where lump sums arrive |
| No effect on 'own income' (2 points, CI −4 to 8) | Few members describe new income; several describe the group as changing control, not earnings | The programme changes control over money more than the amount; the survey's income item was the wrong outcome for the mechanism |
| Non-members report higher fear of banks (62% vs 41%) | Non-members' fear draws on relatives' stories; members' fear is reduced by going 'with the group' | Exposure through the group reduces avoidance; a bank-linkage component would build on it |
| Count | Legitimate? | Because |
|---|---|---|
| '31% of 480 survey respondents cited distance' | Yes, as a proportion | The sample is the survey's; every respondent answered the question; the denominator is known |
| '15 of 18 interviewees with migrant husbands described a shield' | Yes, as a description of the purposive sample and a pointer | The denominator is the interview sample, which was chosen, not drawn |
| '42% of women in the district feel the group protects their savings' | No | A purposive sample of 36 cannot support a population proportion |
| 'The theme of fear was mentioned 94 times' | Rarely | Segment counts reflect talkativeness and segment size; say files, not segments, if anything |
| 'Members were more likely than non-members to mention X (p = .04, Fisher's exact on 36)' | Not as a test | The interviews were not a random sample and the codes were not pre-specified as outcomes; report the pattern and its scope |
| 'Coded open-ends as variables, then regressed re-enrolment on them (n = 480)' | Yes | Quantitised survey data with a defined sample and pre-specified codes |
| Need | MAXQDA | NVivo | ATLAS.ti | QualCoder | Outside the tool |
|---|---|---|---|---|---|
| Import survey variables as attributes | Yes (variables) | Yes (classifications) | Yes (document groups; attributes) | Yes (attributes from CSV) | — |
| Import open-ends as codeable cells | Survey import | Dataset import | Survey import | Import survey | — |
| Crosstab codes by variables | Crosstab; Code Matrix Browser | Matrix coding query | Code-document table | Attribute report | Pivot table on the export |
| Joint display | Mixed Methods menu builds several | By hand | By hand | By hand | A table in Word |
| Export code matrix to statistics | Yes; the Stats module runs it in place | Yes (export to Excel/SPSS) | Yes | Yes (CSV) | jamovi or R |
| Typology from codes and variables | Typology table; Similarity analysis | By hand | By hand | By hand | Cluster analysis in R |
| Practice | Done |
|---|---|
| Integration point stated in the design: connecting, building, merging, or several | |
| Interviewees linked to survey records where consent allows; attributes imported | |
| Purposive qualitative sampling justified from the survey (variation, extremes, moderators) | |
| Matrices of themes by survey-defined groups produced and read | |
| A joint display drafted, with the integrated reading in the third column | |
| Disagreements between strands reported and interpreted, not suppressed | |
| Counts labelled by their denominator: proportion, description, or pointer | |
| Open-ends coded with a short codebook, agreement checked, and exported as variables | |
| The report weaves the strands rather than stacking chapters |
| Criterion (Lincoln and Guba 1985) | Question | Practices | What the project file shows |
|---|---|---|---|
| Credibility | Is the account believable to those who lived it and to careful readers? | Prolonged engagement; triangulation across sources; member checking; negative case analysis; peer debriefing | The retrievals behind every claim; the disconfirming cases coded and memoed |
| Transferability | Could a reader judge whether this applies elsewhere? | Thick description of setting and sample; purposive sampling stated | Attributes; the sampling memo; the case descriptions |
| Dependability | Was the process consistent and could it be followed? | Audit trail; codebook versions; team procedures; agreement checks | The log, the codebook versions, the comparison reports, the milestone files |
| Confirmability | Are the findings grounded in the data rather than the researcher's preferences? | Reflexivity; the chain from data to claim; a second reader | Reflexive memos; the query and retrieval behind each theme; a second coder's work |
| COREQ domain (Tong et al., Int J Qual Health Care 2007, 19:349; 32 items) | Items the software helps answer |
|---|---|
| Research team and reflexivity (items 1–8) | Coder names; reflexive memos; interviewer attribute |
| Study design (9–23): theory, sampling, setting, data collection | Sampling memo; attributes; transcription and translation memos; saturation evidence |
| Analysis and findings (24–32): coders, codebook, derivation of themes, software, participant checking, quotations, consistency, clarity of themes | Codebook versions; agreement table; the chain from retrieval to claim; software and version; quotation register |
| SRQR (O'Brien et al., Academic Medicine 2014, 89:1245; 21 items) | Note |
|---|---|
| Title, abstract, problem, purpose | As any paper |
| Approach and paradigm; researcher characteristics and reflexivity | Method memo; reflexivity statement |
| Context; sampling; ethics; data collection methods and instruments; units of study; data processing; data analysis; trustworthiness techniques | The memos and log, in order |
| Synthesis and interpretation; links to empirical data | Themes with quotations traced to sources |
| Integration with prior work; limitations; conflicts of interest; funding | The discussion |
| Object | Deposit? | Where | Conditions |
|---|---|---|---|
| Codebook with versions | Yes, always | OSF, Zenodo, the institution's repository, with the paper | None |
| Project file (REFI-QDA) with coding and memos, transcripts removed | Usually | As above | Memos may contain identifying detail; review them |
| De-identified transcripts | Where consent allows | Qualitative Data Repository (Syracuse), UK Data Service, ICPSR; with access controls | Consent for archiving; de-identification to a documented standard; often restricted access |
| Audio | Rarely | Restricted repositories only | Voices identify; consent rarely covers it |
| Quotation register | No | With the consent forms, institutional storage | The link between pseudonyms and people |
| Interview guide, consent forms (blank), sampling memo | Yes | With the paper | None |
| Tool | Feature | What it does | Where the data go |
|---|---|---|---|
| ATLAS.ti | Intentional AI coding; AI summaries; conversational AI | Codes a document against a stated intent; summarises documents or code groups; answers questions about the project | To OpenAI via Azure, under ATLAS.ti's terms; opt-in per project |
| MAXQDA | AI Assist | Summarises segments and documents; suggests codes and subcodes; chats with a document; paraphrases | To OpenAI under VERBI's terms; opt-in; can be disabled institution-wide |
| NVivo | AI Assistant | Summarises files and coded content; suggests codes; explains | To Lumivero's provider; opt-in |
| QualCoder | Optional AI assistance | Semantic search and code suggestions via an API key the user supplies (OpenAI or compatible) | To whichever provider the key belongs to; off by default |
| Taguette | None | — | — |
| Outside the tools | General LLMs (ChatGPT, Claude, Gemini), Indic models | Anything, on pasted text | To the provider; usually outside India; terms vary on training use |
| Risk | What happens | Practice |
|---|---|---|
| Data leaves the machine | Transcripts of vulnerable women's accounts go to a server abroad, under terms the participants did not see | No AI features without consent that names external processing; prefer local models (Bodhan's open weights on a lab machine) where consent is narrow; strip identifiers first regardless |
| Hallucinated summaries | A summary states something no participant said; a suggested code has no segment | Every AI summary is checked against the retrieval; every AI code is read before it is kept; the model's output is a draft, never evidence |
| Homogenisation | The model codes in the register of English-language psychology; Indian-language nuance and in vivo phrasing disappear | Code in the source language by hand for the analytic codes; use AI, if at all, for structural and descriptive first-pass codes |
| Weak Indian-language performance | Hindi and Bangla transcripts summarised badly; code-switching mishandled | Test on three transcripts with a bilingual reader before any use; prefer models built for Indian languages |
| Undisclosed use | Reviewers and readers assume human coding; the paper's claims about method are false | Disclose the tool, version, what it was used for, on what, and how its output was validated, in the methods (COPE and most journals now require it) |
| Code | Human-human κ | Human-model κ | Decision |
|---|---|---|---|
| SAVINGS_PURPOSE | 0.84 | 0.77 | Model first pass, human review |
| SAVINGS_SHIELD | 0.79 | 0.41 | Human only |
| DECISION_STRATEGY_TIMING | 0.71 | 0.38 | Human only |
| FEAR_FORMAL_FINANCE | 0.81 | 0.69 | Model first pass, human review |
| Situation | Choose | Because |
|---|---|---|
| First project; under twenty text sources; one analyst | Taguette | Ten minutes to start; everything exports; nothing to unlearn |
| Any project with audio, attributes or a second coder; no budget | QualCoder | The full workflow, free, offline, REFI-QDA |
| Institution licenses NVivo, MAXQDA or ATLAS.ti | That one | Support, supervisors, and site-licensed collaboration |
| Mixed methods with a survey at the centre | MAXQDA | Variables, crosstabs, joint displays, Stats |
| Framework analysis for a policy client with a deadline | NVivo or MAXQDA | Framework matrix and Summary Grid |
| Discourse or narrative work linking passages | ATLAS.ti | Quotations and networks |
| Distributed team, no server, cloud permitted by consent | ATLAS.ti Web, MAXQDA TeamCloud or NVivo Collaboration Cloud | Simultaneous access |
| Distributed team, data must stay in the institution | Self-hosted Taguette, or QualCoder with the divide-and-merge arrangement | No external storage |
| Teaching a methods class with no budget | Taguette, then QualCoder | Section 04's sequence |
| Long programme, staff turnover, recurring rounds | Any REFI-QDA tool, with the codebook as the persistent asset | The tool may change; the codebook and the archive should not |
| Week | Work | Tool | Section |
|---|---|---|---|
| 1 | Consent review; transcription in source languages; native-speaker checking; pseudonymisation; attribute sheet | VaniScribe; Word; a spreadsheet | 02 |
| 2 | Project setup; a priori codebook with definitions; first memo; five transcripts coded; codebook revised; five recoded | QualCoder | 03 |
| 3–5 | Coding by two coders in their languages; weekly meetings; inductive codes proposed and adopted; agreement on eight files; revision; second agreement check | QualCoder; coder comparison | 03, 08 |
| 6 | Merge; retrievals read; matrices by state, membership and migration; co-occurrence; theme memos | QualCoder reports | 07 |
| 7 | Framework matrix charted (36 × 8); negative cases; joint display with survey results; two member-checking meetings | QualCoder export; Word; the survey's jamovi file | 07, 09, 10 |
| 8 | Findings written with quotations from the register; methods paragraph; appendices (codebook versions, agreement, sampling, member checking, code-creation curve); REFI-QDA export deposited | Word; OSF | 10 |
| Error | Section | Fix in one line |
|---|---|---|
| Translating everything to English and coding the translation, without saying so | 02 | Choose a workflow; state it; keep the source |
| Machine transcripts uncorrected | 02 | A native-speaker check against the audio, recorded |
| Codes without definitions | 03 | Fill the memo field for every code |
| Two hundred codes and no theme | 03 | Merge by definition; write theme memos |
| Auto-coding or text search reported as coding | 03, 07 | Use to find; code by reading |
| Matrix cells reported as population proportions | 07 | Files first, denominator stated, purposive sample named |
| Word clouds as analysis | 07 | Delete them |
| Teams merging for the first time on the deadline | 08 | Test the merge with copies in week 2 |
| One kappa for forty codes | 08 | Per code, with the action taken |
| Qualitative and survey chapters that never meet | 09 | A joint display with an integrated column |
| Transcripts uploaded to an AI feature without consent for external processing | 11 | Check consent; strip identifiers; prefer local models; disclose |
| No audit trail beyond the project file | 10 | Codebook versions, log, memos, milestone files, REFI-QDA export |
| Data and process | Done |
|---|---|
| Consent covers recording, transcription, storage, quotation and any external processing | |
| Transcripts in the source language, checked, pseudonymised | |
| Translation workflow stated | |
| Attributes imported; sample described | |
| Codebook with definitions, versioned, in the appendix | |
| Agreement checked per code where the method calls for it; reported | |
| Memos and log kept; milestone files and REFI-QDA export saved |
| Analysis and reporting | Done |
|---|---|
| Every theme traceable to retrievals, matrices and cases | |
| Negative cases sought and reported | |
| Counts labelled by denominator; no purposive-sample proportions | |
| Framework matrix or equivalent for the main themes | |
| Joint display where a survey exists | |
| Quotations chosen for range, introduced, sourced, consented, registered | |
| COREQ or SRQR checklist completed | |
| Software, versions and any AI use disclosed; codebook and project deposited |
| Resource | What it covers | Notes |
|---|---|---|
| Saldaña, The Coding Manual for Qualitative Researchers (4th ed., Sage, 2021) | Coding methods, first and second cycle, memos | The companion to section 03 |
| Miles, Huberman and Saldaña, Qualitative Data Analysis: A Methods Sourcebook (4th ed., Sage, 2020) | Displays, matrices, drawing and verifying conclusions | Section 07 |
| Gale et al., BMC Med Res Methodol 2013, 13:117 | The framework method, step by step | Sections 03 and 07 |
| Braun and Clarke, Thematic Analysis: A Practical Guide (Sage, 2021) | Reflexive thematic analysis and what it is not | Why agreement is not always the goal |
| O'Connor and Joffe, Int J Qual Methods 2020, 19 | Intercoder reliability: debates and guidelines | Section 08 |
| Fetters, Curry and Creswell, Health Serv Res 2013, 48:2134; Guetterman et al. 2015 | Integration and joint displays | Section 09 |
| Tong et al. 2007 (COREQ); O'Brien et al. 2014 (SRQR) | Reporting standards | Section 10 |
| Silver and Lewins, Using Software in Qualitative Research: A Step-by-Step Guide (2nd ed., Sage, 2014); the CAQDAS Networking Project (University of Surrey) | Tool-independent software strategy; comparative reviews of every package | The reference for sections 04 to 06 |
| QualCoder wiki and manual; Taguette documentation; vendor manuals | The tools | Free |
| ImpactMojo: Qualitative Methods 101, Mixed Methods 101, Research Ethics 101, Data Protection & the DPDP Act 101; VaniScribe | The methods, the ethics, the law, and the transcription tool | impactmojo.in |