A qualitative case study methodology chapter answers four questions: why this case, what evidence, how it was analysed, and why the account is trustworthy. Write it as six labeled sections, give every choice a "because" sentence, and tie each trustworthiness word to a move you made.
What the methodology chapter must answer
A marker reads your methodology chapter with four questions in mind, and each one maps to a section. Miss one and the gap is exactly where the comments land.
- Why this case? A case study stakes everything on one bounded setting — a ward, a classroom, a small firm. Show the case was chosen for a reason, not because it was nearest.
- What evidence? Interviews, observations, documents, artifacts — name every stream, how much of it there was, and what each is good at proving.
- How was it analysed? Words do not arrange themselves. Name the coding moves and the plan that turns codes into claims, in enough detail that another person could follow the path.
- Why trust it? Qualitative work replaces statistics with named moves — triangulation, member checks, an audit trail, thick description. Say which you used and what each did.
Notice the shape: this is a methods chapter, not a results chapter — it explains the machinery that will produce the findings. Where the chapter sits in the wider paper is covered in how to write a research paper.
The methods chapter skeleton builder
Make five choices below — design, data sources, participant count, analysis path, trustworthiness strategies. The builder assembles six numbered sections, each pre-written in prose with your choices inside, plus a completeness meter. Treat the output as scaffolding: your case details always win.
Methods chapter skeleton builder
Five choices in, six numbered sections out.
Switching the design rewrites the rationale section live.
Unsure? The analysis paths section explains when each fits.
A rough count is fine — the chapter can say "roughly".
Bracketed prompts mark the sentences only you can write. The skeleton rebuilds as you change any choice.
Case selection wording: the bounded system and its "because"
The sentence that opens case selection does two jobs at once: it draws a boundary and declares a reason.
First, the boundary. A case is a bounded system — a unit with edges: a start date, a membership, a place. "One secondary school's first year with a new behaviour policy" has edges. "Student behaviour" does not; that is a topic, and a case study of a topic collapses into a survey with extra steps. Put the boundary in the first sentence, with its time frame.
Second, the because. Selection reasons come in a handful of honest shapes — say which shape is yours:
- The clear case — the phenomenon shows up here at its most visible, so you can watch it work without guessing.
- The unusual case — something here deviates from the norm, and deviations are where mechanisms expose themselves.
- The typical case — nothing here is special, which is why conclusions about the everyday are fair from it.
- The access case — you could get in, get consent and get depth; say so — a real reason beats an invented one.
A finished selection paragraph sounds like this (illustrative — the school and the people are invented):
The case is Northgate High, a six-form entry secondary school studied across the 2025–2026 academic year — the first year a new behaviour policy operated. It was chosen because it adopted the policy a full year before its sister schools, so the whole arc of introduction and adjustment is visible in one case. Three deputy heads, eight teachers and two policy authors sit inside the boundary; the sister schools are context, not data.
One warning: the reason must survive contact with your literature review. If the review says clear cases are where new policies show their mechanisms, "a year ahead of its sisters" is design, not luck.
Data sources in a qualitative case study
A case study earns its name from its evidence streams. One interview series is an interview study; a case study reads interviews against observation notes against documents, because each stream catches what the others miss. List every stream with its volume — nine interviews, four observation mornings, forty-one documents — and say what each is for.
| Source | Its strength | What it proves | Watch out |
|---|---|---|---|
| Interviews | Meaning in participants' own words — reasons, history, beliefs. | How people inside the case interpret events. | Accounts are shaped by memory and self-image; a claim needs a second source. |
| Observations | Behaviour as it happened, including what people never mention. | What the setting actually does, not what it says it does. | Your presence changes the room; note when it might have. |
| Documents | What the case committed to on paper — minutes, policies, emails — untouched by your questions. | What the setting formally decided and valued. | Documents record intentions; practice drifts, so read them against the interviews. |
Artifacts — booking forms, floor plans, sticky-note walls — belong in the list when they carry evidence. The rule across streams: every claim should trace to at least one named source, the strongest to two that agree.
Interview question stems that produce quotable data
The difference between a transcript full of usable quotes and one full of "I suppose, yeah, probably" is the question shape. Three stems do most of the work:
- Grand tour — "walk me through the whole thing, step by step". Produces the map of a practice: sequence, actors, routines the participant no longer notices.
- Example — "tell me about one specific time when…". Forces abstraction into a story, and stories carry the detail that makes quotes quotable.
- Probe — "you mentioned X — paint the picture". Follows the participant's own emphasis instead of your schedule — where surprises live.
Build one below — pick a stem, type a topic or tap a preset, then copy it into your guide.
Interview stem builder
One topic in, one open question out.
Six illustrative topics — tap one to load it, then edit:
Two stems to avoid: anything answerable with yes or no ("did the policy help?"), and anything that hands the participant the answer ("so the policy mainly failed, didn't it?"). The first flattens the data; the second plants it. More shapes live in the case study interview questions guide.
Analysis paths: thematic, pattern matching, explanation building
The analysis plan is where most methods chapters go quiet — one sentence like "the data were analysed thematically" and then nothing, which a marker reads as "no plan". The three paths below cover nearly every student case study:
- Thematic analysis fits when the question asks what is going on here and the text is rich. Code the chunks close to the words used, gather repeated codes into themes, and let a theme stand only when a quote or field note can testify for it.
- Pattern matching fits when the question already predicts a shape — an expected "if this, then that" chain from the literature. Lay the predicted pattern beside the evidence and report where the case follows it and where it breaks — the breaks are the interesting half.
- Explanation building fits when the question is a why with no predicted answer. Start with a provisional explanation, revise it every time the evidence contradicts it, and keep going until the account survives every source in the case.
The four coding moves you will name — tap each card for its one-line job:
Open coding
The first pass over transcripts and notes.
Its job
Label every meaningful chunk in words close to the data itself — no themes yet, just tags.
Axial coding
The second pass, after the labels pile up.
Its job
Reconnect the labels: which belong together, which sit inside which, which are twins in different clothes.
Pattern matching
For questions that already predict a shape.
Its job
Hold the predicted pattern against the case and call out every place the evidence follows or breaks it.
Cross-case synthesis
Only when more than one case runs.
Its job
Read the cases side by side: what repeats in every case, what shows up in one, what the gap buys.
One boundary: the analysis plan delivers organized evidence, and the meaning you claim from it belongs to the discussion — the split is set out in the discussion vs conclusion guide. Chapters that quietly start interpreting steal their own credibility.
Trustworthiness moves, mapped to rubric language
Quantitative studies borrow their quality words from statistics. Qualitative work has its own four — credibility, transferability, dependability and confirmability — a framing from the classic qualitative research tradition (most rubrics trace it to Lincoln and Guba's widely used account, so treat the words as shared shorthand). Rubrics rarely define them; they deduct marks when the words appear without the moves. Here is the honest mapping:
| Rubric word | What it actually asks | The move that earns it | Where it shows in the chapter |
|---|---|---|---|
| Credibility | Do the findings match what is really true in this setting? | Triangulation — no theme enters the findings on one source's word alone — plus member checks, where participants read and correct the account. | Data sources and procedures |
| Transferability | Could a reader judge whether this applies to their setting? | Thick description — the case reported in enough detail that another reader can do the comparing. | Case selection and findings |
| Dependability | Would the process produce the same account if rerun? | An audit trail — dated files of transcripts, codes and drafts a reader can retrace. | Procedures and analysis plan |
| Confirmability | Is it the data speaking, or the researcher's opinion? | The same audit trail plus reflexivity: a short paragraph on where you stand relative to the case. | Analysis plan |
The failure mode is the buzzword list: four definitions copied from a textbook and nothing about your study. The fix is one move, one sentence, tied to your data: "every theme appears in at least two of the three data streams" beats a page of definitions — it names a rule your evidence followed.
The chapter in prose: a worked, illustrative skeleton
Here is the builder's output filled in and edited — an illustrative study, invented for display: one school, a new behaviour policy, interviews and documents, thematic analysis. Nothing below is real; it shows the register to aim for.
This study is a qualitative case study using a single-case design: one bounded setting carries the study, because the question — how a staff absorbs a new behaviour policy across its first year — asks how the phenomenon works inside a particular context. The chapter says plainly what the findings can and cannot speak to beyond the case.
The case is Northgate High, a six-form entry secondary school, studied across the 2025–2026 academic year. It was selected because it adopted the policy a full year before its sister schools, so the whole arc is visible. Roughly thirteen participants sit inside the case — three deputy heads, eight teachers, two policy authors — each chosen because they operate the policy rather than observe it.
Evidence comes from two streams, so no claim rests on one source alone. Semi-structured interviews carry participants' accounts of the policy's first year; behaviour logs and policy drafts carry what the institution committed to on paper. Where the streams agree, a theme firms up; where they disagree, the disagreement is itself a finding.
Interviews were arranged at each participant's choosing, recorded with consent, and transcribed before coding began. Documents were gathered as they naturally existed, dated, and read with their original purpose in mind. Both streams ran on the same ethics: informed consent, anonymity in the write-up, the right to stop at any point.
Transcripts and documents were coded in two passes: an open pass that labeled chunks close to the words used, then a second pass that gathered repeated labels into themes. Each theme entered the findings only when a quote or dated document could testify for it.
Two moves carry the trustworthiness argument. Triangulation: every theme appears in both the interview and document streams, or is flagged as single-source. An audit trail: transcripts, codebooks and drafts sit in dated files, so a reader could retrace how the account was built.
Adjust the pieces and the register holds. For an assignment, the same six sections compress cleanly — the case study assignment guide shows the two-page version.
Five methodology-chapter mistakes and their fixes
Each mistake below has a mechanical fix; the first can sink the design before a single finding is read. If your study is quantitative wearing a case study's name, case study vs experimental research sorts it out in one read.
| Mistake | What it looks like | The fix |
|---|---|---|
| Method mix-up | A chapter titled "case study" that actually surveys ninety individuals and reports percentages — people sampled, not a bounded system. | Decide what the unit is. A questionnaire to ninety people is a survey; name it so, or redraw the study around a case. |
| No selection rationale | "A case study approach was adopted" — followed by silence about why this case, of all cases. | One because-sentence in one of the four honest shapes: clear, unusual, typical, or access. |
| Leading interview questions | "So the new rota mainly made things worse, right?" — the transcript now contains your opinion. | Rebuild as an example stem: "tell me about one specific time the rota affected your shift". |
| Analysis plan absent | "The data were analysed thematically" with no passes, no order, no checking step. | Name the path and its steps: first pass, second pass, and what a theme must survive before it counts. |
| Trustworthiness as buzzwords | Four textbook definitions under a "Trustworthiness" heading, none connected to the study. | One move, one sentence, tied to your data: which strategy, what rule it imposed, where it shows. |
Quiz: is your methods chapter ready?
Five questions, one pick each; wrong answers point back to the section that fixes them.
1. A study examines how one hospital unit absorbed a new rostering system. In case study terms, what is the case?
2. Which sentence belongs in the case-selection paragraph?
3. A participant says: "We never really used the new form." Which follow-up produces quotable data?
4. The research question predicts a specific "if this, then that" chain. Which analysis path checks the case against it?
5. What does member checking actually do for the chapter?
Methods chapter stalled while the deadline closes in?
If the skeleton will not fill itself before the due date, a quoted, deadline-bound writer can take the methods chapter — or the whole case study — off your hands.
Frequently asked questions
How many interviews does a qualitative case study need?
There is no fixed number, and any chapter that quotes one without a reason is guessing. Keep interviewing until new conversations stop producing new codes, then say the final count and the stopping point in the chapter. Every interviewee should sit inside the case and be chosen for a stated reason.
Can I mix interviews and documents in one case study?
Yes — that combination is standard in case study work. Interviews give you the account from the inside; documents show what the setting committed to on paper. Where the two agree a theme firms up, and where they disagree the disagreement itself becomes evidence worth reporting.
What is the difference between coding and thematic analysis?
Coding is the move — a short label on a chunk of transcript or field note. Thematic analysis is the plan that turns labels into themes and themes into claims. A chapter that says data were analysed thematically without naming the passes or how themes were checked has an analysis plan in name only.
How do I write trustworthiness without sounding like a buzzword list?
Tie every term to a move you actually made. Triangulation is a claim about your data sources, member checking is a sentence about who read what, the audit trail is a sentence about your files. One move, one sentence, one rubric word — that paragraph survives any marker. Four adjectives with nothing behind them do not.
How long should the methods chapter of a case study be?
Proportional to the whole write-up — your rubric overrides every rule of thumb. For a dissertation it can run several thousand words; for an assignment, two pages. Coverage is the fixed part: design rationale, case selection, data sources, procedures, analysis plan and trustworthiness, each earning a paragraph with a because sentence attached.
Was this guide useful?