Freelance Graphic Design Contract: Complete Guide

Why Most Designers Get Burned (And It's Not the Client's Fault)

I've worked with thousands of agency owners and freelancers, and the pattern is always the same. A designer lands a client, they're excited, they start working - and then six weeks later they're doing their twelfth revision round, getting ghosted on invoices, and watching their original concepts get handed off to another designer for execution. None of that happens because the client is evil. It happens because nobody wrote down the rules.

A freelance graphic design contract is the rulebook. Without it, every disagreement becomes a memory contest - and clients almost always remember things differently than you do. With it, you have a document both parties signed that answers every "but I thought" before it becomes a fight.

This guide walks through every clause that matters, the mistakes designers make when they skip or soft-pedal certain sections, how to read a client's contract before you sign it, and how to get your contract signed fast without killing the relationship before the project starts. If you want a ready-to-use starting point, grab the free Agency Contract Template - it covers the core clauses and you can adapt it for design work in about 15 minutes.

What a Freelance Graphic Design Contract Actually Is

Strip away the legal language and a graphic design contract is simply a written agreement that defines scope, deliverables, revision limits, payment terms, intellectual property ownership, and what happens when things go sideways. Both parties sign it before a single pixel gets moved.

The contract protects the designer and the client equally. That framing matters - lead with that when you send it over. You're not sending a contract because you distrust them. You're sending it so both of you are protected and there are zero surprises.

A solid contract also forces a productive conversation before the project starts. Clients who resist signing a basic agreement, or who balk at standard terms, are showing you who they are before you've invested a single hour. That information is worth having early.

The AIGA Standard Form: The Industry Baseline

If you're starting from scratch, you don't need to write a contract from a blank page. The American Institute of Graphic Arts (AIGA) has done most of the heavy lifting for you. The AIGA Standard Form of Agreement for Design Services is a modular document built by a team of design and legal professionals - it's thorough, field-tested, and updated to reflect current industry practice. It covers Basic Terms and Conditions and Intellectual Property Provisions as the core modules, with optional supplements for print-specific, interactive-specific, and environmental-specific work.

The AIGA approach is smart: rather than a one-size-fits-all pre-printed document, it's designed to attach to your custom project proposal, so the combined document becomes the binding agreement. That structure keeps contracts lean while making sure the critical legal scaffolding is in place. You can access it directly from AIGA's website and customize the modules to match the type of design work you do.

That said, the AIGA form is a starting point, not a finished product. You still need to customize scope, payment terms, revision limits, and jurisdiction to fit each engagement. And for larger projects or contracts from corporate clients, you always want a lawyer's eyes on anything before you sign.

The Essential Clauses - In Plain English

1. Identification of Parties

Start with full legal names, business names, and contact information for both sides. This sounds obvious, but disputes frequently arise from vague identifications. Confirm you're contracting with someone who actually has the authority to sign - at larger companies, your day-to-day contact and the person authorized to bind the company legally are sometimes different people.

Also confirm the entity type. Are you contracting with a person, an LLC, a corporation? If something goes wrong, you need to know what you're actually dealing with legally. "John's Marketing" and "John Smith DBA John's Marketing LLC" are very different counterparties.

2. Scope of Work

This is the clause that prevents scope creep, and scope creep is the number-one time-killer in freelance design. Vague statements like "design a branding package" are a trap. Instead, be specific: "Three initial logo concepts, two rounds of revisions on the selected concept, delivered in AI, EPS, PNG, and JPG formats." Every deliverable needs a format, a quantity, and a revision limit attached to it.

When scope is loose, clients picture different pages, features, and outputs than you planned - and the project drags on while you're guessing what's actually included. Write scope lines with exact deliverables so there's no room for interpretation. And explicitly list what is NOT included. If social media templates aren't part of the logo package, say that. The exclusions are as important as the inclusions.

A well-drafted scope section should also address what the client is responsible for providing - brand guidelines, reference images, copy, approved colors. If the client fails to deliver those materials on time, the project timeline extends accordingly. Build that into your contract so you're never waiting on them unpaid.

3. Revision Rounds and What Counts as a New Request

