Notes
What a website ownership clause actually has to say.
Nearly every agency contract contains a sentence about ownership. Nearly every one of them leaves the same four things out.
Search for advice on website ownership and you will find the same paragraph a hundred times: make sure your contract specifies that you own the intellectual property. It is correct and it is nearly useless, because it does not tell you what the clause has to cover, and the gaps are not in the part everybody quotes.
Here is the wording that appears, in some form, in most agreements. Read it and it sounds complete.
That sentence transfers copyright in the design and the code. It does not transfer a single account, it does not say when you get the files, it does not cover anything the agency licensed rather than made, and it stops working the moment there is a dispute about payment. Four gaps, each of which is the one that actually bites.
Gap one: copyright is not access
Intellectual property and account control are two different bodies of law and two different practical problems. A clause can assign you every copyright in existence and leave you unable to log into anything.
Owning the copyright in your website means nobody else may copy it. It does not mean you can deploy it, change the DNS, read the analytics, or stop someone else from doing those things. Those powers follow the account registration, and an account is not intellectual property. It is a contractual relationship between the registrar or host and whoever opened it.
So the clause needs a second half that names the accounts. Not "access to all accounts", which is the weaker thing again, but registration in the client name.
The email address matters more than it looks. Control of the account recovery address is control of the account. If the registrar has an address at the agency domain on file, a password reset restores their access and not yours, and no ownership clause anywhere changes that.
Gap two: the transfer trigger
Almost every version of this clause fires on final payment. That is reasonable and it is also exactly backwards for the situation you are protecting against, because the situation you are protecting against is a disagreement about money.
If the relationship ends badly, it ends over an invoice. Ownership conditioned on final payment means that at the precise moment you most need the assets, the trigger has not fired. You are now negotiating for your own website from a position where the other party holds it.
The fix is not to remove the payment condition, which no supplier will accept and which is not fair anyway. The fix is to separate the two things being held.
- Accounts are registered in your name from day one, not transferred at the end. There is no reason for a domain to ever be registered to a supplier, and a supplier who wants it that way should be asked why.
- Copyright in the deliverables transfers on final payment, as normal.
- A source escrow or repository access clause gives you a copy of the work in progress throughout, held but not licensed until payment. You hold the files; you simply may not use them yet.
That arrangement leaves the supplier the leverage they are entitled to, which is the right to withhold a licence until they are paid, and removes the leverage they are not entitled to, which is possession of your identity on the internet.
Gap three: everything they did not make
A modern website is mostly other people’s work. Fonts, a theme, stock photography, a page builder, plugins, an icon set, a mapping service, a booking widget. The agency cannot assign you rights they never held, so a blanket transfer clause silently excludes all of it, and nothing in the contract tells you which parts those are.
This becomes real in two ways. A licence that was purchased on the agency account lapses when they stop paying for it, and a font licensed for one site is not licensed for the replacement you build later. Neither failure announces itself. Things just stop working, or a letter arrives.
A supplier who cannot produce that list does not know what is in your website. That is worth finding out before you sign rather than after.
Gap four: what happens on the way out
Ownership clauses describe a state. They rarely describe a process, and the process is where the time goes. "The Client owns the deliverables" does not say in what format, within how many days, or by whom.
An exit clause should be boring and specific. A named number of days. A named format. A named person responsible. Continuation of hosting during the handover at the ordinary rate, so that leaving does not mean going dark. And, in writing, that assistance with migration is included rather than billable at whatever rate applies to a client who is leaving.
| Term | Weak wording | What to ask for instead |
|---|---|---|
| Ownership | Client owns the intellectual property | IP assigned on final payment, and all accounts registered in the Client name from the outset |
| Files | Client will be provided the files | Complete source and database export in a named, non-proprietary format within 10 business days of request |
| Third parties | Silent | Written schedule of every third-party licence, holder of record and renewal date |
| Hosting | Silent | Hosting continues at the standard rate for 30 days after termination |
| Migration | Silent, or billable | Reasonable migration assistance included, capped at a named number of hours |
| Portfolio | Silent | Supplier may show the work; Client approves anything naming the Client |
The test that survives every rewrite
Contract language is easy to argue about and easy to soften. So carry one question through the negotiation and check the redraft against it every time.
If this relationship ended today, over money, in bad temper, on the worst possible terms, what could the other party still switch off?
Whatever survives that question is what you actually own. Everything else is an arrangement that has not been tested yet. A supplier who is comfortable with the answer will have no difficulty with any of the wording above, because none of it costs them anything they were entitled to keep.
Questions
Does an ownership clause mean I can log into my hosting?
No. Ownership of intellectual property and control of an account are separate. A clause can assign you every copyright in the work and leave every account registered to the supplier. The clause needs a second part that requires accounts to be registered in your name, under an email address you control, with supplier staff added as delegated users.
Why is "transfers on final payment" a problem?
Because the scenario you are protecting against is a dispute about payment. If ownership only fires once the last invoice is settled, then at the exact moment the relationship breaks down the transfer has not happened. Keep the payment condition for the copyright, but register the accounts in your name from the beginning so possession is never the thing in dispute.
What are third-party components and why do they matter?
Fonts, themes, plugins, stock images, page builders and paid services embedded in the site. Your supplier cannot assign you rights they never owned, so a blanket transfer clause silently excludes all of it. Ask for a written schedule listing each component, its licence, who holds that licence and when it renews.
What should an exit clause say?
A named number of days for delivery, a named non-proprietary format, a named person responsible, hosting continuing at the standard rate through the handover, and migration assistance included rather than billed at a departure rate. Ownership describes a state; the exit clause is the process, and the process is where the delay happens.
Is any of this unusual to ask for?
No. None of it costs a supplier anything they were entitled to keep. It removes possession as a bargaining chip while leaving intact the supplier’s legitimate leverage, which is the right to withhold a licence to use the work until they have been paid. Reluctance to any of it is itself informative.