How to prepare a contract diligence findings report for Consulting Agreements

Prepare a client-side consulting agreement diligence report by establishing the controlling document set, testing the terms against the client’s intended use of the services and deliverables, and linking each material finding to evidence. Review performance, payment, ownership, confidentiality, liability, and exit arrangements together. The resulting deliverable is a decision summary and findings table that distinguishes verified terms, missing evidence, and unresolved legal questions, with a recommended response, accountable owner, and decision milestone for each material issue.

When to use this workflow

Use this workflow when legal must assess existing consulting arrangements before an acquisition, project expansion, renewal, supplier consolidation, or decision to retain a critical consultant. It suits in-house counsel and outside commercial lawyers reviewing one engagement or a portfolio from the client’s perspective.

Define the decision first: continue the engagement, obtain corrective documentation, investigate costs, or require remediation before a transaction milestone. Include completed engagements if the client still relies on their deliverables.

This is a US transactional workflow, with a research cutoff of October 13, 2026. Conclusions depend on wording, governing law, facts, and project context. State-law enforceability, worker classification, tax, privacy, and foreign intellectual-property issues need separate analysis when material. The process recommendations below are review controls, not legal requirements.

What you need

Request the agreement package and operational evidence, not just the signed master:

• Contract documents: executed consulting agreement, statements of work, amendments, side letters, incorporated policies, background-technology licenses, and subcontracting terms.
• Performance records: deliverable inventory, milestone reports, acceptance communications, change requests, staffing substitutions, and unresolved defect reports.
• Financial records: fee schedules, invoices, expense approvals, receipts, disputed charges, and remaining commitments.
• Ownership evidence: creator and subcontractor agreements, assignments, third-party component lists, and restrictions on embedded tools.
• Client instructions: intended use of outputs, project criticality, acceptable exposure, report audience, materiality criteria, and decision deadline.

Assign stable document IDs; preserve version, execution status, and provenance. A project manager’s explanation can establish operational context, but should not silently substitute for missing contractual language.

Use the template

The companion template is Consulting Agreements — Contract diligence findings report. You can copy this table into your working document or spreadsheet. Use one row per decision-relevant issue and a separate document index for larger packages.

In Source / evidence, record document ID, version, section, and page, with a short extract or precise paraphrase. Cite operational records separately. Baseline / actual term distinguishes the client’s requirement from the contractual position.

Keep priority separate from certainty: an unavailable assignment may be highly important while ownership remains undetermined. Gap / dependency identifies missing documents, conflicting terms, assumptions, or specialist questions. Give each action an owner and decision milestone. In Status / decision, distinguish awaiting evidence, verified issue, authorized risk acceptance, and completed remediation supported by documentation.

Step by step

1. Set the decision and reporting threshold

Confirm which services and outputs matter to the client. A strategy presentation, production software tool, and executive advisory engagement create different dependencies. Identify whether the client needs ownership, continued access, modification rights, particular personnel, or an orderly handover.

Set priorities by consequence: project interruption, inability to use outputs, unbudgeted commitments, or an uncertain exit. Do not treat every departure from preferred wording as equally material. If using a client negotiation checklist, identify its date and distinguish preferences from approved requirements.

Record: the applicable baseline, consequence, and business sponsor validating the requirement.

2. Establish the controlling document set

Map statements of work to the master agreement and amendments. Check signatures, effective dates, incorporated documents, and express priority provisions before resolving conflicts. Identify the project phases and deliverables covered by each document.

Document hierarchy can change the answer. The SEC-filed Neoleukin agreement gives its statement of work and specified Contingent Value Rights Agreement precedence over conflicting consulting-agreement terms, and requires signed writings for amendments. This is negotiated wording, not a universal hierarchy rule. Neoleukin Consulting Agreement, § 8.9

For an acquisition, inspect assignment, change-of-control, consent, and notice provisions against the proposed transaction structure. Flag uncertainty rather than assuming every transaction requires consent.

Record: controlling sources, conflicts, execution uncertainty, missing documents, and transaction-specific dependencies. Distinguish “not found in reviewed documents” from “referenced document unavailable.”

3. Test performance and payment provisions together

Connect scope, deliverables, milestones, acceptance, staffing, and change control to fees. Identify whether payment follows elapsed time, delivery, acceptance, or another trigger. Investigate undocumented scope expansion, disputed acceptance, minimum commitments, and payment during disputes.

Review expenses separately. Castle Biosciences’ filed agreement requires reasonable service-related expenses, company policy compliance, prior written approval, and requested verification. Neoleukin’s example instead covers specified reasonable and customary expenses unless the statement of work provides otherwise, with receipts on request. Neither establishes a market standard. Castle, § 3; Neoleukin, § 2.2

Compare invoices with applicable rates, approvals, caps, and milestones. Do not aggregate an unsupported estimate with verified liabilities.

Record: payment triggers, approval evidence, documented exposure, unquantified amounts, and the finance or project owner responsible for factual verification.

4. Trace rights in deliverables and embedded materials

Inventory commissioned output, consultant background tools, third-party components, and subcontractor contributions. Match intended use against assignments and licenses, including modification, sharing, transfer, and post-termination access where relevant.

Federal copyright initially vests in authors, subject to the qualifying work-made-for-hire rule. Ownership of a physical copy does not itself convey copyright. Section 204(a) requires a signed writing evidencing a copyright ownership transfer other than by operation of law, signed by the owner or its authorized agent. 17 U.S.C. §§ 201, 202, 204

A work-made-for-hire label is insufficient by itself. Copyright Office guidance distinguishes employee-created works within employment scope from specially commissioned works, which must satisfy category and signed-agreement requirements. Circular 30