Your contract needs to spell out exactly how many revision rounds are included and, critically, what a "revision" means versus a new request. Most professionals include two or three rounds of revisions in the base price, with additional changes billed at an hourly or per-revision rate. When a client asks for their tenth "minor tweak," you can calmly point to the contract and discuss the additional fee - no confrontation needed, because you both signed it.

The definition of a revision matters here. A revision is a refinement of an approved direction - adjusting color, resizing an element, swapping a font. A new request is a direction change - scrapping the approved concept and starting over. Those are different things, and your contract needs to say so explicitly. If you leave this undefined, every "can we just try a completely different direction?" is going to feel like it's covered under the included revisions.

Consider including a clause that unused initial concepts remain your property. This prevents clients from taking your rejected concepts to a cheaper designer to execute - which happens more than designers want to admit.

Also include an approval deadline clause. If the client hasn't responded with feedback within a set number of business days, the work is considered approved. This prevents projects from going dormant on the client's end while you're holding the timeline open indefinitely.

4. Payment Terms

Unclear payment terms are the direct cause of most invoice disputes. Your contract needs to include: total project fee, deposit amount (50% upfront is standard), milestone payment schedule if applicable, method of payment, due dates, and late payment penalties.

On milestone billing: for project-based work above a certain threshold, a three-part structure is cleaner than two - 50% at kickoff, 25% at first concept presentation, 25% on final delivery. That structure keeps you paid throughout the project and gives the client natural checkpoints to course-correct if the work isn't heading in the right direction.

A critical clause that many designers skip: rights to the work only transfer upon full payment. That means if a client doesn't pay, they legally cannot use the work. You still own it. Put that in writing. It gives you real leverage if someone tries to ghost you post-delivery.

Also add language about what happens if a client requests work outside the original scope - a change order process so any additions get priced and agreed upon in writing before you do the work. Late fees should also be specified - a standard monthly interest rate on overdue balances is industry-normal and most design firms include it.

For retainer engagements, collect the full month in advance before any work begins. Never work on credit in a retainer arrangement.

5. Kill Fee

This deserves its own section because it's the clause most designers skip - and the one that costs them the most money when they skip it. A kill fee (also called a cancellation fee) is the compensation you receive if a client cancels the project after work has begun but before completion. It covers the time you've already invested and the opportunity cost of turning down other projects to accommodate this one.

Kill fees are typically calculated as a percentage of the total project cost and triggered when specific conditions occur. Industry standards vary: advertising and media typically use 50% kill fees, while other design projects commonly land in the 25-50% range depending on how far along the project is. A tiered structure works well - a lower percentage early in the project, escalating as more work is completed. AIGA guidance suggests that projects cancelled after first creative is delivered should be subject to a significant portion of the total contract value, escalating further as revisions are completed.

Without a kill fee, you absorb 100% of the loss when a client cancels. With one, cancellations cost the client money - which also means they're far less likely to cancel frivolously. Kill fees align incentives on both sides. Put the percentage in writing, put the trigger conditions in writing, and make sure it's in every contract you send.

6. Timeline and Deadlines

Include the project start date, key milestone dates, and final delivery date. Structure it concretely - something like "Project runs [start date] to [end date]: initial concepts by [date], feedback due within five business days, final delivery by [date]." That kind of specificity makes timeline disputes almost impossible.

Also cover what happens if the client delays the project on their end. If they go several weeks without providing feedback or approvals, the timeline resets accordingly and any rush fees apply if they then need expedited delivery. Clients are often the bottleneck, and you don't want to be penalized for their delays.

Rush work is a separate line item. If a client needs turnaround faster than your standard timeline, a rush premium is standard practice and should be explicitly permitted in your contract language.

7. Intellectual Property and Copyright

This is the clause designers most commonly get wrong, and it's the most consequential. By default under US copyright law, the creator owns the work. If the client wants to own the copyright outright, that's a transfer - and it should cost more than a license.

Your contract should specify exactly what's being transferred. Is the client getting full copyright ownership? A license for specific uses only? Usage rights limited to a particular medium, region, or time period? These terms directly affect your pricing. A logo for a local bakery's single-location use is a different deal than a brand identity being rolled out globally.

There are several IP structures you'll encounter:

