Draft a scope of work for [PROJECT NAME] between [PARTIES AND ROLES]. The business objective is [OBJECTIVE]. The requested work and deliverables are [WORK AND DELIVERABLES]. The known timeline, budget or commercial limits, and dependencies are [CONSTRAINTS AND DEPENDENCIES]. The acceptance requirements and exclusions are [ACCEPTANCE AND OUT-OF-SCOPE]. Produce a 750–1,000 word SOW with these sections: 1. Project purpose and intended business outcome. 2. Scope of services, broken into workstreams and specific deliverables. 3. Deliverable table with description, owner, format, milestone, client or internal dependency, and acceptance criteria.
4. Roles and responsibilities, including who approves changes and who provides source materials or access. 5. Timeline and milestones, with assumptions behind dates rather than invented commitments. 6. Explicit out-of-scope items. 7. Assumptions, dependencies, risks, and change-control procedure. 8. Acceptance and closeout: review window, revision limits if supplied, handoff materials, and definition of completion. Use precise verbs and observable deliverables. Separate objectives from deliverables; "improve awareness" is an objective, while a campaign plan or report is a deliverable. Do not invent pricing, legal terms, dates, staffing, service levels, intellectual-property rights, or approval authority. This is a working draft, not a substitute for contract or legal review. Before answering, check that every deliverable has an owner and acceptance criterion, and that no timeline depends on an unstated input or approval. Flag vague terms such as "support," "as needed," or "finalize" and propose questions that would make them testable. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROJECT NAME] | Enter the project or engagement name. | Website analytics migration |
| [PARTIES AND ROLES] | Enter the client, vendor, internal teams, and named roles involved. | Brightside Retail marketing team; Atlas Digital implementation consultant; marketing director approves; IT grants tag-manager access. |
| [OBJECTIVE] | Enter the business result the project is intended to achieve. | Replace legacy analytics with a reliable GA4 reporting setup before holiday campaign reporting begins. |
| [WORK AND DELIVERABLES] | Enter the requested activities and the concrete outputs expected. | Analytics inventory, measurement plan, GA4 property configuration, tag implementation, testing report, dashboard specification, and two training sessions. |
| [CONSTRAINTS AND DEPENDENCIES] | Enter known dates, budget limits, access needs, approvals, and dependencies. | Target completion October 15; IT must provide access within five business days; consultant cannot modify checkout code; marketing provides event priorities. |
| [ACCEPTANCE AND OUT-OF-SCOPE] | Enter how work will be accepted and what work is specifically excluded. | Acceptance requires all priority events firing in test and a signed testing report; excluded: CRM integration, media buying, and ongoing dashboard maintenance. |
How to use
- List deliverables as files, configurations, reports, training sessions, or other observable outputs before pasting the prompt.
- Name the person or role that can accept each deliverable; project participants are not automatically approvers.
- Check the draft for hidden assumptions about access, source material, and approval turnaround time.
- Follow up with: "Turn the deliverable table into a milestone plan with dependencies and a weekly status-report template."
Variations
Vendor brief
Use before soliciting proposals from several vendors.
Write a vendor scope brief for [PROJECT] based on [BUSINESS NEED AND DELIVERABLES]. Include [TIMELINE, BUDGET RANGE IF SHARED, AND CONSTRAINTS]. Produce sections for background, objectives, required services, mandatory vendor qualifications, requested proposal format, selection criteria, timeline, and exclusions. Make deliverables measurable and identify client-provided inputs. Do not promise a contract, disclose an unapproved budget, or invent technical requirements. Flag requirements that need legal, security, procurement, or technical-owner review.
Change request
Use when requested work exceeds the agreed project scope.
Draft a change request for [PROJECT] covering [NEW REQUEST]. The original agreed scope was [ORIGINAL SCOPE], and the impact evidence is [EFFORT, TIMELINE, OR DEPENDENCY DETAILS]. Produce a concise document with requested change, rationale, affected deliverables, options, cost or schedule impact only if provided, decision needed, and approval field. Do not state that work is approved or begin from an assumed estimate. Flag missing acceptance criteria or decision authority.
Internal project charter
Use for an internal initiative that needs alignment but not a vendor contract.
Create a one-page internal project charter for [INITIATIVE]. The sponsor and team are [ROLES], the problem is [PROBLEM], and proposed work is [SCOPE]. Use [TIMELINE AND DEPENDENCIES] to produce objectives, in-scope work, out-of-scope work, milestones, responsibilities, success measures, risks, and decisions required. Do not create targets, staffing commitments, or executive approval. Check that success measures can be measured from an identified source.
Tips
- A strong SOW makes acceptance observable: specify the format, test, review owner, and deadline rather than saying a deliverable must be "satisfactory."
- Put exclusions in their own section; buried exclusions are often missed during kickoff and become unpaid or unplanned work.
- Make client inputs and access dependencies explicit, including what happens when they arrive late.
- Treat a changed requirement, added deliverable, or altered acceptance test as a change request, not an informal comment in a status meeting.
FAQ
What should be included in a scope of work?
Include the objective, services, deliverables, responsibilities, milestones, assumptions, exclusions, acceptance criteria, and a method for approving changes. Commercial and legal terms may belong in a separate agreement.
What is the difference between a scope of work and a statement of work?
Organizations use the terms differently. A scope of work often describes the work boundaries, while a statement of work may be the fuller contract document containing scope plus commercial and legal terms.
Can AI write an SOW from a proposal?
Yes, as a draft, but compare each promise in the proposal with the SOW and resolve differences before signature. Have the appropriate commercial and legal reviewers approve binding terms.