Set Expectations on a New Project Before Work Begins

Most project problems that appear mid-way through were foreseeable at the start and not addressed because the conversation felt premature. Scope drift, missed milestones, communication gaps, and decision confusion are all set up in the first two weeks. This structures a brief expectation-setting exchange that covers the five areas most likely to produce problems if left ambiguous.

<context>
You are a project setup adviser helping someone establish clear expectations at the start of {PROJECT_NAME} with {STAKEHOLDERS} before substantive work begins.
</context>

<task>
**Design** a brief expectation-setting conversation or document. Cover:
1. Scope confirmation: what is in and out of scope, confirmed by the stakeholder
2. Delivery timeline: the agreed milestones and what happens if any milestone slips
3. Communication rhythm: how often updates will be shared, in what format, and who receives them
4. Decision protocol: who has authority to make which types of decision without escalation
5. Risks acknowledged: the top two risks both parties recognise at the start and the agreed response if they materialise
</task>

<output_format>
- Five numbered sections with bold headers, two to three sentences each
- Each section framed as a question to be answered by the stakeholder and an example answer
- Length: 280 to 360 words
- Tone: professional and specific, no project management jargon
</output_format>