• Full copyright transfer: The client owns everything outright after full payment. This is the most expensive option for the client and gives you the least ongoing control.
• Exclusive license: The client can use the work exclusively in defined contexts, but you retain copyright ownership. You can't license it to others, but you still own it.
• Non-exclusive license: The client can use the work, but you can license it to others as well. Rare in custom design but possible for template-based work.
• Work-for-hire: Under US copyright law, work-for-hire means the client is legally treated as the creator and automatically owns the copyright. This is most common when a designer works on-site using client equipment. As a freelancer using your own tools and schedule, you are typically not in a work-for-hire situation by default - but some client contracts try to impose this structure contractually. If you're signing a client's contract that says "all work product shall be work-for-hire," understand what you're agreeing to.

Also address your preliminary work - sketches, rejected concepts, and working files. Your contract should state that rejected concepts remain your property. The client is paying for the final approved deliverables, not your entire creative process. If they want source files, that should be a separate line item.

For a deeper dive on writing contracts that hold up, the How to Write a Contract guide walks through the structure from scratch.

8. Confidentiality / NDA

If you're working on unreleased products, internal campaigns, or anything the client considers sensitive, include a mutual confidentiality clause. It protects their information and yours. "Mutual" is the key word - you're agreeing not to share their confidential info, and they're agreeing not to share yours, including your processes and pricing.

Be specific about what counts as confidential. A blanket clause that covers "all information shared" can create problems later if you want to use project insights for case studies or teaching materials. Carve out a path for portfolio use in the same section.

9. Portfolio Usage Rights

Unless the client asks you to sign an NDA that restricts this, include a clause that gives you the right to display the completed work in your portfolio and use it for promotional purposes. This is something you should be getting as a baseline - it's how you win the next client. Get it in writing upfront rather than asking for permission awkwardly after the project ends.

Some clients - particularly in competitive industries or with pre-launch products - will want a time embargo on portfolio usage. That's reasonable. Just make sure the embargo has a specific end date, not an indefinite restriction. "Not until six months after public launch" is workable. "Not unless we give written permission" is a clause you should push back on, because you'll likely never get that permission in practice.

10. Termination Clause

Either party should have the right to terminate the contract, but the terms need to be clear. The most common approach: the client owes payment for all work completed up to the termination date, plus any applicable kill fee. If a client tries to cancel near project completion to avoid the final payment, your contract should explicitly state they're still responsible for that invoice.

Specify required notice periods. A standard notice period of 7-14 business days in writing is reasonable for most projects. For longer engagements or retainers, a 30-day notice period is more appropriate.

Also address who owns copyright over any work that's already been completed at the time of termination. Without this, you're in murky territory. The default position should be: copyright stays with the designer unless the client has paid in full for the completed work up to that point.

11. Independent Contractor Status

This clause matters for your legal and tax situation. Your contract should explicitly state that you are an independent contractor, not an employee. You determine the manner and means by which the services are accomplished. The agreement does not create a partnership, joint venture, or employer-employee relationship. You are responsible for your own taxes, insurance, and business expenses.

This protects you from misclassification issues and makes your status unambiguous if a question ever arises. It also reinforces that the client doesn't get to dictate your hours, your tools, or your process - only the deliverables.

12. Liability Limitation

Cap your liability. If a logo you designed somehow gets challenged legally or a campaign you designed doesn't perform as expected, you don't want unlimited financial exposure. A limitation of liability clause typically caps your liability at the total amount the client paid for the project. Standard, reasonable, and any attorney will confirm it's industry-normal.

Also include an indemnification clause that covers you if the client provides you with assets (logos, images, copy) that infringe on third-party rights. You shouldn't be liable for material the client handed you. The client should indemnify you against any claims arising from their misuse of deliverables or from intellectual property they provided that turns out to be problematic.

13. Dispute Resolution

Specify how disputes get resolved and which state or country's laws govern the contract. Mediation first, arbitration second, court as a last resort - that's a reasonable hierarchy. Pick your home jurisdiction. You don't want to be flying across the country to litigate a logo dispute. And make sure the governing law clause reflects a jurisdiction you can actually operate in practically.

The Mistakes That Cost Designers Real Money

Most contracts fail not because designers don't have one, but because they went soft on the specifics to avoid awkwardness during onboarding. Here's where money actually gets left on the table:

