Statement of Work (SOW)

In Canadian federal procurement, a Statement of Work (SOW) is the narrative description of the work required under a contract: it stipulates the deliverables or services needed to fulfill the contract, becomes part of the resulting contract, and is one of the documents always referred to when disputes arise about what work was actually required.

What it is

Per Public Works and Government Services Canada's official guidance, "The Statement of Work (SOW) is a narrative description of the work required and stipulates the deliverables or services required to fulfill the contract. It defines the task to be accomplished or services to be delivered in clear, concise and meaningful terms." The same guidance stresses that the SOW becomes part of the resulting contract, that nothing should be assumed or left unsaid in it, and that if a conflict arises about the work required, the statement of work is one part of the contract always referred to in resolving disputes. It is developed during the requirement-definition phase (Supply Manual chapter 2, and section 4.30.1 "Requirement and Statement of Work" for what goes into the solicitation).

Qualities of a good SOW

PWGSC's guidance lists what a good SOW does: it defines the nature, extent and quality of the good or service required; it is clear and complete; it is written to allow free competition between vendors; it is written in the imperative mood; and it respects the legal framework, policies, rules and socioeconomic objectives regulating the goods and services being procured. The client department is responsible for developing the Statement of Work — not the contracting officer.

What goes into it

CanadaBuys' procurement-planning guidance says a client's SOW should include a brief introduction, the purpose of the project, the project scope, a work breakdown structure identifying tasks, milestones and deliverables, a project schedule, project requirements and acceptance criteria, and payment terms and conditions. In a bid solicitation, the SOW sits alongside the evaluation criteria and the resulting contract clauses — together they define what you must do, how it will be judged, and on what terms.

What it means for vendors

Before bidding, read the SOW as the future contract it will become: anything ambiguous cuts against you after award, because the SOW is the fallback document in any performance dispute. If the SOW leaves room for interpretation, ask questions during the solicitation Q&A period rather than assuming scope. And scope creep has a formal answer in federal services contracting — additional work is handled by task authorizations or a formal contract amendment, not by informal requests.

Common questions

Is the SOW the same as a specification?

No. The SOW describes the work, deliverables and schedule in narrative form; specifications set the technical characteristics of what must be delivered. A solicitation can contain both, and the Supply Manual treats them as distinct parts of the requirement.

Does a task-based contract use a SOW?

Task-based services on standing offers and supply arrangements still flow from defined work requirements, but they are triggered through task authorizations rather than a one-time SOW in a solicitation. The underlying requirement definition discipline is the same.

What happens if the SOW conflicts with the contract clauses?

That is why PWGSC says nothing should be assumed or left unsaid in the SOW: conflicts within solicitation documents should be raised and resolved during the solicitation period. After contract formation, disputes over the work required are resolved by looking at the SOW as part of the contract — escalating internally first, then through the OPO and CITT channels if needed.

Related definitions

Bid solicitation · Acceptance criteria · Task authorization · Evaluation criteria weighting