7 red flags to watch for in a client contract

A contract that describes your deliverable but does not define what "done" looks like is an invitation to scope creep. If the acceptance criteria are vague — or if the contract explicitly allows unlimited revisions until the client is "satisfied" — you have no basis to close the project or trigger final payment.

This is one of the most common and costly freelance contract problems. The client is not necessarily acting in bad faith; they may not have thought through what acceptance means. But "I'll know it when I see it" is not a deliverable standard.

Many client contracts include an IP clause that grants a "perpetual, worldwide, irrevocable, royalty-free license" to use your work, rather than assigning copyright outright. These two things are not the same, and understanding the difference matters for how you use your own portfolio.

A license lets the client use the work; you retain ownership. That means you can include the work in your portfolio, potentially re-license components to other clients, and retain moral rights. An assignment transfers ownership entirely. Under 17 U.S.C. § 204(a), a copyright assignment must be in a signed writing — which a signed contract is — so either approach is legally effective once you sign.

The red flag is not "license" per se — it is a license so broad that it functions as assignment without giving you the negotiating leverage to ask for higher compensation. If the client needs perpetual irrevocable rights, that is a full transfer of value, and the fee should reflect it.

Indemnification clauses allocate who pays if a third party sues. A mutual indemnity — each party covers claims arising from their own acts — is standard. A red flag is an indemnity that requires you to defend and hold harmless the client for claims arising from the client's own conduct.

Language to look for: "Contractor shall indemnify Client from any and all claims arising out of or related to this agreement" with no carve-out for Client's own negligence or misconduct. That language could require you to fund a client's defense against a claim that has nothing to do with your work.

Without a liability cap, your exposure on a project is theoretically unlimited — including consequential damages like the client's lost revenue, downstream losses, and third-party claims. Courts enforce liability caps and consequential-damage exclusions in commercial contracts under UCC § 2-719 unless they are unconscionable.

A missing cap is especially dangerous for deliverables that will be embedded in the client's product or business operations — software, critical documents, financial models. If something goes wrong downstream, the damages can far exceed what you were paid.

Non-compete and non-solicitation clauses sometimes appear in sections titled "Confidentiality" or "Independent Contractor" rather than in a standalone section, which makes them easy to miss. A non-compete restricts you from working with competitors; a non-solicitation restricts you from working with the client's other contractors or referrals.

For a freelancer serving a niche industry, a one-year non-compete embedded in a single client contract can cut off a large portion of your potential client base. California and Minnesota have statutes that void these clauses for independent contractors. In other states, they are enforceable if a court finds them reasonable.

A termination-for-convenience clause lets either party end the agreement without cause. That is generally fine — flexibility is good. The red flag is a clause that lets the client terminate immediately and pay only for milestones already invoiced, with no obligation to compensate you for partially-completed work.

If a client terminates a three-month project after six weeks of work because they ran out of budget, you should be compensated for the six weeks of work you completed. Without a clause addressing partial work, your remedy is quantum meruit — what a court decides is reasonable — which is slower and less certain than a fixed formula.

Some contracts include a clause allowing the client to modify the agreement unilaterally — "Client may update these terms at any time" or "Client reserves the right to modify the scope." This is sometimes buried in a boilerplate section.

A unilateral amendment clause means that what you signed today may not be what the agreement says tomorrow. Any material change to a contract requires mutual assent — both parties must agree — for the change to be binding. A clause purporting to let one party change the terms without your consent is worth pushing back on.