• No kill fee. If a client cancels mid-project, you need compensation for the time you've already blocked and the opportunity cost of turning down other work. A kill fee of 25-50% of the remaining balance is the industry range, tiered based on project stage. Get it in writing before you start.
• No deposit requirement. Starting work without a deposit is working on credit with a stranger. Get 50% upfront, every time. No exceptions, no matter how good the client seems.
• Vague revision language. "Unlimited revisions" or no revision language at all is how you end up doing six months of work for a three-week project fee. Define "revision" explicitly, cap the rounds included, and spell out the hourly rate for anything beyond that.
• No payment-for-rights-transfer clause. If you don't tie copyright transfer to full payment, a client who ghosts on the final invoice can still claim to use the work. Don't let that happen.
• No client responsibilities section. Your timeline depends on the client providing feedback, approvals, and assets on schedule. If you don't put that in writing, you're absorbing the delay cost every time they go quiet for two weeks.
• No approval deadline. Without a clause stating that silence equals approval after a set number of days, a client can sit on a deliverable indefinitely and then come back six months later claiming they never approved it.
• Signing a client's contract instead of yours. Some clients, especially larger companies, will send you their own vendor agreement. Read it carefully. Their contracts often assign them full ownership of everything you create during the engagement term - including work that has nothing to do with their project. That language is dangerous if you're working with multiple clients simultaneously.

Red Flags in Client Contracts You Should Never Sign Without Changes

When a larger client sends you their vendor agreement to sign, your job is to read it like a lawyer before you sign it like a designer. Here are the clauses that show up repeatedly and cost freelancers badly when they don't catch them:

Broad Work-for-Hire Language

The most dangerous variation you'll see is something like: "All work product created during the term of this agreement shall be considered work-for-hire owned by Client." The phrase "during the term" is the problem. That language could give the client ownership of work you create for completely unrelated projects or clients during the same time period. The fix is to narrow the language: "Work product created specifically for Client under this Statement of Work shall be owned by Client." If they push back on that change, it's a significant red flag.

Payment on Satisfaction

Any clause that ties payment to the client being "satisfied" with the work is a trap. The client can delay payment indefinitely by claiming they're not satisfied - even if you delivered exactly what was specified in the scope. Replace satisfaction-based payment terms with delivery-based ones: payment is due within a defined period after delivery, period. One round of reasonable revisions can be included post-delivery, but payment shouldn't be contingent on subjective satisfaction.

Unlimited Revisions Language

Some client contracts include language granting "reasonable" revisions without defining a limit. "Reasonable" is subjective and unenforceable in any practical sense. Replace it with a specific number. If they won't agree to a revision limit, factor unlimited revision time into your rate - and make sure that math makes sense before you sign.

Non-Compete Clauses

A client asking you not to work for direct competitors during the project is reasonable. A client asking you not to work for anyone in their industry for a year after the project ends is not. Read every non-compete clause carefully and negotiate it down to something sensible - a limited time period, a defined competitor list, and a scope that doesn't effectively end your ability to work in your niche.

Net-60 or Net-90 Payment Terms

Large corporations often have standard payment terms of Net-60 or Net-90 - meaning they'll pay your invoice 60 or 90 days after you submit it. For a project that runs four weeks, that means waiting three to four months for full payment. That's a significant cash flow problem for a solo freelancer. Negotiate Net-30 at minimum, or price the payment delay into your rate. Either way, don't accept standard corporate payment terms without acknowledging the cash flow cost to you.

Indemnification That Covers Client Decisions

Watch for indemnification clauses that make you responsible for legal claims arising from the client's own use of your work - including how they choose to deploy it, what markets they enter, or trademark conflicts they create. You should only be indemnifying the client against claims arising from your own work and your own representations. You should not be on the hook for what they do with the deliverable after you hand it over.

How to Get Contracts Signed Without Killing the Momentum

The biggest objection designers have to contracts isn't that they don't want one - it's that they're afraid sending a contract will scare the client off or make the relationship feel adversarial right from the start.

Frame it right. When you send the contract, say something like: "Attached is the project agreement - it protects both of us and makes sure we're aligned on scope and expectations before we start. Let me know if anything needs adjusting." That framing diffuses 90% of the potential awkwardness. You're not sending a legal threat. You're sending a document that serves both parties - and any reasonable client understands that.

