How to Manage Interior Design Client Approvals Online
Manage interior design client approvals online with live links, per-item decisions, contextual comments, deadlines, and durable proposal records. Learn how to reduce login friction and version confusion.
Manage interior design client approvals online with a workflow that reduces friction and preserves a clear record:
- share a live board or FF&E schedule rather than an exported PDF;
- let clients approve or decline individual items;
- attach comments to the relevant product or board item;
- record the decision and date;
- follow up only on outstanding selections;
- issue a fixed proposal that records the approved scope and prices.
No-login links can reduce signup friction. Account-based portals provide a more persistent client space. Neither model automatically creates durable evidence, so verify how identity and version history are stored.
Why approvals stall
It is almost never disagreement. Designers describe stalled approvals as clients “going quiet”, and the causes are usually mechanical.
Friction. The client received a link, clicked it, hit a signup form, meant to come back to it, and did not. This is a common and avoidable source of delay.
Scale. You sent sixty selections and asked for a yes. The client feels the weight of sixty decisions, defers, and the whole phase waits on the one item they are unsure about.
Ambiguity. Feedback arrives as “love it, but not the blue one” in reply to an email containing eleven products, and now you are reconstructing which blue thing they meant.
Staleness. You sent a PDF, three prices changed, and now nobody is confident which version is being discussed.
Every one of those is a workflow problem rather than a client problem, which is good news — you can fix all four.
The four fixes
1. Remove the login. If your clients are busy homeowners rather than engaged professionals, an account requirement is the difference between an approval this week and an approval this month. Atelier and Densy both work by live link with no client account. Account-based portals — Mydoma is the strongest — give a richer structured space and suit long projects with committees, so this is a genuine trade rather than a universal rule.
2. Ask per item, not per phase. A client who cannot decide on the dining chairs can still approve the rug, the lighting and the case goods. Per-item approval keeps the project moving and isolates the actual blocker, which is also useful information — it tells you exactly where to spend a conversation.
3. Put the comment on the item. Feedback attached to the specific pin or schedule line eliminates the “which blue one” problem entirely, and it means the record of what they said sits with the thing they said it about rather than in a thread you have to search.
4. Send live work, not exports. A shared link that reflects current state cannot go stale. A PDF is out of date the moment a price changes, and re-sending corrected PDFs is how version confusion starts.
Do not use a proofing tool for this
Approval Studio, Adobe’s review tools and similar proofing platforms come up in this search, and they are good software aimed at a different job.
Proofing tools are built to annotate a creative file — mark up a version of an artwork, compare revisions, collect comments. That fits an agency reviewing a layout. It does not fit FF&E selections, because a design approval is a decision about a product, at a price, with a lead time that needs to connect to your schedule and your procurement.
Run approvals in a proofing tool and the decision lives somewhere your schedule cannot see, which means someone transcribes it back — reintroducing exactly the manual step you were trying to remove.
Be honest about the record
This is the part most marketing overstates, including ours until recently, so it is worth being precise.
There is a difference between workflow and evidence.
- Workflow is: has this item been approved, so can I order it? Every platform here answers that.
- Evidence is: what exactly did the client agree to, at what price, in what finish, on what date — provable months later when something is disputed.
Most tools, Atelier included, record the current decision on each item rather than a snapshot of the version that decision was made against. If the item changes afterwards, the approval flag persists while what it referred to has moved. Share links are also typically not tied to a named individual.
The practical implication: treat in-app approvals as workflow, and rely on the issued proposal as the contractual record. A proposal states scope, products and prices at a moment in time and does not change afterwards, which is precisely what evidence requires. Send one for anything you would want to prove.
If durable, version-pinned approval records matter enormously to your practice, the account-based portals are further ahead on that specific dimension, and it is worth testing before you commit.
A workflow that holds
- Board first, at concept. Share a live pinboard link for direction, not for line-item sign-off. You want agreement on the scheme before anyone prices anything.
- Schedule next, per item. Share the schedule and let the client approve or decline each line, with comments on the line.
- Chase the blockers, not the client. Per-item status tells you which three items are outstanding, so the follow-up is specific rather than a general nudge.
- Issue a proposal for what is agreed. This is the record. Proposals generated from the schedule carry the agreed products and prices without retyping.
- Order from approved lines only, and let procurement carry each item from specified through to paid.
Atelier is our product, so weigh accordingly: it does steps 1–5 with no client account, per-item decisions, comments on the item, and documents generated from the schedule. Atelier uses per-seat pricing. Verify current details on the Atelier pricing page. It does not pick your products or design for you, it does no 3D rendering, and it is not an accounting system.
Disclosure: Atelier is our product. This article is explicit that Atelier records a current per-item decision rather than a version snapshot and that account-based portals may offer stronger persistent client history. Features and pricing change frequently; verify current details with each vendor.
Frequently asked questions
- How do I manage interior design client approvals online?
- Use a live board or schedule link, let clients decide item by item, attach comments to the relevant selection, record the date and decision, and issue a fixed proposal for contractual clarity. Choose between a no-login link and an account-based portal according to client behavior and the level of persistent project history required.
- Should I use a proofing tool like Approval Studio or Adobe for design approvals?
- Generally not for FF&E selections. Proofing tools are built to annotate a creative file — a version of an artwork or a layout — and they do that well. A design approval is a decision about a product at a price with a lead time, which needs to connect to your schedule and procurement. Using a proofing tool means the decision lives somewhere your schedule cannot see.
- What is the best way to send a client products for approval?
- As a live link to the actual board or schedule, not an exported PDF. A PDF is stale the moment a price changes and produces the version confusion you are trying to avoid, whereas a live link always shows current state. Make sure the client can respond on the individual item rather than in a general reply, so feedback arrives attached to the thing it is about.
- How do I keep a record of what a client approved?
- Be clear about what your tool actually stores, because this varies more than marketing suggests. Most platforms record a current decision per item, which answers "did they say yes?" but not "at what price and in what finish?" if the item changed afterwards. For contractual clarity, the issued proposal is the document that states scope, products and prices at a moment in time — keep it, and treat in-app approvals as workflow rather than evidence.
- What if a client will not respond to approval requests?
- Reduce what you are asking for. Non-response is usually either friction (a login, an app, a 40-page PDF) or scale (approve these sixty items). Send fewer decisions at a time, make each one a single click, and remove any account requirement. If a client still will not engage, a deadline written into the proposal — selections not confirmed by a date proceed as specified — is a contractual fix rather than a software one.
- Do clients need to create an account to approve work?
- It depends on the platform, and it is the single biggest predictor of whether approvals actually land. Account-based portals like Mydoma give a richer structured experience but add a signup step that leaks. Atelier and Densy use no-login links: the client clicks, sees the live work, comments and decides. Neither approach is universally right — it depends on whether your clients will maintain a login.