Workflow
Turn a vague reaction into a decision you can act on
Show the option, capture what the client actually meant, produce the revised version, and close the loop while the conversation is still open.
Avisual Studio is the visual agent workforce for interior businesses. Client Review and Approval is the workflow for the conversation after the visual exists: your staff member shows a prepared visual, records what the client reacted to, and runs a revised version. "Approval" here means your client's own decision. Studio does not approve anything.
"I like it, but something about the island isn't right"
The client has reacted. Nobody yet knows what they meant.
Most clients cannot read an elevation, a section or a plan. They look at one, nod, and leave holding a picture of the space that nobody in the room has seen. Sometimes they say yes to a proposal they have understood differently from the person who drew it, and the difference surfaces late, as a change.
So feedback arrives as a feeling. Translating it into a change takes a second conversation, and the second conversation happens after the visual has already been revised once.
By the time the revised version comes back, the client has half-forgotten what they meant, and the round starts again.
Every round costs a queue slot
The cost is not the change. It is the wait between the reaction and the revised version.
The review loop today
- The client reacts in a meeting or an email.
- Someone interprets the reaction into a change request.
- The change goes back into the production queue.
- A revised version returns, and the client re-reacts to a version they no longer remember the context for.
The review loop with Studio
- Your staff member shows the prepared visual and captures what the client reacted to, on the visual itself.
- They run the revised version from the same source with the change applied.
- The client sees the alternative alongside the original, in the same conversation where possible.
- The decision is recorded against a specific version, not against a description of one.
Your staff member runs the meeting, interprets the client, and decides which version is presented. Studio produces versions on request; it does not talk to your client and it does not judge which version is correct.
A prepared visual and a clear point of change
This workflow starts after a visual exists. It is the loop, not the first draft.
Bring a prepared visual
An interior visual you have already produced, or one produced through the Design Visual Production workflow.
Produce one firstBring an elevation or drawing
If your client review runs off drawings, start from the drawing and the workflow will produce the reviewable version.
Bring the point of change
Which element the client reacted to, and what they want different about it. The more specific the point, the less is inferred.
Who does what inside the review loop
Producing a version is repeatable work. Reading a client is not, and it does not move.
Your staff member keeps
- The client relationship, and the whole of the conversation with the client.
- Interpretation: deciding what the client's reaction actually asks for.
- Technical judgement: whether the change is buildable, compliant and correct.
- Which version is shown, and which version goes on record as the client's approval.
Drawing-to-Interior
Reads the elevation, section or sketch under discussion and produces an interior visual the client can react to.
Lighting and Mood
Shows a scene you have already agreed under different light, leaving the contents of the room alone.
Two further teams are named for this workflow but are not offered here yet: a floor-plan-to-3D team and a visual-instruction team. Both depend on drawing workflows that have to be validated for this workflow first, and neither is offered in Studio until that validation is done.
The same room, one element changed
A revision is only useful if everything the client already accepted stays exactly as it was.
Preserved from your source
- Room geometry, camera position and every element the client did not comment on.
- The materials and finishes already accepted in the previous version.
- The light setup, unless the change was about the light.
Inferred by the agent team
- How the requested change behaves in the parts of the scene the source did not show.
- The transition between the changed element and what surrounds it.
Must be reviewed by a person
- Whether anything moved that the client did not ask to move.
- Whether the change reads as the change your client described.
- Whether this version is the one you want on record as the decision.
Every visual on this page carries a label, because the label is part of the claim. Both figures here are labelled controlled demonstration: capability shown under defined, controlled conditions, on material chosen to make the point legible. Neither is a case study, and neither is drawn from a customer project.
The worked example this workflow owes you is one review conversation end to end — the source, the point the client raised, the revised version, and the decision that followed. It has not been published yet. When it is, it will appear on the Examples page as a representative example, labelled and explained there rather than asserted here.
Before any version reaches your client, a person on your staff checks it: that nothing moved which the client did not ask to move, that the change reads as the change described, and that the visual is fit to represent the design at this point in the project. That check is not optional and Studio does not perform it.
There is no figure on this page for revision rounds, clarification time or decision speed. Measured performance gets published when it is stable enough to stand as a product claim, and not before.
What changes in the approval cycle
The gain is in closing the loop while the client is still in the room.
The workflow changes
Revision stops being a booking and becomes a step in the meeting.
Staff capacity changes
Your team spends fewer cycles reconstructing what a client meant.
The customer experience changes
The client sees their own comment applied, not a description of it.
The business outcome changes
Whether that reduces the number of rounds in your practice is something a pilot measures.
What still governs the project
A client-readable visual is not technical authority, and this page will not let the two blur.
Do these visuals replace our drawings?
No. They do not replace drawings, and they are not meant to. The drawings, the specifications, the measurements and your professional review still govern the project. The visual is there so the client understands what the drawing describes before they decide.
What does "approval" mean on this page?
Your client's own decision about a design option, recorded against a specific version. Studio does not approve anything: not technically, not contractually, and not for any regulatory purpose.
When is this workflow not a fit?
When the decision needs technical or dimensional verification. If what has to be confirmed is a measurement, a clearance, a tolerance or compliance with a standard, that is a job for the drawing set and a qualified professional, and this workflow is not a fit for it.
What if the drawing is incomplete?
Then more is inferred, and more needs checking by a person on your staff. The workflow tells you what it inferred so you can judge whether the gap matters for this client conversation.
Three ways to start
A prepared elevation, your own drawing, or a process pilot on your own review cycle.
Start from a prepared elevation
Use a prepared elevation we supply and run one review round on it. Nothing of yours is needed, and you see what a revised version looks like before you commit a live project to it.
Set up a run from a prepared elevationStart from your own drawing
Bring a drawing from a project you are reviewing now, and run the point of change your client actually raised.
Set up a run from my own drawingAssess your own approval process
Take one repeatable review cycle, run it through Studio for a defined window, and measure it against your own baseline. Any figure you want to quote about your practice comes from a process pilot like this one, not from this page.
Read how a pilot is measuredWhat Studio does not do
The limits are part of the product. Read them before you plan work around Studio.
- "Approval" on this page means your client's own decision about a design option. Studio does not approve anything: not technically, not contractually, and not for any regulatory purpose.
- Output is a communication visual, not construction documentation, and it does not verify dimensions.
- Approved drawings, specifications, measurements and professional review still govern the project. A client-readable visual supports the conversation; it does not carry technical authority.
- An incomplete drawing means more is inferred, and inferred content needs checking by a qualified person on your staff before it reaches a client.
- A revised version can change something you did not ask it to change. Your staff member checks each version before it is shown.
- Studio does not communicate with your client. Your staff member runs the conversation.
- This page publishes no figure for revision rounds, clarification time or approval speed. Any such number about your business comes from your own pilot.
- This workflow is not a fit where a decision needs technical or dimensional verification. That belongs to the drawing set and a qualified professional.
Choose your next step
Each route below produces something you can look at and judge.