Protect your payment and your rights: scope creep, slow payment, IP that transfers before you are paid, uncapped liability, and kill fees, explained in plain English with the fix for each.
For freelancers and agencies, the contract is where the money is won or lost. It decides whether you get paid on time, whether 'one small change' becomes weeks of unpaid work, who owns what you make, and how much you could be on the hook for if something goes wrong.
This guide covers the clauses that most often hurt independent workers: vague scope, slow or conditional payment, IP that transfers before you are paid, and uncapped liability. For each one it explains the risk and the change to ask for.
It is general information, not legal advice. Use it to read your next client contract with confidence and to negotiate the terms that protect your business.
Red flags to watch
Vague scope and unlimited revisions
Without a defined scope and a revision limit, 'until the client is happy' becomes unpaid work with no end. Scope creep is the single most common way freelancers lose money, because each extra request feels small but the total is unbounded.
Ask for: Ask for a written list of deliverables, a set number of revision rounds, and a clear rate for any work beyond the agreed scope.
Slow or conditional payment
Watch for long payment terms (net-45 or net-60), payment only 'on final approval', or a right to withhold for any reason. Each one delays or endangers your money, and 'on approval' hands the client a reason to stall indefinitely.
Ask for: Ask for a deposit up front, milestone payments on longer jobs, shorter terms such as net-14 or net-30, and a late-payment fee.
IP transfer before full payment
Many contracts assign ownership of your work to the client on creation or on delivery. If ownership passes before you are paid in full, you lose your main leverage if the client does not pay. The timing of the transfer matters as much as the transfer itself.
Ask for: Ask that IP ownership transfers only on receipt of full payment, and that you keep the right to show the work in your portfolio.
Uncapped liability and broad indemnity
An indemnity makes you cover the client's losses in certain situations; uncapped, it can expose you far beyond the value of the job. A small project should not carry unlimited financial risk. Look for a liability cap and a sensible limit on what you indemnify.
Ask for: Ask to cap your total liability at the fees paid, or a small multiple of them, and to exclude indirect and consequential losses.
One-sided termination and missing kill fees
Check what happens if the client cancels mid-project. Without a kill fee or payment for work done, you can be left unpaid for completed work while you may still owe notice or deliverables. Termination terms are often tilted heavily toward the client.
Ask for: Ask for payment for all work completed up to termination, plus a kill fee or notice period, and make the termination rights mutual.
Exclusivity and non-solicit restrictions
Some client contracts quietly stop you from working with competitors, taking similar clients, or being hired directly by the client's contacts. For an independent business, an unexpected exclusivity or non-solicit clause can cut off future income.
Ask for: Ask to remove or narrowly limit any exclusivity and non-solicit terms so they do not restrict your wider freelance business.
Get paid: payment terms that protect you
Take a deposit before you start, break larger projects into milestones with a payment at each one, keep your terms short, and add a late fee so delay has a cost. These four habits prevent most payment disputes before they begin.
Tie the final handover of intellectual property to the final payment. Keeping ownership until you are paid in full is the single strongest piece of leverage a freelancer has, and a clear payment schedule in the contract is what makes it enforceable.
Employee or contractor? Why classification matters
Some client contracts blur the line between a contractor and an employee, which affects your taxes, your benefits, and your independence. If a contract controls your hours, your tools, and your exclusivity the way an employer would, it may misclassify you.
Keep control over how and when you deliver the work, and be cautious of terms that treat you like staff without giving you any of the protections of staff. If a contract reads like employment, it is worth checking the local rules on classification.
Pre-signing checklist
Deliverables and the number of revisions are defined
A deposit and a clear payment schedule are agreed
Payment terms are short, with a late fee
IP transfers only after you are paid in full
You keep portfolio rights to the work
Liability is capped, ideally at the fees paid
Termination pays you for work done (kill fee or notice)
No surprise exclusivity or non-solicit restrictions
How ClauseShift helps
Paste the text, upload a PDF or DOCX, or transcribe a voice note. You get a plain-English risk report: an overall score, the specific clauses that matter with the exact contract text cited, and the key dates you need to track. ClauseShift does not keep the document you upload, only the report is saved to your account, and it trains no AI of its own on your contracts.