IP moves with final payment, not with good intentions.
7 min readWhat IP means in plain terms
Intellectual property is the output you create: documents, designs, code, processes, content. Clients often assume they own everything you make on their dime. You may assume you keep templates and methods. Confusion here leads to fights at project end.
Write down who owns what before the first deliverable.
General rules most VAs follow
| Topic | Common practice |
|---|---|
| Client-owned work | Custom deliverables built for them, after full payment |
| You keep | Your general templates, tools, and pre-existing materials |
| Portfolio use | Only with client permission if the work is confidential |
| Transfer timing | Often tied to final payment, not mid-project drafts |
| Unpaid work | You typically do not hand over final files until paid |
Exact terms depend on your contract. When in doubt, ask a lawyer, not a blog.
What to put in writing (general)
- Who owns final deliverables
- When ownership transfers (often upon final payment)
- Whether you may show work in your portfolio
- What happens if the client stops paying mid-project
- License vs full ownership (if the client only needs usage rights)
Use an agreement template or Salag Agreement Builder for a starting point. Have a lawyer review for high-value or unusual IP deals.
Common mistakes
- No IP clause at all. Both sides guess.
- Sending source files before final payment without agreement.
- Using client assets in other work without permission.
- Assuming Upwork terms cover off-platform work (they may not).
Final thoughts
IP issues are easier at the start than at handoff. One paragraph in your agreement saves awkward conversations when the invoice is due.
How Salag helps
- Client Red Flag Checklist. Screen clients before sharing unreleased work or source files.
- Payment Method Risk Check. Confirm payment terms align with when you hand over deliverables.
- Project Scope Calculator. Scope deliverables clearly so IP boundaries match the work.
Move safer. Not faster.
In short
Freelance IP transfer usually means the client owns the work you create for them once they pay per your agreement. Get those terms in writing before you start. This article gives general freelance practice, not legal advice. For complex IP questions, ask a lawyer.
Common questions
Freelance IP transfer usually means the client owns the work you create for them once they pay per your agreement. Get those terms in writing before you start. This article gives general freelance practice, not legal advice. For complex IP questions, ask a lawyer.
Write down what you agreed on and what changed. Do not start new work on vague terms.
Use plain English, confirm in writing, and set clear hours. Clients hire you for reliability, not cheap labor.
Put the basics in your agreement or a recap email before billable work starts. Bigger projects need fuller terms.
Stay warm but firm. Offer options inside a clear process, like a change order or a short written recap.
CLEAR means: capture facts, compare to your agreement, name tradeoffs, confirm in writing, and save the decision for next time.
Escalate when the same problem repeats: unpaid extras, late approvals plus new asks, or refusal to confirm in writing.
Yes. A clear email with tasks, dates, price, and limits beats a verbal yes every time.
Salag gives you tools and templates so you can set boundaries before small problems grow.
Use written recaps, scope trackers, and Salag tools like agreement builders and scope detectors.
Most recaps take five minutes after a call. That small step saves hours of arguing later.
Yes. Retainers need weekly change logs. Projects need milestone gates. Always compare new asks to written terms.
Pause billable work on unclear items. Send a narrow summary of what you will do. Save their reply either way.