Qualitative data analysis methods - thematic, content, narrative, grounded theory, framework - with the step-by-step process and how to run each one.
Qualitative data analysis methods are the structured ways to read open text: coding, thematic analysis, framework analysis, and content analysis, each turning narrative into patterns against a codebook. Sopact runs these on the Connected Record: each method applied on arrival and tied to the number on one participant record under a persistent Contact ID, so a theme is defensible and read next to the score.
Researchers know the methods; the problem is when they run. Coding a corpus by hand happens months after collection, so a thematic pattern that would have flagged a problem arrives after the program is over. And because the text sits in a coding tool apart from the numbers, a framework theme never meets the rating it should explain, which makes the finding hard to present as a defensible picture.
Key takeaways
The methods themselves are sound; the workflow around them is the issue. A codebook applied in a standalone tool produces themes in a file that has no shared key with the survey data, so a thematic result and the rating it explains cannot be read together without an export and a hand-join. The rigor of the method is lost in the plumbing.
Sopact is record-centric: each method is applied on arrival and tied to the same persistent ID as the numbers, so a coded theme is read against the score on one Connected Record. See the step-by-step on how to analyze survey data, or the combined discipline on mixed-methods data analysis.
Coding, thematic, and framework analysis usually run in NVivo, ATLAS.ti, MAXQDA, and Dedoose, with Excel for a lighter content-analysis pass. Each is a capable workbench for a trained researcher, and each was built to code text in isolation, so a method finishes as a separate deliverable that a team then tries to reconcile with the quantitative results.
The one test that sorts them: ask the tool to apply your codebook and show each theme with its sentence and the number the same respondent gave, on one record. A standalone workbench answers with a coded file to export. Sopact answers from the Connected Record, because the codebook was applied on arrival and tied to the number.
The move that modernizes the methods is applying the codebook as text lands, so thematic and framework analysis produce patterns while responses arrive rather than in a marathon at the end. Sopact drafts the coding from the respondent’s words, quotes the sentence, and ties it to the number, so a researcher confirms a draft and keeps analytic control instead of coding a corpus from scratch.
Kept on the Connected Record, a method is longitudinal: themes across every wave on one persistent ID, each traceable to a sentence and a score. Sopact reads on arrival, so a framework theme meets the rating it explains and a pattern surfaces in time to act.
A standalone workbench applies a method to text in isolation and finishes months later; the Connected Record applies the codebook on arrival and ties each theme to the number. The difference is whether a method’s output meets the score or stays in a separate file.
| The question | Standalone workbench | Connected Record |
|---|---|---|
| Apply a codebook? | Yes: by a trained hand | Yes, on arrival |
| Tie a theme to the number? | A separate export | Yes: one participant record |
| Same themes on every run? | Depends on the coder | Yes: the codebook applied |
| Surface a pattern in time? | No: months later | Yes: read as text lands |
Compare the two families on qualitative vs quantitative, or see software that themes on arrival on thematic analysis software.
A dropping score is worth understanding while you can still respond to it, not in a report written after the program ends. The value of the open-text behind a number is highest the moment it lands, when the reason for a low rating can still change what happens next. That is the premise of the Loop, Sopact’s method for continuous intelligence: collect clean at the source, with the number and the open-text explaining it on one participant record; analyze on arrival, reading each open-text answer against a codebook the moment it lands and tying it to the number; improve in time, so the reason behind a dropping score surfaces while you can still act.
The Loop is also what makes a mixed-methods finding defensible: every theme traces back to the exact sentence a respondent wrote and the number that respondent also gave, the standard detailed in Loop traceability, so a conclusion rests on the Connected Record rather than a hand-coded spreadsheet no one can re-check.
One method, three moves that never stop
Then the next wave reads a little sharper. Read the method: the Loop methodology →
The fastest way to see a method on arrival is to run it on your own data. Export a batch of open-text responses with their IDs and codebook, then paste the prompts below into Sopact Sense’s Assistant, or reason through them with your team. The arrow above each links the Academy walkthrough with the expected output and tips.
Academy walkthrough → Analyze open-ended responses
Here is a batch of open-ended survey responses with each respondent's ID and their rating: [ATTACH]. Read each open-text answer against our codebook as it lands, tag the themes, quote the exact sentence behind each theme, and keep every answer tied to the number the same respondent gave, so I can read the reason next to the score on one record instead of in two separate exports.
Academy walkthrough → Connect the number and the reason
Here is our quantitative data and the open-ended responses on the same participant IDs: [ATTACH]. For each rating, pull the open-text the same respondent wrote that explains it, quote the sentence, and show the number and the reason on one record, so a low score carries the reason a respondent gave rather than sitting in a column with no explanation.
Academy walkthrough → Clean open-ended responses
Here is a raw export of open-ended responses on their participant IDs: [ATTACH]. Flag blanks, duplicates, and off-topic answers, normalize the text so it is analyzable, and keep each cleaned answer tied to its ID and the number that respondent gave, so the open-text is ready to read against a codebook on arrival rather than after a month of hand-cleaning.
Academy walkthrough → Find the drivers behind a score
Here are ratings and the open-ended responses on the same IDs: [ATTACH]. Read the sentiment in each answer, identify the drivers behind the rating with the sentence quoted, and tie each driver to the number, so I can see what is pushing a score up or down from the respondent's own words rather than guessing behind the average.
Each walkthrough is short and practical: what to do, the prompt to run, the output to expect, and the tips that keep it reliable.
Watch: reading open-text against a codebook on arrival and keeping every answer tied to the number on one Connected Record.
Coding, thematic analysis, framework analysis, and content analysis, each turning open text into patterns against a codebook. Sopact runs each on the Connected Record, applied on arrival and tied to the number, so a theme is defensible and read next to the score.
Because a standalone coding tool produces themes in a file with no shared key to the survey data. Sopact is record-centric and ties each theme to the same persistent ID as the numbers on the Connected Record, so a coded theme is read against the score.
Those are workbenches for coding text in isolation, finishing as a separate deliverable. Sopact applies your codebook on arrival and keeps each theme on the Connected Record, tied to the number, so the method’s rigor is not lost in a hand-join.
Yes. Sopact applies the same codebook to every answer, so the themes are the same on each run and each traces to a sentence. The Connected Record keeps the theme tied to the number, which makes the method defensible.
No. Sopact drafts the coding from the respondent’s words with the sentence quoted; a researcher confirms or overrides it, human-in-the-loop. The Connected Record records what was read and against which codebook.
Yes. Sopact applies the codebook the moment text lands, so thematic and framework patterns build while responses arrive rather than in an end-of-study coding pass on the Connected Record.
It depends on the question: thematic for emergent patterns, framework for a set structure, content analysis for frequency. Sopact applies whichever codebook you bring on arrival and keeps the output tied to the number on the Connected Record.
Sopact keeps every coded theme on one persistent ID, so a pattern across waves is read as a trajectory. The Connected Record survives each cycle, which is what makes a longitudinal, defensible method possible.
Next: see software that themes on arrival on thematic analysis software, or read interview transcripts on qualitative interview.
