How to build a clause extraction table for Master Services Agreements

Build a customer-side MSA clause extraction table by identifying the contract package, mapping document precedence, and extracting material provisions into source-linked rows. Preserve operative wording separately from normalized summaries, and record conditions, exceptions, and unresolved questions rather than flattening them into yes/no answers. The deliverable is a reviewable table showing what the supplier and customer agreed, where each term appears, which documents modify it, and what needs follow-up. It supports comparison without replacing the underlying agreements.

When to use this workflow

Use this workflow when commercial counsel or an in-house legal team needs to assess an incoming supplier MSA, compare supplier relationships, or answer a defined diligence question. Triggers include an outsourcing renewal, procurement’s review of exit rights, or an acquisition involving multiple service providers.

Set the scope first. An exit-rights table needs termination, notice, transition, data return, and surviving payment obligations—not merely the clause titled “Termination.” A broader extraction covers acceptance, fees, service levels, intellectual property, confidentiality, security, subcontracting, indemnity, and audit.

This guide addresses US commercial contracting. Record governing law and agreement hierarchy as interpretation inputs; do not treat extraction as an enforceability opinion. The steps are workflow recommendations, not legal requirements.

What you need

Collect the MSA, executed statements of work (SOWs), amendments, change orders, pricing schedules, service-level schedules, security and data-processing addenda, and incorporated online terms. Preserve the relevant online version where available; flag an unavailable historical version rather than substituting today’s wording.

Prepare these supporting inputs:

• A document register with parties, document IDs, versions, dates, signature status, and governing-law provisions.
• The customer’s review questions and internal negotiation checklist, including escalation owners.
• A topic dictionary distinguishing acceptance from service-level remedies, and ownership from license rights.
• Legal and operational reviewers for uncertain wording and missing service facts.

Keep originals alongside searchable copies. Verify OCR against page images, especially numbers, negatives, tables, and cross-references.

Use the template

The companion template is Master Services Agreements — Clause extraction table. Copy this table into your working document or spreadsheet. Use one row per independently meaningful provision, with stable row IDs linking exceptions and overrides.

“Document / version” must resolve to a specific file. In “Clause / page,” distinguish printed page numbers from PDF positions. Preserve operative wording in its own field; for lengthy provisions, link to a complete source extract rather than silently truncating qualifications.

Keep paraphrases in “Normalized result.” Use “Conditions / links” for definitions, exceptions, amendments, and related row IDs. Separate the extracted bargain from recommendations in “Customer impact / action.”

Use distinct evidence statuses: verified, ambiguous, not located in reviewed set, source missing, redacted, and not reviewed. Qualify a verified extract if its application remains uncertain. Reviewer confidence may supplement these statuses, but cannot replace source verification. Record scope and package version above the table.

Step by step

1. Define the question and extraction rules

Write a scope statement identifying the customer entity, supplier, covered services, relevant contract date, and decision the table must support. Specify whether the review covers proposed terms, executed terms, or both.

Set row granularity before extracting. Separate convenience termination from breach termination, ownership from licensing, and invoice timing from dispute rights. Keep qualifications with the operative rule or link them explicitly.

Record: stable topic IDs, document status, and initial “not reviewed” entries. An empty cell must not imply that no obligation exists.

2. Establish the document package and precedence

Assign document IDs and read incorporation, amendment, and precedence clauses before identifying controlling terms. Record whether an override applies to one deliverable, one SOW, or the relationship generally.

The Access Worldwide–E*TRADE MSA gives incorporated MSA terms priority unless an SOW explicitly provides otherwise and requires authorized signatures for SOW effectiveness (§§1.3–1.4). The ProQuest–IBM agreement instead gives conflicting Service Agreement terms priority for the particular undertaking, without changing other Service Agreements (Exhibit B §1.2). These examples demonstrate different contractual structures, not a universal hierarchy.

Record: hierarchy rows, linked overrides, signature-status questions, and missing incorporated documents. Preserve competing readings where precedence is inconsistent.

3. Extract wording before normalizing it

Search by concept, then read surrounding provisions. Acceptance may appear under testing, milestones, invoicing, or deliverables. Supplier relief may appear under customer responsibilities rather than service levels.

Capture the actor, action, beneficiary, trigger, timing, and conditions. For acceptance, distinguish the review period, rejection requirements, deemed acceptance, correction obligations, and effect of productive use. For indemnity, separate covered claims from defense control, cooperation, and settlement conditions.

Check each passage against the source. A search result or generated summary is a locator, not verification.

Record: operative wording, clause/page citation, and evidence status. Identify unavailable definitions or attachments before stating a complete result.

4. Normalize without erasing negotiated mechanics

Use consistent topic names and summary syntax. For fees, distinguish fixed charges, usage charges, expenses, and disputed invoices. For IP, distinguish customer materials, supplier background materials, newly developed deliverables, and third-party components.

Liability requires more than a fee multiple. Invacare–Birlasoft uses a general cap combining a monetary floor with an 18-month charges measure, and a separate specified security-breach cap with a different floor and 27-month measure. Payments reducing either cap do not reduce the other, subject to the surrounding provisions (§19.2(b)–(c)). These are negotiated terms, not benchmarks.

