Master Services Agreement (MSA)

A master services agreement sets the rules for a relationship in which one business provides services to another repeatedly or over a long period: software development, managed IT, marketing, consulting, engineering, logistics or staffing. The MSA holds the terms that rarely change from project to project. The commercial detail of each engagement goes into a statement of work (SOW), sometimes called an order, work order or service order.

Many MSAs state that neither party must buy or perform anything until a SOW is signed. Each signed SOW then incorporates the MSA's terms. A typical contract stack includes:

• the MSA itself
• signed SOWs or order forms
• schedules that apply across projects, such as a service level agreement (SLA), a data processing addendum and a security schedule
• change orders that amend a SOW's scope, timeline or price

For a single, self-contained engagement, a stand-alone contract is usually simpler; Lamba Law's service and consulting agreement template covers that case.

The order of precedence clause decides which document wins when they conflict. The usual rule is that the MSA prevails over a SOW unless the SOW expressly identifies the MSA section it overrides. Without that rule, a project lead could sign a SOW containing an uncapped data-loss indemnity and quietly undo the liability cap the parties negotiated. The same clause should say that pre-printed terms on a purchase order or invoice have no effect, so the customer's procurement system does not replace the MSA.

Name in the MSA who may sign SOWs and change orders for each party. Put the promises from the sales proposal into the SOW itself, because an entire agreement clause will usually exclude anything that appears only in a slide deck or email.

Scope, acceptance and change control. A SOW should describe deliverables precisely enough to test them, set acceptance criteria and a review period, and say whether silence after that period counts as acceptance. A change-order process requiring written approval before extra work starts prevents most fee disputes.

Service levels. An SLA defines a measurable standard, such as monthly availability or response times by severity, with stated exclusions and a calculation method. Service credits, a fee reduction for missed targets, are common. The MSA should say whether credits are the sole remedy and whether repeated misses allow termination.

Intellectual property. Under section 13 of the Copyright Act, the author of a work is generally its first owner, and an assignment of copyright is valid only in writing signed by the owner. Paying an independent provider for code or designs does not by itself transfer ownership; the MSA or SOW needs an IP assignment of the deliverables. A common compromise gives the customer ownership of custom deliverables on payment, while the provider keeps its pre-existing tools and know-how (background IP) and licenses whatever is built into the deliverables.

Liability caps and indemnities. MSAs commonly exclude indirect losses and cap each party's total liability, often by reference to fees paid over a recent period. Whether the cap applies per SOW or across all SOWs can change the number dramatically. Carve-outs commonly cover confidentiality breaches, data incidents, IP infringement claims and wilful misconduct. Read the limitation of liability clause and the indemnification clause together, because a broad indemnity can sit outside the cap.

Time limits for claims. An MSA can also shorten the time to bring a claim. Ontario's basic limitation period is two years from discovery. In a business agreement, one in which no party is a consumer, section 22 of the Limitations Act, 2002 lets the parties vary or exclude that period, and varying includes shortening it.

People. If the customer directs the provider's staff day to day, the line between employee and independent contractor can blur for those individuals. Mutual non-solicitation clauses for key staff are common.

The MSA and each SOW usually have separate terms, so the MSA should state what happens to SOWs in progress when it ends. Often they continue on the MSA's terms until completed or terminated. Termination provisions to settle include:

• termination for convenience on written notice, with payment for work performed and agreed wind-down costs
• termination for material breach after a cure period
• termination for insolvency or chronic SLA failure
• transition assistance, return of data and survival of confidentiality, IP and payment terms

A right to terminate for any reason must still be exercised honestly. In C.M. Callow Inc. v. Zollinger, 2020 SCC 45, condominium corporations could end a winter maintenance contract on ten days' notice for any reason. The Supreme Court of Canada held that they did not have to announce their decision early, but breached the duty of honest performance by actively misleading the contractor into believing the contract would not be ended early. The duty of good faith in contracts entry covers the case in detail.

MSAs commonly prohibit assignment without consent. In a share sale the contracting corporation stays the same, but a change of control clause may give the other party a consent or termination right. In an asset sale, the buyer needs the MSA assigned, or replaced by novation if the seller is to be released.

An MSA governs services. A contract to deliver goods over time is a supply agreement, which in Ontario brings in the Sale of Goods Act's implied conditions. Where a provider delivers both, such as hardware with installation and support, the documents should say which terms govern each part.

A SaaS subscription sits between the two: the customer gets access to a hosted service rather than a copy of software. Vendors often use the same architecture as an MSA, a master subscription agreement with order forms, combined with an SLA and a data processing addendum. Our SaaS agreement checklist compares vendor and customer positions on those terms, and the SaaS legal structure entry covers the wider issues for software companies. Lamba Law's business agreements and contracts practice drafts and negotiates MSAs for providers and customers.

Amira Haddad runs operations at Northbridge Building Supply Inc., a Mississauga distributor that sells lumber and drywall to contractors across the GTA. Northbridge signs an MSA with Kestrel Code Ltd., a Markham developer owned by Daniel Okafor. SOW 1 is a fixed-fee build of an online ordering portal for $180,000. SOW 2 is hosting and support at $6,000 a month, with a 99.5% monthly availability target and service credits capped at 25% of the monthly fee.

Kestrel's draft capped its liability at fees paid in the previous 12 months under the SOW giving rise to the claim. Northbridge's lawyer negotiated the cap up to the greater of $150,000 and all fees paid under the MSA in that period, kept data loss and IP claims outside it, and added an assignment of the portal's code on final payment, with Kestrel licensing its reusable libraries.

Eight months into SOW 2, a faulty update takes the portal down for three days. Northbridge documents $95,000 in temporary order-desk staff, rush deliveries and credits to contractors whose orders arrived late. Kestrel's original wording would have limited recovery to the $48,000 paid under SOW 2. The negotiated cap, by then $228,000 (the $180,000 build fee and eight hosting payments, all paid within the previous 12 months), covered the whole claim. After Kestrel disputed some of the contractor credits, the parties settled at $82,000 plus the maximum $1,500 service credit, and Northbridge ended SOW 2 under the convenience clause, moved hosting to a new provider and kept the code it owned.