A 3D Visualisation Brief: From Supplied Model to Usable Images

“We already have the 3D model” is a useful starting point, but it does not describe a finished visualisation. The model may contain the right shape while lacking the surfaces, lighting, camera views and output settings needed for the intended image.

A clear brief separates those jobs. It also says which decisions are settled and which still need approval. This guide uses a hypothetical furniture project to show how that distinction prevents a beautiful image from answering the wrong question.

Model, render and visualisation: specify the deliverable

A model describes the object in three-dimensional form. Rendering produces an image from a scene using a particular camera and rendering setup. “Visualisation” is often used more broadly for the work that makes a design understandable: preparing the model, choosing a view, assigning materials, lighting the scene and presenting the result.

Those terms are useful, but they are not a substitute for a written scope. Ask whether the delivery includes a still image, an animation, an interactive presentation or an editable scene. A JPEG of a chair is not the chair’s source model; a source model is not necessarily ready for manufacturing or 3D printing.

Start with the object, not a mood board alone

Suppose a manufacturer wants four images of a new dining chair. A convincing brief would identify the approved drawing revision, overall dimensions, intended finishes and any supplied geometry. It would distinguish the real product from optional props used to show its setting.

Keep two kinds of reference separate. A technical drawing constrains the shape. A photograph of a warm dining room suggests atmosphere. If the atmosphere reference has a different chair, its proportions should not quietly override the approved product drawing.

List gaps explicitly. “Underside fixing not yet confirmed” is more useful than an invented fixing that later appears in a close-up. Decide whether the gap can remain outside the chosen views or must be resolved before modelling continues.

Approve decisions in an order that makes changes visible

  1. Geometry check: inspect proportions and important details in a plain view. A neutral surface makes a wrong leg angle easier to spot than a dramatic final image.
  2. Camera check: choose the views and crop. Confirm that each image answers a different question, such as overall form, back support or an assembly detail.
  3. Material check: agree the intended finish using suitable references. Treat colour, texture scale and surface response as related but different decisions.
  4. Lighting and composition check: review whether the product remains understandable in the selected setting.
  5. Output check: inspect the agreed final files at their actual use size and verify the delivery list.

This is a suggested review sequence, not a universal studio procedure. Its purpose is to make approvals specific. “Looks good” is hard to use later; “chair proportions and camera A approved, fabric colour still provisional” records what was actually decided.

Four pictures should do four jobs

A front view, three-quarter view, detail and room scene can be useful together if each reveals something different. Four nearly identical angles may add less information. Before requesting another view, write the question that it should answer.

The Blender camera documentation explains perspective and orthographic projection. They represent depth differently. Choose the projection for the task, and do not present an attractive perspective image as a dimensioned technical drawing.

Compare scope before comparing quotes

A quotation should state which supplied assets can be reused, how much new modelling is needed, the number of views, the level of environmental detail, the revision process and the final formats. An inexpensive first image can become a poor comparison if necessary views or source-file delivery were excluded.

Consider two hypothetical revisions. Changing a background colour within an approved scene and replacing the chair’s entire frame are not equivalent tasks. Agree how a change to the underlying design will be handled after an earlier stage has been approved. This guide does not assign market prices or promise a particular turnaround.

Deliver a package that can be used

Give files descriptive names that identify the product, view, finish and revision. Include agreed pixel dimensions, colour/output requirements and any transparent-background version. If an editable scene is part of the contract, clarify the included assets, dependencies and rights rather than assuming that image delivery includes them.

The resolution guide explains why “300 dpi” alone does not specify a render. For surfaces, see materials and textures. For product-image selection, use the packshot planning guide.

A final review against the brief

Check the approved drawing revision, visible dimensions and features, finish labels, camera list, output files and unresolved assumptions. Look for misleading props or views that conceal a relevant product feature. Verify that an image labelled “final” is the version actually supplied for publication.

A good handoff makes the next action straightforward: the designer can place the image, the product owner can identify the approved version and a future editor can understand what the visual represents. That is a more useful definition of completion than realism alone.

Historical context and verification

This independently written guide revisits the topic of the former studio’s article. It is not a claim to have carried out its projects or to offer its services. Historical source: original archived article.