> For the complete documentation index, see [llms.txt](https://ailyze.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://ailyze.gitbook.io/ailyze-docs/methods-and-best-practices/reporting-findings.md).

# Reporting Findings

This page shows you how to turn your analysis into a clear, credible report. Analysis only matters if people act on it — reporting is where research becomes impact.

## Match the format to the audience

| Audience                    | Format                             | Evidano feature                                                                                     |
| --------------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------- |
| Leadership / clients        | One-page executive summary         | [Create an executive summary](/ailyze-docs/create-deliverables/create-an-executive-summary.md)      |
| Stakeholders / teams        | Themed report with quotes & charts | [Generate a research report](/ailyze-docs/create-deliverables/generate-a-research-report.md) (DOCX) |
| Collaborators / interactive | Live link                          | [Share as Webpage](/ailyze-docs/create-deliverables/export-and-share-findings.md) *(Pro)*           |
| Analysts                    | Coded data                         | [CSV/XLSX export](/ailyze-docs/create-deliverables/export-and-share-findings.md)                    |
| Academic                    | Methods + themes + evidence        | [DOCX report](/ailyze-docs/create-deliverables/generate-a-research-report.md) + documented codebook |

## A structure that works

1. **Executive summary** — the few things that matter, up front.
2. **Method** — data, sample size, and how the analysis was done (including how you used AI).
3. **Findings** — by [theme](/ailyze-docs/reference/glossary.md#theme) or question; each with a claim, a number, and a quote.
4. **Comparisons** — key segment differences.
5. **Recommendations** — prioritized and tied to findings.
6. **Limitations** — sampling, scope, confidence.
7. **Appendix** — codebook, full data export.

## Use evidence well

* **One verified quote per point** beats five unverified ones. Always check quotes against the source.
* **Quantify with denominators** ("47% of 320 responses"), using the [frequency](/ailyze-docs/reference/glossary.md#frequency) charts and coded tables.
* **Show the chart** that supports each major claim (export it as PNG or CSV).
* **Attribute carefully** and anonymize where required.

## Don't overclaim

* Qualitative themes describe **what people said**, not how common something is across the whole population (its prevalence) — so be precise about scope.
* AI assists the analysis, but **you are accountable** for the conclusions. State how AI was used and that you reviewed the output.
* Acknowledge **cases that don't fit** the pattern — it strengthens credibility.

## Let Chat draft, you edit

Use [Chat with your data](/ailyze-docs/analyze-data/chat-with-your-data.md) to draft sections fast (*"write the findings for theme 3 with one quote, about 120 words"*), then edit for voice, verify the evidence, and add your own judgment. The chatbot is for **summarizing** what's already there, not for inventing new analysis.

## Reporting checklist

* [ ] Right format for the audience
* [ ] Findings tied to evidence (quotes + numbers)
* [ ] Quotes verified against source
* [ ] Comparisons not over-interpreted
* [ ] Limitations and AI use stated
* [ ] Codebook and data included as an appendix

## Next steps

* [Generate a research report](/ailyze-docs/create-deliverables/generate-a-research-report.md)
* [Create an executive summary](/ailyze-docs/create-deliverables/create-an-executive-summary.md)
* [Qualitative research best practices](/ailyze-docs/methods-and-best-practices/qualitative-research-best-practices.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ailyze.gitbook.io/ailyze-docs/methods-and-best-practices/reporting-findings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.