Introduction

In service agreements, understanding the difference between deliverables and derivative works is crucial for managing intellectual property (IP) rights and avoiding disputes. Deliverables are the tangible outputs a service provider must produce, while derivative works are new creations based on existing IP. This practice note clarifies these concepts, highlights key distinctions, and offers negotiation strategies and practical approaches for both clients and service providers.

Deliverables

• Tangible outputs the service provider is contractually obligated to produce (e.g., reports, software modules, designs, prototypes).
• Defined in the scope of work and tied to milestones, payments, and acceptance criteria.
• Typically intended for the client’s use and integration into their business.

Derivative Works

• New creations based on or incorporating pre-existing intellectual property (IP).
• Examples: modifications of existing software, adaptations of training materials, enhancements to proprietary tools.
• May blend client IP, provider IP, or third-party IP, raising ownership and licensing complexities.

Key Distinctions

Negotiation Strategies for IP Rights

For Clients

• Assignment of Deliverables: Seek full ownership of deliverables to avoid dependency on the provider.
• License Back to Provider: Allow provider limited rights to use deliverables for internal purposes, ensuring client exclusivity in its market.
• Clear Definition of Derivative Works: Ensure contract specifies whether modifications of provider’s tools become client property or remain provider-owned.
• Avoid Hidden Dependencies: Require disclosure of any embedded provider IP or third-party components.

For Service Providers

• Retain Core IP: Protect proprietary methodologies, frameworks, or tools by carving them out from deliverables.
• License Instead of Assign: Grant clients broad usage rights while retaining ownership of derivative works to preserve reusability.
• Define “Background IP”: Clarify that pre-existing IP remains provider-owned, even if incorporated into deliverables.
• Royalty or Fee Structures: Negotiate additional compensation if client seeks ownership of derivative works that build on provider’s IP.

Practical Approaches

• Hybrid Models: Deliverables are assigned to the client, but derivative works based on provider’s background IP are licensed.
• Modular Contracting: Separate schedules for deliverables and derivative works, with distinct ownership and licensing terms.
• Use Restrictions: Clients may own deliverables but agree not to exploit provider’s embedded IP outside the project scope.
• Cross-Border Considerations: In comparative law contexts, definitions of “work for hire” and enforceability of IP assignments vary (e.g., stricter formalities in Germany vs. more flexible approaches in the US).

Conclusion

Effectively distinguishing between deliverables and derivative works in contracts is essential for protecting intellectual property rights and ensuring clear ownership and usage terms. Both clients and service providers benefit from well-defined agreements that address ownership, licensing, and risk management to foster successful collaborations.

Disclaimer: This practice note provides general information and does not constitute legal advice. Parties should consult qualified legal professionals for advice tailored to their specific circumstances.