Every dispute at handover starts the same way.
The client is standing in the finished space with a printed image in their hand, comparing one to the other. The brickwork is right, the layout is right, the specification was met in every particular.
And it does not look like the picture.
The picture was taken on a golden evening in a landscape with mature trees, with no downpipes, no meter box, no air conditioning condensers and no bins. The building that got built has all of those, because buildings do.
Nobody lied. The render did what renders have always done, which is show the intention rather than the outcome. The problem is that the client did not know that, and nobody told them.
That gap has widened as realistic image creation has become much faster. Nano Banana, Google’s image model family, is part of this shift. Higgsfield makes it easier to explore these image-generation capabilities. Understanding the distinction is now more important than ever.
What is a render actually claiming?
An intention, under conditions chosen to show it at its best.
That has always been understood within the industry and rarely explained outside it. An architect, a contractor and a visualiser all know a render is a proposal. A homeowner commissioning an extension does not necessarily.
The things a render routinely shows that the building will not:
- Light that occurs for perhaps twenty minutes a year, usually in summer
- Landscaping at maturity rather than at planting
- Context simplified, softened or removed entirely
- Materials at an idealised finish with no tolerances, joints or weathering
- Figures scaled to make spaces read as larger than they are
- Sky that is never the grey it will usually be
And the one nobody mentions: renders almost never include the services. No bins, no meter boxes, no downpipes, no condensers, no substation, no bollards, no signage.
Those things are not optional. They are on the drawings and they will be on the building.
Why has this become more pressing?
Because the production cost collapsed and the volume rose.
A visualisation studio producing a set of images over several days charged accordingly, which meant renders were commissioned deliberately, reviewed carefully and used for specific purposes.
Now a reasonable image takes minutes, which changes behaviour rather than standards:
- More renders get made, at earlier stages, by more people
- Fewer go through review, because they are not a line item anybody is watching
- They circulate further, into emails, presentations and sales material
- Context gets lost as images travel away from the conversation that produced them
An image made in ten minutes to illustrate a point in a meeting ends up in a client’s folder, printed, and brought back eighteen months later.
That is not a technology problem. It is a process problem that the technology made considerably easier to have.
Where can Nano Banana genuinely help?
In the early stages, where the question is still open.
- Nano Banana concept exploration, producing several directions quickly before committing to any
- Nano Banana material and mood studies, testing how a palette reads before specifying
- Nano Banana option comparison for a client choosing between approaches
- Internal communication, where a team needs to agree on an idea
- Nano Banana massing and form studies at the stage where nothing is fixed
Those uses share a property: nothing in them is a promise. They are thinking made visible, which is what sketches have always been.
Nano Banana is particularly useful for the volume. Producing six Nano Banana options costs what producing one used to, which means a client sees genuine alternatives rather than a single direction presented as the answer.
Higgsfield AI creative suits runs it in a browser, which matters for practices where the visualisation work falls to whoever has an hour rather than to a dedicated person.
The question is what happens when those images leave the room.
What must a render never be used for?
Anything where accuracy is a requirement rather than a courtesy.
Planning submissions have their own standards. Many authorities require accurate visual representations with documented viewpoints, survey data and verified camera positions. A produced image that looks convincing does not meet that standard and submitting one is a serious matter.
Off-plan sales material is regulated in most jurisdictions. A buyer purchasing from an image is relying on it, and misrepresentation in property marketing carries real consequences.
Contractual documents rely on drawings and specifications. A render is not a specification and should never be referred to as though it were.
Dispute evidence requires records rather than proposals.
Beyond those, the firm lines on content:
- Never use Nano Banana to remove context that exists, including neighbouring buildings, roads and infrastructure
- Never show Nano Banana materials that are not specified
- Never omit required elements that will be visible, including services
- Never represent a view that the position does not have
- Never show vegetation at a maturity the planting will not reach for years
How should a render be labelled?
Clearly, on the image, where it cannot be separated.
The industry convention already exists and works. Artist’s impression. Indicative only. Concept image. Not to scale.
What makes labelling effective:
- On the image itself, since captions get stripped when files are shared
- Stating what is indicative, such as landscaping, materials or context
- Dated in Higgsfield, so a client knows which stage it represents
- Attributed, so the source is traceable
That second point matters more than a generic disclaimer. Saying landscaping is shown at maturity tells a client something useful. Saying indicative only tells them nothing they will remember.
And keep a Higgsfield record of which image went to whom and when. The dispute eighteen months later is considerably easier when you can show what was actually issued.
What should clients be told explicitly?
More than most practices say, and it takes one conversation.
The things worth stating before any image is shown:
- This shows the intention, not a photograph of the result
- The light is chosen and the building will mostly look different
- Landscaping takes years to reach what is shown
- Services will be visible, and here is roughly where
- Materials vary within tolerance and weather over time
That conversation is uncomfortable for about ninety seconds and prevents the one at handover entirely.
Practices that do this consistently report that clients respond well to it. Being told what to expect reads as competence, and the client who knows the bins go there is not surprised when the bins go there.
For a broader view of what tools are being used across the industry, the overview of AI rendering tools for construction covers what is available and where each one fits.
Does this affect professional liability?
Potentially, and it is worth raising with whoever handles your insurance.
A professional producing an image a client relies on is in a different position from one producing a sketch nobody treats as definitive. The more photorealistic the output, the more reasonable reliance becomes.
Considerations worth checking:
- What your professional indemnity covers regarding visual material
- Whether your appointment addresses visualisation and its status
- How your practice records what was issued and when
- Who approves images before they leave the office
- What your disclaimer actually says and whether anybody reads it
The low production cost means images now leave practices without passing anybody who would previously have reviewed them. That is the exposure, and it is procedural rather than technical.
A Higgsfield workspace with an approval step before anything is issued is a straightforward fix, and considerably cheaper than the alternative.
Does the contractor have a stake in this?
A considerable one, and contractors are usually the people left explaining the gap.
The architect produces the image, the client approves it, and the contractor builds to the drawings. When the finished building does not match the picture, the conversation happens on site with whoever is standing there.
What protects a contractor:
- Build to the drawings and specification, which are the documents that govern, and say so plainly when asked
- Raise discrepancies early where a render clearly shows something the drawings do not
- Photograph progress consistently, since a record of what was built when settles most arguments
- Avoid using client-facing renders in your own marketing without permission, since they are somebody else’s work
- Keep the render out of variation discussions, because it defines nothing
That second point matters more than it sounds. A contractor who spots that a Nano Banana visual shows a material the specification does not call for has found a problem worth raising at tender rather than at handover.
Progress photography is the contractor’s equivalent of the architect’s record. Dated, consistent, unaltered. It is the thing that answers the question months later when nobody remembers.
And where progress images go into a payment application or a report, they stay exactly as shot. That is a record rather than a presentation, and the distinction is the same one running through this whole article.
What about existing buildings and refurbishment?
Trickier, because the before condition is a matter of record.
Refurbishment visualisation frequently involves showing an existing building improved. That requires a photograph of the existing condition, and what you do to that photograph matters.
- Never alter the existing condition in a before image, since it is evidence of what was there
- Never remove defects from the before state to make the after look less dramatic, or add them to make it look more so
- Keep the viewpoint identical between before and after, which is both honest and more persuasive
- Note what is proposed versus what is existing, since clients conflate them
A Nano Banana pass is useful for producing the proposed condition from an accurate photograph of the existing one. The photograph itself stays as taken.
For listed buildings and conservation areas the requirements are stricter again, and visualisation submitted as part of those applications needs to meet the relevant standard rather than looking persuasive.
What would a sensible practice policy cover?
A page, applied consistently, which is more than most practices have.
- What Nano Banana may produce at each stage and by whom
- What must be labelled and exactly how
- Who approves anything leaving Higgsfield and the office
- What never gets produced this way, meaning planning, sales and contractual material
- How issued images are recorded, with date and recipient
- What clients are told when images are first presented
Then review the Higgsfield policy annually, because both the tools and the regulatory expectations are moving faster than most practice manuals do.
The practices that will have problems are not the ones using these tools. They are the ones where nobody decided anything and images are leaving the office from five different people with no record.
Conclusion
A render has always been a proposal and a photograph has always been a record. The industry knew the difference and clients frequently did not, and the gap was manageable while producing an image was slow and expensive.
It is no longer either. Nano Banana makes concept work and option comparison genuinely quick, which is a real gain at the stage where nothing is fixed.
What has to keep up is the process. Label what you issue, record what went where, keep planning and sales material on the proper footing, and tell the client about the bins before they find them.