Record: formula components, covered claims, aggregation, lookback trigger, exceptions, and erosion rules. Calculate amounts only with identified supporting data and assumptions.

5. Link dependencies and customer consequences

Connect provisions that operate together. Check whether service credits are exclusive remedies, transition work requires another SOW, or customer cooperation duties qualify supplier commitments.

Test a concrete scenario: if the supplier misses a launch milestone, what must the customer do, what relief is available, and what could restrict it? Keep legal interpretation, commercial exposure, and operational feasibility separate.

“Credit request required within the stated period” describes wording; “operations needs a claims process” is a recommendation.

Record: linked row IDs, customer consequence, and a specific follow-up action. Explain the exposure rather than labeling a clause “unacceptable.”

6. Resolve gaps and validate comparisons

Run a second pass for missing topics, undefined terms, broken cross-references, redactions, and conflicting dates. Search the identified package before reporting a provision as not located. If a referenced schedule is unavailable, use “source missing,” not “no obligation.”

Compare only equivalent propositions. A right to terminate one SOW is not the same as a relationship-wide exit. A service-term license differs from a continuing license. Preserve governing-law, service-scope, and amendment differences that limit comparison.

Record: corrected statuses, comparison limitations, and an owner for every material unresolved issue. Do not silently select the commercially convenient interpretation.

7. Review and freeze the deliverable

Have responsible counsel verify decision-driving rows against the source package. Prioritize hierarchy, liability, indemnities, IP, security, acceptance, termination, and notice mechanics according to the review question.

Check that citations identify the intended version and that filtered rows retain necessary qualifications. Label the table with its scope, package version, and review status. Preserve earlier versions when amendments require updates.

Record: reviewer disposition and remaining actions. Completion means reliable extractions and assigned uncertainties, not a claim that every question is closed.

Worked example

Fictional scenario: Alder Quay Foods is reviewing its customer-side position under an MSA with Juniper Harbor Systems for warehouse scheduling services. Procurement asks whether Alder can reject defective deliverables and exit without losing access to its data. All parties, documents, clauses, and facts below are fictional.

The package contains executed MSA-A v1 and SOW-B v2. MSA-A §2 permits express SOW overrides of identified sections. SOW-B replaces the §6.3 acceptance period only for the scheduling dashboard. MSA-A §14.4 references Schedule T, which was not supplied. Delivery evidence and a separate data-return review remain outstanding.

The table changes the testing decision immediately: the dashboard cannot use the longer MSA window. It does not yet answer the exit question. A transition reference establishes neither adequate migration support nor a confirmed data-return mechanism. Keeping those gaps visible prevents procurement from treating an incomplete extraction as approval to exit.

Common mistakes

• Combining all termination rights. Separate triggers, cure periods, affected documents, charges, and surviving duties so an SOW exit is not mistaken for a relationship-wide exit.
• Treating headings as complete provisions. Follow definitions and cross-references, especially for supplier IP, excluded damages, and customer dependencies.
• Converting gaps to “none.” Distinguish unavailable schedules from a completed search finding no express provision.
• Recording a cap without its mechanics. Preserve claim scope, fee base, lookback trigger, floors, aggregation, and exceptions before comparing results.
• Mixing extraction with negotiation. Keep agreed wording separate from preferred language and proposed actions.

Final quality check

• Every substantive result has a document ID, version, and usable clause/page citation.
• Wording, numbers, negatives, and cross-references match the source.
• Amendments and SOW overrides link to affected rows.
• Definitions, conditions, and remedy limitations survive normalization.
• Missing, ambiguous, redacted, and unreviewed evidence remain distinguishable.
• Customer consequences are separate from unsupported enforceability conclusions.
• Material open issues are resolved or assigned, and scope and review status are explicit.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its transactional capabilities support tabular review across documents; due diligence includes bulk document classification to organize the package and prioritize human review. Contract review can support follow-up on extracted issues. The table remains your work product, with lawyers responsible for verification and interpretation. To discuss customer-side MSA extraction, book a demo.

Frequently asked questions

Should every MSA clause receive a row?

No. Match coverage to the review question, but include provisions qualifying an in-scope answer. Identify excluded topics so readers do not mistake a targeted extraction for a complete contract review.

How much exact text should the table contain?

Enough to preserve the operative rule and qualifications. For lengthy provisions, link a complete source extract and use related rows rather than an unreadable cell or misleading summary.

How should notice provisions be extracted?

Separate notice categories, methods, recipients, effectiveness, and acknowledgment requirements. Invacare–Birlasoft distinguishes specified hard-copy primary notices from other notices permitted by email with affirmative acknowledgment, excluding automatic receipts (§22.3(a)–(b)). Do not normalize both categories to “email permitted.”

Can the table compare unsigned drafts with executed agreements?

Yes, if status is explicit and the purpose is defined. Keep proposed wording separate from the executed baseline; do not present a draft concession as an operative right. Flag signature or authority questions for counsel rather than resolving them from file labels.

Sources

These filed agreements illustrate particular wording, not general law or market standards.

• Access Worldwide–E*TRADE MSA, §§1.3–1.4.
• ProQuest–IBM MSA, Exhibit B §1.2.
• Invacare–Birlasoft MSA, §§19.2 and 22.3.

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.