Report template
Turn findings into a readable explanation with caveats, recommendations, and next steps.
A good report does one job: turn findings into a useful explanation and a next step. The format matters, but the useful part is the thinking behind it. Readers need the context, the recommendation, the proof, and the next step without having to reverse engineer your intent.
Claude can turn research, data, notes, findings, charts, interviews, conclusions, and recommendations into a clear first version. Send turns that version into a live page you can share, track, and revise as the conversation changes.
What to include in the report
- The question, scope, and method.
- Findings with evidence, examples, or data.
- What the findings mean for the reader.
- Risks, caveats, and open questions.
- Recommendations and next steps.
Prompt to use in Claude
Search the registry for the Send connector. Once connected, use their "send/report" skill.
How to create it with Send
Give Claude research, data, notes, findings, charts, interviews, conclusions, and recommendations, plus any constraints, examples, or audience notes that matter. Ask it to create the report with the Send connector so the output becomes a page instead of another loose document.
After you share it, Send helps you see whether teams, clients, and stakeholders open it, come back to it, or share it internally. You can update the same link when details change.
Report structure
Scope
Question, method, source material, and limits.
Findings
Main observations, evidence, and examples.
Interpretation
What the findings mean and what to watch.
Recommendations
Actions, owners, next steps, and open questions.
Why send a report as a page
A report should help someone understand what changed or what to do next. Send makes the report easier to share and update as new evidence arrives.