The contract terms that actually matter
Most studio agreements are signed unread by both parties. A small number of clauses determine what happens when something goes wrong.
Small studios frequently work on a proposal and an email, and most of the time that is fine, because most engagements are uneventful. The clauses below are the ones that matter when an engagement is not.
None of this is legal advice; contract law and its defaults differ by jurisdiction, and anything material warrants a qualified opinion. If monitoring tools are part of an engagement, this resource illustrates why clear notice and expectations matter.
Intellectual property and when it transfers
In many jurisdictions the creator owns the work by default until it is assigned in writing. Clients frequently assume they own it from the moment they pay a deposit.
State plainly what transfers, when, and on what condition — usually full payment. Also state what does not transfer: your tools, libraries, methods and anything pre-existing that the deliverable incorporates.
An assignment conditional on final payment is a standard term and one of the few real protections a studio has. It only works if the contract says so. For UK businesses, GOV.UK guidance on invoicing and payment is a useful reference for the formal payment framework.
Payment terms and the consequence of missing them
Terms with no stated consequence are aspirational. Say what happens: interest, suspension of work, or both. Referencing the statutory position where one exists strengthens it without adverse effect.
Scope, revisions and change
The commercial protection is in the scope document rather than the legal clauses. The contract's job is to point at it: what was agreed is defined there, changes are agreed in writing, and out-of-scope work is charged at a stated rate.
Termination
Both parties should be able to end the engagement, with notice, with a clear rule about what is payable for work done to that point.
Its absence produces the worst version of a failing project: a client who wants out and a supplier who wants paid, with nothing written down about either.
Liability, capped
An uncapped liability clause exposes a small studio to a figure it could never absorb. A cap at the value of the contract, or a multiple of it, is normal and usually accepted without argument.
This is also where professional indemnity insurance belongs in the conversation — worth having, and worth checking that its scope matches the work you actually do.
The practical ones people forget
- Who supplies content and assets, and by when.
- Third-party costs — licences, hosting, stock — and who pays them.
- Confidentiality, in both directions.
- Whether you may show the work in a portfolio, which is easier to agree at the start than after launch.
- What happens to files, accounts and access at the end.
The portfolio clause is the one most often regretted. Asking for permission at the outset is routine; asking a year later, when the relationship has cooled, frequently produces a no.