Docs · Step 6

Export your work

A file you can hand to someone else, with the same caveats and figures you saw on screen.

1. Pick what to export

  • Full Dataset Report: a narrative PDF or PowerPoint stitching together insights, drivers, the Deep Analysis champion, drift and text-analysis findings. The export button for it lives on Chat, Dashboards and Predict, not only one place.
  • A single chart or figure: high-DPI PNG or SVG, journal-themed, with an APA-style caption.
  • A codebook: every column, what it holds, and either the range it covers or the values it takes. A column description CLAIR wrote and nobody has reviewed is marked unreviewed, so a reader can tell which is which.
  • A dashboard: one PDF, a page per chart plus the pinned findings' own text, in the order you arranged the board.
  • A chat session: HTML transcript, PowerPoint, PDF, or a whole-session CSV.

2. Start the export

Use the export button on the relevant page. Most exports finish in seconds; the Full Dataset Report and large dashboards can take longer.

3. Cancel, if it's taking too long

A long-running export (the PowerPoint or the Full Dataset Report) checks a cancel flag between sections, so it stops cleanly before starting the next one rather than finishing a file nobody wants. Nothing partial is written to the export folder.

What's actually in the file

Caveats travel with the answer

A warning Chat attached to an answer, a small group, dropped rows, a possible total row, is not left behind on export. The PDF, PowerPoint, HTML and JSON versions all carry the same warning.

When Chat answers by listing or filtering rows, the HTML transcript and the whole-session CSV carry every row. The PowerPoint slide and the PDF section cap the printed rows for readability, and state in the document exactly how many were left out and where to find the rest.

A report that couldn't build one of its sections (a computation that genuinely failed, as distinct from a section that legitimately found nothing) says so in a Report Notes section inside the document, and the save confirmation names how many sections were affected rather than showing the same plain success message either way.