Consider attaching the contract to your proposal rather than sending it separately after the client has verbally agreed. Some designers include terms at the bottom of their proposals and call it the agreement. Others send a proposal first, then follow up with a contract after verbal agreement. Either approach works - what matters is that the contract is in front of them before any work begins.

Use e-signature tools. DocuSign, HelloSign, or even the signing features inside most proposal tools let clients sign digitally in under two minutes. The faster it is to sign, the faster they sign. Don't email a PDF and ask them to print, sign, scan, and return it - that's a friction wall that delays your start date and gives the client's hesitations time to compound.

If a client genuinely pushes back on a specific clause, engage with it. Ask what specifically concerns them. Often their objection is to the language, not the underlying protection. You can rewrite a clause to address their concern without giving up the protection you need. What you can't do is operate without a signed agreement.

For smaller projects where a full multi-page agreement might feel like overkill, consider a streamlined version that still covers the essentials. The One-Page Contract Template is a solid option for lighter scopes - everything that matters, none of the bulk.

How to Handle Contracts for Specific Project Types

Logo and Brand Identity Contracts

Logo and brand identity contracts need to be particularly tight on IP and revision language. The deliverable is subjective by nature - there's no objective standard for "good logo" - which means revision scope can balloon fast if it's not defined. Specify exactly how many initial concepts you'll present, how many revision rounds are included on the selected concept, and what file formats are in the final delivery package. Establish clearly whether brand guidelines, typography systems, color palettes, and secondary logo variations are included or separate line items.

For logo work specifically, include a clause about what happens to rejected concepts. Your initial concepts - the ones the client doesn't select - remain your property. The client is buying the one they choose to develop, not the full batch of explorations. This matters because some clients will ask you to "combine elements" from multiple rejected concepts, which is essentially asking for additional concept development work under the guise of a revision.

Web Design Contracts

Web design contracts carry additional complexity because they often involve third-party tools, hosting environments, and content the client provides. Your scope section needs to be explicit about what's included: number of pages, whether you're building in a CMS, whether you're responsible for copywriting, what happens if the client's content doesn't arrive on schedule, and whether ongoing maintenance is included post-launch.

For web work, a Statement of Work (SOW) that repeats the content of your proposal - plus everything else agreed verbally - is the standard approach. The SOW becomes an exhibit to your master services agreement. Any additional work beyond the SOW triggers a change order, priced and agreed upon in writing before the work begins.

Social Media and Ongoing Content Design

Ongoing content design - social media graphics, email templates, regular campaign assets - doesn't fit a project contract. You need a retainer agreement. The structure shifts: instead of milestone deliverables, you're agreeing on a monthly scope (a defined number of assets or hours per month), a flat monthly retainer fee, and a notice period for either party to exit.

Retainer contracts are typically better for your cash flow and better for the client relationship. Predictable monthly income on your side, predictable design capacity on theirs. Collect the full month in advance before work begins. Include a minimum retainer term - most designers work with a three-month minimum on retainer arrangements to make the onboarding investment worthwhile.

Print Design Contracts

Print contracts need additional clauses around production approvals. Make explicit that once a design goes to print, errors that were present in the client-approved proof are the client's responsibility. Include a clause requiring written sign-off on the final proof before any print run begins. If you're managing the print vendor relationship, clarify who bears the cost if a print run needs to be redone due to client-approved errors versus production errors.

Retainer Contracts vs. Project Contracts

If you're doing ongoing work for a client - monthly social graphics, regular brand updates, a content design workflow - a project contract doesn't fit. You need a retainer agreement. The structure shifts: instead of deliverable-by-deliverable milestones, you're agreeing on a monthly scope (for example, a set number of hours or assets per month), a flat monthly retainer fee, and a notice period for either party to exit the retainer.

Retainer contracts are typically better for your cash flow and better for the client relationship. Predictable monthly income on your side, predictable design capacity on theirs. If you're pitching retainer arrangements, your proposals matter as much as your contract - the Proposal AI Templates can help you put together proposals that close.

