Most freelancers sign bad contracts not because they are naive, but because the pressure to just start the project is stronger than the instinct to read the paperwork carefully. The client seems reasonable. The project seems clear. The contract is three pages and looks standard. You sign, you start, and two months later you discover something in clause 7 that creates a serious problem.

This checklist covers the nine clauses that create the most problems in freelance contracts — what fair language looks like, what red flags look like, and what questions to ask before you sign.

Clause 1: Scope of Work

What it should say: A specific, enumerated description of what you will deliver. Not "website design" — "five-page website including homepage, about, services, contact, and blog index, designed to the provided wireframes, delivered as Figma files and production-ready HTML/CSS."

Red flag: Vague scope language. "And any other tasks as required by the client" is unlimited unpaid work. If the scope is not defined in the contract, everything the client thinks is included is included — in their view.

Clause 2: Payment Terms

What it should say: Exact amounts, payment schedule (milestone-based or time-based), due dates, and what happens if payment is late. A late payment penalty clause — 1.5-2% per month on overdue amounts — is standard and enforceable.

Red flag: "Payment upon satisfactory completion" with no definition of what satisfactory means. This gives the client indefinite power to delay payment by claiming the work is not satisfactory.

Clause 3: Intellectual Property Ownership

What it should say: IP transfers to the client upon receipt of final payment in full. You retain the right to display the work in your portfolio.

Red flag: IP transfers upon signing or upon project start — before any payment has been received. If the project gets cancelled before you are paid, the client owns your work. Also watch for clauses that claim ownership of your tools, frameworks, or pre-existing code libraries.

Clause 4: Revision Policy

What it should say: A specific number of revision rounds included in the project fee, a definition of what constitutes a revision versus new scope, and a rate for additional revisions beyond the included rounds.

Red flag: No revision limit specified. "Revisions until the client is satisfied" is not a scope — it is an open-ended commitment. Creative and technical work with unlimited revisions has no floor on your time investment.

Clause 5: Kill Fee / Project Cancellation

What it should say: If the client cancels the project after work has commenced, you are entitled to payment for work completed to date, plus a kill fee (typically 25-50% of the remaining project value) to compensate for blocked calendar time.

Red flag: No cancellation clause. Without one, the client can stop the project at any point without paying for work done or time blocked.

Clause 6: Confidentiality Scope

What it should say: You agree not to disclose specific confidential information (trade secrets, client data, proprietary processes) shared during the project. The scope is limited to what the client explicitly marks as confidential.

Red flag: Overly broad confidentiality language that prevents you from using skills and knowledge gained during the project in future work, or that prevents you from mentioning the client's name at all (which would prevent portfolio use).

Clause 7: Non-Solicitation

What it should say: A narrow non-solicitation clause prevents you from directly approaching the client's existing customers to offer competing services — reasonable for ongoing client relationships.

Red flag: A non-solicitation clause that prevents you from working with anyone in the same industry as the client, or that has an unreasonably long duration (anything beyond 12 months is aggressive for freelance).

Clause 8: Dispute Resolution

What it should say: Disputes are resolved through mediation first, then arbitration or a specified court, under the law of a jurisdiction that is accessible to you.

Red flag: Disputes must be resolved in a foreign jurisdiction (a city or country you cannot easily travel to), or through arbitration panels that are expensive to access. For freelancers working with international clients, ensure the governing law is clearly stated.

Clause 9: Termination Rights

What it should say: Either party can terminate with reasonable written notice (14-30 days). Termination triggers the kill fee clause and payment for completed work.

Red flag: Only the client has termination rights, or you can only terminate "for cause" with conditions that are difficult to meet. A contract you cannot exit without penalty is a trap.

Before You Sign

Read the contract once end-to-end before trying to negotiate anything. Flag every clause that is vague, absent, or one-sided. Then address them one at a time — most clients with reasonable intentions will accept straightforward amendments. The ones who push back hard on standard protective clauses are telling you something important about how the project will go.

Rewrite Labs Tool

Understand any contract clause in plain English with Unclause

Paste any clause from your freelance contract into Unclause. Get a plain-English explanation of what it means, what rights it affects, and what to ask before signing. Built for freelancers, contractors, and anyone who needs to understand legal language without a lawyer on retainer.

Try Unclause Free →