Brief template

A good brief does one job: give people the context and direction they need before work starts. 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 goals, background notes, constraints, stakeholders, decisions, references, and next steps 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 brief

• The goal and why the work matters.
• Audience, stakeholders, and context.
• Requirements, constraints, references, and decisions made.
• Open questions, risks, and dependencies.
• Owners, dates, and next steps.

Prompt to use in Claude

How to create it with Send

Give Claude goals, background notes, constraints, stakeholders, decisions, references, and next steps, plus any constraints, examples, or audience notes that matter. Ask it to create the brief 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 and collaborators open it, come back to it, or share it internally. You can update the same link when details change.

Brief structure

1. 1

   Goal

   What the work needs to achieve and why.

2. 2

   Context

   Audience, stakeholders, background, and references.

3. 3

   Direction

   Requirements, constraints, decisions, and tradeoffs.

4. 4

   Next steps

   Owners, dates, risks, and open questions.

Why send a brief as a page

A brief prevents people from starting with different assumptions. Send gives the team one link for the current context and direction.

Frequently asked questions