THE RIGHT DOCUMENT FOR THE JOB
When to use a statement of work
Use it for a project or work package under a broader service relationship. Align it before work begins, and issue a reviewed revision when material scope, timing, or ownership changes.
BEFORE YOU START
What to have ready
- Purpose, objectives, deliverables, and measurable acceptance criteria
- In-scope tasks, exclusions, client inputs, and working assumptions
- Named roles, decision rights, dependencies, and communication cadence
- Milestones, target dates, review windows, and delivery location or method
- Fees, expenses, invoicing triggers, change process, and governing documents
Deliverables and acceptance
Describe each output by format, quality, quantity, and due point. Explain who reviews it, how long review takes, what counts as a correction, and what happens if feedback is late. Avoid criteria that depend only on subjective satisfaction.
Responsibilities and assumptions
List the information, access, decisions, environments, and staff each party supplies. Connect a missed dependency to its possible schedule or cost effect. Keep assumptions visible so a changed premise can be discussed rather than treated as a surprise.
Changes and administration
Describe who may request a change, what impact information is required, and when work may proceed. Connect fees and invoicing to clear events. If the SOW sits under a master agreement, identify which document controls a conflict and seek local legal review when appropriate.
Common mistakes to avoid
- Listing activities without a testable description of the resulting deliverable
- Using a target date without stating the client dependency behind it
- Allowing informal requests to expand work without a documented decision
A FEW THINGS WORTH KNOWING
Statement of Work questions, answered
Can one SOW cover several phases?
Yes, if each phase has its own output, acceptance point, dependency, and commercial trigger. Separate phases when approval or funding decisions should occur between them.
What belongs in an SOW rather than a proposal?
Put agreed delivery detail in the SOW: scope, outputs, responsibilities, dates, and controls. Keep exploratory alternatives and persuasive background in the proposal unless the parties intentionally incorporate them.
Who should sign or approve an SOW?
Use the authority defined by the governing relationship and each organization’s purchasing process. Confirm the approvers can commit the stated budget and responsibilities before work starts.
A draft is the beginning—not the final review.
Check names, figures, dates, and every obligation before you use or sign your document. For legal, employment, property, or financial matters, consult a qualified local professional when needed. This is an AI drafting tool, not an official government form or a guarantee of legal validity.