
Why small contract mistakes cause big problems
Most disputes I see between freelancers, small businesses and their clients don't start with a dramatic betrayal. They start with a sentence nobody thought twice about, a page that never got signed, or a clause that seemed like standard boilerplate until the relationship turned sour. A contract is not a ritual you perform to look professional. It's the document you'll rely on when things go wrong, and by then it's too late to fix weak wording. The good news is that the most common mistakes are also the easiest to avoid, provided you build a habit of reviewing every agreement carefully before you sign or send it.
Vague scope and deliverables
The single most frequent problem is a scope section that sounds reassuring but commits to almost nothing specific. Phrases like "ongoing support", "reasonable revisions" or "as discussed" feel friendly when you're keen to get started. Six weeks later, when the client expects unlimited changes and you expected two rounds, nobody can point to a clear answer.
- Describe deliverables in plain, countable terms: "two logo concepts, one revision round, final files in PNG and SVG".
- State what is explicitly not included, such as hosting, copywriting or third-party licence fees.
- Put a number on revisions and a deadline on feedback, for example "client feedback within five working days".
- Reference any separate specification or brief as an annex, and make sure that document is dated and version-controlled.
If you can't describe the work in measurable terms, you don't yet have a contract, you have a hope.
Missing signatures and unclear acceptance
An unsigned contract is not automatically worthless in England and Wales, but relying on that argument is expensive and stressful. Verbal agreements and email chains can form binding contracts, yet proving the exact terms is far harder than producing a signed document. Don't leave this to chance.
- Use a signature block with printed name, position, company and date for each party.
- Accept electronic signatures, which are generally valid, but keep a clear record of who signed and when.
- For smaller jobs, use a written acceptance line: "Please reply confirming acceptance of these terms." A reply saying "agreed" is better than silence.
- Check that the person signing actually has authority to bind the business, especially with larger clients.
- Keep the final version, not a draft with tracked changes, and store it somewhere you can find it in two years.
A contract only protects you if you can prove what was agreed. Signatures and dated acceptance records do exactly that.
Ignoring termination and exit rights
Termination clauses get skimmed because nobody plans for the relationship to end. That's precisely why they matter. A contract with no exit route can trap you in unpaid or unworkable arrangements, while one with a poorly drafted exit route can leave you liable for work you never delivered.
- Check the notice period. Thirty days is common, but rolling contracts sometimes require three months or more.
- Look for termination for convenience versus termination for breach, and understand which applies to you.
- Confirm what happens to unpaid invoices, work in progress and intellectual property on termination.
- Watch for auto-renewal clauses and diarise the cancellation deadline well in advance.
- If you're the supplier, insist on the right to suspend work if invoices go unpaid beyond an agreed period.
Read the exit before you commit to the entrance. If the termination terms feel unreasonable now, they'll feel much worse when you actually need them.
Payment terms that quietly work against you
Payment clauses are where goodwill meets cash flow. "Payment on completion" sounds fine until the client disputes completion. "Payment within 30 days of invoice" sounds standard until you realise the clock starts when they approve the invoice, not when you send it.
- Set a fixed payment period, such as 14 or 30 days from invoice date, and state the invoice date clearly.
- Agree a deposit or staged payments for larger projects, for example 50 per cent upfront.
- Include a late payment interest provision. UK law gives businesses a default entitlement, but stating it in the contract removes any argument.
- Clarify who bears bank fees for international transfers.
- Say what happens if an invoice is queried, so payment of the undisputed portion isn't held up.
Cash flow kills more small businesses than bad ideas do. Your contract should make getting paid predictable, not optional.
Liability, IP and the clauses people skip
These sections are dense, which is why they're skipped. That's a mistake, because they decide who carries risk when something goes wrong.
- Check whether liability is capped and at what level. An uncapped indemnity can expose you to losses far beyond the value of the job.
- Confirm who owns the intellectual property, and when ownership transfers. Ideally, it passes to the client on full payment, not before.
- If you reuse components or pre-existing code, reserve those rights explicitly.
- Ensure confidentiality obligations run both ways, not just against you.
- Check whether the contract allows the client to assign it to another company without your consent.
None of this requires a solicitor for every routine job. It requires you to read, ask questions and push back when a clause doesn't fit the work you're actually doing.
A simple review routine that pays off
Before you sign or send any agreement, run through the same short checklist every time. Does the scope say exactly what's included and excluded? Is there a signature or written acceptance? Do you understand how either side can exit? Are payment dates, amounts and consequences clear? Are liability and IP terms something you can live with? If any answer is no, fix it before work begins, not after.
You don't need impenetrable legal language to be well protected. You need clear terms, a signed record and the discipline to review every contract carefully. Do that consistently and you'll avoid the disputes that catch most freelancers and small businesses out.





John Doe
14 January, 2022Having no content in post should have adverse..
Chauffina Carr
10 April, 2022We use these tests all time! Killer stuff!
Jim Séchen
16 July, 2022Thanks for all the comments, everyone!