Most design project disappointments happen because expectations were unclear from the start — not because the designer was incompetent. The client expected something that wasn't in scope. The designer delivered something technically correct that didn't match the client's unstated vision. The timeline slipped because feedback arrived late and nobody had agreed on what late meant.
Setting clear expectations at the start of a design project is the highest-leverage thing you can do to ensure a good outcome. Here's how to do it.
The 7 Areas Where Expectations Need to Be Set
1. Deliverables: What Are You Actually Getting?
The first expectation to clarify is the most fundamental: what exact deliverables will be produced? A "brand identity" project can mean vastly different things to different designers. Some examples:
Minimal brand identity:
- Logo (one version, one format)
- Two brand colours with Hex codes
Standard brand identity:
- Logo system (primary, stacked, icon, reversed)
- Colour palette with full colour specifications (Pantone, CMYK, RGB, Hex)
- Typography selection (primary and secondary typefaces)
- Basic brand guidelines (1–3 pages)
Comprehensive brand identity:
- All of the above, plus
- Extended colour palette
- Iconography system
- Imagery style guidelines
- Application examples (business card, email signature, social media)
- Detailed brand guidelines document (15–30 pages)
Before signing any agreement, get a specific deliverables list. "Brand identity" without specifics is ambiguous. "Logo in SVG, EPS, and PNG formats with five variations, Pantone colour specifications, two typeface selections, and a one-page brand guidelines summary" is a deliverable.
2. Scope: What Is and Isn't Included
Scope defines the boundaries of the project. Scope creep — where additional work is added incrementally without formal agreement — is one of the most common causes of project strain and client-designer relationship breakdown.
At the start, clarify:
- How many logo concepts will be presented initially?
- How many rounds of revisions are included?
- What counts as a revision versus a new direction?
- Are all file formats included, or are some extra?
- Is the brand guidelines document included, or is it a separate scope item?
Get the answers in writing. A verbal agreement is not an agreement.
3. Timeline: When Will Things Happen?
A project timeline should specify:
- Start date — when design work begins (often after brief/deposit)
- Concepts presentation date — when you'll see initial design options
- Revision turnaround — how long each revision round takes after feedback
- Feedback windows — how long you have to respond to each deliverable
- Completion date — when final files are delivered
Be honest about your own responsiveness. If you know you travel frequently, have competing priorities, or need to gather input from multiple stakeholders, build that into the timeline. A project that needs 2 weeks of design work but requires 6 weeks of client feedback time takes 8 weeks — not 2.
4. Communication: How and How Often
Set expectations about:
- Primary communication channel — email, Slack, project management tool?
- Response time expectations — what's the expected turnaround on messages?
- Who is the designer's point of contact? — one person on the client side
- How will work be presented? — shared file links, PDF documents, video walkthroughs?
- Meeting cadence — are there project check-in calls? How often?
The less ambiguous the communication expectations, the less anxiety both parties feel during the project.
5. Feedback Process: How Will You Review Work?
Set expectations about how feedback will work:
- Feedback will be consolidated from all stakeholders before sending — not sent in multiple waves
- Feedback will be provided within [X] business days of receiving work
- Feedback will be specific and prioritised — not just "I don't love it"
- Design rationale will be shared with feedback, not just change requests
Also discuss: what happens if you want to change direction significantly after concepts are presented? Is there a cost? Is there a process? Clarify this upfront, not when the situation arises.
6. Payment: Amount, Schedule, and What Happens If Things Change
Expectations to clarify:
- Total project cost
- Payment schedule (deposit, milestone payments, completion)
- What triggers each payment
- What happens if the project scope changes significantly
- What happens if the project is paused or cancelled
Financial clarity prevents the awkwardness of discussing money mid-project, when relationships may already be strained by unexpected scope changes or delays.
7. Ownership and Usage Rights: Who Owns the Work?
Upon final payment, most professional design agreements transfer full ownership of the final logo and brand identity to the client. Clarify:
- When does ownership transfer? (Typically on final payment)
- Are there any usage restrictions? (Unusual, but worth confirming)
- Does the designer retain the right to show the work in their portfolio? (Standard and acceptable)
- Who owns the working files (AI/Figma source files)? (Often not included in standard agreements — ask if you need them)
The Expectations Document
Consolidate all of the above into a single document before the project starts. It doesn't need to be a formal contract (though a contract is better) — even a shared notes document or email thread that both parties confirm is sufficient.
The goal is that both the designer and the client have the same understanding of: what is being made, when it will be done, what it costs, how communication will work, and who owns what at the end.
Red Flags to Watch For
Before signing:
- Vague deliverables list ("we'll design your brand")
- No revision count specified
- No timeline provided
- Payment upfront with no milestone structure
During the project:
- Designer goes quiet for extended periods without communication
- Significant scope changes added without pricing discussion
- Work delivered that doesn't address the brief at all (suggests the brief wasn't read)
On the client side:
- Feedback arriving days after agreed windows
- New stakeholders introduced mid-project with new opinions
- Direction changes after approval of a previous stage
Both parties have responsibilities to make a project go well. Clear expectations at the start give both sides the framework to hold each other accountable — and to address problems when they arise.
Looking for a design agency with a clear, structured process?
Evoke Studio's brand identity projects come with a clear brief, a transparent timeline, and one round of focused feedback — no ambiguity, no scope creep.
A complete brand identity agreement should include: specific deliverables list, revision count and process, timeline with key dates, payment schedule, communication expectations, ownership/IP transfer terms, and what happens if scope changes. The more specific the agreement, the less ambiguity exists when complications arise.
Two to three rounds is standard for most professional logo and brand identity projects. More rounds typically indicate either an inadequate brief (which produced off-target initial work) or unclear feedback (which doesn't give the designer enough to redirect accurately). The quality of brief and feedback matters more than the number of rounds.
If the final result doesn't match the brief — and you provided a clear, specific brief — that's a legitimate dispute and should be addressed with the designer directly, referencing the brief. If the result doesn't match an unstated expectation that wasn't in the brief — that's a brief problem, not a design problem. Prevention is always better: the more specific your brief, the more likely the outcome matches your expectations.
Yes, for any project over a few hundred dollars. A contract doesn't need to be complex — a clear statement of deliverables, timeline, payment, and IP transfer is sufficient. Many professional designers provide a standard agreement; if yours doesn't, ask for one or provide one. The conversation about what goes in it is itself a useful expectations-setting exercise.
A kill fee (or cancellation fee) is a payment made to the designer if the project is cancelled partway through. It compensates the designer for time spent and opportunity cost of the cancelled project. Kill fees are typically structured as a percentage of the total project value for work completed to date. Fair and reasonable — designers reserve time for your project, and cancellation has a cost.