How to prepare a contract diligence findings report for Statements of Work

Prepare a customer-side Statement of Work diligence report by establishing the controlling document set, tracing deliverables through acceptance and payment, and recording material risks with clause-level evidence. Review each SOW alongside its master agreement, incorporated specifications, and approved changes—not as a standalone scope description. The resulting report should distinguish confirmed contractual exposure from missing evidence, explain the decision each finding requires, and assign an owner and decision date. Use the findings table below as the working record supporting a concise executive summary.

When to use this workflow

Use this workflow when legal, procurement, or a transaction team must assess proposed or existing SOW commitments before approving spend, acquiring a business, renewing services, or resolving an incomplete contract file. It focuses on reporting findings, not conducting a full renegotiation or managing delivery.

The perspective is the customer’s: what must the supplier deliver, what must the customer contribute, when does payment become due, and what happens if performance falls short? This professional workflow guide assumes US commercial practice without selecting a governing state law. Rights depend on the actual language, governing law, facts, and deal context; federal procurement requirements are outside its scope.

What you need

Collect the executed or proposed SOW, applicable master services agreement (MSA), amendments, purchase orders, specifications, pricing schedules, security terms, incorporated policies, and change requests. Include signature pages and attachment versions. Distinguish operative documents from proposals, drafts, and project records whose contractual status requires confirmation.

Obtain delivery records, acceptance or rejection notices, test results, invoices, change approvals, and evidence of production use. Request the customer’s approval checklist, budget authority, and materiality criteria. These are review inputs, not substitutes for contractual wording.

Define the decision and evidence cutoff. For an acquisition, the question might be whether an integration-critical SOW needs remediation before closing. For an implementation, it might be whether a milestone requires immediate testing or notice. Record unavailable materials before drawing conclusions.

Use the template

Use Statements of Work — Contract diligence findings report as the working template. You can copy this table into your working document or spreadsheet. Create one row per actionable finding, combining linked clauses where they produce a single commercial consequence.

In Source / version, record document IDs, versions, and section or page citations for every linked provision. Preserve exact extracts in a supporting evidence sheet when needed, cross-referencing its record IDs or cells.

Evidence / gap distinguishes verified wording, operational evidence, unavailable attachments, and extraction failures. Priority / confidence separates urgency from certainty: a potentially critical issue can remain unconfirmed. Action / owner / date identifies the next action, responsible person, and target date. Decision / status records remediation, escalation, risk acceptance, or closure, including the approver and rationale. Do not confuse accepting a report finding with contractual acceptance of deliverables.

Step by step

1. Establish the controlling package

Assign document IDs and record version, signature status, parties, service, and effective period. Map each SOW to its MSA and identify incorporation and precedence language. Compare the executed package with the last approved draft where available, including exhibits and pricing tables.

Do not assume either document always prevails. The NCR-filed Development Services Exhibit, section 1.2, requires both parties’ execution for SOW effectiveness. Its Appendix 1 form places the SOW above the Exhibit and Purchase Agreement in its conflict hierarchy. These are contract-specific choices, not general rules.

Record findings for missing controlling documents, unexplained version conflicts, or unresolved execution questions. Name the person responsible for confirming the package before conclusions become final.

2. Map scope to verifiable delivery

For each material deliverable, connect its description to specifications, exclusions, assumptions, customer dependencies, staffing commitments, and completion evidence. Ask whether a reviewer could determine that the promised work was delivered without relying on undocumented understandings.

A dependency matters when it changes timing, price, or supplier responsibility. A customer data-migration obligation may qualify a supplier’s completion date; record both provisions rather than reporting an unconditional deadline. For phased implementation, distinguish completion of one module from completion of the whole solution.

In the template, identify the affected deliverable and missing specification or unresolved boundary. Explain the consequence—such as inability to distinguish included remediation from additional work—and assign the question to a technical or business owner.

3. Trace acceptance through payment and remedies

Map each deliverable to test criteria, environment, approver, review window, rejection notice, correction, retesting, and payment consequence. Check whether silence, production use, or partial delivery can trigger acceptance. Identify evidence establishing whether each trigger occurred.

The ICELOUNGE MEDIA filed SOW’s Acceptance and Rejection provisions illustrate the interaction: alternative deemed-acceptance triggers connect to milestone payment, while Services Warranty claims are expressly preserved. Rejection requires detailed written notice within its five-business-day testing period. These provisions illustrate wording, not default legal rules.

Record combined exposure where appropriate. Distinguish uncertainty about acceptance from uncertainty about warranty relief. If an invoice is under review, identify applicable invoice-dispute provisions as well; the findings report alone does not determine whether withholding payment is permitted.

4. Reconcile fees, changes, and customer duties

Compare milestone prices, rate cards, expenses, invoice triggers, and approved changes. Separate committed fees from estimates, caps, and contingent amounts. Quantify exposure only when documents and facts support the calculation; otherwise identify the missing input. Distinguish an amount invoiced from an amount established as payable.

Trace who can request, assess, price, approve, and implement a change. Approval to investigate may differ from approval to perform. The NCR example’s Appendix 1, Attachment 1 Change Request Form separates those approvals and records effects on work products, schedule, and price.

Record disputed charges, approval gaps, and customer cooperation duties affecting performance. Assign financial reconciliation to finance and unresolved authority questions to legal or procurement. Preserve relevant correspondence without assuming it changes the contract.

5. Test protections against the actual service

Review intellectual-property rights, confidentiality, security, liability, termination, and exit support against this SOW’s deliverables. Identify whether the customer needs source materials, data exports, transition assistance, or continued access to finish implementation with another supplier.

