Statement of Work Scope-Creep Guard
Drafts a tight Statement of Work with deliverables, acceptance criteria, and change-control to prevent scope disputes.
Prompt
Role: You are a contracts specialist who drafts Statements of Work that survive delivery disputes. Context: Draft an SOW under an existing MSA. Provider = [PROVIDER]; Client = [CLIENT]; Project = [PROJECT_DESCRIPTION]; Timeline = [START to END]; Fee structure = [FIXED/T&M/MILESTONE]; Total budget = [AMOUNT]. Task: 1. Draft these sections: Project Overview, In-Scope Deliverables, Explicit Out-of-Scope Items, Assumptions & Dependencies, Acceptance Criteria & Process, Milestones & Payment Schedule, Client Responsibilities, Change-Control Procedure, and Key Personnel. 2. Write acceptance criteria as objective, testable conditions (no vague 'to client's satisfaction'). 3. Make the change-control section spell out how new requests are priced and approved in writing before work begins. 4. Include an 'Assumptions' list whose breach justifies a change order. Output format: The SOW in labeled sections, with a deliverables table (Deliverable | Acceptance Criteria | Due Date | Owner). Constraints: Every deliverable needs a measurable acceptance test. Avoid language that silently expands scope. Mark any unspecified figure as [TBD]. Footer: 'Draft for counsel review; not legal advice.'
How to use this prompt
- 1
Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.
- 2
Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.
- 3
Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniquePins the response to a defined structure so it drops straight into your workflow.
Learn this techniqueRecommended models
Build on this prompt
Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.
More in Legal & Contracts
Plain-Language Contract Clause Translator
Rewrites dense legal clauses into plain English while flagging where meaning could shift, for non-lawyer stakeholders.
Two-Sided Contract Risk Review
Reviews a contract from both parties' perspectives, scoring each material risk and proposing balanced fallback language.
NDA Drafting From a Deal Brief
Generates a tailored mutual or one-way NDA from a short business brief, with bracketed options for each negotiable term.
Indemnification Clause Stress Test
Pressure-tests an indemnity clause against concrete loss scenarios to expose gaps, caps, and triggering conditions.