Record: affected outputs, reviewed rights documents, missing creator evidence, and intended uses potentially restricted. Do not extend copyright conclusions to patents or foreign rights without separate analysis.

5. Assess protections and exit against project dependencies

Review confidentiality, permitted disclosures, data handling, indemnities, liability limitations, termination, and transition against the engagement. Trace whether caps, exclusions, and carveouts affect a remedy the client expects to use. Separate commercial disadvantage from unresolved enforceability.

Read termination rights together with notice mechanics, payment consequences, survival, and delivery obligations. Castle’s example combines ten days’ prior written notice with specified delivery methods and a five-business-day deemed-notice rule for mailed notices. Do not calculate an action date from the termination provision alone. Castle, §§ 6–7

Test whether the client can actually operate after exit: files, credentials, background tools, knowledge transfer, and replacement personnel may matter independently of ownership.

Record: protection gaps, operational dependencies, proposed mitigation, and the person responsible for verifying any notice calculation before action.

6. Convert observations into actionable findings

Write each finding as evidence, departure from the baseline, consequence, uncertainty, and response. “IP clause inadequate” does not identify what decision is needed. Specify the deliverable, missing right or evidence, and proposed corrective document or business restriction.

Separate evidence requests from amendments. An unavailable subcontractor assignment requires investigation; a confirmed license restriction may require negotiation. Identify consequential changes to statements of work, definitions, survival, and related licenses.

Record: a concrete action, accountable owner, decision milestone, and approval authority. Explain whether the recommendation is a transaction condition, post-closing action, operational control, or proposed risk acceptance.

7. Assemble and verify the decision report

Place a short decision summary above the table. State the reviewed population, cutoff, material exclusions, highest-priority findings, recommended conditions, and decisions required. Group portfolio findings by consequence without erasing project-specific differences.

Recheck material findings against controlling documents, not extraction notes alone. Confirm that remediation addresses substance: receiving an assignment does not establish that it covers the relevant creators and outputs. Where execution is proposed, compare the signed correction with approved terms.

Record: final status, decision authority, remediation evidence, and unresolved assumptions. Keep accepted residual risk distinct from a corrected issue.

Worked example

Fictional scenario: Alder Quay Devices proposes acquiring a business that retained Marrow Peak Consulting to develop a forecasting tool for $180,000. Alder Quay plans internal modification after closing. The package contains signed master CA-01, signed statement of work SOW-02, invoice INV-07, and delivery email EM-04. Referenced subcontractor documents and an incorporated travel policy are unavailable.

CA-01 § 8 assigns project output but excludes background materials. SOW-02 identifies a consultant-owned calculation library without specifying license scope. CA-01 § 4 requires written travel preapproval; INV-07 bills $8,400 for travel. CA-01 § 11 requires completed and unfinished project work on termination. EM-04 attaches a presentation and executable, but no editable source files. All parties, documents, amounts, and terms are fictional.

The decision becomes conditional operational readiness, not “signed contract and delivered tool.” F-01 takes priority because modification is essential to the acquisition plan. F-02 supports investigation, not automatic invoice rejection. F-03 requires technical confirmation before relying on delivery wording. Missing source files do not establish nondelivery across the entire engagement, and no missing evidence is supplied by assumption.

Common mistakes

• Reviewing only the master. Read statements of work, amendments, and priority terms before identifying the obligation.
• Equating delivery with usable rights. Check creator title, excluded tools, licenses, and technical access separately.
• Calling unavailable approval a breach. Report the evidentiary gap unless the record supports a stronger conclusion.
• Ignoring transaction structure. Assess consent and continuity against the actual proposed acquisition.
• Closing findings on promises. Require supporting evidence or explicit risk acceptance by an authorized owner.

Final quality check

• Every material finding has a verified document ID and pinpoint citation.
• Execution status, hierarchy, scope exclusions, and missing incorporated documents are visible.
• Findings distinguish contractual text, operational evidence, and inference.
• Rights analysis addresses creators, background materials, and intended use.
• Financial exposure separates verified amounts from estimates and unknowns.
• Exit recommendations address notice mechanics and practical handover.
• Open issues have owners and milestones; accepted risks identify approval authority.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use due diligence classification to organize documents and prioritize human review, and tabular review to examine multiple agreements. In Word, contract review findings quote clauses, rank severity, locate text, and identify missing language as not present. Treat that absence finding as limited to the reviewed material until incorporated documents are checked. Lawyers retain responsibility for source verification and report conclusions. Book a demo to discuss this consulting-agreement workflow.

Frequently asked questions

Should every clause appear in the findings report?

No. Preserve coverage in working notes; emphasize decision-relevant deviations, gaps, and dependencies. Include acceptable terms when they resolve a material question or explain a recommendation.

How should an unavailable statement of work be reported?

Identify its reference, affected project, and blocked conclusions. Assign retrieval and a decision milestone. Do not call language absent when the unavailable document might contain it.

Does payment establish ownership of consulting deliverables?

Payment alone is not a sufficient ownership analysis. Review assignment language, work-made-for-hire facts, exclusions, and creator documentation against the federal copyright rules described above. Separately determine whether the client has the permissions its intended use requires.

Should the report include proposed redlines?

Include targeted drafting recommendations where correction is justified. Separate them from evidence requests and identify linked changes to scope, fees, licenses, or survival. Explain why the amendment matters rather than attaching unexplained markup.

Sources

• U.S. Copyright Office: Copyright Act, Chapter 2 — copyright ownership and transfer provisions.
• U.S. Copyright Office: Circular 30 — work-made-for-hire guidance.
• Castle Biosciences consulting agreement, SEC filing — negotiated expense and notice provisions, not market standards.
• Neoleukin Therapeutics consulting agreement, SEC filing — negotiated expense and document-priority provisions, not general law.

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.