Freelance Contract Red Flags to Catch Before You Sign
The clauses and missing terms that quietly turn a good project into a money pit, and the exact lines to push back on.
The Delivvo team· June 13, 2026 10 min read
A freelance contract is dangerous when it does one of two things. It moves risk onto you that the client should carry. Or it stays vague exactly where you need it specific. Most one-sided agreements are not malicious. Someone's lawyer wrote a template to protect the company, the client forwarded it without reading, and now it is sitting in your inbox waiting for a signature. Your job is to find the five or six lines that matter and fix them before the work starts, because almost nothing in a contract is negotiable after you have already delivered.
The stakes are not theoretical. According to a Bonsai analysis of three years of freelance invoicing data, 29% of invoices were paid after they were due, and the same study found female freelancers were paid late 31% of the time versus 24% for men. Late payment is the norm here, not the exception, which means the payment clause is one of the first things you should read, not the last.
Below are the clauses, and the missing terms, that should make you slow down. For each one I will tell you what the red flag looks like and the line to ask for instead.
Who owns the work, and when the rights actually transfer
The single most common trap in creative contracts is an intellectual property clause that hands the client everything the moment you deliver, whether or not they have paid. Read the IP section and ask one question. Does ownership transfer on delivery, or on final payment? If it transfers on delivery, the client can take your work, never pay the final invoice, and you have given away your only leverage.
There is a second layer that catches freelancers off guard. Under US copyright law you are the default owner of what you create. The Copyright Office is explicit that "once you create an original work and fix it, like taking a photograph, writing a poem or blog, or recording a new song, you are the author and the owner" (according to the US Copyright Office). A client only gets ownership if you sign it over. That is why so many templates contain "work made for hire" language. The same office notes that this doctrine "establishes that works created by an employee within the scope of employment are owned by the employer," and for independent contractors it only applies to a few narrow commissioned categories with a written agreement. If a contract calls you an independent contractor and then labels everything "work made for hire," that wording may not even hold up. Replace it with a clean assignment that triggers on payment.
Keep reading
What to ask for:
Ownership transfers "upon receipt of final payment," not on delivery.
You keep the right to show the finished work in your portfolio and case studies.
Any pre-existing tools, code, or templates you bring stay yours, licensed to the client, not assigned.
That last point matters more than people think. If you build with a component library you reuse across clients, a blanket assignment clause can technically sign away your own toolkit. Carve it out.
A freelancer reviewing printed documents and notes at a desk before signing
Payment terms that quietly favor the client
A payment clause is a red flag when it is vague about timing or silent about consequences. "Payment within a reasonable time" means nothing. "Net 60" on a project you will finish in three weeks means you are financing the client for two months. A contract with no late fee at all tells the client there is no cost to paying you whenever they feel like it.
This is where the data should change how you read. Late payment is widespread across business, not only in freelancing. A 2024 Atradius report on US B2B payment practices found that half of US invoices were overdue and only 42% were paid on time, with 8% written off as bad debt (according to Clockify's late invoice statistics). Separate research in the same roundup found US small businesses receive payment on average 8.2 days after the agreed deadline. If your contract has no teeth, you walk into that statistic with no protection.
Push for specifics:
A fixed due date, ideally Net 14 or Net 7, not "upon completion."
A deposit before work begins. I treat anything under 30% upfront as a yellow flag.
A defined late fee, commonly 1% to 1.5% per month on the overdue balance.
A pause-work clause: if an invoice goes unpaid past the due date, you stop and the timeline shifts.
"Unlimited revisions" and the scope clause that never closes
If a contract promises "unlimited revisions" or describes deliverables with phrases like "as needed" and "ongoing support," that is not generosity. It is an open door for the project to grow while your fee stays flat. Scope creep is the quiet killer of freelance margins. One 2025 analysis citing Ignition found that 57% of agencies lose between $1,000 and $5,000 per month to unbilled scope creep, another 30% lose more than $5,000, and only 1% successfully bill for all out-of-scope work. Those are agencies with operations teams behind them. A solo freelancer absorbs the loss with no buffer at all.
The fix is precision. A strong scope section says exactly what is included, names a revision limit, and states what happens past it.
What to ask for:
A specific deliverable list with numbers ("two rounds of revisions," "up to five page layouts").
A definition of what counts as a revision versus a new request.
An hourly or fixed rate for out-of-scope work, agreed in writing before it starts.
Vague scope and vague payment terms compound each other. When neither the work nor the price is pinned down, every disagreement becomes a negotiation you are having for free. If your current contracts let scope drift, the tactics in how to stop scope creep on freelance projects, plus a tight statement of work, close most of the gaps.
Indemnity and liability: the clause that can cost more than the project
This is the clause freelancers skip and lawyers read first. An indemnity clause makes you responsible for certain claims and costs. A broad, uncapped one can make you liable for damages far larger than your fee. The classic example. You build a site for 5,000 dollars, a bug contributes to a loss the client values at 500,000 dollars, and the contract says you indemnify them "for any and all claims." On paper, you owe the half million.
You almost never need to accept that. Look for two things in the liability section. First, is the indemnity mutual, so both sides cover claims arising from their own conduct? Second, is there a liability cap, ideally limiting your total liability to the fees paid under the contract? A one-way indemnity with no cap is a hard stop. Either negotiate a mutual, capped version or do not sign.
Watch for a few more things in the same part of the document:
A warranty that your work will be "error-free" or "fit for any purpose." No one can promise that. Narrow it to "performed in a professional manner."
A non-compete that bars you from working with anyone in the client's industry. Defined too broadly, it can lock you out of most of your market.
An NDA that runs forever or covers far more than the project actually requires.
None of these are automatically deal-breakers. They are negotiation points. The signal to watch is whether every clause tilts the same direction. A contract where the client carries no risk and you carry all of it was not written to be fair, and it usually will not be applied fairly either.
Termination, kill fees, and the exit nobody plans for
Read the termination clause assuming the relationship ends badly, because that is the only time it matters. The red flag is a one-sided exit. The client can cancel at any time, for any reason, with no notice and no payment for work already done, while you stay locked in. That structure means you can pour two weeks into a project and walk away with nothing because the client changed their mind.
A fair termination section protects both sides. It should include a kill fee, so if the client cancels partway through, you are paid for work completed plus a percentage of the remaining fee to cover the time you held for them. It should also give you the right to terminate if the client breaches, most importantly if they stop paying. Notice periods should be symmetrical. If they get 30 days, so do you.
What to ask for:
Payment for all completed and in-progress work on termination, billed up to the cancellation date.
A kill fee, often 25% to 50% of the remaining contract value, for a cancellation the client starts.
Mutual termination rights, including your right to exit for non-payment.
The exit clause and the payment clause work together. If you have a strong pause-on-non-payment term and a fair kill fee, a client who stops paying cannot also string you along or cancel for free.
How do you push back on a contract without losing the client?
Treat edits as normal, because they are. Send your changes as specific redlines, not vague objections, and explain each one in a sentence: "I move IP transfer to final payment so we are both protected if something interrupts the project." Reasonable clients accept reasonable edits. A client who refuses to add a payment date, a liability cap, or a kill fee is telling you how the relationship will go. The full playbook lives in how to negotiate a freelance contract with a client. The short version. Ask early, ask in writing, and frame every change as protecting both sides.
What is the fastest way to avoid a one-sided contract entirely?
Bring your own. When you send the agreement, you start from terms that already protect you instead of editing terms written to protect someone else. A short, fair contract you control beats a long, lopsided one you inherited. If you do not have one yet, a solid starting point is one of the best free freelance contract templates, which you can adapt and reuse.
Send your own terms, signed up front
The cleanest way to dodge every red flag above is to never be the one reacting to a contract. Lead with yours. When your proposal, scope, payment schedule, and signature all come from your side, the client responds to your terms, and the load-bearing clauses are already in place. IP on final payment, a real due date, a liability cap, a kill fee.
This is where a client portal earns its keep. Delivvo lets you send a branded proposal, a clear contract with e-signature, and the invoice from one place, so the client signs your terms before any work starts and pays you directly through your own gateway, with Delivvo taking 0%. Owning the paperwork from the first message is the difference between setting the terms and inheriting them. See how it works
A contract is the one part of a freelance project you can control completely before anything goes wrong. Spend the twenty minutes. Read the IP, payment, scope, indemnity, and termination clauses with the assumption that the relationship could sour, fix the lines that put all the risk on you, and only then sign. The clients worth working with will respect that you read it. The ones who push back on every fair edit just told you something useful for free.
