MSA Anatomy — Master Agreement vs SOW Hierarchy & Order of Precedence
A Master Service Agreement sits at the top of a two-tier (sometimes three-tier) contract stack. The MSA establishes the permanent legal framework — liability, IP ownership, confidentiality, indemnification, dispute resolution, payment defaults. Below it, individual Statements of Work (SOWs), Work Orders, or Order Forms describe specific projects: deliverables, timelines, fees, milestones, and acceptance criteria.
| Document | What It Contains | Typical Length | Renegotiated How Often? |
|---|---|---|---|
| MSA | IP, liability, confidentiality, indemnification, payment defaults, termination, dispute resolution | 10–30 pages | Once (at relationship start) |
| SOW / Work Order | Project scope, deliverables, timeline, fees, milestones, acceptance criteria | 2–10 pages | Per project |
| Change Order | Modifications to active SOW — added scope, adjusted timeline, revised fee | 1–3 pages | Per scope change |
The order of precedence provision — which document controls on conflict — is one of the most consequential clauses in the entire MSA. The standard enterprise position is MSA controls unless the SOW expressly states otherwise. This protects the client from vendors sneaking favorable terms into individual SOWs. But it also means every SOW silently inherits the MSA's legal framework unless a specific override is written in.
Key Principle
A third document tier sometimes appears: exhibits or schedules attached to the MSA (SLA exhibit, data processing addendum, security requirements schedule). These rank below the MSA body unless the MSA explicitly elevates them. Know the full document stack before you negotiate any single provision.
Does your MSA protect you?
Get an instant AI review — red flags, one-sided clauses, and plain-English analysis in under 60 seconds.
Check My MSA Free →Standard Form vs Negotiated MSAs — Adhesion Contract Risks & Duty to Read
Enterprise clients frequently present MSAs as standard, non-negotiable forms. From a legal standpoint, these are adhesion contracts — agreements offered on a take-it-or-leave-it basis where the weaker party had no meaningful opportunity to negotiate. Adhesion status does not automatically invalidate an agreement, but it does make certain provisions vulnerable to a two-part unconscionability challenge:
- Procedural unconscionability: Was the agreement presented fairly? Was the weaker party given time to review? Were onerous terms buried in fine print?
- Substantive unconscionability: Is the challenged term oppressively one-sided, such that no reasonable party would voluntarily agree to it?
The duty to read doctrine cuts the other way: a party who signs a contract is generally bound by its terms even without reading them. In ProCD v. Zeidenberg (7th Cir. 1996), the court enforced shrinkwrap license terms the buyer could only access after purchase, holding that the buyer had a reasonable opportunity to read and return the product. For business parties dealing at arm's length, "I didn't read the MSA" is rarely a successful defense.
Red Flag
If you receive a "non-negotiable" MSA, the practical move is to identify the three to five provisions with the most financial exposure and propose targeted redlines on those. Many enterprise clients who claim the MSA is non-negotiable will accept changes on specific high-exposure provisions if the redlines are commercially reasonable and clearly explained.
What to Do
See also: Indemnification Clause Guide and Limitation of Liability Guide for deeper analysis of these two high-exposure provisions.
Key MSA Clauses Deep Dive — IP Ownership, Change Orders, Acceptance Testing & SLAs
Intellectual Property Ownership
IP ownership is the most frequently misunderstood and most financially consequential clause in any MSA. The core distinction is between background IP (tools, frameworks, methodologies, and code the vendor built before or outside this engagement) and foreground IP (deliverables created specifically for the client under this SOW).
Red Flag
The vendor-protective solution: retain ownership of all background IP and grant the client a perpetual, non-exclusive license to use background IP embedded in deliverables. Assign only the project-specific foreground IP that the client actually needs. Include a retained IP schedule listing specific tools and frameworks retained by the vendor.
Change Orders
A change order is the contractually required mechanism for modifying scope, timeline, or price under an active SOW. The standard provision requires change orders to be in writing and signed by authorized representatives before the vendor performs out-of-scope work.
Watch Out
Acceptance Testing
An acceptance testing clause defines how the client formally approves deliverables before the vendor's payment obligation triggers. A complete acceptance testing provision specifies: (1) a testing window (typically 10–30 days after delivery); (2) objective acceptance criteria tied to SOW specifications; (3) a process for notifying the vendor of defects; (4) a vendor cure period; and critically, (5) a deemed-acceptance provision — if the client does not respond within the testing window with specific written objections, the deliverable is deemed accepted.
What to Do
Service Level Agreements (SLAs)
SLAs define measurable performance standards and the remedies for failure. They may appear in the MSA body, a dedicated SLA exhibit, or individual SOWs. Key SLA provisions to scrutinize:
- Measurement methodology: Is uptime calculated on a calendar month or rolling 30 days? Scheduled maintenance excluded? Who measures — vendor self-reporting or a third-party tool?
- Remedies: Are service credits the exclusive remedy for SLA failure, or does the client also retain termination rights for chronic underperformance?
- Credit caps: Many SLA exhibits cap total credits at a small percentage of monthly fees — often 10–30% — even for complete outages.
- Force majeure carve-outs: Broad force majeure clauses can excuse SLA failures that were actually caused by vendor infrastructure decisions.
See also: Scope of Work Clause Guide for detailed guidance on drafting enforceable deliverable specifications.
SOW Management — How SOWs Interact With MSA Terms & Conflict Resolution
Every SOW executed under the MSA is governed by the MSA's legal framework unless the SOW contains an explicit override. This means a vendor who negotiated a 12-month liability cap in their MSA in year one is protected by that cap for every SOW they execute in years two, three, and four — unless a later SOW explicitly expands liability. The same applies in reverse: an unfavorable indemnification provision in the MSA silently applies to every SOW.
Key Principle
Common SOW-MSA conflicts and how courts resolve them:
- Payment terms: MSA says net-60; SOW says net-30. If MSA controls, the client gets 60 days. If SOW controls on commercial terms, net-30 applies. Ambiguity creates disputes — specify which document controls on payment.
- IP scope: MSA assigns "all deliverables" to client; SOW describes deliverables that include vendor background IP. Conflict — the SOW should explicitly carve out background IP or reference the MSA's background IP definition.
- Termination rights: MSA allows termination for convenience with 30 days' notice; SOW contemplates a 90-day project. If the client terminates for convenience on day 10, the 30-day notice period may require payment through day 40 of a 90-day project — leaving the vendor significantly undercompensated. SOW-specific termination language should address compensation for partially completed work.
See also: Termination Clause Guide for detailed guidance on termination for convenience, kill fees, and post-termination obligations.
Does your MSA protect you?
Get an instant AI review — red flags, one-sided clauses, and plain-English analysis in under 60 seconds.
Check My MSA Free →Vendor vs Client MSA — Different Risk Profiles & Who Drafts Matters
The risk profile of an MSA shifts dramatically depending on whether you are the vendor (service provider) or the client (buyer of services) — and on whether you drafted the agreement or are reviewing the other side's form.
| Clause | Vendor Wants | Client Wants | Balanced Middle |
|---|---|---|---|
| IP Ownership | License to client; vendor retains all IP | Full assignment of all work product | Assign foreground IP; license background IP |
| Liability Cap | Cap at fees paid; broad consequential damages exclusion | High cap; carve-outs for IP breach, data breach, fraud | Mutual cap at 12-month fees; mutual consequential damages exclusion |
| Indemnification | Fault-based, mutual, capped | Broad vendor indemnification including IP, data, regulatory | Mutual fault-based; IP indemnification from vendor; data indemnification from client if client provides data |
| Termination | Long notice periods; payment for all completed work | Short notice; minimal kill fee; right to terminate immediately for cause | 30-day notice for convenience; payment through notice period; 15-day cure for non-monetary breach |
| Dispute Forum | Vendor's home jurisdiction | Client's home jurisdiction | Neutral forum (Delaware, AAA arbitration) |
See also: Confidentiality Clause Guide for detailed analysis of mutual vs one-sided NDA provisions that commonly appear in MSA confidentiality sections.
Industry-Specific MSAs — IT/Consulting, Construction, Marketing/Creative & Staffing
IT & Technology Consulting
IT MSAs carry the highest IP complexity. Key issues: source code ownership, SaaS access rights vs code ownership, data processing addenda (required for GDPR/CCPA compliance), security requirements schedules, and software escrow for mission-critical deliverables. Watch for work for hire classifications that apply to software — courts have split on whether software development qualifies as a work for hire under the Copyright Act, so explicit IP assignment language is always safer than relying on work-for-hire doctrine.
Construction & Engineering
Construction MSAs (often paired with master subcontracts) involve additional complexity: mechanic's liens, prevailing wage requirements, insurance and bonding obligations, flow-down clauses from prime contracts, and pay-when-paid vs pay-if-paid provisions. AIA standard form agreements (A201, B101) have their own priority-of-terms framework that interacts with owner-drafted MSAs.
Marketing & Creative Services
Creative MSAs have two unique issues: (1) moral rights — some jurisdictions (California, international) give creators rights to attribution and to object to mutilation of their work, which can conflict with client IP assignments; (2) portfolio rights — agencies typically want the right to display client work in their portfolio; clients may want to restrict this. Address both explicitly in the MSA.
Staffing & Managed Services
Staffing MSAs add worker classification risk. If the MSA describes workers as independent contractors but the day-to-day working relationship looks like employment (client controls hours, provides tools, sets procedures), the client may face misclassification liability. Anti-hire provisions (prohibiting the client from directly hiring the vendor's staff) are standard but must be reasonable in duration and scope to be enforceable.
See also: Intellectual Property in Contracts for a full analysis of work-for-hire, assignment, and moral rights provisions.
MSA Lifecycle — Renewal, Amendment Procedures & Evergreen Clauses
An MSA typically has an initial term (one to three years) with automatic renewal unless a party provides written non-renewal notice within a specified window. This is the evergreen clause — and it is one of the most commonly overlooked provisions in long-running vendor relationships.
Watch Out
Amendment procedures define how the MSA itself can be changed during its term. Standard provisions require a written amendment signed by authorized representatives of both parties. Red flags in amendment clauses:
- Unilateral amendment rights: Enterprise vendors (SaaS, staffing agencies, large consulting firms) sometimes include provisions allowing them to amend the MSA with 30 days' written notice. In Caspi v. Microsoft (NJ App. Div. 1999), the court upheld a clickwrap forum selection clause — but unilateral amendment rights remain more vulnerable to unconscionability challenges than bilateral amendment requirements.
- Informal modification doctrines: Some courts enforce course-of-dealing modifications that contradict written amendment requirements — e.g., if both parties consistently acted as if a particular MSA term did not apply, a court may find it was informally waived. Document every intentional deviation from MSA terms with a written amendment to avoid creating unintended modifications.
Survival clauses specify which MSA provisions continue to be binding after the agreement expires or is terminated. Provisions that should survive: confidentiality, IP assignment, indemnification, limitation of liability, dispute resolution, and governing law. A survival clause that is silent about specific provisions creates ambiguity — courts will look to the nature and purpose of each provision to determine whether it was intended to survive.
What to Do
Does your MSA protect you?
Get an instant AI review — red flags, one-sided clauses, and plain-English analysis in under 60 seconds.
Check My MSA Free →6 Landmark Cases Every Party Should Know
Williams v. Walker-Thomas Furniture Co.
D.C. Circuit Court of Appeals · 1965
Holding
The court established that contracts of adhesion could be invalidated as unconscionable when they result from a gross inequality of bargaining power and contain oppressive terms that one party had no meaningful opportunity to understand or reject.
Why It Matters
The foundational unconscionability case in American contract law. Established the procedural/substantive unconscionability framework used in virtually every subsequent challenge to standard-form agreements, including MSAs. A vendor or client challenging an oppressive MSA provision will invoke this doctrine.
Carnival Cruise Lines, Inc. v. Shute
U.S. Supreme Court · 1991
Holding
Enforced a forum selection clause printed on the back of a cruise ticket — a standard form contract — even though the passengers never saw or negotiated the clause before purchase.
Why It Matters
Established that forum selection clauses in standard form contracts are presumptively enforceable in federal courts, even in adhesion contracts, so long as they do not violate fundamental fairness. Directly supports enforceability of MSA forum selection clauses against the weaker party. The practical message: the jurisdiction clause in your MSA will likely be enforced even if you never negotiated it.
AT&T Mobility LLC v. Concepcion
U.S. Supreme Court · 2011
Holding
The Federal Arbitration Act preempts state laws that categorically invalidate class arbitration waivers in adhesion contracts. California's rule treating class action waivers in adhesion contracts as unconscionable was preempted.
Why It Matters
The single most important arbitration case of the modern era. After Concepcion, arbitration clauses with class action waivers in MSAs are broadly enforceable across the U.S. — even if the arbitration is effectively cost-prohibitive for smaller claims, and even if state law would otherwise invalidate the waiver. Review every MSA arbitration clause: if it prohibits class actions and requires individual arbitration, claims aggregation is off the table.
Broemmer v. Abortion Services of Phoenix, Ltd.
Arizona Supreme Court · 1992
Holding
Invalidated a mandatory arbitration clause in a standard medical service form signed under time pressure, finding it procedurally unconscionable because the patient was in a vulnerable position and was not told the arbitration provision was optional.
Why It Matters
A key counterweight to Concepcion in state courts. Demonstrates that when a contract is presented in a high-pressure context without clear explanation of the arbitration requirement, procedural unconscionability can still invalidate the clause. MSA recipients who were pressured to sign quickly — or who were not told arbitration was mandatory — may have viable unconscionability arguments in Arizona and states with similar standards.
Caspi v. Microsoft Network, LLC
New Jersey Appellate Division · 1999
Holding
Enforced a forum selection clause in a clickwrap MSN subscriber agreement, holding that users who clicked "I Agree" after being given the opportunity to scroll through the terms were bound by those terms including the forum selection clause.
Why It Matters
The foundational clickwrap enforceability case. Establishes that clicking through a standard-form agreement — even without reading it — creates a binding contract, provided the terms were reasonably accessible and the user had notice of them. Directly supports enforceability of online MSAs, master terms of service, and vendor portal agreements. If you accepted a vendor MSA via a checkbox, you are bound by its terms.
ProCD, Inc. v. Zeidenberg
7th Circuit Court of Appeals · 1996
Holding
Enforced shrinkwrap software license terms that the purchaser could only read after opening the package, holding that a buyer who is given the opportunity to read terms and return the product for a full refund is bound by those terms if they choose to keep the product.
Why It Matters
Established the duty to read doctrine as applied to standard-form commercial agreements. Supports the enforceability of MSAs and standard vendor agreements even when the contracting party did not actually read the terms. The practical consequence: "I didn't read the MSA" is not a defense to enforcement, provided the terms were reasonably accessible. Used by vendors to enforce IP, liability, and payment terms that clients claim they did not understand.
15-State MSA Law Table
Unconscionability standard, forum selection enforceability, arbitration clause standard, amendment requirements, and key precedent for 15 major states.
| State | Unconscionability Standard | Forum Selection | Arbitration Standard | Amendment Requirements | Key Precedent |
|---|---|---|---|---|---|
| CA | Procedural + substantive both required; Armendariz sets high bar for employment/adhesion | Enforceable with carve-outs for consumer contracts; Cal. CCP §410.40 | FAA governs; Concepcion preempts state class waiver invalidation; PAGA claims partially exempt | Written bilateral required; unilateral modification clauses closely scrutinized | Armendariz v. Foundation Health (2000) |
| TX | Both procedural and substantive required; courts rarely invalidate commercial MSAs | Strongly enforceable; Tex. Bus. & Com. Code §35.51 governs international | FAA governs; class waivers enforceable; AAA/JAMS rules commonly adopted | Written bilateral; course-of-dealing modifications recognized | In re Poly-America (Tex. 2004) |
| NY | Commercially sophisticated parties face very high bar; courts enforce freely negotiated MSAs | Enforceable unless unreasonable or procured by fraud | FAA governs; broad arbitration clauses interpreted expansively | Written required; oral modifications enforceable where parties acted on them | Gillman v. Chase Manhattan Bank (1988) |
| FL | Dual test required; adhesion status alone not sufficient | Enforceable; Fla. Stat. §685.101 validates choice of law/forum clauses | FAA governs; Concepcion applies; consumer carve-outs under FDUTPA | Written bilateral; NOM clauses enforceable | Fonte v. AT&T Wireless (2006) |
| IL | Procedural + substantive; courts look at totality of circumstances | Enforceable unless unfair or unreasonable under Calanca factors | FAA governs; IUAA backstop; class waivers enforceable post-Concepcion | Written bilateral; extrinsic evidence of prior negotiations admissible | Razor v. Hyundai Motor Am. (2006) |
| PA | Dual test; commercial parties held to higher standard of review | Enforceable when reasonable nexus to chosen forum | FAA governs; PUAA applies where FAA silent; class waivers enforceable | Written bilateral; integration clause strongly enforced | Salley v. Option One Mortgage (2007) |
| OH | Both elements required; courts enforce most commercial MSA terms | Enforceable when parties had reasonable relationship to chosen forum | FAA governs; Ohio UAA; class waivers enforceable | Written required; NOM clauses followed strictly | Eagle v. Fred Martin Motor Co. (2004) |
| GA | Dual test; courts reluctant to void commercial agreements | Strongly enforceable; Ga. Code Ann. §9-10-31.1 | FAA governs; GUAA; class waivers broadly enforceable | Written bilateral; oral modifications not binding if NOM clause present | NEC Technologies v. Nelson (1996) |
| MI | Both required; courts apply rigorous factual analysis | Enforceable with reasonable nexus to forum | FAA governs; MUAA; class waivers enforceable post-Concepcion | Written bilateral; course-of-dealing evidence admissible | Rory v. Continental Ins. Co. (2005) |
| WA | Courts use totality of circumstances; consumer protection statutes create additional scrutiny | Enforceable; RCW 4.28.185; long-arm statute limits reach | FAA governs; WUAA; unilateral modification of arbitration terms scrutinized | Written bilateral; consumer contracts subject to WAC requirements | Scott v. Cingular Wireless (2007) |
| CO | Both required; commercial parties held to duty to read | Enforceable when reasonable nexus to chosen forum | FAA governs; CUAA; class waivers enforceable | Written bilateral; NOM clauses enforced | Howard v. County of Boulder (1990) |
| MA | Dual test; G.L. c. 93A creates additional consumer/small business protections | Enforceable in commercial context; consumer contracts subject to G.L. c. 93A | FAA governs; MUAA; G.L. c. 251; class waivers enforceable for commercial parties | Written bilateral; consumer contracts subject to G.L. c. 93A § 2 | Zapatha v. Dairy Mart (1980) |
| NJ | New Jersey applies stringent consumer protection scrutiny; commercial parties more latitude | Enforceable with reasonable nexus; consumer carve-outs | FAA governs; NJAA; Atalese standard for waiver of rights clarity | Written bilateral; NOM clauses generally enforced | Caspi v. Microsoft (1999) |
| VA | Both required; courts strongly enforce commercial agreements between sophisticated parties | Enforceable; Va. Code §8.01-262 | FAA governs; VUAA; class waivers enforceable | Written bilateral; strict integration clause enforcement | Wainwright's Travel Service v. Schmolk (1982) |
| MN | Both required; courts use gross inadequacy of consideration as factor | Enforceable; Minn. Stat. §80C.21 restricts forum selection in franchise agreements | FAA governs; MUAA; franchise arbitration subject to additional scrutiny | Written bilateral; NOM clauses enforced unless waived by conduct | Hennepin Paper Co. v. Fort Wayne Corrugated Paper (8th Cir. 1997) |
Table is for general educational reference only; state law evolves rapidly. Consult a licensed attorney for jurisdiction-specific advice.
MSA Negotiation Matrix — 8 Clause Scenarios
For each standard clause language pattern: the risk level, your leverage, what counter-offer to propose, and the walkaway signal.
| Clause Language | Risk Level | Your Leverage | Counter-Offer | Walkaway Signal |
|---|---|---|---|---|
| "All work product shall be sole property of Client, including all background IP" | 🔴 Critical | High — most vendors won't sign this; ask what specific IP they actually need | Assign foreground IP only; grant non-exclusive background IP license | Client refuses any background IP carve-out |
| "Vendor's aggregate liability shall not exceed $500 regardless of form of action" | 🔴 Critical | High — this cap is commercially unreasonable for any material engagement | Cap at 12 months of fees paid; mutual consequential damages exclusion | Client refuses to set cap above nominal amount or insists on uncapped indemnification |
| "Client may terminate for convenience upon 5 days' notice with no further obligation" | 🔴 Critical | Medium — common in enterprise forms but negotiable | 30-day notice; payment for all completed/in-progress work through notice period; kill fee equal to 25% of remaining SOW value | Client refuses any payment obligation upon termination for convenience |
| "Vendor shall indemnify Client for any and all claims arising from or related to services" | 🟠 High | High — "arising from or related to" is overbroad and fault-agnostic | Limit to claims arising from vendor's negligence or willful misconduct; exclude claims arising from client-provided materials or specifications | Client refuses to limit indemnification to fault-based claims |
| "Client may amend this Agreement upon 30 days' written notice to Vendor" | 🟠 High | High — unilateral amendment rights are rarely commercially justified | Bilateral written amendment signed by authorized representatives; no unilateral modification rights for either party | Client refuses bilateral amendment requirement |
| "All disputes shall be resolved by arbitration in [Client's City], with each party bearing its own costs" | 🟡 Medium | Medium — geography is negotiable; fee allocation less so | AAA or JAMS commercial arbitration; mutually convenient location or virtual; loser-pays (or AAA consumer fee schedule if you are a small vendor) | Client insists on remote location with no cost-shifting even for frivolous claims |
| "Agreement automatically renews for successive one-year terms unless either party provides 90 days' written notice" | 🟡 Medium | Medium — notice window is negotiable; renewal itself is standard | Shorten non-renewal notice to 30 days; add right to negotiate updated terms at each renewal | Client insists on renewal with no right to renegotiate any terms |
| "Confidential Information includes any information disclosed by either party, whether oral or written, marked or unmarked" | 🟢 Low-Medium | Low — broad definition is common and generally acceptable if mutual | If not already mutual, make it mutual; add standard exceptions (publicly known, independently developed, legally required disclosure) | Confidentiality obligation is one-sided without legitimate business justification |
8 Common MSA Mistakes with Dollar Costs
Signing without a background IP carve-out
A vendor who assigns all IP — including background IP — to the client may be required to hand over proprietary tools, frameworks, or code libraries that form the core of their business. Rebuilding or licensing back these assets can cost hundreds of thousands of dollars, and the client may refuse to license them back at all.
Accepting a nominal or token liability cap
A cap at $500 or $1,000 on a six-figure engagement means the vendor (or client) bears essentially unlimited real-world exposure for any claim exceeding that amount. One data breach, IP infringement claim, or project failure can result in litigation costs that dwarf the contract value.
Performing out-of-scope work without a signed change order
Verbal or email approvals for out-of-scope work are frequently disputed when payment comes due. If the MSA requires a signed change order and the vendor performed without one, they may have no enforceable right to payment for that work.
Missing the evergreen non-renewal deadline
An MSA that auto-renews for another year at unfavorable rates or with outdated terms — because no one calendared the non-renewal deadline — can cost the full annual contract value in avoidable fees. In long-term managed services agreements, this can reach six figures annually.
Not specifying acceptance criteria in the SOW
Without objective acceptance criteria, the client can withhold acceptance indefinitely on subjective grounds. The vendor delivers, the client says "this isn't what we wanted," and neither party can point to an objective standard for what "acceptable" means. The resulting dispute typically costs as much to resolve as the original project.
Accepting one-sided indemnification without a liability cap carve-out
When broad indemnification obligations (covering all claims "arising from" services) are combined with a carve-out that exempts indemnification claims from the liability cap, the vendor faces potentially unlimited financial exposure on every engagement. This combination is a critical red flag that should trigger a hard negotiation or a walkaway.
Failing to address IP ownership in SOWs that modify MSA defaults
An MSA that assigns foreground IP to the client but a specific SOW that involves the vendor building on top of the client's existing platform creates a hybrid ownership problem. If the SOW does not address how new IP that blends vendor methods and client technology is owned, both parties may claim ownership and neither can enforce their claim without litigation.
Not reading the MSA at SOW renewal
A 3-year-old MSA may contain provisions that were market-standard when signed but are now out of step with current data privacy law, regulatory requirements, or the parties' evolved relationship. Executing new SOWs against a stale MSA without review embeds outdated (and potentially illegal) terms into every new project.
Does your MSA protect you?
Get an instant AI review — red flags, one-sided clauses, and plain-English analysis in under 60 seconds.
Check My MSA Free →14 Frequently Asked Questions
What is a Master Service Agreement and why do businesses use one?
What is the difference between an MSA and a Statement of Work?
Who should draft the MSA — vendor or client?
What is an adhesion contract and does it affect my MSA?
What is background IP and why does it matter in an MSA?
What is an acceptance testing clause in an MSA?
How do change orders work under an MSA?
What is a limitation of liability clause and what should it cap?
What does a typical MSA indemnification clause require?
How do SLAs fit into an MSA?
What is an evergreen clause and why is it risky?
Which states most frequently challenge MSA forum selection and arbitration clauses?
What is the duty to read and how does it affect MSA enforceability?
What are the six most important things to negotiate in an MSA?
Related Guides
Educational content only. This guide is for general informational purposes and does not constitute legal advice. Master Service Agreement law varies significantly by state and by the specific facts of each relationship. Consult a licensed attorney before signing, drafting, or amending any Master Service Agreement.