Example

One review conversation, from the first version to the decision

This is where the client review and approval example will be published: the version that went to the client, the point the client raised, the revised version, and the decision that followed. None of it has been produced, and this page says so rather than filling the space.

Avisual Studio is the visual agent workforce for interior businesses. This page is the home of one worked example: the material it will start from, the direction a person will give, the workflow and agent teams that will run it, and an account of what the result will and will not establish. The example itself has not been produced. No source and no result is published here yet, and every figure on this page is a placeholder that states what it will contain.

Illustration in productionFour empty frames in a row: the version sent, the point raised, the revision, the decision
explanatory schematicThe shape this page is built to carry: the version that went out, what the client said about it, what came back, and what was decided. The frames are empty because the conversation has not been run.

What this page is, and what it is not

This is the published home of one example Avisual has committed to. The example has not been produced, and the commitment below is carried in the words the Examples hub uses for it.

Every part of the evidence sequence below is on this page except the evidence. That is deliberate rather than unfinished: the structure is published so you can see what this example will have to carry before it carries it, and so that the commitment has an address you can hold Avisual to.

What that means for you today is simple. You cannot judge Studio from this page. You can judge what Studio will be willing to publish about itself, which is a different and smaller thing, and the workflow page linked below is where the argument actually lives until the run happens.

Client review and approval — one review conversation end to end
Not published yet. It will show the source, the point the client raised, the revised version, and the decision that followed. It will carry the representative example label. Until the run happens, every figure on this page renders as a placeholder and this page establishes nothing about what Studio produces.

What it will start from

The source will be published at the same size as the result, because a result without its source is decoration. Neither exists yet, so both frames below state what they will hold.

Illustration in productionThe version that will go to the client
representative exampleSource, not yet produced. It will be the version that actually went to the client, shown at the same size as the revision that replaced it.
Illustration in productionThe revised version the client will respond to
representative exampleResult, not yet produced. It will be the revision the client responded to, shown beside the version it replaced, with the decision that followed stated underneath.

Direction, not yet published. It will be quoted here word for word: what the client said, and — separately — what the staff member decided that meant and asked for. Those two are not the same sentence, and an example that publishes only the second one hides the step where the judgement actually happened.

What a person will ask for

The direction will be quoted as it was given, not tidied up afterwards to suit the result. Its length is part of the evidence.

A review conversation has two directions in it, and they belong to different people. The client says something about a visual. A staff member decides what that reaction actually asks for, and turns it into an instruction. This page will publish both, in that order, because the gap between them is where an approval process is either sound or not.

No agent team makes that judgement, and none of them will be described here as making it. What will be shown is the instruction a person wrote and the version that came back from it.

The workflow and the teams that will run it

One workflow, named specialist stages, and a person who stays responsible for the result at the end of it.

Your staff member keeps

  • The brief, and the decision about what each stage is being asked for.
  • The judgement at every stage: whether the result is right enough to build on.
  • Technical judgement: whether what is shown is buildable, compliant and correct.
  • What is put in front of a client, and when.

Drawing-to-Interior

Will read the elevation, section or sketch under discussion and produce the interior visual the client reacts to.

Lighting and Mood

Will show the scene that was already agreed under different light, leaving the contents of the room alone.

Client Review and Approval

The workflow this example belongs to, with its own inputs, outputs and stated limits.

Read the workflow this example runs in

Drawing-to-Interior

Will read the elevation, section or sketch under discussion and produce the interior visual the client reacts to.

Read this team's limits

Lighting and Mood

Will show the scene that was already agreed under different light, leaving the contents of the room alone.

Read this team's limits

What will come back

There is no result on this page. What follows is what the result will have to be published with when there is one.

There is no result on this page. The figure at the top is a diagram of the page's own structure, and the two frames above are placeholders; neither shows an output, and no claim on this site rests on any of them.

When the conversation is run, what gets published here is the revised version exactly as it arrives, beside the version it replaces, and the decision that follows it — including the case where the client does not accept the revision. A review example that ends in an approval every time is a review example that has been selected, and one of those is worth less to you than the honest one.

What will be kept, supplied, and checked

The most important section on the page, and the one that will be worth reading first when the example lands. The three columns below are what this example will have to account for.

Preserved from your source

  • Everything in the approved version that the client did not raise.
  • The camera position, the framing and the geometry of the room.
  • The fixed elements of the scene, and anything the conversation did not put in question.

Inferred by the agent team

  • How the change the client asked for reads across the rest of the scene.
  • Material character wherever the version under discussion left it unresolved.
  • How the light in the scene falls on anything that changed.

Must be reviewed by a person

  • Whether the revision answers what the client actually meant, which is a judgement no agent team makes.
  • Whether anything outside the point the client raised has moved.
  • Whether this version is the one that should go on record as the client's approval.

What this example will establish

Stated narrowly, so that it will still hold when the figures arrive. Today it holds nothing, because there are no figures.

That one review conversation can be shown end to end — the version sent, the reaction, the instruction a person wrote, the revision, and the decision — rather than as a before-and-after pair with the argument removed from between them.

That a revision can answer one point without disturbing what the client already agreed to, which is the property that makes a second round shorter than the first rather than longer.

None of that is established today. It is what the published example will be able to support, and nothing on this page supports it in the meantime.

What this example will not establish

Published at the same weight as the section above it, and true both before and after the run.

It will not establish dimensional accuracy. No dimension in a Studio visual is measured or verified.

It will not be construction documentation and it will not constitute technical or regulatory approval.

It will not establish a colour-calibrated match between a rendered material and a physical sample.

It will show one conversation on material Avisual selected. It will not establish how many rounds a review takes in your practice, or that it takes fewer of them.

Why this matters in an interior business

Tied to the process step, not to a number.

Approval rounds are expensive because most of each round is spent establishing what the client meant, not producing the visual. This example is being produced to show one conversation end to end, including the round that did not land, so that the step your process would actually be changing is the visible one.

Whether that changes anything in your studio is a judgement measured on your own work and your own clients. This page will not answer it, and no number for your business appears on it.

What Studio does not do

The limits are part of the product. Read them before you plan work around Studio.

  • No source and no result is published on this page yet. Every figure here is a placeholder that states what it will contain, and nothing on this page should be read as a result Studio has produced.
  • It will not establish dimensional accuracy. No dimension in a Studio visual is measured or verified.
  • It will not be construction documentation and it will not constitute technical or regulatory approval.
  • It will not establish a colour-calibrated match between a rendered material and a physical sample.
  • It will show one conversation on material Avisual selected. It will not establish how many rounds a review takes in your practice, or that it takes fewer of them.
  • An example shows a behaviour on the specific material it started from. It does not promise the same result on different material.
  • No Studio visual establishes dimensional accuracy, technical approval, or a colour-calibrated match to a physical product.
  • Studio is operated by your staff. Nothing on this page describes a tool handed to your customer to run on their own.

Choose your next step

Each route below produces something you can look at and judge.