Turn a client brief into a statement of work with clear exclusions
A statement of work with objectives, deliverables, acceptance criteria, assumptions, and exclusions that prevents scope arguments later.
The prompt
Turn my notes from a client conversation into a statement of work (SOW).
Client and their goal: [WHO THEY ARE and what they want to achieve]
What I'm proposing to do: [ACTIVITIES, in rough notes]
Deliverables I have in mind: [e.g. "audit report", "5 landing pages", "2 workshops"]
Timeline: [START, END, key milestones]
Fee and payment structure: [AMOUNT and schedule, or "leave blank"]
What the client must provide: [access, data, people, approvals]
Things I will NOT do: [anything I already know is out of scope]
Draft the SOW with these sections:
1. Background and objectives (2-3 sentences, in the client's language).
2. Scope of work: activities grouped by phase.
3. Deliverables table: deliverable | description | format | due date | acceptance criteria.
4. Client responsibilities and dependencies, with what happens to the timeline if they slip.
5. Assumptions (number of revision rounds, meeting cadence, stakeholders involved, working hours).
6. Out of scope: an explicit list, including the gray areas clients most often assume are included for this type of work.
7. Change request process: how new requests are quoted and approved.
8. Fees, payment schedule, and expenses.
Rules:
- Make every deliverable concrete enough that both sides could agree it's done.
- Flag any vague phrase in my notes ("support", "optimize", "ongoing") and suggest tighter wording.
- Do not invent fees, dates, or numbers. Use [ADD ...] where I haven't given them.
- This is a business document, not legal advice; recommend I have a lawyer review the governing contract it sits under.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- WHO THEY ARE and what they want to achieve
- ACTIVITIES, in rough notes
- e.g. "audit report", "5 landing pages", "2 workshops"
- START, END, key milestones
- AMOUNT and schedule, or "leave blank"
- access, data, people, approvals
- anything I already know is out of scope
- ADD ...
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a procurement plan for a projectA project procurement plan with make-or-buy decisions, sourcing methods, contract types, a lead-time schedule, risks, and roles.
- Write purchasing rules for when quotes, bids, and POs are requiredA practical buying policy setting competition rules by spend level, PO and purchasing card rules, and controls against maverick and split buying.
- Write a risk assessment for a guided tour or group tripA tour risk assessment with hazards by activity, controls, emergency plan, and guide briefing notes.
- Build a contract-to-close timeline with every deadlineA dated transaction checklist covering contingencies, earnest money, appraisal, loan, title, and closing, with owner and reminders.