How Do You Stop Mood Board Revisions From Living in Your Inbox?

How do you stop mood board revisions from living in your inbox?

Every interior designer knows this thread: v1 goes out, the client replies with three changes buried in paragraph form, v2 goes out with those changes plus a couple you added on your own judgment, the client comes back with "actually I liked the first fabric better," and by v4 nobody — including you — can say with certainty which combination of choices the client actually signed off on. It's not a client problem or a communication-skills problem. It's a structural problem: revisions happening inside an email thread have no clear state, no clean version boundary, and no explicit "yes, this is final" moment.

Why email makes this specifically worse for mood boards

A drawing revision at least has version numbers most firms are disciplined about. A mood board revision often doesn't — it's the same email thread with new attachments, and "the fabric I liked" could refer to any of four different swatches mentioned across a week of back-and-forth. Threads also fork: a client replies to an old message instead of the latest one, and now there are two live conversations about two different revision states, both claiming to be current.

What actually needs to exist to fix this

Not more discipline — a structure that makes the ambiguity impossible in the first place:

• A single place each mood board revision lives, not scattered across separate email attachments

• An explicit approval state per revision — not inferred from the tone of a reply

• A record of exactly which revision a client's "yes" applies to

• A comment tied directly to the specific item under discussion, not a paragraph that has to specify which fabric or finish it's referring to

How this maps to Wallxy's structure

Mood boards and design media fit into the same project structure used for drawings — organized by floor or room, moving through the same explicit approval flow: Pending → Submitted → Under Review → Approved, or sent back as Revision Required. That last state matters specifically for interior design work — "revision required" is a distinct, recorded status, not an unanswered email waiting for someone to notice it needs a reply.

Clients get Viewer-level access to the actual project — not a forwarded PDF, the live record — so they're looking at the current revision, not whatever attachment happens to be at the bottom of their inbox. And on projects where the firm has a Go or Pro subscription, clients can comment directly against a specific item rather than replying to an email thread that has to describe which swatch or finish they mean in prose.

What this changes in practice

Instead of "which email had the final fabric choice," the answer lives as a status: this mood board revision is Approved, this one was sent back as Revision Required with a comment attached explaining why. There's no reconstruction required — the state is just there, tied to the specific version.

Getting started — a short checklist

• Move your next mood board revision into the project structure instead of a new email attachment

• Ask your client to comment directly on the specific item instead of replying in prose

• Treat "revision required" as a real status you track, not an unanswered message

• Don't consider a version final until it's explicitly marked Approved — not just "no objections so far"

FAQ

Does this work for physical material samples too, or just digital boards?
The approval and comment structure applies to whatever's uploaded as project media — digital renders or photographed physical samples both work the same way.

What if my client still prefers replying by email?
The record can still exist on your side even if the client's habit is email — you log their reply against the correct revision rather than losing which version it refers to.

Can the client see revision history, or just the current version?
As a Viewer, they see the actual live project record — including where a revision sits in the approval flow, not just a static final file.

Is commenting available on every plan?
No — project discussions and comments are available on Go and Pro plans, not Free.