> For the complete documentation index, see [llms.txt](https://docs.smaq.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.smaq.io/documentation/features/reports.md).

# Reports

A **report** in SMAQ is a presentation-quality document derived from a dashboard. Think of dashboards as your working canvas and reports as the cleaned-up deliverable you hand to a client or executive.

> **\[Screenshot needed]** Report list page with three reports and the "Generate Report AI" button visible.

### How reports relate to dashboards

* **Dashboards** are interactive, live, editable.
* **Reports** are written, structured, exportable.

You build a dashboard once. You generate many reports from it over time — one per month, one per campaign, one per stakeholder review.

### Generating a report

The fastest path is from the dashboard itself: **Generate Report AI** in the dashboard header. See [Generate report from dashboard](/documentation/features/reports/generate-from-dashboard.md) for the full walkthrough.

Alternatives:

* **From scratch** — start an empty report and drag in charts manually.
* **From a template** — start from a saved structure (intro, KPI summary, channel deep-dives, recommendations).

### Editing a report

The report editor exposes:

* **Slide list** in a left rail — reorder by dragging.
* **Current slide** in the center — edit title, body text, headers.
* **Chart preview** on the right (when a slide contains a chart).
* **Re-run AI on this slide** — regenerate the narrative without affecting other slides.

> **\[Screenshot needed]** Report editor with the slide list, edit pane, and chart preview all visible.

### Themes

Reports inherit your project's [report theme](/documentation/features/reports/report-themes.md). Themes control colors, fonts, slide layouts, and chart styles.

Two ways to set theme:

* **Project default** — set in **Settings → Report Theme**. Every new report uses it.
* **Per-report override** — change theme on a specific report without affecting the project default.

### Exporting

Click **Export** in the report header. Options:

* **PowerPoint (.pptx)** — most common. Opens in PowerPoint, Keynote, or Google Slides with layout preserved.
* **PDF** — for archival or email distribution where you don't want editable slides.

### Scheduled reports

For recurring stakeholder deliveries, schedule a [Dashboard Summary](/documentation/features/automations/dashboard-summary.md) instead. A Dashboard Summary covers similar ground but in email format on a schedule — no manual editing required.

### Tips

* **Use clear chart titles on the source dashboard.** The Report AI uses titles as narrative anchors.
* **Lock the date range before generating.** The report inherits the dashboard's current state — wrong date range, wrong report.
* **Edit selectively.** The AI's first draft is usually 80% there. Editing 20% is faster than starting from scratch.
* **Save report theme work for last.** Style after structure.

### Tier availability

* **Growth, Scale, Agency** — full Reports.
* **Starter** — basic reports without AI generation (manual mode only).

### What's next

* [Generate report from dashboard](/documentation/features/reports/generate-from-dashboard.md) — full step-by-step.
* [Report themes](/documentation/features/reports/report-themes.md) — style your exports.
* [Generate your first report (tutorial)](/documentation/get-started/tutorials/generate-your-first-report.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:

```
GET https://docs.smaq.io/documentation/features/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.