Read protections through the precedence structure established in step 1. Check for SOW exceptions to master provisions before calling a protection available or missing. For example, identify whether a deliverable-specific license restricts the customer’s proposed use or whether exit assistance excludes unfinished work.

Record the service consequence, linked sources, and proposed response. Where governing law or disputed facts affect the answer, assign a specific legal question rather than declaring the provision enforceable or ineffective.

6. Prioritize findings and validate uncertainty

Assess impact and likelihood separately, then account for decision timing. A short acceptance window may require attention before a larger but remote exit concern. Apply the customer’s materiality criteria rather than presenting internal thresholds as market practice.

Validate facts with project owners without replacing contract evidence with operational explanations. Classify findings as confirmed, conditional, or evidence incomplete. For event-driven periods, capture the trigger, business-day definition, notice method, recipient, and receipt requirements before calculating a response date.

Record priority, confidence, owner, and decision date. Keep an unverified trigger unresolved, with someone responsible for obtaining evidence. Distinguish internal action targets from contractual deadlines; do not invent a response date when the trigger date is unknown.

7. Assemble the decision-ready report

Lead with the decision requested, review perimeter, evidence cutoff, and findings that could change approval, spend, or remediation priorities. Follow with the findings table and source index. Identify excluded SOWs or unavailable documents that materially limit conclusions.

For each significant finding, state the contractual mechanism, customer consequence, missing evidence, recommended action, and approval status. Separate amendments from testing, document retrieval, and internal risk decisions. Where a proposed fix requires supplier agreement, identify it as proposed rather than completed remediation.

Reconcile the summary against the table. Every summarized concern needs a supporting row; every high-priority row should appear in the summary or have an explicit reason for exclusion. Preserve unresolved issues in the circulated report rather than removing them for presentation.

Worked example

Fictional scenario: Alder Quay Foods is reviewing its SOW with North Lantern Systems before approving an implementation payment. All parties, documents, amounts, provisions, and events below are invented.

The file contains executed SOW-07 version 1, executed MSA-01 version 2, invoice INV-12, and change request CR-03 version 1. The package’s hierarchy places SOW-specific terms above conflicting MSA terms. SOW-07 section 4 prices the integration milestone at $120,000 and treats production deployment as acceptance; MSA-01 section 6 links milestone payment to acceptance. The referenced acceptance appendix is unavailable, and deployment is unconfirmed.

INV-12 requests the milestone payment and $18,000 for a reporting enhancement. CR-03 section 2 records approval to study that enhancement and requires separate implementation authorization. No such authorization was supplied. The internal payment decision is scheduled for October 20, 2026; that is not an established contractual due date.

The report changes routine invoice approval into targeted verification. F1 identifies potential exposure, not a confirmed debt. F2 prevents invented test criteria and may change F1 once retrieved. F3 supports a narrow authorization inquiry, not a conclusion that no charge is justified. The invoice’s dispute and payment terms must also be checked before recommending a payment response.

Common mistakes

• Reviewing only the SOW. Establish the incorporated package and precedence structure before characterizing protections.
• Calling unavailable language absent. Retrieve the referenced attachment; distinguish missing evidence from verified omission.
• Separating acceptance from payment. Consolidate linked triggers so the report explains the financial decision and surviving remedies.
• Equating project discussion with change approval. Verify what was approved, by whom, and for which stage and price.
• Ranking every deviation equally. Prioritize supported consequences, uncertainty, and decision timing without concealing lower-priority findings.

Final quality check

• Verify citations against originals, including OCR-sensitive prices, dates, and clause numbers.
• Confirm each SOW’s MSA, hierarchy, signature status, and incorporated versions.
• Trace material deliverables through testing, acceptance, rejection, remediation, and payment.
• Identify customer dependencies and conditional supplier duties.
• Support exposure amounts with stated inputs and label contingent amounts.
• Separate contractual deadlines from internal targets and verify trigger evidence.
• Resolve open issues or assign an owner, evidence request, and decision date.
• Match summary recommendations to findings and recorded approval status.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its due diligence capabilities include bulk document classification to organize materials and prioritize human review; tabular review supports work across multiple documents. For follow-up contract review in Word, lawyers can select the customer as represented party, provide deal-specific instructions, and assess findings that quote and locate clauses, rank severity, and identify missing language. Lawyers retain verification and decision responsibility. Book a demo to discuss this SOW reporting workflow.

Frequently asked questions

Should each SOW have a separate report?

Not necessarily. A portfolio report can share a findings table if each row identifies its SOW, applicable MSA, and version. Separate summaries help where services, decision owners, or approval dates differ materially.

How should we report an unsigned SOW?

Identify execution status, contractual execution requirements, and evidence of work or approvals. Assign authority and contractual-status questions to counsel. Do not automatically classify the document as operative or irrelevant.

Is a missing acceptance appendix a critical finding?

Priority depends on the decision it obstructs. Retrieval may be urgent when testing or payment is imminent. Report the evidence gap and consequence, not an unsupported conclusion that no acceptance standards exist.

Should the findings report include proposed redlines?

Include targeted wording when useful, distinct from the existing contract record. State the preferred response, permitted fallback, linked provisions, and required approval using the customer’s own checklist. Do not present a proposed fix as agreed remediation.

Sources

• NCR SEC Exhibit 10.1 — Development Services Exhibit and Appendix 1: execution, hierarchy, and change-control examples.
• ICELOUNGE MEDIA SEC Exhibit 10.01 — Acceptance and Rejection: acceptance, payment, rejection, and warranty relationships.

Filed agreements illustrate wording, not generally applicable 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.