⚡ Promptolis Original · Legal
📝 Contractor IP Assignment Agreement — Protect Your Company's Work
The structured contractor IP assignment covering work-for-hire requirements, specific IP transfer language, pre-existing IP carve-outs, moral rights waivers, and the legal-enforceability framework that prevents disputes over who owns the work you paid for.
Why this is epic
Most contractor agreements have weak IP assignment language. Result: disputes over ownership of code, content, designs produced during engagement. This Original produces proper IP assignment: work-for-hire where applicable, explicit transfer, pre-existing IP handling.
Names the 5 IP contractor mistakes (no written agreement / work-for-hire misused / no pre-existing carve-out / moral rights issue / open-source complications).
Produces complete IP framework. NOT legal advice — attorney review for significant engagements.
The prompt
Example: input → output
Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.
<engagement-type>Software development contractor. Hiring freelancer to build specific feature for our SaaS platform.</engagement-type> <work-scope>Code for: new dashboard feature (backend API + React frontend), integration with existing product. ~6 weeks engagement.</work-scope> <ip-intent>Full ownership to our company.</ip-intent> <contractor-type>Independent US contractor. California resident.</contractor-type> <pre-existing-work>Contractor has open-source libraries they've built, may want to reuse portions. Has shared code from prior contract with another client (with permission).</pre-existing-work> <open-source-considerations>Will use standard OSS libraries (React, Node, Express). No GPL concerns typically.</open-source-considerations> <budget>$25K fixed-fee engagement.</budget> <timeline>6 weeks.</timeline>
Contractor IP Agreement: Software Development, $25K, 6 Weeks, California
A contractor IP assignment produces structured ownership framework preventing future disputes. NOT legal advice. Your situation — US contractor, software development, pre-existing work considerations, OSS usage — requires specific provisions. This framework produces: assignment language (not work-for-hire), pre-existing IP carve-outs, OSS protection, execution requirements.
Work-For-Hire vs. Assignment
Software development by contractor (not employee):
NOT work-for-hire typically. Copyright Act limits work-for-hire to:
- Works by employees
- Specifically commissioned works in 9 categories (contribution to collective works, film, translation, supplementary work, compilation, instructional text, test, answer material, atlas)
Software generally doesn't fit these categories. Therefore:
Use EXPRESS ASSIGNMENT language:
- Contractor retains copyright upon creation
- Upon delivery + payment, copyright ASSIGNED to company
- Must be in writing, signed by contractor
Why not just 'work for hire'? Because a court may invalidate work-for-hire designation for non-listed works. Then contractor owns the code + you have no rights.
Specific Assignment Language
Required clauses:
Assignment Clause:
'Contractor hereby irrevocably and unconditionally assigns, transfers, and conveys to Company, without further consideration, all rights, title, and interest in and to all works of authorship, inventions, designs, improvements, discoveries, trade secrets, know-how, and all related intellectual property rights (including copyrights, patents, trademarks, and trade secrets) conceived, developed, or reduced to practice by Contractor in connection with the services provided under this Agreement (the 'Work Product'). This assignment includes all rights to reproduce, prepare derivative works, distribute, perform, display, and commercialize the Work Product in any manner.'
Cooperation Clause:
'Contractor agrees to execute any additional documents reasonably requested by Company to perfect and record the assignment. Contractor hereby appoints Company as attorney-in-fact to execute such documents on Contractor's behalf if Contractor fails or is unable to do so.'
Waiver of Further Consideration:
'Contractor acknowledges that the consideration for this Agreement includes sufficient consideration for the assignment of the Work Product.'
Representation of Originality:
'Contractor represents and warrants that (a) the Work Product will be Contractor's original work, (b) no third party has any rights in the Work Product except as otherwise provided in this Agreement, (c) the Work Product will not infringe any third party's intellectual property rights.'
Pre-Existing IP Carve-Outs
Critical for software developers who bring prior code.
Pre-Existing IP Clause:
'The following pre-existing intellectual property owned by Contractor prior to this engagement ('Pre-Existing IP') is excluded from the assignment above:
[List specific items, such as:]
- Contractor's open-source libraries [list]
- Contractor's personal framework [name]
- [Any other identified prior work]
If Contractor incorporates any Pre-Existing IP into the Work Product, Contractor hereby grants Company a perpetual, worldwide, royalty-free, non-exclusive, sublicensable license to use, reproduce, modify, and distribute such Pre-Existing IP solely as incorporated into the Work Product.'
Pre-Existing IP Schedule:
Attached as Exhibit A:
- Specific descriptions of pre-existing work
- GitHub/repository links where possible
- Date of creation
- Contractor's continuing ownership + right to use elsewhere
For your contractor's situation:
- Their OSS libraries: list in schedule
- Shared code from prior client (with permission): verify permission, list in schedule
- Any proprietary frameworks: list
Third-Party Prior Work:
'Contractor represents that any third-party work referenced in Exhibit A: (a) Contractor has the legal right to incorporate into Work Product, (b) incorporation doesn't infringe third-party rights, (c) licenses are permissive (MIT, BSD, Apache 2.0 — NOT copyleft like GPL).'
Moral Rights + Waivers
Moral rights = attribution + integrity rights of creators. Recognized more in EU/Canada, less in US.
For US contractor, limited issue BUT include:
Moral Rights Waiver:
'To the extent any moral rights or similar rights exist or may exist in the Work Product, Contractor hereby waives such rights in favor of Company. This includes, without limitation, any right to be identified as the author of the Work Product or to object to any derogatory treatment of the Work Product.'
For international contractors (EU, Canada): moral rights cannot always be fully waived. Consult attorney for cross-border work.
Open-Source Protection
GPL contamination = biggest risk. GPL'd code incorporated into your proprietary product = must license your product under GPL.
OSS Usage Restriction:
'Contractor agrees to use only open-source software licensed under permissive licenses (MIT, BSD, Apache 2.0, or similar) in Work Product. Contractor represents that no GPL, LGPL, AGPL, or other copyleft-licensed software has been incorporated into Work Product without Company's explicit written consent.'
OSS Disclosure Clause:
'Contractor shall identify in Exhibit B all open-source software incorporated into Work Product, including licenses + versions. Contractor represents such incorporation complies with applicable license terms.'
Violation Remediation:
'If OSS contamination is discovered post-delivery, Contractor shall use best efforts to remediate at Contractor's expense, including replacing contaminated components with comparable non-contaminated alternatives.'
Confidentiality Integration
NDA is separate from IP assignment. Both needed:
NDA covers:
- Company confidential information
- Trade secrets
- Business strategies
- Customer data
- Duration: during + post-engagement (2-5 years typical)
IP Assignment covers:
- Work product ownership
- Specific deliverables
- Rights transfer
Common but different:
'Contractor acknowledges that during the engagement, Contractor will have access to Company's confidential information. Contractor agrees to maintain confidentiality per the separate Non-Disclosure Agreement executed on [date]. This Agreement does not modify or supersede such NDA obligations.'
Execution Requirements
Critical timing:
1. Sign BEFORE work begins. Retroactive IP assignments have weaker enforceability.
2. Written agreement — verbal commitments not enforceable for IP transfer (Copyright Act requirement).
3. Both parties sign: contractor + authorized company representative.
4. Consideration exchanged: payment or other consideration must be documented.
5. Delivery + acceptance: separate document confirming work product delivered + accepted.
Execution checklist:
- [ ] Agreement drafted (attorney-reviewed for $500-1,500)
- [ ] Exhibit A (pre-existing IP) completed
- [ ] Exhibit B (OSS list) completed after work begins
- [ ] NDA separately executed
- [ ] Agreement signed by both parties BEFORE work begins
- [ ] Copies retained + timestamped
- [ ] Post-engagement: final delivery + acceptance letter
Attorney Review Triggers
Attorney review required for:
1. Engagements >$10K — risk justifies review ($500-1,500 investment)
2. International contractors — cross-border IP considerations
3. Pre-existing IP concerns — specific carve-outs need legal review
4. Patents or patentable subject matter — inventor rights + disclosure
5. Any dispute during engagement — early intervention prevents escalation
Cost: $500-1,500 for 1-2 hours of attorney review on standard contractor agreement.
Worth it for: $25K engagement with ongoing platform value. Potential IP dispute cost could be 10x the review cost.
Key Takeaways
- Software development by contractor: use EXPRESS ASSIGNMENT language, NOT work-for-hire. Work-for-hire doesn't cover software under Copyright Act — designation could be invalidated leaving contractor with ownership.
- Pre-existing IP schedule (Exhibit A) essential. Contractor's OSS libraries + shared code from prior clients listed specifically. Protects both parties.
- Open-source protection: no GPL/copyleft code in deliverables. OSS schedule (Exhibit B) post-completion. Prevents contamination destroying proprietary product.
- Sign BEFORE work begins. Retroactive IP assignments have weaker enforceability. $500-1,500 attorney review + $25K engagement = worth prevention cost.
- NDA separate from IP assignment. Both documents needed. NDA covers confidential info; IP Assignment covers work product ownership. Don't combine into single generic document.
Common use cases
- Companies hiring freelance developers, designers, writers
- Consulting firms engaging sub-contractors
- Content creators hiring creative collaborators
- Startups outsourcing product development
- Companies wanting clean IP ownership for future fundraise/sale
Best AI model for this
Claude Opus 4 or Sonnet 4.5. IP assignment requires careful legal drafting + business awareness. Top-tier reasoning matters. NOT legal advice.
Pro tips
- NOT legal advice. Attorney review for significant engagements.
- Work-for-hire ONLY for specific work types: commissioned works listed in Copyright Act + employment context.
- For non-employee non-listed work: assignment language, not work-for-hire.
- Pre-existing IP carve-out protects contractor's prior work.
- Moral rights waiver in jurisdictions that recognize them (EU, Canada).
- Open-source use: contractor represents no GPL/copyleft contamination.
- Confidentiality + non-disclosure separate from IP assignment.
- Get agreement SIGNED before work begins. Retroactive assignment legally shaky.
Customization tips
- Build contractor agreement template with attorney. Reuse for each engagement. Updates based on learnings.
- For major contractors (ongoing), consider W-2 employment vs. 1099. Employment has stronger IP protection (automatic work-for-hire), but higher admin burden.
- Track all contractor contracts + engagements in searchable system. Institutional memory + audit trail for future fundraise/exit.
- International contractors have jurisdictional complexity. EU contractors: GDPR considerations. Indian/Eastern European: different IP frameworks.
- For open-source code you MUST include (e.g., using React, Express), standard + permissive. GPL concerns apply to less-common libraries. Be specific in OSS schedule.
Variants
Software Developer Contractor
For code + software development.
Content Writer + Designer
For creative work.
Consultant/Advisor
For strategic advisory work.
International Contractor
For cross-border considerations.
Frequently asked questions
How do I use the Contractor IP Assignment Agreement — Protect Your Company's Work prompt?
Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.
Which AI model works best with Contractor IP Assignment Agreement — Protect Your Company's Work?
Claude Opus 4 or Sonnet 4.5. IP assignment requires careful legal drafting + business awareness. Top-tier reasoning matters. NOT legal advice.
Can I customize the Contractor IP Assignment Agreement — Protect Your Company's Work prompt for my use case?
Yes — every Promptolis Original is designed to be customized. Key levers: NOT legal advice. Attorney review for significant engagements.; Work-for-hire ONLY for specific work types: commissioned works listed in Copyright Act + employment context.
Explore more Originals
Hand-crafted 2026-grade prompts that actually change how you work.
← All Promptolis Originals