Define what the image can and cannot demonstrate
A flood-resilience rendering communicates the spatial consequences of a design strategy; it does not prove that a building is safe from flooding. Decide whether the audience needs design coordination, a planning illustration or marketing imagery. A normal-day image and a specialist-defined flood-event scenario are different deliverables. Never imply that a waterline or a dry access route has been verified merely because it appears convincing in CGI.
Request levels and technical sources before modelling
Collect current topographic survey data, sections, finished-floor levels, civil drainage plans, landscape grading and the flood-risk strategy from the responsible specialists. Record the vertical datum, units, drawing revision and source for each relevant level. An elevation without a datum can put a threshold in the wrong place. Distinguish approved details from provisional flood barriers, vents, gates, pumps and landscape measures. Do not derive a supposed flood level from a photograph or a guessed river height.
Show raised thresholds and access gradients honestly
A raised lobby may be central to the strategy yet disappear when a camera is placed too high or foreground planting masks the plinth. Check finished floor, door sill, external steps, ramps and surrounding grades against coordinated sections. Include an annotated section where the perspective cannot reveal the difference in levels. If a temporary barrier is required under an operational plan, show it only in the relevant scenario and label the assumption. Its deployment and effectiveness need specialist confirmation.
Preserve drainage features in the landscape
Swales, rain gardens, retention areas and overland flow routes are not decorative flowerbeds. Model their edges, inlets, outlets and relative levels from civil and landscape information. Avoid adding planters, walls or mature trees that could obscure the intended route. Planting size and maintenance can change the appearance, so separate an illustrative mature landscape from the specified installation. See the landscape accuracy guide for a separate review of planting assumptions.
Separate normal operation from flood-event illustrations
Start with a normal-day view showing the actual architectural features without dramatic effects. If a flood-event image is needed, ask the responsible technical team for a defined scenario and approved water extent. A guessed water surface is not a flood model. Do not invent flow speed, event frequency, depth or performance claims. Label the event, assumptions and source date. Keep weather and lighting choices from implying a level of technical precision that the underlying data does not support.
Keep the surrounding streets and ground levels visible
A site may depend on connections beyond its boundary. Preserve relevant pavement gradients, road levels, neighbouring land and entrances where reliable data exists. Mark simplified context rather than silently flattening it for a cleaner composition. Emergency access or passability during a flood cannot be established by a perspective rendering. Those questions belong to the architect and appropriate specialists. A carefully chosen camera should reveal the critical level changes rather than crop them out.
Use a fixed camera for alternative designs
When comparing a revised flood wall, entrance plinth or landscape berm, use identical camera coordinates, lens, exposure, season and context geometry. Change only the design variable under review. A new camera angle can make a wall look shorter or conceal an awkward ramp. Pair the images with a plan and section identifying the observer position. The design-option comparison guide explains how to avoid visual bias.
Fictional example: a riverside residential entrance
Fictional illustrative example, not a real commission or engineering assessment. A concept apartment building has a raised lobby and a shallow planted depression in its forecourt. The first marketing draft depicts flat turf and a flush entry. The architect requests a corrected normal-day view and a section. No flood-event waterline is shown because no specialist scenario has been supplied.
| Item | Evidence | Visual decision |
|---|---|---|
| Lobby threshold | Architectural section and level datum | Restore raised plinth and steps |
| Accessible approach | Coordinated grading plan | Show actual route and gradient |
| Planted depression | Civil and landscape drawings | Model basin geometry, not flat lawn |
| Flood-event view | No approved scenario available | Do not fabricate a waterline |
Use captions that state the limits of the evidence
A public-facing caption should identify whether the image depicts ordinary conditions or a specialist-specified event. Mention approximate surrounding levels and provisional features where material. Avoid phrases such as “flood-proof” or “guaranteed dry”. Any performance statement must be reviewed by the responsible technical team. Keep approved captions with the exports so a sales brochure does not accidentally attach a stronger claim than the design evidence supports.
Keep sources, cameras and approvals traceable
Archive drawing revisions, datum, scenario sources, model version, camera ID, assumptions, approval owner and caption text. When a civil engineer changes levels or a landscape designer moves a swale, identify every affected rendering and replace obsolete campaign assets. The change-control guide describes a practical asset register. A visually attractive still is only evidence of one model revision, not a permanent statement about project performance.
Flood-resilience rendering sign-off checklist
- Purpose and audience are explicit.
- Current survey and coordinated drawings are recorded.
- Every relevant level has a documented vertical datum.
- Thresholds, steps and ramps match the design.
- Drainage features and ground gradients are not decorative guesses.
- Temporary barriers are labelled by their operational scenario.
- Adjacent access and approximate context are identified.
- Flood-event waterlines are shown only from approved specialist inputs.
- Option comparisons use fixed cameras.
- Captions avoid unsupported safety claims.
- Architect and specialists approve relevant statements.
- Model revisions and final exports remain traceable.
Architectural visualisation supports communication and coordination; it does not replace hydraulic analysis, regulatory review or the judgement of responsible professionals.
Need accurate visualisations for resilient architecture?
Share current sections, levels and the design questions your team needs to communicate. We can plan views with clear assumptions and accountable approvals.
Discuss a visualisation brief ↗