Who owns consulting deliverables: the client or the consultant?

Who owns consulting deliverables when the contract is silent?#

Consulting deliverables under a silent contract are an uncertain area, which is why most firms never rely on the default. Under 17 U.S.C. 201(b), the employer is treated as the author of a work made for hire and owns the copyright unless a signed written instrument says otherwise, which generally covers what a firm's employees create within the scope of their jobs. For commissioned work, 17 U.S.C. 101 limits work made for hire to listed categories, such as a compilation, an instructional text or a supplementary work, and only where the parties expressly agree in a signed writing. A typical strategy report may not fit those categories, so a client that wants ownership usually needs an express assignment.

Courts may still find that a paying client holds an implied license to use what it commissioned for the purpose it was created. That leaves both sides exposed: the client may not be able to modify or resell the work freely, and the firm may not be able to reuse it without dispute. Most MSAs and SOWs therefore state ownership expressly.

Ownership by clause type#

Ownership of consulting work usually turns on a handful of clause types, and the combination matters more than any single clause. Use the table to sort your client agreements before deciding what can be reused or licensed.

Read each row against the definitions section. A clause that assigns deliverables means little until you know whether deliverables means the final report or every file created during the engagement.

What counts as a deliverable, and what does not?#

A deliverable is whatever the contract defines it to be, and the definitions vary more than most partners expect. Narrow definitions cover the final report, model or presentation named in the SOW. Broad work product definitions can include drafts, interview notes, workshop outputs, analyses and data files created during the engagement.

Internal firm records sit in a different place. Proposals, staffing plans, timesheets, project review notes and internal playbooks are usually firm records, yet they often quote or summarize client confidential information. Treat them as firm-owned but not automatically free to share.

Joint ownership is the third pattern, and it is harder to manage than it sounds. Co-owners' rights to use, modify and license shared work differ by jurisdiction and by contract, so a clause that says the parties jointly own the deliverables can block either side from licensing without the other's consent. If joint ownership is unavoidable, spell out exactly what each party may do on its own.

Can a consultancy use aggregated engagement data for AI?#

A consultancy can use aggregated engagement data for AI only where its contracts allow that use or the data has been de-identified so that no client confidential information remains, and that judgment should be made with counsel. An aggregated data clause that permits improving services may not extend to licensing records to a third party such as an AI developer.

Privacy law adds another layer. Engagement files often contain names and details of client employees and interviewees, and laws such as GDPR or CCPA may apply depending on whose data it is and where they are. A residuals clause does not help here, because residuals cover unaided memory, not stored records.

• 1Pull the MSA, SOWs and amendments for every engagement in scope.
• 2Classify each client by clause type: assignment, license-back, aggregated data permission or silent.
• 3Check confidentiality survival and any return or destroy obligations already triggered.
• 4Confirm whether permitted purposes include licensing, not just internal improvement.
• 5Identify personal data of client staff, interviewees and end customers.
• 6Decide per client: include after de-identification, ask for consent, or exclude.
• 7Record the decision and the contract language it rests on.

How to draft MSAs that preserve data rights going forward#

MSAs that preserve data rights do so by naming what the firm keeps and what it may do with engagement data, in plain terms the client can accept. Clients increasingly ask how consultants use AI and their information, so a clear clause is easier to negotiate than a vague one.

Common drafting points include a schedule listing pre-existing IP such as methodologies, templates and diagnostic tools, a license-back for generic elements of deliverables, and an aggregated data clause that names its purposes, including developing and licensing de-identified datasets where that is the intent. Pair any such clause with a de-identification standard and an archival carve-out from return or destroy duties.

Fix the definitions as well. A deliverables definition tied to the items named in each SOW keeps working notes, internal analyses and firm templates out of the assignment, while a separate clause can still give the client access to supporting materials it reasonably needs.

Illustrative: an operations consultancy sorts its client agreements#

Illustrative: a fictional IT strategy consultancy wants to know which engagement records it could license. Its MSAs sit in a contract management tool, engagement files in Google Drive, and time and staffing data in BQE Core.

Counsel sorts the client agreements into three groups. Clients with full assignment and broad work product definitions are excluded entirely. Clients with a license-back and an aggregated data clause that names licensing are in scope for de-identified project review notes. Silent or ambiguous agreements are parked until the firm decides whether to ask those clients for consent.

The resulting scope covers firm-authored playbooks and de-identified internal project reviews. Client deliverables stay out, and the decision log shows which clause supported each inclusion.

How SourceX handles deliverable ownership#

SourceX treats deliverable ownership as part of the Rights step in the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Client-owned deliverables are carved out by default, and firm records are reviewed for embedded client confidential information during Preparation.

The SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization for each package, so the contract basis for every included record family is written down. Final rights decisions rest with the firm and its counsel.