Statement of Work vs. Master Service Agreement: How the Two Work Together in Ontario

Businesses that expect to work with the same vendor or contractor across multiple projects rarely negotiate a full contract from scratch every time. Instead, they typically use a two-document structure: a Master Service Agreement (MSA) that sets the ground rules once, and a series of Statements of Work (SOWs) that define each individual project.

Understanding how these two documents divide responsibilities — and what happens when they conflict — matters whether you're the client or the service provider.

What a Master Service Agreement Covers

An MSA is the umbrella contract that governs the overall relationship between the parties. It typically addresses the terms that should stay consistent across every project, including:

• Payment terms and invoicing procedures
• Intellectual property ownership and licensing
• Confidentiality obligations
• Limitation of liability and indemnification
• Warranties
• Termination rights and dispute resolution

The MSA is negotiated once, ideally before the parties are under time pressure to start a specific project, which generally leads to better terms than negotiating everything from scratch mid-engagement.

What a Statement of Work Covers

A SOW is a project-specific document executed under the umbrella of an existing MSA. It typically defines:

• The specific scope of work and deliverables for that project
• The timeline and key milestones
• The price or fee structure for that particular engagement
• Acceptance criteria — how the parties will agree the deliverables meet requirements
• Any project-specific personnel, dependencies, or assumptions

A well-drafted SOW is detailed enough that scope disputes are rare, while staying short enough that it doesn't need to repeat the general legal terms already sitting in the MSA.

How the Two Documents Relate to Each Other

The MSA and each SOW are meant to work as one integrated agreement, not two separate contracts. A properly structured MSA typically states, expressly, that:

• Every SOW is governed by, and incorporates, the terms of the MSA
• If a SOW's terms conflict with the MSA, the MSA generally controls — unless the SOW expressly and specifically states that it overrides a particular MSA provision
• Terminating a single SOW does not automatically terminate the MSA itself, and vice versa, unless the agreement says otherwise

This order-of-precedence language is one of the most important — and most often overlooked — clauses in the whole structure, because it determines what happens the moment the two documents say something different.

A Typical MSA + SOW Relationship in Practice

1. The parties negotiate and sign one MSA covering the general legal terms of the relationship.
2. When a new project comes up, the parties sign a short SOW that references the MSA and defines that project's scope, price, and timeline.
3. The MSA's terms — liability caps, IP ownership, confidentiality, termination rights — apply automatically to that project without needing to be renegotiated.
4. As more projects arise, each gets its own SOW under the same MSA, keeping the legal terms consistent while the scope of work changes.

Common Problems When the Two Don't Line Up

• A SOW silently tries to change a key MSA term, such as a higher liability cap or different IP ownership, without expressly saying so — creating ambiguity about which document controls
• The MSA has no order-of-precedence clause at all, leaving a genuine conflict unresolved
• Scope creep occurs mid-project with no formal SOW change-order process, so it's unclear whether the original price and timeline still apply
• A SOW is signed by someone without the individual authority to bind the company beyond what the MSA contemplated

Checklist for a Sound MSA/SOW Structure

• [ ] The MSA includes a clear order-of-precedence clause addressing conflicts with a SOW
• [ ] Every SOW expressly references and incorporates the governing MSA
• [ ] The MSA includes a defined process for changing an in-progress SOW's scope, price, or timeline
• [ ] Termination provisions clarify whether ending one SOW affects the MSA, and vice versa
• [ ] Each SOW is specific enough on deliverables and acceptance criteria to prevent scope disputes

Frequently asked questions