Reports

Reports

A report is a Word (.docx) document saved into the project as evidence.

Reports are the formal end of the writing spectrum. Where a note is a scratchpad you keep editing, a report is something you hand to someone: permanent, checksummed, and traceable back to the project it came from.

Where reports come from

There are two routes, and both produce exactly the same thing:

1. From the assistant. Ask it to draft something, review what it writes, then click Save as report on that reply.
2. From a note. Every note in the Notes panel has a Save a copy as report action. The note stays where it is — you get a document copy alongside it.

Both land in the project's reports/ folder and appear under a single Reports tool in the Results Hub, regardless of which route created them.

Nothing is written without you

The assistant drafts in the chat first. Nothing reaches disk until you click. This is platform-wide and deliberate: there is no path where model output becomes a project file unreviewed.

What a report contains

The document opens with its title, the project name, and the project's scientific question, then the body converted from markdown — headings and bullet lists carry across.

Editing a report

Unlike other evidence, a report's file can be edited after it's created — click Edit on it in the Results Hub to open it in a full docx editor, right in the browser. Changes save back to the same report: same id, same place in the project, same provenance. There's no separate "final" copy to remember to re-save; the report is whatever it currently says.

If you'd rather keep the original untouched and draft changes separately, save another copy as a new report, or use a note instead — notes are the free-editing scratchpad this platform also has.