7 Contract Red Flags Every Freelancer Should Know

Most freelancers get burned on contracts not because they signed something obviously bad — but because they signed something that looked fine until it didn't. The language was vague. A clause was missing. A term that seemed reasonable turned into a problem three months into the project.

Here are the 7 red flags to spot before you sign anything.

Red Flag 1: No Scope Definition (or a Vague One)

The most expensive words in any freelance contract are "and related tasks" or "as needed." These phrases hand the client unlimited rights to expand what you're doing without additional pay.

A proper scope section lists specific deliverables — not categories. Not "website design" but "5-page website including homepage, about, services, contact, and blog — designed in Figma and delivered as an approved prototype." Every word outside that list is out of scope.

If the contract you're reviewing has a one-line scope section, stop. Either negotiate detailed scope language before you sign, or add an explicit out-of-scope clause: "Any work not described above requires a written Change Order signed by both parties before work begins."

Red Flag 2: Unlimited Revisions

Any contract that uses the phrase "unlimited revisions" or that doesn't address revisions at all is a warning sign. Revision rounds are where freelance projects go to die.

You quote 10 hours. Four revision cycles later, you're at 22. Without a revision limit in the contract, you have no grounds to charge for the extra work.

Standard language: "This agreement includes [2] rounds of revisions. Additional revision rounds will be billed at [hourly rate]."

If a client pushes back hard on revision limits, that tells you something about how they operate.

Red Flag 3: Delayed or Milestone-Free Payment Terms

A contract that says "payment due on completion" with no upfront deposit is a payment risk. "Completion" is subjective. Clients who want to delay payment can always find something that isn't finished yet.

What to look for in healthy payment terms:

• A deposit of 25–50% due before work starts
• Milestone payments tied to specific deliverables (not subjective outcomes like "client approval")
• A final payment due date with a specific number of days (net 15 is standard; net 30 for larger projects)

If a contract has no deposit and no milestone structure, you're doing the work before you have any financial commitment from the client. That's a risk that compounds quickly on larger projects.

The Freelance Contract Template Pack includes payment term clauses covering deposits, milestone structure, and late fee language — already drafted in plain English.

Red Flag 4: Broad IP Assignment Language

Some contracts — particularly from agencies, larger companies, or clients who've worked with agencies before — include IP transfer clauses that go much further than necessary.

Watch for language like: "All work product, including drafts, concepts, and preliminary materials, is the exclusive property of the Client as a work made for hire."

That's extreme. It claims your drafts, your approach, even your rejected concepts. A reasonable IP clause transfers ownership of the final approved deliverable — not everything that went into producing it.

Specifically, be careful about:

• Claims over work that isn't completed or paid for
• Portfolio rights (your right to show the work as an example)
• Ownership of tools, frameworks, or templates you bring to the project
• Broad "moral rights" waivers in some jurisdictions

If the IP clause is unusually broad, flag it before signing. Add a portfolio rights clause if it's not already there: "Freelancer retains the right to display the final deliverables in their professional portfolio."

Red Flag 5: No Kill Fee or Termination Clause

Every freelance contract should address what happens if the project ends before completion — whether the client cancels, the project goes on hold, or the relationship breaks down.

Without a kill fee clause, a client can cancel after you've done 70% of the work and pay you nothing (or only what was already invoiced). That's a real scenario that happens regularly.

A kill fee clause specifies: if the client cancels, they owe you a percentage of the remaining project value or a flat fee. Standard language:

"If the Client cancels this project after work has begun, the Client agrees to pay a kill fee equal to [50%] of the remaining project value, in addition to all work completed to date."

If there's no termination clause, ask for one. It's a reasonable request, and a client who refuses to agree to any kill fee is signaling something.

Red Flag 6: Liability Clauses With No Cap

Some contracts — especially those drafted by the client's legal team — include indemnification language that can make you liable for consequential damages, lost profits, or other indirect losses that have nothing to do with the work you actually did.

An example of language to watch: "Freelancer agrees to indemnify Client for any and all losses, damages, or liabilities arising from Freelancer's work."

This is overbroad. You should be liable for your direct errors — not for every possible downstream consequence of a client's business decisions made using your deliverable.

A reasonable limitation of liability clause caps your exposure at the total amount paid under the contract. If you were paid $3,000 for a project, your liability should not exceed $3,000.

If the contract has no limitation of liability, add one before signing. If the client refuses any liability cap, consult a legal professional before proceeding.

Red Flag 7: Missing Communication and Feedback Terms

This one gets overlooked because it doesn't seem like a legal issue — but it costs freelancers real money.

A contract that doesn't address:

• Feedback timelines — how long the client has to review and respond
• What constitutes approval — does silence equal approval after X days?
• Response expectations — communication channels, expected turnaround

...creates projects that drag on indefinitely while the client takes 3 weeks to give you one round of feedback.

Standard protective language: "Client agrees to provide feedback within [5] business days of receiving deliverables. If the Client does not respond within this period, the Freelancer may consider the deliverable approved and may invoice accordingly."

This clause protects your timeline and gives you leverage if a client's delays push the project past your quoted deadline.

How to Handle a Contract That Has These Red Flags

If a client sends you a contract with one or more of these issues, you have three options:

Option 1: Redline and return. Mark up the contract with your proposed changes and send it back. For professional clients, this is a normal part of the process. A client who refuses all negotiation on a one-sided contract is worth reconsidering.

Option 2: Use your own contract as the base. For smaller clients who don't have legal infrastructure, it's often more efficient to use your own contract rather than theirs. A well-drafted contract template like the Freelance Contract Template Pack gives you a starting document that protects your interests without requiring negotiation on every clause.

Option 3: Walk away. Some contracts represent a fundamentally bad risk. If a client insists on unlimited scope, no kill fee, broad IP assignment, and uncapped liability — that combination is a pattern, not an oversight. Declining projects with contracts that can't be improved is a business decision, not a failure.

The Contract You Want

A healthy freelance contract is specific about scope, protects you financially if the project falls apart, limits your liability exposure, and preserves your portfolio rights. It's not adversarial — it's the document that lets you do the work without constantly wondering what the rules are.

If you're working from a template that addresses all these points from the start, most of the negotiation disappears. You're not asking clients to add protections — you're presenting a professional document that both sides can sign.

See the Freelance Contract Template Pack for templates that cover all seven areas above, across five freelance service types.