What It Does
A consulting agreement can pay for advice, implementation, reports, design, code, research, or a finished work product. The deliverable clause turns that service description into an output that can be reviewed. The IP clause then distinguishes new work product from the consultant’s pre-existing tools, methods, know-how, and third-party materials.
Acceptance should be tied to agreed criteria rather than a client’s unbounded preference. It should state the review period, the required rejection detail, the correction cycle, and whether payment or ownership turns on acceptance. Counsel should also test whether the client has the rights needed to operate, modify, sublicense, and transfer the deliverable after the engagement ends. GC AI’s Acceptance Clause guide covers review periods, rejection notices, and remediation.
Defines deliverables, milestones, dependencies, assumptions, and completion evidence
Allocates ownership of new work product and rights to pre-existing materials
Sets acceptance criteria, review windows, rejection notices, and remediation
Connects acceptance to payment, warranty, release, and ownership or license rights
Allocates third-party materials, open-source components, confidentiality, and infringement risk
When You'll See It
These provisions appear in management consulting, technical consulting, design, research, implementation, engineering, marketing, and independent contractor agreements. They may be in the main agreement, a statement of work, a project schedule, or a change order.
Examples
California Micro Devices Corporation / Kevin Berry
Consulting Agreement, SEC Exhibit 10.24
Work product ownership
One-Sided
2006
“does hereby assign, to Company all worldwide right, title and interest in and to the Work Product”
DentonX Inc. / LocusX Technologies Inc.
Technical Consulting Agreement, SEC Exhibit 10.4
Client acceptance rights
One-Sided
2025
“Consultant shall submit each Deliverable for review and acceptance upon completion”
Negotiate
Define each deliverable, milestone, acceptance criterion, dependency, and delivery format in the scope.
Require written acceptance or a detailed rejection that identifies the unmet criterion.
Make the consultant correct nonconforming work within a defined period and at no additional fee where appropriate.
Take ownership of new work product with a present assignment and require further-assurance cooperation.
Secure a broad enough license to pre-existing tools, methods, know-how, and third-party materials embedded in the deliverable.
Separate client-owned deliverables from pre-existing materials, general know-how, reusable tools, and third-party components.
Tie acceptance to objective criteria and prevent rejection based solely on a new preference or scope change.
Limit review rounds and require timely feedback so the project does not remain open indefinitely.
Preserve payment for completed work and set a process for approved changes and additional services.
Represent that the deliverables do not knowingly infringe third-party rights, subject to client materials and instructions.
Red Flags
“Work product” is undefined, so ownership may extend to the consultant’s general tools and know-how.
The client may reject for any reason, but the agreement contains no objective criteria or review deadline.
Pre-existing IP is listed as excluded without a license broad enough for the client’s intended use.
Ownership is said to transfer on payment or acceptance, but a dispute can leave the client without operational rights.
Third-party or open-source materials are used without attribution, license, security, or replacement obligations.
FAQs
This content is for informational purposes only and does not constitute legal advice.
