← Back to Blog

Landscape Detail in Site Plan Rendering

Site plan rendering showing planted courtyards, street trees and hardscape paving around a group of buildings

Landscape often occupies more of a site plan rendering than the buildings do, so it needs specification rather than assumption. Supply the hardscape layout, planting zones, tree species or at least character and caliper, and the intended maturity at the moment the image depicts. The single most consequential choice is maturity: showing twenty year canopy on a project that will be planted with young stock is the credibility failure we see most often in this category, and reviewers who know the site will catch it.

When a site plan comes to us without landscape direction, we still have to draw something, and that something becomes our invention rather than the landscape architect's design. On any site with real open space, this is the input worth resolving before production starts. It is a recurring theme in site plan rendering scopes.

What actually needs specifying

Hardscape. Paving extents, materials and patterns for walks, plazas, drives and parking. This is geometry and it is not something to guess at, because it defines circulation.

Planting zones. Where lawn, groundcover, shrub massing, ornamental planting and tree canopy go. Zones are enough. Every plant does not need to be named.

Trees. The item that most affects the image. Species or at minimum character, deciduous or evergreen, columnar or spreading, plus planting size. Street trees and parking lot trees are frequently required by ordinance in specific counts and sizes, and the image should match the requirement.

Season and maturity. Which season the image depicts and how grown in the planting is meant to look.

The maturity question

Two honest options exist. Depict planting at installation size, which is accurate at delivery and makes the site look sparse. Or depict it at a stated point of growth, commonly a few years in, which shows design intent and looks better.

Either is defensible. What is not defensible is mature canopy shown without qualification on a project whose landscape budget buys young stock. In approval contexts we prefer stating the assumption directly in the caption, because a reviewer who raises it themselves will discount everything else in the package.

How much detail is enough

  • Overall aerial. Massing level. Correct canopy footprint, correct planting character, correct hardscape. Individual leaves are not visible and not useful.
  • Eye level view. Considerably more, because planting is in the foreground at human distance. Trunk character, understory and ground condition all read.
  • Amenity or courtyard view. The highest detail on the project, since the landscape is the subject rather than the setting.

Detail costs production time, so it is worth spending it where the camera is close and saving it where it is not.

Where landscape breaks a rendering

Planting that does not survive the climate, which local reviewers notice immediately. Trees placed where utilities, drives or fire access actually run. Canopy that hides the building the image was commissioned to show. A season that contradicts the rest of the package, deciduous trees in full leaf in one view and bare in another.

The camera choice that determines how much of this matters is covered in aerial versus eye level site plan views, and the ground the planting sits on comes from survey data for site plan rendering. Project stage context is on new construction renderings.

Send us your landscape plan, or tell us there is not one yet and we will scope the planting detail to the views that need it.