Web design contracts and deposits UK: the basics worth getting right

Web design contracts and deposits in the UK don't need a solicitor or a twenty-page document to do their job. Most disputes between a freelancer and a client trace back to the same handful of things left unsaid at the start: what counts as finished, who owns the work until it's paid for, and what happens if either side wants out halfway through. A short, plain-language contract that covers those points does more to prevent a bad project than any amount of chasing after the fact.

What the contract actually needs to say

A working web design contract is closer to a clearly written proposal than a legal instrument. It needs to name both parties, set out the deliverables in specific terms (a five-page site built on a named platform, not “a new website”), state the number of design revisions included before extra work is billed separately, and give a start date and a rough timeline. It should also say, in one sentence, what happens if the client goes quiet for an extended period: whether the project pauses, whether a restart fee applies, and after how long. None of this needs legal phrasing. It needs to be specific enough that neither side can genuinely misremember what was agreed six weeks later.

Deposits: what to ask for and why it holds up

A deposit taken before any design work begins is standard practice and rarely questioned by a serious client. A third to half of the total fee upfront, with the rest split across remaining milestones, is common and easy to justify in the contract itself: it's a share of the money in exchange for blocking out the time, not a request to fund the whole project before the client has seen anything. The deposit terms belong in the contract, not a separate email, so there's one document to point back to if a payment milestone is missed later. The chasing side of this, what UK law actually gives you once an invoice is overdue, is covered in invoicing and getting paid on time as a web designer; the contract is what makes that chasing easier, because the terms were agreed before either side had anything to argue about.

Who owns the work, and when

A point that catches out a lot of freelancers early on: without a clause saying otherwise, it's not automatically clear that a client owns the finished design and code the moment the project ends. A simple, fair approach is to state that ownership and any licence to use the work transfers to the client on receipt of final payment, not before. Until then, the freelancer retains rights to the work produced. This isn't an aggressive position, it's a normal commercial term, and stating it plainly avoids the awkward conversation that happens when a client asks for the source files with an invoice still outstanding.

A cancellation clause saves both sides an argument

Projects get cancelled. A client's circumstances change, a business closes, priorities shift. A cancellation clause doesn't need to be punitive, it needs to exist. A reasonable version says that the deposit is non-refundable once work has started, and that any milestone already reached at the point of cancellation is due in full, with work beyond that point billed at an agreed hourly or day rate. Writing this down before a project starts means a cancellation partway through is a straightforward calculation rather than a negotiation conducted while one side is already frustrated.

Getting it signed without slowing things down

A contract that never gets signed protects nobody. Free or low-cost e-signature tools cover this without adding friction: a client clicks a link, reads a short document, and signs from a phone in a couple of minutes. Sending the contract alongside the deposit invoice, both due before any design file is opened, keeps it attached to a decision the client is already making rather than a separate hurdle to clear later. This sits naturally inside a proper onboarding process, as one of the first things agreed rather than something raised after the first milestone has already slipped.

Keep it short enough to actually use

The most common failure mode isn't a badly written contract, it's no contract at all, because the freelancer assumed a long legal document was the only option and skipped it under deadline pressure. A one or two page agreement covering scope, deposit, ownership and cancellation, reused as a template for every new client with the specifics swapped in, gets signed far more reliably than something that looks like it needs a lawyer to read. It's worth revisiting the template once a year, but it doesn't need to be perfect on day one. It needs to exist before the first deposit invoice goes out.

None of this is something Patchscout touches directly, contracts and deposits sit entirely on your side of the relationship, but the kind of prospect who signs a contract and pays a deposit without an argument tends to be the kind who took the outreach seriously in the first place. An email grounded in a real audit of a business's website, rather than a generic pitch, tends to attract exactly that kind of client.

The three free searches at app.patchscout.co.uk/signup are enough to see whether Patchscout finds you that kind of prospect before you draft the first contract.