Sooner or later someone asks the qualitative researcher the uncomfortable question: how did you know you had enough data? The usual answer is saturation, the point where new interviews stop turning up new ideas. That is a sound principle. The trouble is that saturation often gets reported as a feeling, a sense that the researcher had heard it all, offered to a reader with no way to check it. Stated that way, it invites exactly the skepticism qualitative work already fights. Saturation is a claim about your data, and a claim needs evidence.
What saturation actually means
Saturation is not the moment you get tired or the moment your recruitment budget runs out. It is the point where additional data stops adding new codes or themes, where the last several interviews mostly repeat what earlier ones already established. That is a statement about the shape of your coding over time, not about your stamina. Which means it is something you can observe and record, rather than something you simply assert at the end.
Show the curve, do not just claim the point
The way to make saturation credible is to track it. As you code, watch how often genuinely new codes appear. Early on, nearly every interview introduces something. As the study goes on, new codes get rarer, and eventually a run of interviews adds little that is new. That flattening is the evidence. A reader who can see that your last handful of interviews produced almost no new codes does not have to take your word for it, because the pattern of diminishing novelty is right there, and it is far more convincing than a sentence asserting that saturation was reached.
A few honest caveats
Saturation is not a blank check. A pattern can look settled simply because your sample was narrow, so reaching it quickly can be a sign you have not heard from enough different kinds of people rather than a sign you are done. And some questions, especially about rare experiences or diverse populations, resist saturation by their nature. The goal is not to force the claim. It is to be honest about whether you reached it, and to say so plainly when the answer is not clean.
Where Qual Studio turns the claim into evidence
Judging saturation by memory is where the feeling creeps back in, because no one can hold the full history of their coding in their head. ReliCheck's Qual Studio keeps that history for you. Because coding and codes live in one place, you can see how new codes accumulated across your data and where that growth flattened, which turns a soft assertion into something you can show. That is the through-line of defensible qualitative work: not claiming rigor but demonstrating it. Qual Studio is built so the answer to how did you know you had enough is a record you can point to, not a feeling you ask a reviewer to trust.
ReliCheck's Qual Studio keeps your coding and codes in one place, so you can see how new codes accumulated and where growth flattened, turning a saturation claim into visible evidence. See it at relichecksurvey.com.