A report is a decision document. It opens with the conclusion and its uncertainty, then gives the reader what they need to trust it or push back.
A report header: the project name, the update date and the project's recorded tokens, the headline conclusion, and a summary paragraph

The top of a report

​
Reading a report

  • Header: the project, when the report was last updated and the model tokens the project’s runs recorded. On an earlier revision it also says which revision you are reading and links to the latest.
  • Headline and summary: the conclusion in one sentence, then the argument in a paragraph. Superscript numbers are footnotes.
  • Sections: each one is a card or a set of cards: tables you can sort and filter, charts with their underlying data, key figures, questions and answers, callouts and methods.
  • Data sources: what data the analysis used, which fields, the quality alerts found, and what the data cannot support.
The Data sources card with counts of sources, rows, fields used and alerts, and the statement of what the data will not support

The Data sources card

The Model comparison section: its heading and a table of cross-validated and holdout ROC-AUC and recall per model, with sort buttons and a filter box per column

A section with a table you can sort and filter

A cumulative subscriber reach chart comparing logistic regression, gradient boosting and random order, with its legend, a Data disclosure and the data file output/run1/gains.json

A chart with its data file

The files attached to the revision, such as code, data extracts and notebooks, are at the end of the report: the ones it cites under Sources, the rest under Attached files, each with a download link and, for a slide deck, a preview. The report’s own presentation and exports are under Project actions, and the whole package is in Outputs. Every footnote points to an entry in Sources at the end of the report, and each source is a pinned revision of a file in the project. The outline at the right edge shows where you are; select a line to jump to that section.

​
Revisions

Publishing again from the terminal creates a new revision of the same report; earlier revisions stay readable. When a project has more than one report, a switcher above the report lets you move between them, and Outputs lists them all. Members who can write to the project can edit a report’s text from the pencil button in the header. The Headline group holds the Report name (used in lists, the report switcher and the browser tab), the headline readers see, the summary, and the Review status (Draft, Reviewed or Approved), which you set and which shows beside the date. Each group’s Save and Revert appear once you change it; Revert goes back to the last save. An edit creates a new revision; it never changes a revision someone has already shared.

​
Printing and exporting

The ⋯ menu prints the report and exports it as an Excel workbook or a CSV dataset. When the agent authored a presentation for the report, Preview presentation opens it.