Draft a Scope of Work with Deliverables, Exclusions and Revision Limits
You get a client-ready scope of work with a deliverables table, acceptance criteria, a specific 'not included' list, revision caps and a change request process.
Prompt
You are an experienced freelance consultant who writes scopes of work that stop scope creep before it starts.
Your job: draft a scope of work (SOW) for my next client project. Before writing, ask me these questions in one message, numbered, then wait for my answers:
1. What is the project and who is the client?
2. What will you deliver, and in what format?
3. What are the timeline, fee and payment terms?
4. What have past clients asked for that you do not want to include?
Rules:
- Every deliverable has a quantity, a format and 2-3 acceptance criteria the client can check with a yes or no.
- Write a 'Not included' list of at least 6 specific items in plain words, never a vague 'anything else'.
- Give a numbered revision cap per deliverable, define what one round means, and state the price of extra rounds.
- List client responsibilities with deadlines and say what happens to the timeline if they are late.
- Plain English, no legalese.
Output format:
1. Project summary (3 sentences)
2. Deliverables table: # | Deliverable | Format and quantity | Acceptance criteria | Revision rounds | Due date
3. Not included
4. Revisions and change requests
5. Client responsibilities
6. Timeline and payment
7. Sign-off
End with one line listing assumptions you made or gaps I should fill. This is not legal advice; have a lawyer review contracts with large fees or IP terms.Example output
Tips and common edits
Why this works
- Yes-or-no acceptance criteria per deliverable make 'done' measurable, so the client can't keep moving the finish line.
- A required 'Not included' list of 6+ specific items blocks the most common free extras before they're requested.
- Defining one revision round and pricing extra rounds turns endless feedback into a paid change request.
Use before sending a proposal or contract to a new client. Have your deliverables, fee, deadline and past scope creep headaches ready. Works well in ChatGPT, Claude or Gemini.
Common edits
- Add a cancellation and kill-fee section for higher-value projects.
- Ask for a one-paragraph email version to send alongside the full SOW.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Politely End a Bad-Fit Client Relationship with a Clean Handover Plan
Get a calm, firm exit email plus a wrap-up checklist and pushback reply, so you can end work with a difficult client and keep your reputation intact.
Build a New-Client Onboarding Email Sequence and Kickoff Checklist
Get a dated onboarding email sequence, focused intake questions, exact access requests, a timed kickoff agenda and a checklist so day one isn't blocked.
Plan a Weekly Freelance Schedule for Client Work, Admin and Outreach
Get an hour-by-hour weekly plan that blocks deep client work, invoicing and new-business outreach, keeps buffer time for overruns, and flags overbooking.
Raise Your Freelance Rates with Existing Clients Without Apologizing
You get a short rate increase email with notice date, new rate and one reason, plus ready reply scripts for pushback, delay requests and a client who leaves.
Reply to Client Scope Creep with a Friendly Change Order Email
You get a short, warm client email that separates the new request from the original scope and offers a priced add-on or a budget-neutral swap.
Review a Freelance Contract in Plain English and Flag Risky Clauses
Paste a client contract and get a plain-English risk table covering IP, payment, liability, termination and non-compete, with a suggested redline for each clause.