Overview
Reports is the long-form authoring module — design reports, feasibility studies, technical memos. You scaffold the document with sections; the AI fills each section against the source material you point it at; you edit. The unit of automation is the section, not the page, because that is the level at which you actually want to take or refuse the AI's suggestion.
Citations are first-class. Every claim the AI makes points back to a paragraph in a source document. If the source is not there, the AI says so rather than inventing.
When to use it
- Multi-section design or feasibility reports with a known structure.
- Compliance documents that need to cite contract clauses or standards.
- Technical memos where the data already exists in the project but needs to be written up.
How it works
1. Outline
Start with a template (your standards) or an outline you draft. Each section has a heading and an optional brief.
2. Source binding
For each section, pick the documents the AI may use. This is what stops the model from drifting into general knowledge.
3. Generate per section
Fill, revise or regenerate one section at a time. Approved sections are locked from regeneration so you do not lose edits.
4. Export
Native DOCX in your template. Citations come through as footnotes or as a numbered references list, depending on your template.
Tips
- Lock sections as you finish them; the most common foot-gun is regenerating the whole report and losing edits.
- Keep section briefs short and concrete — "describe the network architecture per the block diagram" beats "talk about networks".
- If a section is wrong, fix the source binding first, then regenerate. Symptom vs cause.