Client Contract Red Flags: What Freelancers Should Catch Before Signing

Most projects come with a client contract. Not the one you drafted — theirs. A document designed by their team, often reviewed by their lawyer, and written to protect their interests. That doesn't make it adversarial. It does mean nobody was thinking about yours when they wrote it.

Most freelancers sign client agreements with a quick scan and good faith. The ones who've been burned know exactly which paragraphs they wish they'd read more carefully. Here's a practical checklist of what to look for before your signature goes on anything.

The clauses worth reading twice

• Overly broad IP assignment. Transferring ownership of the final, approved deliverables upon payment is standard. The red flag is language that assigns everything created during the engagement — drafts, exploratory directions, anything 'related to' the project — whether or not you ever showed it to the client. Look for phrases like 'all work product, whether or not delivered' or 'including all derivative works,' and push back for language limited to the specific deliverables described in the scope.
• Non-compete clauses. Some contracts prohibit you from working with the client's competitors for 12 to 24 months after the engagement ends. In a narrow niche, this can close off a significant portion of your available work. Push to remove the clause entirely or negotiate a definition of 'competitor' narrow enough to be workable — ideally naming specific companies rather than broad industry categories.
• Open-ended approval language. A contract that says the project is complete 'upon client approval' with no revision limit and no definition of what acceptance means is a contract with no natural end date. Check whether revision rounds are defined and whether acceptance criteria are objective. If neither is present, add your own scope language before you sign.
• On-call or availability requirements. Language like 'contractor shall be reasonably available during standard business hours' or 'will prioritize client requests within 24 hours' can read as an unpaid retainer. If you aren't being separately compensated for availability, push back on any clause that implies it.
• Broad indemnification. A basic indemnification clause holds you responsible for third-party claims arising from IP you created — reasonable when the work is original. The red flag is language covering claims arising from how the client uses your work after delivery. That's outside your control. Limit indemnification to claims directly caused by your errors or omissions, not the client's downstream use.
• Payment terms buried mid-contract. Net 60 or Net 90 language occasionally appears in a general terms section that conflicts with your proposal or with the fee section you actually read. Check every section that mentions payment timing, not just the obvious one, and get written confirmation of which governs if they conflict.

What's normal — and what actually warrants a conversation

Most client contracts include boilerplate you don't need to fight: a basic confidentiality clause, a requirement to deliver work by a certain date, an arbitration clause for disputes. These are standard and not worth negotiating unless the terms are genuinely unusual. The clauses above are different — they can affect who owns your work, what future clients you can take, and whether the project has a defined finish line.

What to do when you spot a red flag

Most of these clauses are negotiable, and raising them is professional practice, not a sign of distrust. Clients who work regularly with freelancers expect some back-and-forth on contract terms. A brief, specific note works better than a formal objection: name the clause, explain what you'd like it to say instead, and offer a specific alternative. Clients rarely drafted the agreement themselves — they're using a template, and no one on their side has read section 7 recently either.

When a clause can't be removed, the question is whether the project is worth the constraint. A non-compete that covers one specific company for six months is different from one that closes off an entire industry for two years. If you accept a real restriction, price it into your rate accordingly — or decline.

For any project significant enough to come with a detailed client contract, a freelance contract lawyer can review it for $150 to $400 and flag what actually matters faster than you could research it yourself. If a clause could cost you the rights to your own work or prevent future clients, the review almost always pays for itself.