5 Red Flags in Freelance Contracts (And How to Spot Them)

Freelancing gives you independence, but it also means you're your own legal department. Every new client relationship usually starts with a contract — and most freelancers sign whatever they receive because pushing back feels awkward, or because hiring a lawyer to review a $3,000 engagement doesn't make financial sense.

The problem is that many freelance contracts are drafted entirely from the client's perspective. That doesn't mean the client is trying to take advantage of you — it usually means their lawyer wrote a template that maximizes the client's protection without much thought about what's fair to you.

Here are the five most common issues I see in freelance contracts, and what they actually mean for you.

1. IP Assignment That Extends Beyond the Project

What it looks like: "Contractor hereby assigns to Company all right, title, and interest in any and all work product, inventions, ideas, and intellectual property created during the term of this Agreement."

The problem with this language is the phrase "during the term." Read literally, it could mean that anything you create while this contract is active — including work for other clients, personal projects, or pre-existing tools you use in your workflow — belongs to the company.

What to look for: Does the IP clause specifically limit assignment to work created for this client and within the scope of this project? Or is it broad enough to capture everything you do during the contract period?

A reasonable IP clause ties ownership to the deliverables defined in the scope of work. An unreasonable one claims everything you touch.

2. Non-Compete Clauses That Don't Fit the Engagement

What it looks like: "For a period of two (2) years following termination, Contractor shall not provide services to any company that competes with Company in any market in which Company operates."

Non-competes in freelance contracts are more common than most people realize, and they can be devastating. If you're a freelance web developer and you sign a 2-year non-compete with a client in the e-commerce space, you've potentially locked yourself out of a huge portion of your market for two years.

What to look for: Duration (anything over 12 months for a freelance engagement is aggressive), geographic scope (worldwide restrictions are a red flag), and definition of "compete" (is it limited to direct competitors, or is it broad enough to cover adjacent industries?).

It's worth noting that enforceability varies significantly by jurisdiction. Some states are much more protective of workers when it comes to non-competes. But even an unenforceable non-compete can be expensive to fight — the cost of the legal battle itself is the deterrent.

3. One-Sided Termination Rights

What it looks like: "Company may terminate this Agreement at any time, for any reason, upon written notice to Contractor."

Meanwhile, your termination right says: "Contractor may terminate this Agreement with 30 days written notice, subject to completion of all work in progress."

This means the client can walk away at any time, but you're locked in until you finish everything in the pipeline AND give 30 days notice. If the client terminates mid-project, the question becomes: do you get paid for work already completed? Look for language about payment upon termination — if it's not there, that's a gap worth understanding.

What to look for: Are termination rights symmetric? What happens to payment for completed work if either party terminates? Is there a kill fee or minimum payment provision?

4. Unlimited Liability With No Cap

What it looks like: "Contractor shall indemnify and hold harmless Company from any and all claims, damages, losses, costs, and expenses arising from Contractor's performance of services."

There's no dollar limit on this. If something goes wrong — even something partially outside your control — you're on the hook for the full amount of damages, which could far exceed what you're being paid for the project.

What to look for: Is there a liability cap? A common and reasonable approach is to cap liability at the total fees paid under the contract. So if you're being paid $10,000 for a project, your maximum liability exposure would be $10,000. Without a cap, a $10,000 project could theoretically expose you to $1,000,000 in liability.

5. Vague or Conditional Payment Terms

What it looks like: "Company shall pay Contractor upon satisfactory completion of deliverables, as determined by Company in its sole discretion."

That phrase — "sole discretion" — means the client decides when they're satisfied, and you don't get paid until they are. There's no objective standard, no timeline, and no recourse if they keep requesting revisions indefinitely.

What to look for: Specific payment triggers (delivery of defined milestones, not subjective satisfaction), specific timelines (Net 30 from invoice, not "when determined appropriate"), and what happens if the client is late on payment (interest, right to pause work).

The Pattern

You'll notice a theme across all five of these issues: they're not exotic legal traps. They're standard contract language that happens to be written entirely from one side's perspective. Most clients aren't intentionally trying to exploit you — they're using templates drafted by their lawyer whose job is to protect the client.

Your job is to understand what you're agreeing to so you can make an informed decision about whether the terms work for you, and whether anything is worth discussing before you sign.

Check Your Contract

If you want to see how your current contract stacks up, paste it into dott.legal and get a free risk analysis in 30 seconds. The tool identifies all of the issues above — and dozens more — and gives you a risk score so you know where you stand.

For contracts where the stakes are higher and you want a licensed attorney to review the findings, Dott offers attorney-validated review for $349.