Approvals rarely die because the client disagrees. They die of ambiguity — a proposal photo texted casually, a verbal yes at a site visit that never gets written down, an email reply that answers two of your four questions and leaves the sofa in limbo. The industry knows this is where the friction lives: in Houzz's 2025 State of the Industry report, roughly a third of design professionals named improving communication with clients and teams as a priority — in a year when designers took the sector's largest revenue dip. Slow yes's aren't a personality quirk of your clients. They're the category's most expensive open problem.
The good news is that most of it is fixable with how you ask.
Where approvals die
Trace your last stalled decision and you'll almost always find one of three failure points. The ask was scattered — the image in one email, the price in another, the question implied. The ask was vague — "thoughts?" invites conversation, not commitment. Or the yes happened out loud — at the site, on a call — and evaporated because nobody wrote it down.
The structural version is worse: approvals in email, specifications in files, no single record connecting them. When a dispute surfaces months later, there's nothing to point to, and "I never approved that" becomes a genuinely unresolvable argument. It's no accident that when designers describe why they moved off email-and-spreadsheet systems, the most repeated relief in this category's reviews is consolidation — in one reviewer's words, "One place, completely organized, no more wasting time finding emails."
What a real approval needs
Four elements, visible together, at the same moment: the image, the spec, the price, and a clear question. When those four scatter across messages, a ten-second decision becomes a research project — the client has to reassemble your ask before they can answer it, so they park it for the weekend, and the weekend never comes.
And make the question answerable. "What do you think?" cannot be answered with yes. "Approve this sofa at $4,200, or let me know what you'd change" can.
Decisions made in person don't count until they're written down
Site visits generate more unrecorded decisions than anywhere else in a project. The client points at the tile, says "love it, do it," everyone feels great — and six weeks later that moment exists only as two people's differing memories of it.
The fix isn't distrust of the client — it's treating a verbal yes as a draft of a decision. Same day, while it's fresh, restate it in writing: the image, the spec, the price, and what was agreed. Thirty seconds. Designer Nicole White is blunt about why her studio sends every decision through a documented approval request: "so there's no denying they ever read it… you'll be amazed at how many times clients deny having a conversation verbally or via text." That's not cynicism about clients — memory is genuinely unreliable on both sides of a months-long project. As the industry framing goes, documentation isn't a sign of distrust; it's a sign of professional organization. Your record protects the client's decisions exactly as much as it protects yours.
Following up without nagging
First, name what's really going on when you don't follow up. You drafted the reminder, softened it, added "sorry to bug you again!", then deleted the whole thing — not because the follow-up is unreasonable, but because some part of you is scared that one email too many is the one that makes you the difficult designer, the one they don't recommend, the one they leave. Designers are, in their own words, people-pleasers — "we love to make clients happy," as designer Kirsten Kaplan put it — and the fear underneath the un-sent reminder is losing the client, not annoying them. It helps to say that out loud, because the fear is doing the scheduling, and the fear is wrong: clients don't churn over designers who follow up. They churn over decisions that took longer than expected.
Now the structural fix, which mostly removes the need to chase at all: attach the deadline to the original ask, with its reason. "I'll need an answer by Friday to hold this lead time." When Friday arrives, the deadline is doing the uncomfortable job, not you — you're not nagging, you're reporting a fact about the lead time. And if the deadline passes, don't send a bare "just checking in!" Re-send the complete decision — image, spec, price, question — because by now they've forgotten the details, and a reminder without the details just asks them to go find the original email you're both pretending they read.
Building the paper trail as you go
The record you'll need in month nine can only be built in month two. Every decision, captured when it's made: the date, the exact item, the price, who approved it. Not reconstructed later from a thread archaeology session — captured at the moment, as a habit.
Solo, running two or three projects, you can hold this together manually with the same-day-confirmation rule and a disciplined folder. It's real work, but it's doable, and none of this requires new software to start practicing tomorrow.
Where it stops being doable is scale: more projects, more decisions per week, a new assistant who wasn't in the room for the verbal yes. That's the point of the way Mortar handles approvals — each selection goes to the client with its image, spec, and price together, they approve with one click, and the decision is logged with a timestamp against the item. The paper trail assembles itself as a by-product of asking properly, which is all it ever should have been.
Ask with all four elements. Put deadlines on the ask, not guilt on the follow-up. Write down every yes the day it happens. The chasing stops when the asking changes.
