Freelance Designer Contract Red Flags: What to Check Before You Sign

A client sends you a contract. It's 12 pages. The payment terms look fine, the project scope seems right, and the deadline matches what you agreed on. So you skim the rest and sign.

That's how designers lose their work.

The payment terms are almost never the problem. The problem is on page 8, in a clause called "Intellectual Property Assignment," or sometimes "Work Made for Hire," or sometimes "Ownership of Deliverables." That's the clause that decides whether the logo you spent 40 hours on, or the design system you built from scratch, actually belongs to you or to them.

Here's what to look for before you sign any freelance design contract.

IP Assignment: The Clause That Takes Everything

Every design contract has some version of an IP clause. The question is how broad it is.

A narrow version says the client owns the final, approved deliverables you deliver for this project. That's reasonable. You got paid, they get the files.

A broad version says the client owns everything you created in connection with this engagement, including drafts, concepts, explorations, and anything developed using company materials or direction. Some versions go further and claim ownership of anything you created during the contract period that is "related to the company's business."

That last version is the dangerous one. If you're a brand designer working for a tech company, "related to the company's business" could theoretically cover any UI work you do, any logo for any tech client, any visual identity work during the contract period. That's overreach. But if you signed it, you signed it.

What to do: ask for the IP clause to cover only the final approved deliverables explicitly listed in the project scope. Nothing else. The broader issues with IP assignment clauses in freelance contracts apply just as much to designers as they do to developers.

The "All Concepts and Drafts" Trap

Even when the IP clause looks reasonable, watch for language that includes concepts, mockups, explorations, and rejected ideas.

This matters because you own those things by default. A design process involves generating a lot of ideas. Most don't get used. Under standard copyright law, if a client rejects a concept, you retain that work. But if your contract says "all concepts and explorations prepared for this project become client property," you've signed away work they're not even paying for.

Rejected concepts can become the foundation of work you do for other clients, or work you put in your portfolio, or a direction you come back to in a personal project. Get those carved out of the IP clause or make sure the language says "approved, final deliverables" only.

Prior Work Provisions

Some contracts include a clause that tries to capture work you created before the engagement started. It usually reads something like: "Contractor represents that the deliverables do not incorporate any prior work, and any prior work incorporated is hereby assigned to the company."

Read that carefully. If you use a component from your personal library, a texture you developed, or an icon set you've been building for years, a clause like this could transfer ownership of those assets to the client.

Before you sign, document what pre-existing work you intend to use. List it explicitly in the contract as excluded from the IP assignment. If you built the icon set, you keep the icon set.

Unlimited Revision Language

This one is less about ownership and more about scope, but it can cost just as much.

Watch for phrases like "revisions as needed until the client is satisfied," "unlimited rounds of feedback," or "project includes all changes requested through final approval." That language has no ceiling. A client can request 30 revision rounds on a logo and the contract gives them the right to do it.

A good contract specifies the number of revision rounds included and what counts as a revision versus a new project scope. Three rounds is typical. More than that should be billed at an agreed hourly rate.

If the contract you're looking at doesn't define revisions, define them yourself in writing before you sign.

Moral Rights Waiver

This clause is short and easy to miss: "Contractor waives all moral rights in the deliverables."

Moral rights give you two things: the right to be attributed as the creator, and the right to object if the work is modified in a way that harms your reputation. Waiving them means the client can alter your work however they want, remove your name, and use it in contexts you might find objectionable, without your permission.

For most commercial projects, a waiver is standard and not worth fighting. But if you care about attribution, especially for high-profile work you'd want in your portfolio, push for a clause that says you retain the right to credit the work in your portfolio, even if you waive other moral rights.

Portfolio and Attribution Rights

Even if you waive formal moral rights, you should negotiate explicit portfolio rights into your contract.

Portfolio rights give you permission to display the work you created for the client in your professional portfolio, on your website, and in case studies. Many clients assume this is automatic. It is not. If your contract is silent on portfolio use, the client can demand you take down any public display of their project.

This matters most for high-value brand work, identity systems, and campaigns. A client who later pivots or rebrands may not want your version of their logo circulating in your portfolio. Negotiate portfolio rights at signing, not after delivery.

Some contracts include a time delay on portfolio use: you can display the work after six months, or after the client launches it publicly, or after the contract period ends. A time-delayed portfolio right is better than none. Get it in writing.

Attribution is a separate issue from portfolio rights. Attribution is whether your name appears as the creator when the work is published. Many commercial clients won't credit individual designers publicly, which is normal. But if attribution matters to you, for an award submission or industry recognition, discuss it explicitly before signing.

Confidentiality and NDA Language

Many freelance design contracts include a confidentiality clause requiring you to keep the project details, the client's business information, and the creative work confidential, often indefinitely.

The problem arises when the confidentiality clause is so broad that it prohibits you from discussing the nature of the work you did even after the project is public. If you designed a product that launched publicly, being prohibited from saying "I designed that" in a job interview is an overreach.

Read the confidentiality clause carefully for scope and duration. "Confidential information" should be defined specifically, not broadly. The clause should have a defined end date, or at minimum an exception for information that becomes public through the client's own publication of it.

If you need to show portfolio pieces that include confidential business information (unreleased products, internal processes), negotiate a "portfolio carve-out" that lets you show the visual work in controlled settings like interviews or award submissions, even if you can't discuss the underlying business context.

Non-Solicitation of Clients

Some freelance design contracts include a non-solicitation clause that restricts you from working for certain companies after the engagement ends. It usually covers clients you were introduced to through this client or projects you learned about through this engagement.

The dangerous version covers any company in the same industry as the client. If you're designing for a fintech company, a clause like that could restrict you from taking fintech work for the next 12 months.

Ask for the clause to be removed entirely or narrowed to specific named companies you were directly introduced to.

Payment Terms and Kill Fees

This one isn't a red flag exactly, but it's where designers get burned most after IP issues.

Watch for contracts that make full payment contingent on "final approval" with no defined criteria for what approval means. If the client can withhold payment indefinitely by simply never approving the work, you have no leverage.

A strong contract includes milestone payments tied to deliverable stages, not client satisfaction. A deposit at signing, a payment at concept delivery, and final payment at approved final files. If the project gets cancelled, a kill fee provision should specify that you keep work already completed and paid for.

If the contract has no kill fee and no milestone payments, add them before you sign.

Check It Before You Sign

When a client sends you a design contract, the things that will cost you money are almost never on the first page. They're buried in the IP clause, the revision language, and the payment terms on pages 7 through 11.

Clausely will flag every one of these clauses, quote the exact language, and tell you what you'd be agreeing to. You'll know before you sign, not after you've already delivered the files.

The contract you sign is the contract you're stuck with. Read it.