> 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/create-deliverables/create-an-executive-summary.md).

# Create an Executive Summary

Get a short executive summary of a finished analysis: steer it in the report options, refine it on the results page, or write your own with chat.

This page shows researchers and evaluators how to get a short summary of a finished analysis that busy leaders will actually read: what you found, and what to do about it. Document analysis writes one for you, which you can steer before the run and refine after it; for any project you can also ask chat for exactly the format you need. At the end you will have a summary you can paste into a slide deck or an email. The report options are listed in [Document Analysis Settings](/ailyze-docs/reference/settings/document-analysis.md#you-will-receive-a-report).

## Before you start

* A document analysis project for the built-in summary, or any completed project for the chat route.
* The Pro plan to edit or refresh the summary and to type in chat. Reading and copying it work on every plan.

## Step 1: Keep the executive summary in the report

While you set up a document project, look under **You will receive a report**, at the top of the draft. **Executive summary** is ticked by default. Click its pencil (**Instructions for the executive summary**) and say how it should read, for example "One page for the district health board: lead with the biggest barriers to using the clinic, then where North Valley and South Ridge differ." The AI pre-fills these instructions from your brief, so read them before you click **Review and start analysis**.

You should see the instructions box under **Executive summary**.

<figure><img src="https://1178311500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi4GBXPMUDxszIpUVOARU%2Fuploads%2Fgit-blob-d76f7449dacf0c2dddce5d91edff0e3e3776bd43%2Fsettings-document-analysis-30-report.png?alt=media" alt="You will receive a report with Executive summary ticked and its pre-filled instructions open below it"><figcaption><p>Badge 1 is the pencil next to Executive summary. The pre-filled instructions already name an audience; change it to yours.</p></figcaption></figure>

## Step 2: Read the summary on the results page

Open the finished project. **Executive Summary** comes first and is already open, on its outline; **Show full summary** shows the rest. A chip above the text says when it was written, for example "Generated", "Edited", or "Refreshed" with the date. The info icon beside the title shows the instructions it followed.

You should see the summary of the whole project, then a summary of each file if you kept **Summary of each document**.

<figure><img src="https://1178311500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi4GBXPMUDxszIpUVOARU%2Fuploads%2Fgit-blob-ddbc43306dfba75453eed7d980a85ed10a1d6f4e%2Fsettings-document-analysis-43-executive-summary.png?alt=media" alt="Executive Summary section expanded, with its Generated chip, the outline, and four action icons on the right"><figcaption><p>The icons on the right are chat, Edit, Copy, and a ⋯ menu with Rewrite with AI and Delete; the header's download icon saves the section.</p></figcaption></figure>

## Step 3: Tighten or rewrite it

Use the icons at the top right of the summary:

* **Edit** rewrites it by hand (Pro). The stamp changes to "Edited".
* **Refresh** has the AI rewrite it (Pro). Under **Optional Instructions**, pick a **Language of Response**, add instructions such as "End with three prioritized recommendations", and click **Send**.
* **Copy** copies it for a deck or an email.
* **Chat with this analysis** opens a chat that starts from this summary, so you can ask for a shorter or differently framed version.

You should see the new text with an updated stamp.

## Step 4: Write one with chat instead

Open **Chat to generate custom report/analysis** from **Actions** and ask for the format you need:

> *"Write a one-page executive summary for a non-technical leadership audience: 3 key findings as headers, 2–3 sentences each, the single most important quote overall, and 3 prioritized recommendations. Plain language, no jargon."*

The standalone chatbot suggests prompts such as *"Write a five-paragraph essay about the top challenges in the document."* See [Chat With Your Data](/ailyze-docs/analyze-data/chat-with-your-data.md).

You should see a draft in the chat panel. Check every number and quote against the results before you use it.

## A reliable structure

1. Context: one sentence on what was examined and how (sample size, method).
2. Top findings: three to five, each a clear claim with a number and a quote.
3. Differences that matter: key [segment](/ailyze-docs/reference/glossary.md#segment) contrasts (see [Compare Groups (Segments)](/ailyze-docs/analyze-data/compare-groups-segments.md)).
4. Recommendations: prioritized, tied to findings.
5. Caveats: sample limits and how confident you are.

## Make it trustworthy

* Lead with the decision, not the methodology.
* Quantify ("62% of detractors mentioned onboarding") using the [frequency](/ailyze-docs/reference/glossary.md#frequency) data.
* Use one quote per point, verified against the source.
* Be honest about limitations; see [Reporting Findings](/ailyze-docs/methods-and-best-practices/reporting-findings.md).

<details>

<summary>Optional: a worked example</summary>

* Project: the guide's mobile-clinic evaluation, three staff interviews and a parents' focus group.
* Before the run: **Executive summary** stays ticked, with the instructions from Step 1.
* After the run: **Refresh** with "End with three prioritized recommendations", then **Copy** the result into the board paper.
* Last check: each claim against its theme's quotes and the codebook counts.

</details>

## Next steps

* [Generate a Research Report](/ailyze-docs/create-deliverables/generate-a-research-report.md) — when readers need the full report behind the summary.
* [Export & Share Findings](/ailyze-docs/create-deliverables/export-and-share-findings.md) — send the files or the live project to stakeholders.
* [Reporting Findings](/ailyze-docs/methods-and-best-practices/reporting-findings.md) — present findings honestly and clearly.