How to use the Statement of Work Generator.
A statement of work needs boundaries as well as deliverables. Define responsibilities, acceptance and change handling before polishing the wording.
Make the workflow fit your task.
Define deliverables, exclusions, responsibilities and acceptance criteria together. Connect revision limits and dependencies to a change process, leaving unagreed dates or commercial terms explicitly unresolved before review.
- What you provide
- Agreed scope, deliverables and responsibilities.
- What you get
- SOW draft with exclusions and acceptance conditions.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Draft a scope section for three landing pages: Home, Services and Contact. Includes one consolidated revision round. Client supplies approved copy and branding before design. Acceptance means the pages match the agreed copy, branding and page list; no backend integration included.
Completed example
Deliverables: Home, Services and Contact landing pages using the approved copy and branding. Client inputs: final copy and brand assets before design begins. Revisions: one consolidated round addressing the supplied feedback. Acceptance basis: the agreed page list, approved copy and branding. Exclusion: backend integration is outside this scope. Changes: additional pages, revision rounds or integrations require a separate scope decision. Commercial terms and delivery dates are not supplied in this example.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a statement of work include exclusions?
Yes, when they clarify likely misunderstandings. State what is outside the agreed deliverables without relying on vague assumptions about normal practice.
Why does a revision request create a scope dispute?
Compare it with the deliverable and acceptance definitions. Clarify whether it corrects agreed work or adds a new requirement.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