Key differences in a retainer contract structure: you're selling capacity, not deliverables. Define what "capacity" means - is it hours? Asset counts? Unlimited requests within a defined category? Each definition has different risk profiles. Hours are clean and easy to track. Asset counts work well for templated, repeatable work. Unlimited requests within a category require careful definition of what's in and out of scope or you'll end up doing five-figure volume for a four-figure retainer.

Using Project Management Tools to Enforce Your Contract Terms

A contract is only as good as your ability to document what actually happened during the project. If a dispute arises about whether a client approved a concept, whether a revision was requested verbally or in writing, or whether a scope change was agreed upon, your email trail and project management records are what prove your case.

Keep all project communication in writing. If a client calls you with a direction change, follow up the call immediately with an email summarizing what was discussed: "Following up on our call - here's my understanding of the direction change we agreed to: [details]. Please confirm this is correct before I proceed." That email is now part of your project record.

Use project management tools that timestamp approvals and change requests. Tools like Monday.com make it easy to track deliverables, get written approvals on each milestone, and document scope changes in a way that's timestamped and tied to specific project items. If a client later claims they never approved something, you have a timestamped record of their approval click. That kind of documentation makes your contract terms practically enforceable, not just theoretically enforceable.

What to Do When a Client Doesn't Pay

Despite a solid contract, non-payment happens. Here's the escalation path that actually works:

Step 1: Send a formal overdue notice. Plain, professional, no emotion. "Invoice [number] is now [X] days past due. Per our agreement, a late fee of [X]% per month applies to overdue balances. Please remit payment by [specific date]." Most late payments resolve at this step.

Step 2: Stop all work immediately. Do not do another hour of work on any project for this client until the overdue invoice is resolved. This is non-negotiable. Continuing to work while a payment is overdue sends the message that the payment terms in your contract don't actually mean anything.

Step 3: Enforce your IP clause. If the client is already using work they haven't paid for, your contract's IP clause - specifically the provision that rights only transfer upon full payment - gives you legal standing to demand they cease use. Put that in writing in your overdue notice. A client who has already published a logo you designed and hasn't paid for it is now using copyrighted material they don't legally own. That's a meaningful lever.

Step 4: Send a demand letter. A formal demand letter from you (or ideally from an attorney) specifying the amount owed, the legal basis, and the consequences of continued non-payment often moves things that persistent invoices don't. Keep it factual, not emotional.

Step 5: Small claims court. For amounts below your state's small claims threshold (typically a few thousand dollars), small claims court is faster, cheaper, and more practical than hiring an attorney for litigation. Your signed contract and documented work records are your evidence. Most judges in small claims are not sympathetic to clients who ignore invoices on completed, approved creative work.

Finding the Right Clients to Contract With in the First Place

The best way to avoid bad contract situations is to start with better clients. The quality of who you're contracting with matters as much as the quality of your contract language. If you're building a freelance design business and want to expand your client base beyond referrals, you need a systematic way to find and qualify prospects before you ever get to the contract stage.

Referrals are the gold standard, but they cap out. Once you've exhausted your warm network, you need outbound. Cold email to targeted lists is how most freelancers I've worked with break out of the referral ceiling. The key is list quality - you need to be reaching the right decision-makers at companies that actually buy design work. That means filtering by company size, industry, and job title of the person who'd actually have budget for your services.

For building those prospect lists, a tool like ScraperCity's B2B email database lets you filter by title, seniority, industry, and company size to pull targeted lists of marketing directors, brand managers, and founders who are likely to need design work. Once you've identified the right targets, you can reach out with a cold email sequence that positions your services and your process - including the fact that you work on contract - as a signal of professionalism, not a red flag.

If you're prospecting local businesses - retail brands, restaurants, real estate agencies - a Google Maps scraping tool can pull local business contact data at scale so you're not manually searching directory by directory. Local service businesses are often underserved on professional design and receptive to outreach when it's positioned well.

The moment you send a proposal to a new prospect, your contract process starts. A strong proposal sets expectations on scope, timeline, and payment structure - and the contract formalizes those expectations into something binding. The two documents work together. If you want help building proposals that lead to signed contracts faster, the Proposal AI Templates are built specifically for that pipeline.

Red-Flag Client Behaviors Before You Send the Contract

Your contract protects you after a client engagement begins. But recognizing clients who are likely to be problems before you sign saves you even more time. Here are the behaviors that predict bad contract experiences:

