Freelance Contract Red Flags: The Eight Clauses That Eat Your Margin

Most freelance disputes don't start in the work. They start in the contract you signed without reading.

You took the gig. You did the work. Now the client is quoting a clause you don't remember to explain why they're paying half, owning everything you made, and reserving the right to come after you if their lawyer ever complains. That clause was on page seven of the SOW you skimmed at 11pm.

This is the freelancer's version of the contract red flags guide. Eight clauses that show up in real client agreements, what they actually do, and the one-line redline that fixes each of them.

TL;DR

• The eight freelance contract red flags below cover payment, scope, IP, indemnification, non-competes, late fees, kill fees, and integration.
• Severity tiers: High risk means walk away or rewrite. Medium risk means negotiate. Low risk means know what you signed.
• Three states (California, New York, Illinois) now require written freelance contracts and timely payment by statute. If your client is in one of those states and skipped the paperwork, the law is on your side.
• Receiving a 1099 does not make you an independent contractor. The clauses below decide that, and so does state classification law.
• The single best protection is a deposit before you start.

What's in this guide

1. The "we'll pay on completion" trap. Payment terms and deposits.
2. The unlimited revisions clause. Scope creep with no exit.
3. The IP grab. Work-for-hire and prior-work assignment.
4. The indemnification trap. You cover their lawyers.
5. The freelance non-compete. You can't take similar work.
6. The late-fee asymmetry. They cap yours, theirs is uncapped.
7. The missing kill fee. They cancel, you eat it.
8. The integration clause that erased the email. Verbal promises, gone.
9. State laws that protect freelancers in 2026
10. Frequently asked questions

The "we'll pay on completion" trap

High risk

In a typical client SOW:

Payment shall be due within sixty (60) days following Client's
acceptance of all Deliverables. Acceptance shall occur upon Client's
written confirmation that Deliverables conform to the Specifications,
in Client's reasonable judgment.

What it means: You don't get paid when the work is delivered. You get paid when the client decides the work is acceptable, which they have 60 days to do. If they sit on it, you wait. If they nitpick, the clock restarts. There is no deposit and no progress payment, so you carry the entire cost of the project until they say so.

Push back: ask for 30 to 50 percent up front, milestone payments tied to delivery dates, "deemed accepted" if the client doesn't reject in writing within 10 business days, and net-15 or net-30 payment terms. The deeper breakdown is in the payment terms in contracts guide. If a client refuses every form of upfront payment, that is the answer to the question of whether they intend to pay you.

The unlimited revisions clause

High risk

In a creative services agreement:

Contractor shall provide such revisions as Client reasonably requests
until Client is satisfied with the Deliverables. The fees set forth
herein are inclusive of all such revisions.

What it means: Scope is whatever the client says it is. "Until satisfied" with no cap means three rounds, fifteen rounds, the project lasts a year. The flat fee absorbs every "just one more thing." This is the contractual home of scope creep.

Push back: cap revisions at two or three rounds, define what counts as a revision versus a new request, and add a change-order clause: "Revisions beyond the scope set forth in Exhibit A shall be billed at $X per hour with prior written approval." The first time you invoke it, the client learns scope is real.

The IP grab

High risk

In a work-for-hire clause:

All deliverables, work product, intellectual property, and any related
materials, including without limitation any pre-existing materials,
tools, methodologies, and know-how used in connection with the Services,
shall be the sole and exclusive property of Client.

What it means: "Including without limitation any pre-existing materials" is the trap. The client now owns the templates, the brushes, the code library, the Figma components you brought into the project. You can't reuse them on the next gig because they no longer belong to you.

Push back: split the IP. Deliverables transfer to the client on full payment. Pre-existing materials, tools, and methodologies remain yours, and you grant the client a license to use them in the deliverables. "On full payment" matters. Without it, the client owns the work the moment it leaves your laptop, even if they never pay.

The indemnification trap

High risk

In a freelance services agreement:

Contractor shall defend, indemnify, and hold harmless Client and its
officers, directors, employees, and agents from and against any and
all claims, losses, damages, liabilities, and expenses, including
reasonable attorneys' fees, arising out of or relating in any way to
Contractor's performance of the Services.

What it means: If anything goes wrong, even something the client caused, you pay their lawyers. "Arising out of or relating in any way" is a phrase that does an enormous amount of work. The phrase "and shall defend" is more expensive than just indemnifying, because it requires you to fund the defense as legal bills come in, before any verdict.

Push back: indemnification should run both ways. Cap it at the contract value. Limit it to losses caused by your gross negligence, willful misconduct, or breach of confidentiality. Strike "defend" if you can. The full breakdown is in the indemnification clause guide. For solo freelancers, this clause is the closest thing to a personal guarantee you'll sign without realizing it.

The freelance non-compete

Medium risk

In a contractor agreement:

For a period of two (2) years following termination of this Agreement,
Contractor shall not directly or indirectly provide services to any
entity that competes with Client in the field of [industry] within
the United States.

What it means: A two-year ban on working with anyone in the client's industry. The phrase "directly or indirectly" sweeps in subcontracting, agency placements, even moonlight work for a friend. For a freelancer who specializes in one industry, this is a sentence to stop earning.

Push back: narrow the time to six to twelve months. Narrow the geography to specific competitors named in an exhibit, not the whole industry. Narrow the activity to direct solicitation of the client's customers, not all work in the field. Or strike it entirely. The full state-by-state enforceability map is in the non-compete clause guide.

The late-fee asymmetry

Medium risk

In a payment terms section:

If Contractor fails to deliver any Deliverable by the date specified
in Exhibit A, Client may assess liquidated damages of one percent
(1%) of the total fees per day of delay, up to the full contract value.

