How to manage client expectations as a designer — before the first deliverable

You drop a Figma link into Slack at 11:42 p.m. The client opens it the next morning and replies with: “Can you make everything pop more? Also change the header, the CTA, and is that the final type?” That reply contains three dangerous things: vague demands, unstated deadlines, and no idea whether this is their first set of comments or the last.

You won't fix this after the fact. You fix it before you ship the first deliverable. That starts the moment you say yes to the project. This piece is about how to manage client expectations as a designer before any file lands in their inbox — so you don't end up reconciling five different PDFs, an email thread, and an MS Paint markup.

Why set expectations before the first deliverable?

Because once you share a file, assumptions multiply. Clients assume unlimited rounds. PMs assume thumbnails are final. Stakeholders assume the last PDF is the source of truth. And you assume they read your last email. All of those assumptions are wrong.

Set expectations up front and you get fewer late-night redesigns, cleaner invoices, and a client relationship that treats you like a partner instead of a do-over machine.

What to cover in the kickoff message (say this in writing)

Keep it short, usable, and concrete. Send a one-paragraph kickoff followed by a 5-bullet checklist. Put it in the contract and paste it into the kickoff email or the first Slack message.

Your paragraph: a short statement of what you're delivering and how the review will work. Example:

• "I'll deliver initial designs in Figma by May 10. You'll have 48 hours to review each deliverable. We have 3 rounds of revisions included; each round must include consolidated feedback from your team. Approved designs will be signed off with a typed name and date. Extra rounds billed at $X/hr."

Why these specifics matter:

• 48 hours creates momentum and prevents perpetual 'I'll get back to you.'
• 'Consolidated feedback' stops you from merging three different stakeholders' competing requests into one Frankenstein design.
• A typed-signature approval is the simplest legal primitive you can use to close a design — no hunt for emails.

How to phrase the revisions policy so it's not a scalpel but a handshake

Don't sound defensive. Use practical language. Example:

• "We include three revision rounds. A round is one consolidated set of feedback per deliverable. Requests after sign-off are out of scope and billed."

Then give one quick example: "Round 1: layout changes. Round 2: copy and microcopy. Round 3: final polish and assets." Real clients will appreciate the map.

Choose one feedback channel and own it

If you let clients use email, Figma comments, PDFs, MS Paint markups, and carrier pigeons, you'll spend your time stitching context. Pick one channel for review and gate it.

• If you need precise pixel feedback: use Figma comments or an annotated screenshot tool.
• If stakeholders prefer PDFs: export and specify exactly how to mark comments (no annotations outside the comment box).
• If you want zero friction for non-technical clients: send a ClientMarkup link so they can pin/draw and record a screen without signing up.

When the channel is set, explicitly refuse other channels. Say: "We'll take feedback only through X. If you send it elsewhere, we'll ask you to re-submit through X so we can track change requests." People comply when you make it easy and formal.

Create a feedback template clients can paste

Most feedback is useless because clients don't know how to describe what they mean. Give them a one-paragraph template:

• Page / Frame: (e.g., Homepage hero)
• Change: (what you want changed)
• Why: (what problem this solves)
• Priority: (High / Medium / Low)

Ask them to consolidate comments from everyone and paste them into the review tool. This turns vague notes like "make it pop" into actionable tasks.

When feedback is specific and prioritized, you stop guessing and start delivering.

Timeboxes, SLAs, and the money part

Say how long reviews take, and what happens after the clock runs out. For example:

• "Review window: 48 hours. If we don't receive consolidated feedback, the design is considered approved and work proceeds."

Also define turnaround times for you: "Minor changes: 24–48 hours. Major revisions: 3–5 business days." That way the client knows whether that 'small nit' will actually take an hour or two days.

Make scope creep a billing event. You're not being petty. You're being a business.

Example scripts (copy-paste friendly)

Kickoff summary to send with your estimate:

"Deliverables: Homepage mockup, mobile mockup, and asset export. Review process: 3 revision rounds. Each round requires consolidated feedback via Figma comments (or the agreed tool). Review window: 48 hours per deliverable. Approved designs require a typed signature and date. Additional rounds billed at $X/hr."

Reminder to a client mid-review who is fragmenting feedback:

"Quick ask: please paste all feedback from the team into a single comment thread in Figma (or upload a single annotated PDF). I'll consolidate and address everything in the next round. Thanks — saves everyone time."

Small ways to make this painless (and look professional)

• Share export-ready PDFs for stakeholders who don't use Figma. But include a link back to the source and label the PDF "For review only — comment in X."
• Use quick video recordings for sticky decisions: a 90-second Loom explaining why you chose a layout shrinks long threads.
• When you need final approval, send a clear one-click action (typed signature, checkbox, or a ClientMarkup approval) and an automatic timestamp. You won't enjoy guessing whether "Looks good" meant sign-off.

When things still go off the rails

If a client ignores the process, escalate. Re-send the kickoff paragraph. Offer to hop on a 20-minute call to consolidate feedback. If the same scope creep repeats, put the extra work on a change order. Respect yourself and your calendar.

Set expectations before the first deliverable and you've solved half your problems. You will still have subjective feedback. You will still get 'make it pop' notes. But you'll have fewer surprises, cleaner decisions, and a contract that matches reality. That matters more than the perfect pixel.

If you want a lightweight way to collect annotated feedback and a typed sign-off without forcing clients to make accounts, try ClientMarkup. It stops the multiple-file mess and keeps sign-off simple.

Finish your kickoff message now. Write the single paragraph. Paste it in the contract. Then ship on time and refuse to rebuild ghost requests. That first sentence you send sets the tone for the whole project.