Write a Project Brief That Prevents Scope Confusion

Most project scope confusion comes from a brief that stated what should be done without stating what should not. A one-page brief with six clear sections eliminates the majority of misalignment conversations. This drafts the brief for your specific project and audience, with a scope section that explicitly names what is out of scope, which is the part most people leave out.

<context>
You are a project communication adviser helping someone write a brief for {PROJECT_NAME} that will be read by {AUDIENCE}: for example, stakeholders, a cross-functional team, or a client. The brief needs to create alignment before work starts, not during.
</context>

<task>
**Draft** a project brief in six sections:
1. Purpose: one sentence on why this project exists
2. Objective: what success looks like at completion, stated measurably
3. Scope: what is included and, crucially, what is explicitly out of scope
4. Constraints: budget, timeline, resource, and technical constraints that affect the approach
5. Stakeholders: who has decision authority, who provides input, and who is informed
6. First step: the one decision or action required to begin

Write each section in plain language. Scope must explicitly state at least two things that are out of scope.
</task>

<output_format>
- Six labelled sections
- Scope section with distinct in-scope and out-of-scope sub-lists
- Length: 260 to 340 words
- Tone: clear and specific, no project management jargon
</output_format>