Clarify source files, portfolio rights, licenses, and when ownership transfers.
Key takeaways
- List final deliverables that transfer to the client.
- Carve out pre-existing code, fonts, stock assets, and methods.
- Connect transfer to full payment and third-party licenses.
Ownership, licenses, and reusable tools
A developer delivers a custom website while reusing a private component library. The client can own the paid-for design and project code while the developer retains the underlying library and grants the client a permanent license to use it within the finished site.
Run a contract-specific review
Separate intellectual-property assets into three groups: material created specifically for the client, pre-existing tools or methods, and third-party material. Then state whether each group is assigned, licensed, or excluded and identify the event that activates the transfer.
1. Inventory assets
List source files, final exports, code libraries, fonts, stock media, prompts, methods, and portfolio samples.
2. Choose the right grant
Distinguish an assignment from an exclusive or nonexclusive license and state territory, duration, and uses.
3. Handle dependencies
Record third-party licenses and pre-existing components that cannot be transferred outright.
4. Link transfer to payment
State whether ownership or the final license begins only after cleared final payment.
Stress-test the difficult case
Modern deliverables often combine employee work, subcontractor contributions, open-source code, stock assets, fonts, templates, and AI-assisted output. The freelancer cannot transfer broader rights than those sources permit. A client may also need editable source files while the creator needs reusable tools and portfolio rights. The agreement should address each component separately, including attribution, license continuity, model or dataset restrictions where relevant, and responsibility for replacing an asset that cannot be used as planned. A blanket ownership sentence rarely resolves this mixed chain of rights.
Verification pass before signing
Build a provenance ledger before final delivery. For each material component, record its creator, source, license or assignment, permitted uses, restrictions, receipt or repository link, and whether it transfers to the client. Match the ledger to the source-file inventory and final exports. Confirm that subcontractor agreements support the promised grant and that client-supplied assets are identified as client responsibility. At payment, issue a short transfer notice listing the assets whose ownership or license has activated and the components that remain subject to separate terms.
Evidence to retain
Preserve source inventories, third-party receipts, license terms, authorship records, approvals, payment confirmation, and the final transfer notice.
Worked example
A client may own the finished logo after payment while the designer keeps reusable sketching methods and properly licensed fonts remain governed by their vendor terms.
What to verify
1. Scope
List final deliverables that transfer to the client.
2. Trigger
Carve out pre-existing code, fonts, stock assets, and methods.
3. Evidence
Connect transfer to full payment and third-party licenses.
4. Fallback
Address portfolio display and confidential launch timing.
Build the decision record
| Review item | Record before signing |
|---|---|
| Inventory assets | List source files, final exports, code libraries, fonts, stock media, prompts, methods, and portfolio samples. |
| Choose the right grant | Distinguish an assignment from an exclusive or nonexclusive license and state territory, duration, and uses. |
| Handle dependencies | Record third-party licenses and pre-existing components that cannot be transferred outright. |
| Link transfer to payment | State whether ownership or the final license begins only after cleared final payment. |
Warning signs
- “All ideas” can sweep in unrelated know-how.
- Third-party assets cannot always be reassigned.
- Moral rights and employee rules vary by jurisdiction.
Questions to resolve before signing
- What would prove that “inventory assets” is satisfied if the parties later disagree?
- What would prove that “choose the right grant” is satisfied if the parties later disagree?
- What would prove that “handle dependencies” is satisfied if the parties later disagree?
- What would prove that “link transfer to payment” is satisfied if the parties later disagree?
Sources and further reading
- IRS: Independent contractor status
- U.S. Copyright Office: Works made for hire
- FTC: Endorsements and testimonials
External sources explain general rules and terminology. Your signed agreement, current policy, jurisdiction, provider documents, and individual facts control the actual outcome.
Open the related ContractFixPro tool