First, distinguish existing trees, designed planting and visual atmosphere.
Landscape is often the last layer added to a visualisation and the first one a viewer believes. A tree in the foreground may simply frame a view. A tree next to a terrace may imply privacy. A row of mature canopies along a boundary may look like a confirmed design feature. Those three jobs have different evidence requirements, even when the same 3D plant asset could perform them.
Start with three labels: existing and retained, proposed and specified, and illustrative or undecided. Existing vegetation should be located and sized from an appropriate survey or documented site observations. Proposed vegetation should follow the landscape architect's current drawing and schedule. Illustrative vegetation can communicate atmosphere, but must not be quietly promoted to a promise about species, screening or maturity.
Agree which landscape elements materially affect the architectural claim. A tree screening a ground-floor bedroom, a hedge dividing private gardens and a canopy shading a courtyard deserve closer review than a distant decorative shrub. The question is not whether the image looks green enough. It is which parts of the greenery the audience may reasonably treat as information.
Give the visualisation artist one authoritative planting pack.
A PDF mood board is useful for colour and character; it is not a planting plan. For a coordinated rendering, request the current landscape drawing with revision, site boundary, existing tree inventory where available, proposed planting zones, species or plant groups, intended sizes and any phasing notes. Provide the architectural model revision and a clear reference for terrain and finished levels.
Where exact species are not decided, write “ornamental multi-stem tree, species to be confirmed” instead of choosing a named cultivar solely because the 3D library happens to contain it. The landscape designer should approve botanical and spatial decisions; the visualisation artist should not accidentally become the project's planting consultant.
Use a simple status field for each visible element: confirmed, provisional, illustrative or excluded. Mark who can approve changes. A rendering artist can flag that a hedge intersects a gate or that a canopy blocks a sign; deciding to move the hedge belongs to the design team. If the model and planting plan disagree, log the conflict rather than resolving it invisibly in the scene.
Survey and approved existing-tree data describe what is on site. Current landscape design describes what is proposed. Architectural model and levels establish the built context. Visual references establish intended character. A marketing reference should never silently override a dimensioned drawing.
Scale the plants to the site and to the intended year.
A vegetation asset has at least three dimensions that matter: its current height, its crown or spread, and its position relative to the building. Library names such as “small tree” or “medium hedge” do not establish those dimensions. Compare the asset against a known architectural datum such as a door height, balcony parapet or storey level, then check the planting centre against the plan.
Decide whether the image represents planting at installation, after an agreed establishment period or as an aspirational mature landscape. These are different pictures. A mature canopy placed over a newly built terrace may make the space feel comfortable while concealing how exposed it will be at handover. When a future-growth scenario is shown, label it as such and avoid assigning a precise maturity year without supporting planting information.
Spacing also matters. Plants that overlap attractively in a composition may be impossible to place at the shown centres, or may crowd an entrance, cycle path or maintenance route. Check trunks, root-zone assumptions where documented, fences, drainage features and the clear width of pedestrian circulation. Do not infer that a visualisation proves a plant will thrive in a particular soil or climate.
Use species identity as design information, not decoration.
Species can affect silhouette, leaf density, habit, colour, seasonal behaviour and perceived scale. If the landscape specification names a species or cultivar, the chosen 3D asset should be checked against its general form. A broad, spreading canopy should not be replaced with a narrow columnar tree simply because the latter fits the camera better. If a precise match is unavailable, agree on a representative asset and document the substitution.
Check the most visible characteristics: evergreen or deciduous, approximate crown shape, branching pattern, foliage texture, flowering or fruiting only where relevant, and expected density at the depicted stage. Photorealism does not guarantee botanical accuracy. A convincing tree model can still be the wrong species, age or season.
For a concept-stage project, it may be more honest to show an indicative planting palette than a fully specified botanical inventory. Label the image accordingly. For a tender or approved landscape package, use the current schedule as the reference and record which details remain simplified. The goal is to avoid implying a level of design certainty that does not exist.
Make foliage, weather and the claimed season agree.
Seasonal mismatch is easy to miss in a warm colour grade. A bare deciduous tree beside a fully leafed neighbour, summer flowering in an otherwise late-autumn scene, or dense green ground cover under a winter sun can make the landscape internally inconsistent. Review the scene as a whole, not plant by plant.
Choose a season and intended condition in the brief. If the image is a general marketing illustration, use a plausible coherent palette and avoid a caption that claims an exact calendar day. If it claims a particular date or time, the vegetation state and solar setup need to be compatible with that claim. The sun-and-shadow accuracy guide explains the separate checks for true north, date, time zone and contextual shadows.
Also consider the difference between planting at completion and established landscape in the same season. A newly planted hedge is not automatically a continuous privacy screen. If the visual story depends on that screen, show the relevant growth assumption or explain that the planting is illustrative. Attractive autumn colour is a valid artistic choice; it should not stand in for a verified species specification.
Check what the greenery hides, reveals and shades.
Landscape changes how a building is read. A foreground tree can soften a façade, but it can also hide an entrance, obscure a required sightline or conceal a design feature the image was commissioned to explain. Review the view first with vegetation temporarily hidden, then with the approved planting visible. If the composition changes dramatically, decide whether that change is intended.
For residential marketing, test views from the pavement, garden, terrace and neighbouring edge as appropriate. A hedge shown at full height may imply privacy that the installation-stage planting cannot provide. A mature tree may imply summer shade but also change the perception of winter light. Do not use foliage as a convenient mask for unresolved architecture or awkward site conditions.
Shadow-casting vegetation needs its own status. Existing trees should be represented where they materially affect a time-specific image. Proposed trees may be relevant to a future scenario but should not be treated as current obstructions. For measured sunlight or daylight studies, specialist methodology and validated inputs take precedence over this visualisation checklist.
Coordinate planting with ground levels and hardscape.
Even a well-chosen plant looks false when it floats above paving, sinks into a retaining wall or grows through a terrace. Match the ground mesh to the current civil and landscape levels before distributing assets. Check transitions at thresholds, paths, kerbs, planting beds, ramps, walls and the building perimeter. A texture replacement cannot correct the wrong geometry.
Surface finishes need the same discipline as vegetation. Identify which zones are lawn, meadow, gravel, paving, mulch or planting bed, and whether their boundaries are fixed. A continuous lawn where the plan shows permeable paving may change the apparent accessibility and maintenance of the site. Avoid inventing decorative gravel bands or planting strips to hide modelling seams.
Close-up views deserve more detail than distant aerials: realistic edge thicknesses, sensible texture scale, contact shadows and consistent mowing or maintenance character. However, “neatly maintained” is an aesthetic direction, not evidence that the landscape is maintainable. Drainage, irrigation and long-term maintenance remain design responsibilities outside the scope of a rendering alone.
Approve landscape across the whole camera set.
One convincing hero view is not enough. A tree that frames the entrance beautifully from the street may block the building from the courtyard camera or collide with a balcony in a second view. Keep a stable planting scene shared across the approved cameras. Do not move a tree separately for each rendering unless the discrepancy is deliberate and disclosed.
Review the landscape at the actual delivery crops: full-resolution image, mobile hero, website gallery thumbnail and print crop where relevant. A clipped crown or missing hedge in a narrow mobile crop can change the story. Compare the same model revision across all images and note where illustrative foreground foliage has been added solely for composition.
When a camera is based on a real site photograph, landscape placement must also respect the photographed context. Follow the photomontage camera-matching guide for perspective, occlusion and source-photo records. When the camera is fully virtual, still keep eye height and lens choice consistent with the architectural purpose.
Make the image caption as precise as the design status.
A caption need not reproduce a full planting schedule. It should, however, avoid claiming that provisional landscape is an approved built outcome. A useful concise formulation might be “Architectural visualisation; planting species, growth and seasonal appearance are illustrative.” If a future-growth scenario is central to the picture, say so explicitly.
Do not use the same image as both an installation-stage representation and a mature-landscape promise. Where a marketing campaign needs both, prepare distinct, labelled variants. Keep the original approval record so a later design revision can be checked against the published image, not against someone's memory of what was agreed.
For developers, the caption and sales materials should agree with the current project information. If a boundary hedge is removed or a planting zone changes after publication, include the affected images in the rendering change-control workflow. Replacing a tree asset in a 3D scene is not the end of the task if an old picture is still on the public website.
Fictional example: a courtyard image with an unresolved hedge.
The following record is fictional. It illustrates a review method, not an actual client, commissioned project, planting design or measured result. Imagine a small residential courtyard whose sales image shows a dense boundary hedge and three established trees. The current landscape plan specifies the hedge zone but does not confirm its final species or installation height.
| Element | Known input | Visualisation decision | Approval needed |
|---|---|---|---|
| Boundary hedge | Location confirmed; height and species open | Use an indicative, clearly qualified screen; do not promise full privacy | Landscape architect |
| Three courtyard trees | Centres on latest plan; crown size provisional | Use consistent scale across all views and label future-growth assumptions | Design team |
| Terrace edge | Level and paving boundary confirmed | Model geometry from the issued drawing, not from a reference photograph | Architect / landscape lead |
| Sunny seating area | Marketing scene, no date-specific solar study | Present as atmospheric illustration, not proof of sunshine duration | Project owner |
The critical decision is not whether the hedge looks realistic. It is whether a buyer might reasonably infer that a dense privacy screen will exist on handover day. If that remains undecided, the team can revise the depiction or qualify it. Either choice is better than silently using a fully mature asset because it makes the image more attractive.
This fictional example is a documentation template, not a claim about any Atmosferi project.
Landscape sign-off checklist before publishing.
- Existing, proposed and illustrative planting are distinguished in the brief.
- The source planting plan, tree inventory and model revisions are recorded where available.
- Ground levels, terrace edges and planting centres agree with the approved drawings.
- Plant height, crown spread and hedge density reflect the stated installation or growth stage.
- Species-specific claims are checked by the responsible landscape designer.
- Season, foliage state, lighting and any date-specific caption are mutually consistent.
- Planting does not conceal an entrance, path, neighbouring context or unresolved design change.
- Time-specific shadows use the correct contextual geometry and documented assumptions.
- Surface materials, edges and texture scales are consistent across the camera set.
- All views share the same approved planting positions unless a difference is explicitly documented.
- Mobile and print crops retain important planting context and disclosures.
- Provisional or future-growth landscape is clearly qualified in the published caption.
- One owner has approved the planting depiction against the current design issue.
- Final exports and source-scene versions are traceable for later updates.
Architectural visualisation is a communication tool, not a substitute for a planting design, arboricultural survey, ecological assessment or specialist sunlight study. The useful standard is simple: make the scene visually coherent, technically reviewable and honest about what is known.