# Produce Reports

Simulations produce findings. Reports package those findings into a document you can share — with an executive, a client, or a colleague who doesn't work in the platform.

RootCause reports are living documents. Charts and metrics stay connected to live data, so a report you build today reflects updated numbers tomorrow without manual edits. They also serve as an audit trail: by linking conclusions to specific Data Views, Digital Twins, and simulation runs, you document not just what you found but how you found it.

***

## Create a report

Navigate to **Reports** in the left sidebar.

<figure><img src="/files/qcGJIgAOj7eecfNE1IWR" alt="Reports home showing the AI generation field and existing reports list"><figcaption><p>The Reports home. Describe what you want and RootCause generates a structured report, or start from a blank document.</p></figcaption></figure>

Two paths:

**Generate with AI** — describe the report in the text field (for example, "Causal analysis of churn drivers and the impact of service enhancement interventions") and click **Connect** to reference datasets, data views, or digital twins. RootCause generates a structured report with an Executive Summary, section headings, and evidence-linked prose drawn from your workspace data.

**Start from scratch** — opens a blank editor. Build the report manually using the editor toolbar.

***

## The report editor

<figure><img src="/files/XhAcitc6JKpWj9iX2P1n" alt="Report editor showing a generated report with Executive Summary and Introduction"><figcaption><p>A generated report. Sections are structured and findings are linked to evidence. The report can be edited freely after generation.</p></figcaption></figure>

The editor works like a modern document tool. Type to add text; use `/` to insert blocks:

* `/heading` — H1, H2, H3 for structure
* `/bullet` — bullet list
* `/quote` — block quote
* `/widget` — embed a live chart, KPI, or table from your workspace data

**Widgets** connect directly to Data Views and simulation results. A chart widget referencing a Data View updates automatically when the underlying data changes — no manual refresh or re-export needed.

**Mentions** — type `@` to reference workspace objects inline. `@Sales_2024` becomes a clickable link to that Data View; `@Q4_Simulation` links to a specific simulation run. Readers can follow the link to inspect the underlying analysis.

***

## Evidence and audit trail

For conclusions that will drive decisions, link them to evidence:

1. Select the text of a claim or recommendation
2. Click **Add Evidence**
3. Choose the source — Data View, Simulation, or Digital Twin
4. Select the specific object

The evidence link is embedded in the report. Readers can click through to verify the data behind each conclusion. This is what separates a report from a presentation: the reasoning is inspectable, not just asserted.

***

## Export and share

**PDF Export** — click **Export PDF** in the top right to generate a polished PDF snapshot. Suitable for sharing outside the platform with clients or leadership. The PDF is static — it captures the report at the moment of export.

**Within the workspace** — reports are visible to all workspace members. Anyone with access can view and navigate the evidence links.

***

## Suggested structure

Generated reports follow a standard pattern. For manually built reports, the same structure works well:

```
# Executive Summary
## Key Findings
## Recommendations

# Analysis
## Data Overview
## Causal Relationships
## Simulation Results

# Appendix
## Methodology
## Data Sources
```

Lead with conclusions — executives read the top. Provide supporting detail below for those who want it.


---

# Agent Instructions: 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:

```
GET https://docs.rootcause.ai/user-guide/reports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.