Review a customer-side Master Services Agreement by testing the complete contract package against the services being purchased, operational requirements, and realistic supplier failures. Establish document precedence, then connect scope, acceptance, fees, ownership, security, remedies, and exit rights. Record each material issue with its source, customer consequence, proposed position, and decision owner. The deliverable is a source-linked review checklist supporting targeted redlines and identifying terms that require business approval, further evidence, or specialist advice before signature.
Use this workflow when procurement or a business sponsor sends legal a supplier MSA, renewal package, or new statement of work under an existing agreement. It addresses customer-side review of implementation projects, managed services, outsourced operations, and recurring professional services.
Review the documents that determine whether the customer can obtain, verify, use, and replace the services—not merely the supplier’s main form. Keep findings tied to the proposed transaction rather than expanding the exercise into contract administration.
This guide uses a US commercial-contracting orientation. Evaluate interpretation and enforceability under the applicable governing law, complete agreement, and facts; do not infer either from the illustrative agreements below. The checklist organizes professional review, not advice for a particular transaction.
Collect these inputs before reaching substantive conclusions:
Assign stable document IDs and versions. Identify the contracting entities and intended service recipients, including affiliates. Distinguish contextual documents from contractual attachments. Record missing schedules rather than inferring their content.
Copy the Master Services Agreements — Contract review checklist into your working document or spreadsheet. Use one row per material issue; split topics where sources, remedies, or decision owners differ.
| ID / topic | Source / version | Text / status | Customer impact | Dependencies | Priority | Action / rationale | Owner / decision |
|---|---|---|---|---|---|---|---|
In Source / version, record the document ID, version date, clause, and page where available. Preserve a short exact extract in Text / status, with a source link for longer language. Distinguish absent, ambiguous, redacted, and not reviewed.
Use Dependencies for provisions or facts that could change the assessment, such as an SOW override or unverified fee base. Set Priority by customer consequence, not textual novelty. Action / rationale states the requested change and reason. Owner / decision identifies the responsible person, disposition, and any approval conditions. Keep evidence uncertainty separate from an accepted commercial risk.
Read incorporation, precedence, and amendment provisions together. Determine whether overrides must be explicit, who must approve them, and whether a departure affects one engagement or the entire relationship. Check whether incorporated online terms can change during performance.
Filed agreements illustrate different approaches. Access Worldwide–E*TRADE §§1.3–1.4 prioritize the MSA unless an SOW explicitly provides otherwise. ProQuest–IBM Exhibit B §1.2 prioritizes a conflicting Service Agreement for that undertaking. These are agreement-specific provisions, not universal rules. See the Access Worldwide–E*TRADE MSA and ProQuest–IBM MSA.
Record each material conflict, controlling priority language, approval requirement, and missing document. Escalate circular hierarchies rather than selecting whichever term favors the customer.
Identify what the supplier must deliver, how completion is measured, and when payment becomes due. For projects, compare milestones with acceptance criteria, testing periods, rejection procedures, and correction obligations. For recurring services, compare measurement methods with reporting, credits, and persistent-failure remedies.
Check whether deemed acceptance, productive use, invoice timing, or customer delay provisions undermine verification. Ask the implementation team whether it can complete the required tests within the proposed period. Distinguish acceptance of a deliverable from waiver of later warranty claims.
Record each mismatch with the affected deliverable, required evidence, and proposed correction. An undefined milestone may need a revised SOW rather than another general warranty in the MSA.
Separate customer materials, new deliverables, supplier background technology, and third-party components. Test whether ownership and licenses support intended use, maintenance, affiliate access, and replacement services. Identify necessary rights after termination.
Connect confidentiality and security commitments to actual data flows. Check subcontractor access, supplier responsibility for subcontractors, incident-response duties, audit evidence, and return or deletion requirements. Do not treat confidentiality language as a substitute for operational safeguards.
Record missing permissions, undefined categories, and unavailable schedules. Assign specific questions to security, privacy, or engineering—for example, whether proposed deletion timing permits migration—while retaining legal ownership of the resulting contractual position.
Choose concrete scenarios: failed implementation, prolonged outage, customer-data loss, or a third-party IP claim. Trace each through correction rights, credits, indemnities, damages exclusions, caps, and termination. Check exclusivity and indemnity procedures, including defense control and settlement restrictions.
Model the cap using its fee scope, lookback trigger, floor, aggregation, exceptions, and erosion rules. Test early-term incidents and concurrent claims rather than comparing fee multiples alone.
Invacare–Birlasoft §19.2 illustrates a general cap and a separate specified security-breach cap, with different formulas and non-erosion treatment. These negotiated terms are not benchmarks or legal minima. See the filed agreement, §19.2.
Record the scenario, calculation assumptions, residual exposure, and proposed mitigation. Separate commercial inadequacy from questions requiring governing-law analysis.
List customer inputs, system access, approvals, and staffing commitments. Determine what relief follows a missed dependency: extra fees, extensions, suspension, or another consequence. Check whether relief requires notice and a demonstrated connection to the customer’s failure.
Review who may authorize scope changes and whether change control can alter acceptance criteria, rates, staffing, or dates. Compare expenses, minimum commitments, disputed-invoice procedures, suspension rights, and price adjustments with budget assumptions.
Record the operational owner and proposed boundary for each material dependency or charge. A clearly drafted customer obligation remains problematic if nobody can perform it. Identify whether the correction belongs in the MSA, pricing schedule, or affected SOW.
Distinguish MSA expiration from individual SOW expiration. Review nonrenewal windows, termination grounds, cure provisions, committed charges, and effects on continuing work. Assess transition assistance, usable data exports, continuing licenses, and transition pricing against the replacement plan.
Extract notice methods and recipients beside each event. Invacare–Birlasoft §22.3 distinguishes primary hard-copy notices from other notices permitted by email with affirmative acknowledgment. Do not generalize that wording or assume an account-manager email suffices. See §22.3 of the filed MSA.
Record triggers, contractual periods, delivery requirements, and internal lead times for handoff. Assign contradictory dates and missing transition terms for resolution rather than silently repairing them.
Consolidate overlapping issues and prepare targeted redlines against the identified draft. Apply the customer’s own negotiation checklist, explain departures, and identify fallbacks. Recheck affected definitions, cross-references, and SOW provisions.
Distinguish missing facts, drafting disagreements, and risks requiring approval. Specify what closes each issue: a supplied schedule, revised clause, operational confirmation, or authorized acceptance. Include material governing-law and dispute-resolution departures in the appropriate escalation rather than assuming the commercial analysis resolves them.
Record the disposition, owner, and conditions. The negotiating lawyer should be able to explain each material request without reconstructing the analysis from scattered comments.
Fictional scenario: Harbor Fern Retail is purchasing an inventory-system implementation and managed support from Kestrel Bridge Services. All parties, documents, amounts, and quoted clauses below are fictional. The package contains MSA-01 v3 and SOW-01 v2. Expected first-year fees total $480,000. Referenced Security Schedule C is missing.
MSA-01 gives the MSA priority unless an SOW expressly identifies an override. The SOW requires migration testing but contains no express acceptance override. The implementation lead confirms that five business days is insufficient, but has not supplied an approved testing period.
| ID / topic | Source / version | Text / status | Customer impact | Dependencies | Priority | Action / rationale | Owner / decision |
|---|---|---|---|---|---|---|---|
| R1 Acceptance | MSA-01 v3 §4; SOW-01 v2 §3 | MSA: “Accepted five business days after delivery”; SOW requires migration testing | Acceptance may occur before validation | No express override; replacement period unresolved | High | Tie acceptance to documented tests and clarify priority | Legal + implementation lead; open |
| R2 Liability | MSA-01 v3 §12 | Cap: “Fees paid under the affected SOW in the preceding three months” | Low recovery ceiling during ramp-up | Incident date; fee evidence; remedy restrictions | High | Model exposure; negotiate floor and clear lookback trigger | Legal + finance; open |
| R3 Security | MSA-01 v3 §8 | Schedule C referenced; not supplied | Safeguards and incident duties cannot be assessed | Missing schedule; actual data access | High | Obtain schedule and security assessment before closing issue | Security + legal; evidence pending |
For R2, assume solely for modeling that the relevant lookback ends on the incident date and $20,000 was paid during that period. The formula then produces $20,000 before other terms are considered. The quoted clause does not itself identify the lookback endpoint; clarification is therefore part of the requested amendment. Nor does the calculation establish recoverability of any particular loss.
The findings change negotiating priorities. Acceptance needs both drafting and an operational testing decision. Liability needs clarified mechanics before finance can assess a concession; projected annual fees do not establish the cap. Security requires evidence first: an unseen schedule cannot responsibly be classified as adequate or deficient.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. In its contract review workflow, choose the customer as the represented party in Word and provide deal-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. The lawyer can edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name, or dismiss findings with reasons. Tabular review supports work across documents; the checklist remains your work product and legal judgment remains with counsel. To assess this workflow for your MSA package, book a demo.
Screen the full package, but reserve substantive rows for material issues and dependencies. Record completed topic checks concisely so an omitted issue is not mistaken for an accepted position.
Review the general risk allocation and identify decisions deferred to SOWs. Mark project-specific acceptance criteria, pricing, measurements, and dependencies unresolved; do not assume future drafting will supply them adequately.
Check the actual hierarchy and override requirements. Identify whether the proposed change addresses only that engagement or whether the customer needs an MSA amendment covering other SOWs.
Record the exposure, assumptions, authorized approver, and mitigation or conditions. Keep approval separate from the legal assessment. Revisit it if scope, fees, data access, or other material assumptions change.
These filed agreements illustrate particular wording, not governing law or market standards.
This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.