← IndexEntry № 144·legal

Draft a Statement of Work With Scope and Deliverables

Drafts a structured SOW with deliverables, milestones, and acceptance criteria, plus flagged assumptions and a review reminder.

Optimized for
ChatGPTClaude
§ When to use this

A statement of work translates a master agreement into a concrete project: what gets built, by when, for how much, and how you know it is done. This prompt drafts an SOW that references an existing MSA rather than restating it, keeping the document focused on scope, deliverables, milestones, and acceptance. Clear acceptance criteria and a defined change-order process are what prevent scope disputes later, so the prompt foregrounds both. It also separates assumptions and dependencies, which is where consultants most often get caught when a client expectation was never written down. This output is a drafting aid, not legal advice. Because the SOW sits under a governing MSA, the two documents must align on precedence and defined terms, and a qualified attorney should confirm that before signature. Use the assumptions list to flag anything you need to verify with stakeholders.

§ The Prompt— fill in the fields, then copy or open in a tool
§ Customize0/5 fields filled
your prompt — fill the fields above
You are an experienced contract drafting assistant. Draft a statement of work under an existing master services agreement between [PROVIDER] and [CLIENT] for the project [PROJECT NAME]. Include a scope description, itemized deliverables, milestone schedule with [TIMELINE], acceptance criteria, fees of [FEE STRUCTURE], assumptions and dependencies, and a change-order process. Reference the governing MSA rather than restating its terms. Use numbered sections and a deliverables table. After the draft, list every assumption you made and flag anything I should confirm with stakeholders. End by recommending attorney review, since this is a drafting aid and not legal advice.
Open with your prompt →ChatGPTClaudeSends your filled-in prompt straight into a new chat.
§ Example Output

What you can expect back

STATEMENT OF WORK NO. 1
Under the Master Services Agreement between Lumen Consulting and Harbor Health Systems.

1. Project: Patient Portal Redesign.
2. Scope: Discovery, UX design, and front-end build of the patient portal.
3. Deliverables:
| # | Deliverable | Due |
| 1 | Research findings | Week 2 |
| 2 | High-fidelity designs | Week 5 |
| 3 | Production-ready front end | Week 10 |
4. Fees: Fixed fee of $48,000 billed at milestones 1-3.
5. Acceptance: Client has 5 business days to accept or provide written deficiencies.
6. Assumptions/Dependencies: Client provides API access and brand assets by Week 1.
7. Change Orders: Scope changes require a signed change order.

Assumptions: single SOW; client-side resources available. Confirm API readiness with stakeholders. Drafting aid only, not legal advice; have an attorney review.

Illustrative example — your results will vary by tool and inputs.

§ Pro Tips

Get sharper results

  • 01Write acceptance criteria you can objectively test; vague criteria like 'works well' invite disputes.
  • 02List client-side dependencies explicitly so delays caused by the client do not become your problem.
  • 03Make sure fees and milestones in the SOW reconcile with the payment terms in the governing MSA.
  • 04Have counsel confirm the SOW aligns with the MSA's precedence and IP terms before both parties sign.
§ Variations

Adapt it for your case

Time-and-materials version

Switch the fee structure to hourly rates with a not-to-exceed cap and rate table.

Add an SLA section

Request a service-level section with response times and remedies if the project includes ongoing support.

Milestone-only summary

Ask for a one-page milestone and payment schedule to share with finance.

Best For — Roles
Use For — Tasks
Tags#sow#deliverables#scope
§ FAQ

Common questions

Is this legal advice?

No. It is a drafting aid that produces an SOW template. A qualified attorney should confirm it aligns with your governing MSA before signing.

Does it restate the MSA terms?

No. By design it references the master agreement and only covers project-specific scope, deliverables, and fees to avoid conflicting language.

What if there is no MSA in place?

Then the SOW alone may be insufficient. Consider a standalone services agreement, and have counsel advise on the right structure.

§ Related Entries

You may also need