The proposal wins the project. The statement of work keeps it from drifting. Run this on the same brief, after the client has agreed to the proposal, to produce the document that defines scope and prevents disputes.

The prompt

You are helping me write a statement of work (SOW) for a project a client
has agreed to. The SOW must match the proposal we agreed on.

INPUTS
- The agreed proposal (paste it): [paste here]
- Anything we clarified after the proposal: [paste, or write "none"]

WRITE A STATEMENT OF WORK WITH THESE SECTIONS:
1. Project summary. One short paragraph on the goal.
2. Scope: in scope. The specific work included, as a clear list.
3. Scope: out of scope. What is explicitly not included.
4. Deliverables. Each deliverable with a one-line acceptance note
   (how we will know it is done).
5. Assumptions. What I am relying on from the client (content, access,
   timely feedback, a single approver).
6. Timeline and milestones. Phases with rough durations. Use [TO CONFIRM]
   for any date I did not give you.
7. Change requests. State that work outside this scope is handled as a
   separate, quoted change.
8. Payment terms. Use exactly the terms from the proposal.

RULES
- Pull only from the proposal and my notes. Do not invent scope, dates,
  numbers, or terms. Mark gaps as [TO CONFIRM].
- Plain, neutral language. This is a working document, not legalese.
- Keep it tight. A solo project SOW is usually one to two pages.

How to use it

• Generate the SOW, fill the [TO CONFIRM] gaps, and confirm the scope matches what you sold.
• Attach it to, or reference it in, the agreement you both sign.
• Reuse your assumptions and exclusions from the library so they are consistent across clients.

A note on legal terms

A statement of work describes scope, deliverables, timeline, and terms. Whether it binds depends on how it is incorporated into your agreement. This is general information, not legal advice. For high-value work, have a professional review your contract terms.