A quote for twenty product renders says little about whether the images will cover the decisions your audience needs to make. Several files may show almost the same configuration, while a critical size or mounting view is absent. Define the coverage before comparing image counts.
For a construction-product visualisation, the useful unit is a view of an identified configuration serving a stated purpose. File quantity follows from that requirement; it should not substitute for it.
Build a small coverage map
List the approved configurations down one side and the necessary views across the other. Mark which combinations genuinely need an image. A general overview, a connection detail and an installed-context view may each have a different role.
A simple working map might look like this:
| Configuration | Recognition view | Connection detail | Installed context |
|---|---|---|---|
| Standard unit | Required | Required | Shared context may suffice |
| Alternate body size | Required | Confirm whether different | Required if relationship changes |
| Finish-only option | Required if visibly distinct | Usually not repeated without a reason | Consider whether needed |
These are illustrative planning categories, not rules for any product. The subject owner should decide where one view genuinely represents several configurations and where sharing would hide a material difference.
Epic's variant documentation separates variant sets from the properties they control. An option count is therefore not the same thing as a required output count.
Identify shared work without assuming free outputs
Ask the supplier which scene preparation can be reused and which images require new geometry, framing or review. A finish substitution may reuse much of a setup, while a different body shape may invalidate the camera or reveal an unsupported side.
Avoid assuming that one prepared model makes every possible view costless. Conversely, do not pay for independent preparation where an agreed shared scene would meet the task. The proposal should explain its actual reuse assumptions.
Keep output formats separate from visual coverage. A second crop or file size may be a necessary deliverable, but it does not automatically add another product view. Make the distinction visible so both parties understand what the image count includes.
A hypothetical catalogue extension
Imagine a supplier adding three approved product configurations to a construction film and a related presentation. The initial request asks for six renders of each. During planning, the buyer discovers that several rear views would be identical, while one configuration needs a unique mounting detail that none of the six generic angles reveals.
The coverage map replaces redundant views with the necessary detail and identifies shared context images honestly. This invented example makes no claim about a lower price; it shows how the same conversation can produce a more useful deliverable set.
Accept against the map
At review, check configuration identity, view purpose and completeness of the required cells. A folder containing the expected number of files can still omit a task or duplicate the wrong state. Use recognisable names and a contact sheet to make that check practical.
If a new configuration is introduced, add it to the map before asking for more outputs. Bring the coverage map to Live Images to discuss whether the film and associated visual assets are suitable, and confirm the specialist preparation and delivery scope rather than buying an unexplained bundle of renders.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.