> For the complete documentation index, see [llms.txt](https://evidano.gitbook.io/ailyze-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://evidano.gitbook.io/ailyze-docs/analyze-data/discover-themes-and-patterns.md).

# Discover Themes & Patterns

Let Evidano draft the themes in your documents or survey answers, or bring your own codebook, then refine them into a set you can defend.

This page shows researchers how to get a first set of [themes](/ailyze-docs/reference/glossary.md#theme) and sub-themes for a document analysis, either drafted by the AI from your files or brought from a codebook you already have, then refine them and read the patterns in the results. Spreadsheet analysis is covered at the end. Every control is listed in [Document Analysis Settings](/ailyze-docs/reference/settings/document-analysis.md#you-will-receive-themes-generated-from-the-entire-dataset).

Letting themes emerge from the data is [inductive coding](/ailyze-docs/reference/glossary.md#inductive-coding); applying a framework you bring is [deductive coding](/ailyze-docs/reference/glossary.md#deductive-coding). Most projects mix the two: let the AI draft, then edit toward your framework. [Choosing the Right Analysis Approach](/ailyze-docs/methods-and-best-practices/choosing-the-right-analysis-approach.md) explains when each fits.

## Before you start

* Files chosen for a document analysis, with the draft open on **Your table**. [Analyze Interview Transcripts](/ailyze-docs/common-research-workflows/analyze-interview-transcripts.md) gets you there.
* Optional: a codebook or framework to apply, as a file or as text.
* Optional: an earlier project whose themes you want to reuse.

## Step 1: Find the themes section

Themes have their own section in the draft, **You will receive themes generated from the entire dataset**, between the report options and the table of answers and metadata. If it is missing, click **Add** › **Add theme** above the table of answers and metadata. Look at what the **Themes and sub-themes** panel shows:

* A numbered list of themes and sub-themes: they are ready. A codebook you attached under **Supporting files** is imported word for word; otherwise the AI drafted them from your files. Go to Step 4.
* "Drafting themes and sub-themes…": the AI is drafting them from your files. Keep working; they appear when ready. Go to Step 4.
* **Configuration required**, with a choice between **Generate draft themes and sub-themes now** and **Add manually**: there are no themes yet. Go to Step 2 or Step 3.

You should see one of these three states in the panel.

<figure><img src="https://1178311500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi4GBXPMUDxszIpUVOARU%2Fuploads%2Fgit-blob-6cee73df76c37fa0858a2671bd2e80e9f58f1802%2Fsettings-document-analysis-24-themes-empty.png?alt=media" alt="Themes section with Levels, Configuration required, Generate draft themes and sub-themes now, and Add manually"><figcaption><p>The empty state: nothing is analyzed until the themes are drafted or added.</p></figcaption></figure>

## Step 2: Let the AI draft the themes

1. Pick **2 levels** (themes and codes) or **3 levels** (themes, sub-themes, and codes), then choose **Generate draft themes and sub-themes now**.
2. Edit the instructions, which are pre-filled from the project draft. Say what kinds of themes you want, for example "Focus on barriers to using the clinic and how parents work around them; keep sub-themes concrete."
3. Click **Generate draft themes and sub-themes now**.

You should see "Drafting themes and sub-themes…" in the panel, then the draft themes as a numbered list, with a note that the AI suggested them.

<figure><img src="https://1178311500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi4GBXPMUDxszIpUVOARU%2Fuploads%2Fgit-blob-4b8bce74bc61b7108a18e8a06beddeffb3f0e94e%2Fsettings-document-analysis-25-generate-themes.png?alt=media" alt="Generate draft themes and sub-themes dialog with pre-filled instructions about the mobile clinic and the generate button"><figcaption><p>The pre-filled instructions already name your project's focus; add the angle you care about before you generate.</p></figcaption></figure>

## Step 3: Or bring your own codebook

In the panel, choose **Add manually**, then pick a source:

1. **Type**: enter themes and sub-themes one by one, each with a description.
2. **Paste**: paste a list, an outline, or a codebook table; the AI arranges it into themes and sub-themes.
3. **Upload**: read themes from a PDF, Word, text, or spreadsheet file.
4. **Use previous**: reuse the themes of an earlier project, so waves or sites are coded alike.

Once themes exist, **Paste**, **Upload**, and **Use previous** sit under **Replace with** in the theme set-up. **Use previous** brings the codes and their definitions too.

You should see your themes in the panel, in your wording.

## Step 4: Refine the themes before you start the analysis

Click **Edit themes and sub-themes** under the themes and work through the list:

* Rename vague themes in your project's language.
* Merge near-duplicates; split a theme that holds two ideas. **+ sub-theme** and **+ Add theme** add one; the arrows on hover move one; the x removes one, with **Undo**.
* Give each one a short description, so coding stays consistent. The sparkle button (**Write with AI**) drafts one for you.

Leave codes on "Let the AI create codes during the analysis" unless you have a code list; **Add manually now** lets you enter one. Click **Done** when you finish. **Undo** in the builder bar reverses any change.

You should see the edited themes as a numbered list in the panel and in the **Sample table output** under it.

<figure><img src="https://1178311500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi4GBXPMUDxszIpUVOARU%2Fuploads%2Fgit-blob-e00146be339b428e15d00f855b3aeff21d85c250%2Fsettings-document-analysis-23-theme-setup.png?alt=media" alt="Theme set-up with Levels, Regenerate, theme cards with descriptions, Replace with, Codes and Done"><figcaption><p>Editing here is quicker than editing the codebook after the run, and the AI codes every file against your version.</p></figcaption></figure>

After the run you can still change themes with **Edit** in the **Codebook** header or add them with **Add Theme** (both Pro). See [Build a Codebook](/ailyze-docs/analyze-data/build-a-codebook.md).

## Step 5: Read the patterns in your results

When the analysis is done, look beyond the theme list:

* [Frequency](/ailyze-docs/reference/glossary.md#frequency): the counts in the **Codebook** section and its frequency charts show what is most common.
* [Co-occurrence network](/ailyze-docs/reference/glossary.md#co-occurrence-network): which themes appear together, revealing relationships and tensions.
* [Hierarchy graph](/ailyze-docs/reference/glossary.md#hierarchy-graph): how sub-themes sit under themes.
* Segment comparisons: whether a theme belongs mostly to one group. See [Compare Groups (Segments)](/ailyze-docs/analyze-data/compare-groups-segments.md).
* Quotes: the evidence. Read them; do not trust counts alone.

You should see the network and the hierarchy graph under **Visualizations** in the **Codebook** section.

<figure><img src="https://1178311500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi4GBXPMUDxszIpUVOARU%2Fuploads%2Fhtjl2DKQ524mY5klRyT4%2FDiscover%20themes%202.png?alt=media&amp;token=68f4e03e-86c4-44ce-a209-f5e136f54328" alt="Co-occurrence network of codes, colored by sub-theme, with Absolute and Normalized options"><figcaption><p>Thick clusters of links mark codes that keep appearing in the same passages.</p></figcaption></figure>

[How to Read Your Results](/ailyze-docs/analyze-data/how-to-read-your-results.md) defines each chart.

## In spreadsheet analysis

When you reach the themes step in a spreadsheet analysis, you choose how the themes are created:

1. **Let Evidano generate them** — the AI proposes a [codebook](/ailyze-docs/reference/glossary.md#codebook) of themes and sub-themes from your data. Best for exploration and speed.
2. **Enter your own** — type or paste a codebook you already have. Best when you're applying a framework you bring to the data.
3. **Reuse a previous codebook** — choose **Use previous** to apply the codebook from an earlier project, keeping projects consistent.

Every option is in [Spreadsheet Analysis Settings](/ailyze-docs/reference/settings/spreadsheet-analysis.md).

<details>

<summary>Optional: a quality checklist for your themes</summary>

* Do the themes answer your research question?
* Are they distinct, with little overlap, and clearly named?
* Does each theme have quotes you have checked against the source?
* Did you look for disconfirming evidence? [Chat With Your Data](/ailyze-docs/analyze-data/chat-with-your-data.md) helps: "What contradicts this theme?"
* If you compared groups, are the differences real or an effect of small numbers?

</details>

## Next steps

* [Build a Codebook](/ailyze-docs/analyze-data/build-a-codebook.md) — refine the themes after the run and check how reliably they were applied.
* [Compare Groups (Segments)](/ailyze-docs/analyze-data/compare-groups-segments.md) — see which groups a theme belongs to.
* [Qualitative Research Best Practices](/ailyze-docs/methods-and-best-practices/qualitative-research-best-practices.md) — the methods behind good themes.