Most design disputes aren't caused by bad faith. They're caused by two people who had different pictures in their heads and never wrote either one down.
A contract isn't about distrust. It's about making sure you both mean the same thing before anyone spends money.
This is general guidance on what design agreements commonly cover, not legal advice. For anything significant, have an attorney review it.
The single biggest source of trouble.
"Logo design" is not a scope. "Three initial logo concepts, two rounds of revision on one selected concept, final files delivered in the formats listed below" is a scope.
Get specific about deliverables and quantity: how many concepts, how many pages, how many designs, how many clips. Vague scope is where projects go sideways for both sides.
Design contract scope should specify deliverables and quantities, not service categories. "Logo design" is a category; "three concepts, two revision rounds, and a defined list of final file formats" is a scope that both parties can actually hold each other to.
List them. This prevents the most common post-project problem.
For a logo, that generally means vector source files, transparent PNGs at multiple sizes, CMYK versions for print, RGB versions for screen, single-color black and white versions, and any layout variations. For a website, credentials and account access. For video, the final export and any agreed source project files.
If source files aren't included, that should be stated plainly rather than discovered later.
Address this directly, because paying for work does not automatically transfer copyright in the US. Ownership generally transfers through a written work-for-hire arrangement or an assignment.
The agreement should cover who owns the final work, when ownership transfers (commonly on final payment), what happens to concepts that weren't selected, and whether the designer may show the work in a portfolio.
Also worth naming: any third-party assets in the project. Stock photography, icons, and fonts carry their own licenses, and those licenses may not extend to every use you have in mind.
How many rounds, what counts as one, what distinguishes a revision from a new direction, and the rate for anything beyond the included rounds.
Also worth including: how long you have to use them. Projects that go quiet for six months and then come back with feedback create genuine problems.
A timeline that only lists the designer's obligations is half a timeline.
Good agreements name what the client owes and when — content, photography, brand assets, feedback, approvals. Projects stall on client deliverables far more often than on production, and stating that upfront isn't defensive, it's realistic.
Include what happens when a dependency is late, since that's the situation everyone would rather not think about until it happens.
Total cost, deposit, payment schedule, and terms. Whether a deposit is refundable. What happens if the project is cancelled partway. When final files are released, which is commonly on final payment.
Also worth covering: what triggers additional charges. Rush requests, scope additions, extra revision rounds, and extra concepts should each have a stated rate rather than becoming a negotiation mid-project.
A design agreement should state what triggers additional charges — rush requests, scope additions, extra revisions — with rates attached. Agreeing on those numbers before the project prevents them from becoming a negotiation at the worst possible moment.
Small clause, disproportionate value.
Naming who is authorized to give feedback and approve work prevents the scenario where a project is nearly finished and someone who hasn't been involved decides they'd like it to be different.
Nobody wants to write this section. Everybody is glad it exists when they need it.
How either party can end the engagement, what notice is required, what's owed for work completed, what gets handed over, and what happens to files and credentials. For ongoing retainers, also cover how to pause or cancel.
If the project involves unreleased products, sensitive information, or a white label arrangement, say so explicitly. Confidentiality that both parties assumed but never wrote down is confidentiality that only exists until it's inconvenient.
It's not a weapon. It's a shared document that both sides can point at when memories differ, which they will.
The best contracts get signed and never referenced again, because the act of writing them surfaced the disagreements before they cost anyone anything.
If a designer resists putting scope, files, and ownership in writing, that resistance is information.
What should be included in a design contract?
Specific scope and deliverable quantities, an itemized list of files you'll receive, ownership and rights terms, revision rounds and definitions, timeline with client dependencies, payment terms and triggers for additional charges, who can approve work, and how either party ends the engagement.
Do I need a contract for a small design project?
Even a short written agreement covering scope, files, ownership, revisions, and payment prevents most disputes. It doesn't need to be long — it needs to be specific.
Who owns the design work in a contract?
Whoever the agreement says owns it. In the US, paying for work does not automatically transfer copyright; that generally requires a written work-for-hire arrangement or assignment. Address it explicitly.
Should a design contract include source files?
It should state clearly whether they're included. Some designers include them, some charge separately, some retain them. All are legitimate — what isn't legitimate is leaving it ambiguous until the project ends.
What if the designer and I disagree about scope mid-project?
Return to the written scope. If it's specific, the answer is usually clear. If it isn't, that's the lesson for next time — and the practical path forward is agreeing on a change order rather than arguing about intent.
Can I use a contract template for design work?
Templates are a reasonable starting point, but they need adapting to your actual project and jurisdiction. For anything of significant value, have an attorney review it.
Want a scope written clearly before anyone starts? Schedule a free consultation at jpetrous.com | contact@jpetrous.com | 586-563-6634.
.jpg)
.jpg)
The businesses winning in Michigan aren't chasing trends. Jonathan Petrous shares a practical 2027 marketing playbook built specifically for the Michigan small business market.
Read More
Great local businesses in Marysville, Chesterfield, and Macomb Township are invisible online — and it's fixable. Jonathan Petrous explains the three most common causes and exactly what to do about them.
Read More
Tight marketing budget in Port Huron or the surrounding area? Jonathan Petrous shares the highest-leverage moves local businesses can make right now — most of them free or nearly free.
Read More
Before you go
Call or send a message. Tell me what you're working on and I'll tell you honestly whether I'm the right fit.