What it means: You get fined for being late. The contract is silent on what happens when the client is late paying you. "Up to the full contract value" means a thirty-day delay wipes the entire fee. Meanwhile, the client could sit on your invoice for sixty days with no penalty.

Push back: make the late fee mutual. If the client pays late, they owe you 1.5 percent per month on the overdue balance, which is the standard commercial rate. If they refuse to make late fees mutual, that tells you what they think of the deal.

The missing kill fee

High risk

In a project termination clause:

Either party may terminate this Agreement at any time for convenience
upon written notice. Upon termination, Contractor shall be paid for
Services satisfactorily performed through the date of termination.

What it means: They can cancel for any reason and pay you for the hours you logged. There is no kill fee. If you turned down other work to take the project, that's your problem. If you bought software or hired a sub for the project, that's your problem.

Push back: add a kill fee. A common structure is 25 to 50 percent of the remaining contract value, payable on cancellation. Tie kill-fee tiers to project milestones, with bigger fees later in the project. The clause does two things at once: it pays you for time you'll never recover, and it raises the cost of canceling enough that the client thinks twice.

The integration clause that erased the email

High risk when the client made promises in email or on a call

In most freelance contracts, near the signature block:

This Agreement constitutes the entire agreement between the parties
and supersedes all prior negotiations, communications, and understandings,
whether written or oral, with respect to the subject matter hereof.

What it means: Every promise the client made in email, on Zoom, or in Slack is gone the moment you sign. The "we'll add a referral bonus if this goes well" message. The "we'll cover the stock photos" Slack DM. The "we'll let you keep this in your portfolio" Zoom comment. None of it is in the document, so none of it exists.

Push back: any promise that mattered to your decision belongs in the contract before you sign. Add a section called "Additional Agreed Terms" listing them in plain language. Or attach the email as an exhibit and reference it. Saving the email isn't enough; the integration clause excludes it from the deal.

State laws that protect freelancers in 2026

For most of the last few years, the rules around freelance work have been a mix of federal regulation and state innovation. The federal layer has narrowed. State law is now the meaningful protection.

State	Law	What it requires
California	SB 988, the Freelance Worker Protection Act (effective Jan 1, 2025)	Written contract for any freelance gig of $250 or more. Payment by the contract due date or within 30 days of completion if no due date is specified. The hiring party must keep the contract for four years. Anti-retaliation protections.
New York	Freelance Isn't Free Act (effective Aug 28, 2024 statewide)	Written contract for any gig of $800 or more. Payment by the contract due date or within 30 days. Double damages and attorneys' fees for non-payment.
Illinois	Freelance Worker Protection Act (effective Jul 1, 2024)	Written contract for any gig of $500 or more (or $4,000 over a 120-day period). Payment within 30 days of work completion if not specified.

These laws shift the burden. If a client in California, New York, or Illinois hires you for a covered amount and skips the written contract, that is itself a violation. If they pay late, you get statutory damages, often double the unpaid amount, plus attorneys' fees, without having to prove anything else. The Department of Labor's misclassification guidance is also worth bookmarking, but state law is where the freelance-specific teeth live.

The state laws don't override the contract clauses above. A California freelancer can still sign an indemnification clause that costs them everything. The laws set a floor, not a ceiling. The contract is still where the real work happens.

Frequently asked questions

Do I really need a deposit?

Yes. A client who refuses to pay any deposit is a client who hasn't decided they're going to pay you. Deposits aren't a flex; they're a filter. If the project is large, structure milestone payments instead of one deposit, but the first dollar should hit your account before the first hour of work.

What if the client wants me to sign their contract, no changes?

Read it as if it's a take-it-or-leave-it deal, because that's what they're telling you it is. Decide whether you'll take it, leave it, or push back anyway. "No changes" is a negotiating position, not a fact. Many clients accept changes when asked, especially on the indemnification, non-compete, and kill-fee clauses, because they know those are aggressive.

Is a 1099 a contract?

No. The 1099 is a tax form the client sends you at year-end. The contract is the document that defines the work, the payment, and the obligations. Receiving a 1099 doesn't mean you're correctly classified as an independent contractor either; the federal and state classification tests look at the actual relationship, not the form. The offer letter red flags guide covers the employment side; the freelance version is in the next post in this series.

Can I just use a template?

Yes, and you should. A short, clear contract you wrote yourself is better than a 30-page client agreement you didn't read. Cover scope, payment terms, deposit, kill fee, IP, and a mutual indemnity. The Freelancers Union, Bonsai, and HelloBonsai all have decent free starting points. Adapt one and reuse it across clients.

What if the client is in California, New York, or Illinois and skips the written contract?

That itself is a violation. Document the engagement (emails, invoices, deliverables, dates). Send a written demand for payment that cites the relevant statute. The state-level FWPA and FIFA give you statutory damages and attorneys' fees, which means a private lawyer can take the case on contingency without you paying out of pocket. The City of New York's Department of Consumer and Worker Protection has a free FIFA complaint process for the NYC variant.

Read the paper before the work

The bad news: most client contracts are drafted by their lawyer, for them. The good news: most clients accept changes when asked, because they're not paying their lawyer per redline. The redlines above are the cheapest insurance you'll buy on a freelance project.

Eight shapes. Payment, scope, IP, indemnity, non-compete, late fees, kill fees, integration. If you can spot all eight in the document on the table, you're already negotiating better than 90 percent of the freelancers around you.

Redline scans contracts in plain English and flags the eight clauses above in your specific document. Photograph the SOW, paste the email attachment, or upload the PDF. It tells you which clauses are aggressive, what to ask for instead, and which ones the law won't let your client enforce. One scan, one dollar. Available on iOS and Android.