A project scope describes what the organisation intends to achieve. A Statement of Work must describe what the supplier is actually expected to do.
The Week 6 study notes give detailed attention to the Statement of Work. They identify scope of work, work location, period of performance, deliverable schedule, applicable standards, acceptance criteria and special requirements as typical elements.
This is one of the most important translations in procurement.
Internal project language must become an external obligation clear enough for suppliers to price, perform and be assessed against.
The Strategic Context
Many commercial disputes begin with a scope document that everyone thought was clear.
The project team understood the background.
The supplier interpreted the words differently.
The contract then becomes a debate about what was included.
A strong SOW reduces that ambiguity by describing not just activities but boundaries, deliverables, conditions and evidence of acceptance.
It should be precise enough for accountability without prescribing unnecessary detail that prevents better delivery methods.
What Leaders Commonly Misread
The first mistake is copying the project scope statement into a tender and calling it an SOW.
The second is describing activities without defining outputs.
The third is writing acceptance criteria after the supplier has already delivered.
The fourth is omitting interfaces because “everyone knows” who owns them.
The fifth is hiding assumptions inside technical language instead of stating them explicitly.
Reframing the Issue
The SOW should be treated as a commercial interface specification.
It explains how the supplier's work connects with:
- project objectives;
- client responsibilities;
- site conditions;
- other contractors;
- schedule;
- standards;
- acceptance.
This makes it both a delivery and governance document.
Strategic Analysis: Ambiguity Becomes Variation
Hypothetical engineering example: A supplier is engaged to “install and commission” a machine.
Does that include:
- electrical isolation?
- new cable?
- network configuration?
- operator training?
- trial material?
- performance testing?
- disposal of packaging?
If the SOW does not say, each party may price a different scope.
The resulting variation is not necessarily evidence of supplier opportunism. It may be evidence that the buyer transferred ambiguity to the market.
The Week 6 source's inclusion of location, standards and acceptance criteria is therefore commercially significant.
Decision Framework
A robust SOW should answer seven questions.
Work
What must the supplier do?
Boundary
What is explicitly included and excluded?
Location
Where must performance occur?
Time
When must work start, finish and meet intermediate milestones?
Deliverables
What tangible outputs must be provided?
Standards
What technical, quality or other standards apply?
Acceptance
How will the buyer determine that performance is satisfactory?
These questions should be tested with people who did not write the document. If they interpret the scope differently, the market may too.
From Strategy to Execution
Immediate action: require acceptance criteria in the SOW before tender release.
Medium-term capability building: create cross-functional SOW reviews involving technical, operational, procurement and contract-management perspectives.
Long-term strategic positioning: build reusable scope patterns for recurring procurement categories while preventing templates from replacing project-specific thinking.
Governance Implication
A strong SOW should also separate supplier obligations from buyer-furnished inputs. If the buyer must provide drawings, utilities, data, approvals, access or free-issue materials, those dependencies should be visible beside the supplier's deliverables. This helps prevent later disputes in which each side assumes the other was responsible for an enabling activity.
For complex work, the SOW should also identify the evidence required at completion. A deliverable may exist physically but still be incomplete commercially if certificates, test records, software backups, drawings, training records or operating documentation are missing. Acceptance therefore needs to cover the complete information package required for future operation.
Leaders should resist the temptation to make the SOW infinitely detailed. Detail is useful when it clarifies accountability. It becomes harmful when it locks the supplier into an unnecessary method or creates contradictions with other contract documents. The goal is controlled clarity, not document volume.
The document hierarchy also matters. Where drawings, schedules, technical specifications and commercial conditions overlap, the contract should make clear how inconsistencies are resolved. A well-written SOW can still fail if another document quietly contradicts it. Procurement planning should therefore review the complete set of contractual documents as one system.
A simple final check is whether the SOW could be administered by a contract manager who did not participate in drafting. If not, too much meaning remains trapped in project memory rather than in the commercial document.
Signals to Monitor
Watch for high numbers of tender clarifications, supplier assumptions that redefine basic scope, repeated post-award debate over “included” work, acceptance based on subjective satisfaction and contract schedules that conflict with technical documentation.
Questions for the Leadership Team
- Can an external supplier understand the required outcome without relying on internal context?
- Are responsibilities at every major interface explicit?
- Do deliverables correspond to payment and schedule milestones?
- Are standards current and genuinely necessary?
- Are acceptance criteria measurable?
- Which assumptions would create a variation if they prove false?
Closing Perspective
The Statement of Work is where project intent becomes commercial accountability.
When that translation is weak, the contract inherits ambiguity.
When it is strong, suppliers can price the same requirement the organisation actually intends to buy.
Related article: Contract Certainty: Why Vague Agreements Transfer Control Away From the Parties
Related article: Write Requirements Suppliers Can Actually Bid Against
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.