How to actually read the handover clause in a web design contract
Where the handover clause sits in a contract
You're on page three of the contract, and one sentence about "upon completion of the project" has stopped you cold. The handover clause is rarely labeled as such. There's no bold heading that says "ownership transfer" in most agreements, and nothing tells you to slow down when you reach it.
People read a contract front to back, once, at the pace of skimming. This is the one paragraph that deserves a different pace entirely.
Think of everything before it as scene-setting. This is the paragraph where the actual outcome gets decided, in language that never announces its own importance.
A good habit: bookmark the page or fold the corner the moment you spot it, so you can come back to it after finishing the rest of the document with fresh eyes.
A fresh read, even five minutes later, catches things a tired first pass misses entirely. It's a small habit that costs nothing and occasionally saves everything, which is a fair trade by any measure.
It's a few dense sentences, buried near the payment terms or the closing paragraphs, easy to skim past the first time through. It's also the part that actually decides who owns what once the invoice is paid, which makes it the single most important paragraph in the whole document, however plain it looks.
Read it twice. Read it out loud if that helps you catch the wording. Then read it a third time, slowly, before you sign anything.
A clause that's easy to find and plainly worded is a good early sign. One that takes real digging to locate is worth noting on its own.
Ask the designer to point to it directly if you can't find it yourself. Their reaction to that request tells you something before you've even read the sentence.
Phrases that transfer ownership versus phrases that don't
Some phrasing is direct: ownership of the completed website transfers to the client upon final payment. Short, clear, and easy to point to later if a question ever comes up.
Other phrasing sounds similar but isn't: the client is granted a license to use the website, or the designer retains rights to the work. A license and a transfer of ownership read almost the same to someone skimming quickly, and they mean very different things in practice.
The difference often comes down to a single verb. "Transfers" is not the same promise as "grants a license to use." Read for that verb specifically.
A contract can use warm, reassuring language everywhere else and still hinge entirely on that one word. Don't let the tone of the surrounding paragraph distract from it.
Friendly wording and clear ownership terms aren't the same thing, and a contract can offer plenty of the first while quietly skipping the second entirely, without ever sounding unfriendly or evasive along the way to anyone reading quickly.
Underline it if you're reading on paper. Highlight it if you're reading on screen. Either way, mark the exact word that does the work.
If the contract uses both words in different places, that's worth flagging directly. Inconsistent language is often just sloppiness, but it's still worth resolving before you sign.
Conditional handover language and what triggers it
Watch for the word "upon." A clause that transfers ownership upon final payment is doing real work. It names a specific, checkable event that either happened or hasn't.
A clause that transfers access at the designer's discretion, or after some undefined review period, is doing the opposite. That kind of wording keeps control with the designer indefinitely, phrased to sound like a routine formality rather than an open-ended condition.
Ask what the trigger actually is, in plain terms, and get the answer added to the clause itself, in writing, before you sign.
A trigger you can point to on a calendar is worth far more than one that depends on someone else's judgment. If the clause won't name one, ask directly why not, and wait for a real answer. A designer with nothing to hide can explain the timing in a single sentence.
Handover clauses that mention third-party licensed elements
Some contracts carve out an exception for licensed elements — a purchased template, a stock photo set, a plugin — that stay under someone else's license no matter what else transfers.
That carve-out isn't automatically unfair. Template and theme licensing explains why those pieces work differently from everything else in the build.
What matters is that the exception is spelled out clearly, not buried in language vague enough to cover more than it should. A named exception is fine. An open-ended one is not.
Ask for the specific items covered by the exception, by name, rather than accepting a general reference to "third-party materials" that could mean almost anything.
Asking for a rewrite when the clause is vague
If a clause is vague, ask for it to be rewritten before you sign, not after. Say specifically what you want it to say. A specific version is a short edit for a designer working in good faith and a real problem for one who isn't.
That single reaction — a quick, clean rewrite versus resistance — tells you almost everything about who you're about to work with.
A reasonable designer will treat the request as normal, even routine. Pushback on a plain clarification is worth paying attention to before you commit further.
Who owns your website is the bigger picture this one clause sits inside, and what to get in writing before you pay for a website covers the other terms worth pinning down at the same time, before a single dollar changes hands.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go