How to prepare a contract diligence findings report for Master Services Agreements

Prepare a customer-side MSA diligence findings report by reconstructing the contract package, determining which terms govern each service, and translating material issues into customer consequences and assigned actions. Review the MSA together with statements of work, amendments, pricing schedules, and operational addenda. The deliverable should combine a concise decision summary with a source-linked findings table showing evidence, uncertainty, priority, recommended treatment, and ownership. Keep missing evidence separate from confirmed contractual gaps, and distinguish legal uncertainty from commercial exposure and operational constraints.

When to use this workflow

Use this workflow when legal, procurement, or a transaction team must decide whether customer service arrangements can continue unchanged, require remediation, or need investigation. Triggers include acquisition diligence, outsourcing consolidation, critical-supplier review, and preparation for MSA renewal negotiations.

Define the customer entities, suppliers, services, active SOWs, and reporting date covered. Do not exclude an expired MSA without checking whether continuing SOWs or surviving obligations remain relevant. For acquisition diligence, include assignment and change-of-control restrictions within the review scope.

This is a US commercial-contracting workflow, not advice on a particular agreement. Conclusions require the governing law, complete contract hierarchy, and relevant facts. The recommendations below are review methods, not legal mandates; filed agreements illustrate particular wording rather than general rules or market standards.

What you need

Gather inputs that connect the agreement to the customer's dependence on the services:

• Executed MSAs, relevant SOWs, amendments, change orders, signature pages, and affiliate agreements.
• Pricing, service levels, specifications, acceptance criteria, security and data-processing addenda, and captured versions of incorporated online terms.
• Business owners, service criticality, supplier access to systems or data, subcontracting arrangements, and replacement constraints.
• Fee records, acceptance communications, material service failures, and notices relevant to identified issues.
• The customer's versioned review checklist, including preferred positions, fallbacks, escalation criteria, and approval owners.

Agree on materiality before extraction. Useful triggers include interruption of critical services, uncertain deliverable ownership, restricted recovery, and an impractical exit. Distinguish confirmed exposure from the urgency of investigating missing evidence.

Use the template

Use the Master Services Agreements — Contract diligence findings report companion template below. Copy this table into your working document or spreadsheet and add rows as findings emerge.

Assign stable finding IDs. Contract scope identifies the supplier, customer entity, and affected SOWs. Source references identify document ID, version, clause, and page; link supporting evidence records when several documents establish one finding. Use a short exact extract where ambiguity warrants it.

Distinguish confirmed terms, ambiguous wording, missing documents, redacted provisions, and topics not reviewed. “Not present in reviewed documents” does not establish absence throughout an incomplete package.

Explain priority through customer consequences. In the final column, distinguish the action owner from the authorized risk approver and include the target decision point. Above the table, summarize scope, principal decisions, exclusions, and outstanding evidence requests.

Step by step

1. Establish the document package and review perimeter

Assign document IDs and identify parties, dates, execution status, and service relationships. Reconcile procurement's active-service list against supplied SOWs. Identify missing attachments, incorporated terms, historical amendments, and documents whose applicability remains uncertain.

Designate the version used for analysis. If signed and editable copies differ, investigate material discrepancies; compare execution against the approved draft where that question falls within scope. A filename marked “final” does not resolve version uncertainty.

Record: package limitations, affected services, evidence requests, and owners. Explain whether each gap prevents a conclusion or reduces confidence in it.

2. Map precedence for each active service

Read incorporation, conflict, amendment, and signature provisions together. Do not assume a favorable MSA term governs every SOW.

The Access Worldwide–E*TRADE agreement incorporates the MSA into each SOW and gives it priority unless the SOW explicitly states otherwise. Its authorized-signature condition applies specifically to SOW effectiveness (§§1.3–1.4). By contrast, ProQuest–IBM gives conflicting Service Agreement terms priority for the particular undertaking, without changing other Service Agreements (Exhibit B §1.2).

Record: the governing provision, service-specific override, affected documents, and unresolved conflicts. Separate uncertainty about execution evidence from uncertainty about contractual priority; neither establishes a universal enforceability conclusion.

3. Extract terms around customer failure scenarios

Organize extraction around defective deliverables, service interruption, unexpected charges, security incidents, disputed IP rights, and supplier replacement. Connect each promise to its conditions and remedy.

For acceptance, check testing periods, rejection requirements, deemed acceptance, and re-performance. For service levels, check measurement exclusions, customer claim duties, credits, and any exclusive-remedy wording. Link IP ownership to payment conditions, background technology, and continuing license rights. Review confidentiality, security, subcontracting, audit, indemnity, and customer cooperation duties through the same lens.

Record: the finding, supporting clauses, dependencies, and customer consequence. Consolidate clauses that create one exposure rather than multiplying substantially identical findings.

4. Assess remedies and liability together

Identify fee scope, lookback trigger, aggregation, exclusions, separate caps, exceptions, and erosion rules. Test whether the remedy addresses the identified failure scenario before comparing headline multiples.

Invacare–Birlasoft uses a general cap tied to the greater of a fixed amount or an 18-month charges measure. Specified security-breach liability has a separate cap, reciprocal non-erosion, and different treatment under the damages exclusion, subject to other exceptions. These features illustrate why the complete structure matters (§19.2); they are not benchmarks.

