Generate and Read a Report
Choose completed runs, generate a synthesis, and trace findings back to responses.
このページの翻訳はまだありません。英語の原文を表示しています。
A report synthesizes a selected scope of completed research. It is separate from the result cards you already see in the conversation.
Choose the scope
After research finishes, use the report entry above the conversation composer. Select the completed runs that belong to the study. The composer report icon can bring the entry back if you dismissed it.
Include runs that answer the same decision and retain any comparison or contradictory evidence. Do not add unrelated runs solely to make the report longer. Check the scope and charge before starting generation.
The conversation shows a report progress card. Open View report when it finishes. You can also return through Library's Report tab.
Research conversation
New generation is separate from viewing results.
Choose what a report covers
Use the report entry above the conversation composer.
Read the report in layers
Start with the executive summary and key findings. Then inspect detailed findings, per-question highlights and cross-segment patterns where present. Check the recommendations against the evidence rather than treating a confident sentence as proof.
Use the analysis, responses and coding views available on the report to trace a theme back to answers. Limitations, appendix and disclosure explain how to interpret the result and what was included. The exact sections depend on the research and report format.
Cost and regeneration
Reports are priced from the credits of the runs they cover, with a minimum of 20 credits. Deep analysis is included; there is no separate 50-credit Deep Dive upgrade in the current workflow.
Opening a completed report does not generate it again. If you explicitly confirm a rewrite, or generate a report over a new scope, that is a new charged generation. Retrying the same in-flight request is different from intentionally regenerating a finished report.
See the tiered calculation and examples in Pricing & credits.
If generation fails
Return to the conversation and inspect the report card. A request that failed to start may leave the generation action available. Check the usage ledger before deliberately retrying a failed generation; do not infer a refund from an error message alone.
When the report is ready, share or export it with its methodology and synthetic-data disclosure.