• They ask for spec work. "Show us a few options before we commit" is a request for free labor. The professional response: absolutely, once we've signed a contract and processed a deposit. Any client who won't agree to that structure isn't a client worth having.
• They want to pay on completion only. No deposit, payment only when the project is done - that structure puts 100% of the risk on you. If they can walk away at any point without having paid anything, some of them will.
• Multiple people are sending you feedback with no designated decision-maker. If four people are all sending you conflicting feedback, you're heading into an endless revision cycle. Designate one decision-maker before you start - and put that requirement in your contract.
• They've burned other designers. Freelance communities on Reddit and in Facebook groups are good places to research potential clients. If someone has a reputation for not paying or for endless scope changes, that information usually exists. Look for it before you sign.
• They balk at the deposit. A client who argues about a standard 50% deposit before work begins is telling you something important about how the rest of the relationship will go. Take that signal seriously.
• They send you a 40-page vendor agreement for a logo project. Disproportionate contract length is a red flag. It usually means the agreement is heavily one-sided and full of clauses designed to protect them at your expense. Read everything carefully, or have a lawyer look at it, before you sign anything of that scope for a small engagement.

When to Have a Lawyer Review It

For most freelance projects, a solid template you understand and customize is enough. But get a lawyer to review your contract if: you're working on projects above five figures, a large corporation is sending you their vendor agreement to sign, the project involves sensitive IP like software, patents, or unreleased products, or you're being asked to sign anything with a non-compete or non-solicitation clause. The cost of an hour of legal review is nothing compared to the cost of a bad contract on a major engagement.

You don't need a design-specialist attorney for most of this - a general business or contracts attorney can review a freelance design agreement and flag the problem clauses in an hour. Treat that hour as a business expense, not a luxury. If your contract is protecting five-figure engagements, a few hundred dollars in legal review is a fraction of the protection it provides.

A Sample Clause-by-Clause Contract Checklist

Before you send any design contract, run through this list. Every item should be explicitly addressed:

• Full legal names and contact info for both parties
• Entity type confirmation (individual, LLC, corporation)
• Detailed scope of work with specific deliverables, formats, and quantities
• Explicit list of exclusions (what is NOT included)
• Client responsibilities (assets, copy, feedback timelines)
• Number of included revision rounds with a definition of what counts as a revision vs. a new request
• Rate for additional revisions beyond included rounds
• Approval deadline clause (silence = approval after X business days)
• Ownership of rejected concepts and preliminary work
• Project start date, milestone dates, and final delivery date
• Client delay clause (timeline resets if client misses feedback deadlines)
• Rush fee language
• Total project fee
• Deposit amount and payment method
• Milestone payment schedule
• Late payment penalty
• Rights transfer tied to full payment
• IP transfer structure (full copyright, exclusive license, non-exclusive license, work-for-hire)
• Source file delivery terms (included or separate line item)
• Portfolio usage rights
• Confidentiality terms
• Kill fee percentage and trigger conditions
• Termination notice period
• Who owns work completed at time of termination
• Independent contractor status language
• Liability cap
• Indemnification clause (client indemnifies you for their assets and misuse of deliverables)
• Dispute resolution process
• Governing law and jurisdiction

If your current contract is missing more than a handful of items on that list, it's worth rebuilding from a solid template. The free Agency Contract Template covers the core structure - customize it for design work by adapting the scope and IP sections to match your specific deliverables and licensing approach.

The Bottom Line

A freelance graphic design contract isn't bureaucracy - it's how professionals operate. It's what separates "I assumed" from "we agreed." Every clause in your contract is a conversation you're having before the project starts instead of during a dispute after it ends. The designers who hate contracts are almost always the ones who've never been in a serious dispute. One bad client experience fixes that permanently.

The goal isn't to send an intimidating legal document that scares clients. It's to send a clear, professional agreement that shows you run a real business with real standards - and that protects both parties when memory and expectations inevitably diverge. Clients who are worth working with don't balk at that. Clients who do balk at it are handing you free information about who they are before you've invested a single hour.

Get the contract done, get it signed, then do the work. In that order, every time. If you want to go deeper on the business side of building a sustainable freelance or agency practice - pricing, outbound, client management - that's exactly what I work through inside Galadon Gold.