Record: the applicable formula, fee evidence, assumptions, and unresolved claim classification. Attach reviewer-prepared calculations where useful, including early-term scenarios and possible cap depletion. Do not present a modeled ceiling as assured recovery.

5. Identify operational and timing constraints

Review renewal, acceptance, cure, termination, and transition separately. Confirm triggers, calculation conventions, recipients, delivery methods, copy requirements, and evidence of receipt. Preserve contradictory dates as open issues instead of silently choosing one.

Do not assume email suffices. Invacare–Birlasoft distinguishes primary notices requiring specified hard-copy delivery, effective upon receipt, from other notices permitting email with affirmative acknowledgment rather than automatic receipts (§22.3).

Ask whether operational teams can satisfy testing windows, cooperation duties, and transition prerequisites. For exit rights, consider continued service, data return, assistance charges, and replacement lead time together.

Record: verified dates or unresolved triggers, constraints, operational owners, and recommended calendar entries. The report identifies timing risks; it does not itself monitor compliance.

6. Convert findings into requested decisions

Separate what the available text establishes, what remains legally uncertain, and what the customer can tolerate commercially or operationally. Use the customer's checklist as review instructions, not as evidence that a clause is unlawful or outside market practice.

Assign priority using service criticality, credible consequence, available remedy, and decision timing. Select a concrete disposition: obtain evidence, clarify interpretation, negotiate an amendment, implement mitigation, or seek authorized risk acceptance. Replace “review further” with a defined question.

Record: requested decision, owner, decision point, escalation route, and proposed disposition. Keep remediation proposals separate from completed actions and approvals.

7. Reconcile and issue the findings report

Verify material findings against operative documents, definitions, cross-references, and amendments. Resolve inconsistent rows. If one package-level issue affects several SOWs, identify its reach without inflating the count of distinct risks.

Draft the decision summary last. State the affected services, highest-priority decisions, evidence limitations, and matters permitted to remain open under an assigned plan. Normalize definitions and scope before aggregating portfolio findings.

Record: final dispositions and open issues. Issue a dated report tied to an identifiable document set; retain the evidence and calculation workpapers so later revisions remain traceable.

Worked example

Fictional scenario: Cedar Vale Devices is reviewing its relationship with North Lantern Systems before consolidating support vendors. The package contains MSA-01, signed SOW-02 for production application support and associated change deliverables, and pricing schedule P-01. All parties, documents, clauses, page references, and amounts below are invented.

MSA-01 §3 allows a SOW expressly identifying an MSA section to override it. SOW-02 §8 expressly overrides MSA-01 §7: change deliverables are deemed accepted five business days after delivery unless rejected in writing. The service owner reports a ten-business-day testing cycle, but supporting requirements have not been provided. SOW-02 also incorporates an unavailable Security Schedule D.

P-01 specifies a $20,000 monthly fee. Assuming an incident immediately after three such payments, no other qualifying payments, and application of the general cap, the modeled ceiling is $60,000. Actual payments, claim classification, exceptions, and prior erosion remain unverified; the absent security schedule also prevents a complete incident-remedy assessment.

The report supports three different decisions: validate and potentially amend acceptance mechanics, obtain missing security evidence, and complete liability analysis. It does not turn uncertainty into a finding that no security duties exist or that $60,000 is recoverable.

Common mistakes

• Reviewing the MSA alone. Check SOW overrides, addenda, and amendments before making relationship-wide findings.
• Converting missing evidence into missing protection. Identify the unavailable document and the conclusion it prevents.
• Reporting a cap without remedy restrictions. Connect exclusions, indemnities, separate caps, and procedural conditions to the scenario.
• Treating every deviation as equally urgent. Explain criticality, consequence, and decision timing separately from textual departure.
• Closing a recommendation without evidence. Require the executed amendment, implemented control, or authorized acceptance before marking resolution.

Final quality check

• Customer entities, services, reporting date, and reviewed versions are identified.
• Material findings trace to verified document, clause, and page references.
• SOW overrides, amendments, and relevant definitions are reflected.
• Missing, ambiguous, redacted, and unreviewed material remain distinguishable.
• Calculations disclose inputs, assumptions, and unresolved dependencies.
• Actions address customer consequences and have decision points.
• Open issues are resolved or assigned; accepted exposure identifies approval authority.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its due diligence capabilities support bulk document classification to organize the package and prioritize human review; tabular review supports work across documents. For follow-on contract review in Word, choose the represented party and provide deal-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. Lawyers verify the source package and decide treatment. To assess fit for customer-side MSA reporting, book a demo.

Frequently asked questions

Should every reviewed clause appear in the findings report?

No. Keep routine extraction in supporting workpapers. Report material issues and limitations under the agreed threshold, while preserving coverage records so silence is not mistaken for an unreviewed topic.

Can one finding cover several SOWs?

Yes, where governing wording and consequences are shared. Identify included SOWs and separate exceptions. Different acceptance windows, caps, or exit regimes usually require separate treatment.

What if the supplier withholds an incorporated schedule?

Document the request and blocked conclusions. Ask the authorized decision-maker whether to defer the decision, require delivery, or accept specifically described uncertainty. Do not infer favorable or unfavorable missing language.

Does diligence require a complete redline?

No. The deliverable is a supported decision report. Prepare targeted amendments or redlines when the disposition requires them, linked to finding IDs and customer approval requirements.

Sources

These filed agreements illustrate negotiated 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.