Intellectual property fights arrive late: at final payment, at portfolio publish time, or when a client clones your process with another vendor. Independent agencies often discover they promised assignment in the contract while behaving like licence in delivery — or they assumed “we always keep portfolio rights” because that is how the last studio worked.
This guide explains how IP usually shows up in agency work: work-product, licences, assignment, portfolio use, and subcontractor flow-down. It is not legal advice. Use it to read your own agreements and prepare sharper questions for qualified counsel in your jurisdiction.
Pair it with agency client contracts for the full clause set, and with insurance when IP disputes touch indemnity or professional liability.
What IP means for marketing and creative studios
Intellectual property (IP) here means the legal rights in creative and strategic outputs — copy, design, code, frameworks, footage, layouts, media plans, and sometimes methodologies — plus the rights to use third-party assets embedded in deliverables.
Agencies typically juggle four buckets:
| Bucket | Typical examples | Who often expects to own |
|---|---|---|
| Client materials | Logo files, brand guidelines, product data | Client |
| Deliverables | Final ads, pages, edited video, campaign assets | Client after payment (varies) |
| Agency pre-existing IP | Methods, templates, internal tools, style systems | Agency |
| Third-party IP | Stock, fonts, music, platform content | Licence terms of vendor |
Disputes start when the contract does not sort deliverables from pre-existing IP, or when payment and transfer triggers are missing.
Default traps independent agencies step into
Trap 1 — “Work for hire” language you do not mean
Some client paper assigns everything automatically, including your reusable frameworks. Signing without review can transfer more than the engagement priced.
Trap 2 — Payment and transfer misaligned
The team sends final files while an invoice is outstanding. The client assumes ownership; your contract might say transfer happens on payment. Everyone is angry; counsel bills both sides.
Trap 3 — Portfolio silence
Neither side names whether you may show the work. You publish a case study; legal sends a takedown. Or you never publish and lose years of proof.
Trap 4 — Subcontractor gaps
A freelancer creates key art. Your client contract warrants you own deliverables — but your freelancer agreement never assigned rights. The chain is broken.
Trap 5 — Open-ended “all work product”
Broad definitions sweep in drafts, explorations, and pitch concepts you intended to discard or reuse.
Operational hygiene: match delivery behaviour to the contract. If transfer is on payment, withhold licence or final exports until accounts are current — only if counsel confirms that is enforceable for your deals.
Worked scenario: the case study that was not yours to post
Imagine a branding project completes. The client pays in full. The creative director posts a Behance-style breakdown with mocks and strategy slides.
The client’s legal team objects: the MSA assigns all deliverables including derivatives; internal strategy slides were marked confidential; the contract required written portfolio approval after a waiting period.
The agency removes the post, apologises, and learns the contract had a portfolio clause nobody enforced at kickoff. Sales had promised “we will feature you” verbally; the paper required client sign-off.
Fix forward:
- Portfolio clause in the kickoff checklist
- Case study plan submitted before publish
- Anonymised or partial assets when approval is slow
No invented outcomes — just a common pattern when portfolio rights are vague.
Licence vs assignment (plain language)
Assignment usually means transferring ownership (or all substantial rights) to the client, subject to contract triggers.
Licence means the client may use the work under defined terms while you retain ownership — exclusive or non-exclusive, territory, duration, media, and sublicensing rules.
Agencies often licence until final payment, then assign deliverables defined in the schedule. Pre-existing IP stays licensed, not sold.
Questions for your lawyer (examples, not prescriptions):
- Does assignment happen on final payment, per milestone, or on acceptance?
- Do you retain rights to unused concepts?
- May the client modify work without credit?
- What happens to WIP if the project ends early?
Write the answers in the SOW so producers do not guess.
Portfolio and marketing use rights
Portfolio rights are commercial assets for studios. Negotiate them explicitly:
- Permitted assets — final public-facing work vs internal decks
- Timing — after launch, after N days, after payment
- Approval — silence vs written opt-in
- Credit — named or anonymised case studies
- Employee and freelancer visibility — whether individuals may show pieces in personal portfolios
Some clients refuse all publicity; price that restriction if it hurts new business. Others allow anonymised vertical case studies. Document what you got.
Client content and approvals
Clients warrant they have rights to materials they supply — logos, user photos, music, claims. Your contract should say they indemnify you for their content breaches within limits counsel approves.
You warrant you will deliver work you have rights to — which loops back to freelancer agreements and stock licences. Keep licence PDFs with the project.
Subcontractors and the IP chain
When freelancers deliver:
- Their agreement should assign or licence rights to your agency consistent with client promises
- Moral rights and credit vary by jurisdiction — counsel flags what matters locally
- AI-assisted outputs may need separate disclosure and ownership language [NEED: counsel review as practice evolves]
Do not let procurement speed bypass the chain. One missing freelancer assignment can void a client warranty.
Align IP promises with insurance cover when you give advice touching trademarks, claims, or technical implementation.
Clause comparison (starting points for review)
Use this when reading client paper or drafting schedules — not as final wording.
| Topic | Agency-friendly starting posture | Client paper often pushes |
|---|---|---|
| Pre-existing IP | Retained; licence to client as needed | Broad “all work product” capture |
| Deliverables | Assign on payment / acceptance | Assign on creation |
| WIP on termination | Agency keeps unpaid explorations | Client keeps all concepts |
| Portfolio | Non-exclusive right after approval | No use without separate consent |
| Third-party assets | Client responsible for their inputs | Agency warrants entire stack |
Redline toward clarity, not toward winning every word fight. Escalate material gaps to counsel.
IP readiness checklist
| Item | Status | Notes |
|---|---|---|
| Master agreement defines pre-existing IP | ||
| SOW lists deliverables subject to transfer | ||
| Payment trigger matches file release practice | ||
| Portfolio clause in kickoff checklist | ||
| Freelancer / vendor agreements reviewed annually | ||
| Stock and font licences saved per project | ||
| AI use disclosed where contract requires |
Frequently asked questions
Do clients always own the work we make?
Not automatically — it depends on contract, jurisdiction, and who created the work. Assume nothing; read the transfer clause.
Can we reuse code or design components?
Only if you retained ownership or have a reusable licence. Generic libraries you built before the client engagement are different from bespoke deliverables.
What if the client never pays?
Contracts often tie transfer to payment. Enforcement is legal and commercial — discuss remedies with counsel before withholding deliverables.
Should we register trademarks for clients?
That is usually a distinct service and risk. Do not imply registration expertise in proposals unless licensed and insured for it.
Is this article enough to draft our contract?
No. This is orientation for owners and producers. Have a qualified lawyer bless templates you reuse.
Explore related risk topics on the Risk hub.
More agency reading
Share
