Plain-English guide · free
Freelance Contract Red Flags & What to Look For
A freelance contract is often the only protection you have. There's no HR department, no employee handbook, no manager smoothing things over — just the words on the page.
Most freelance contracts are written by the client, for the client. That's not necessarily sinister, but it means the default terms usually favor them. Knowing what to look for turns a one-sided document into a fair one — or at least helps you spot trouble before you're in it.
Don’t just read about red flags — find the ones in your contract.
Upload your freelance contract and PlainClause gives you a plain-English review — what you’re signing, every red flag, and what to negotiate. Your first preview is free.
Get your free review →What is a Freelance Contract?
A freelance contract (sometimes called an independent contractor agreement) is a written agreement between a client and a self-employed person doing a specific piece of work. It's different from an employment contract — you're not an employee, you don't get benefits or guaranteed hours, and you're generally responsible for your own taxes and tools. You'd sign one before starting any paid project: a logo design, a website build, a batch of articles, a consulting engagement. The contract exists to answer questions before they become disputes: What exactly is being delivered? When do you get paid? Who owns the work? What happens if either side wants out?
Scope of work
This section defines what you're actually agreeing to do. It should list specific deliverables, formats, and any limits (number of revisions, pages, hours). Vague scope is the single biggest source of freelance disputes — 'design a website' can mean two pages or twenty, one round of feedback or endless tweaks.
If the scope is fuzzy, the client's expectations will expand to fill the space. A tight scope protects you as much as it protects them — it's the line you can point to when someone asks for 'just one more small thing.'
Payment terms
Look for the amount, the currency, the payment schedule (upfront deposit, milestones, or on completion), and what counts as late. Contracts that pay 100% on final delivery put all the risk on you — if the client vanishes or stalls, you've done the work for nothing.
Also check for late payment consequences. A contract that's silent on late fees or interest gives you no leverage if a client pays 60 days late — or never.
Ownership and intellectual property (IP)
This clause decides who owns what you create. Many contracts say ownership transfers to the client only after final payment clears — which is fair. Some say it transfers the moment you start working, payment or not, which isn't.
Also watch for language about your own reusable tools, templates, or pre-existing code/designs. A badly worded IP clause can accidentally hand over things you built long before this project and plan to reuse for other clients.
Termination and kill fees
This covers how either side can end the contract early, and what happens to work already done. Look for a 'kill fee' — payment for work completed if the project is cancelled partway through. Without one, a client can cancel on day one of a three-month project and owe you nothing.
Check the notice period too. A contract that lets the client terminate 'immediately, for any reason' with no payment for work-in-progress leaves you exposed.
Liability and indemnification
Liability clauses decide who pays if something goes wrong — a bug causes a client's site to crash, a design infringes someone's trademark, a project runs over and causes losses downstream. Indemnification means agreeing to cover the other party's legal costs or damages in certain situations.
For a freelancer, uncapped liability is dangerous: a project worth a few hundred could theoretically expose you to damages worth far more. Reasonable contracts cap your liability at the amount you were paid, or exclude indirect/consequential damages.
Red flags to watch for
No cap on liability
Without a liability cap, you could be on the hook for damages far larger than what you were paid for the project — even for problems only loosely connected to your work.
Ownership transfers before final payment
If IP transfers upon delivery rather than payment, a client can take your work and never pay, and you've lost the ability to withhold it as leverage.
No kill fee or early termination payment
If the client can cancel anytime with zero payment for work already done, you carry all the financial risk of a project falling through.
Unlimited or undefined revisions
Phrases like 'revisions until client is satisfied' have no natural endpoint. This is how a fixed-price project turns into unpaid, unlimited labor.
Broad non-compete or non-solicitation clauses
A clause barring you from working with 'competitors' or similar clients for a year or more can effectively lock you out of your own industry, especially if it's not limited to a reasonable time, place, or scope.
One-sided indemnification
If you must indemnify the client for almost anything, but they owe you nothing in return, you're absorbing risk that should be shared or excluded.
Payment terms with no deadline or late penalty
'Payment due upon client's review and approval' with no fixed date can mean payment gets delayed indefinitely, with no consequence for the client.
Automatic renewal with no easy exit
Some ongoing/retainer contracts auto-renew unless you cancel within a narrow window (e.g., 30 days before renewal). Miss it, and you're locked in for another term.
What to look for before you sign
- Is the scope of work specific enough that you could hand it to a stranger and they'd know exactly what to deliver?
- Is the payment amount, currency, and schedule clearly stated, with a firm due date (not just 'upon approval')?
- Does ownership of the work transfer only after full payment is received?
- Is there a kill fee or partial payment clause if the project ends early?
- Is your liability capped, and are indirect/consequential damages excluded?
- Are revision rounds limited to a specific number?
- Does any non-compete or exclusivity clause have a reasonable time limit and narrow scope?
- Can you terminate the contract too, not just the client — and with reasonable notice?
- Does the contract say what happens to unfinished work or partial deliverables if either side ends it early?
- Is there anything indemnifying the client that feels open-ended or unrelated to your actual work?
Got a freelance contract in front of you? PlainClause reads your actual document and finds the red flags in about a minute.
Review your contract free →Frequently asked questions
Do I need a lawyer to review every freelance contract?
Not necessarily — for small, low-risk projects, careful self-review against a checklist like this is often enough. For larger contracts, longer engagements, or anything with unusual liability or IP terms, it's worth having someone knowledgeable look it over before you sign.
Can I negotiate a contract the client sends me?
Yes. Most freelance contracts are starting points, not fixed law. Asking to adjust payment terms, add a kill fee, or cap liability is a normal, professional request — a client who refuses to discuss any changes at all is itself worth noting.
What happens if there's no written contract at all?
Verbal or informal agreements can still be legally binding in many places, but they're much harder to prove and enforce if something goes wrong. Without written terms, disputes over scope, payment, and ownership become he-said-she-said.
Is a non-compete clause in a freelance contract enforceable?
It depends on where you are and how the clause is written — very broad or long-lasting restrictions are less likely to hold up than narrow, reasonable ones. Because this varies a lot by location, it's worth getting local advice if a non-compete feels overly restrictive.
What's a fair kill fee?
There's no universal standard — it depends on the industry, project size, and how much work is typically front-loaded. The key is that some payment for work already completed is addressed at all, rather than the contract being silent on it.
Key takeaways
- A freelance contract is usually drafted by the client, so its default terms tend to favor them — read it as if nothing is neutral until you check.
- Vague scope, unlimited revisions, and payment tied only to 'client satisfaction' are common ways a fixed project quietly becomes unpaid, unlimited work.
- Watch closely for uncapped liability, IP transferring before payment, and missing kill fees — these are the clauses most likely to hurt a freelancer financially.
- Almost everything in a freelance contract is negotiable; asking for fairer terms is normal business practice, not a red flag on your end.
- When liability, IP, or long-term exclusivity terms feel unusual or one-sided, it's worth a second, informed opinion before signing.
More guides
This guide is general information to help you understand a common type of contract — it is not legal adviceand doesn’t cover your specific situation or local laws. For a high-stakes contract, consult a lawyer.