Short answer: building information modeling can make the intent, responsibility, and interfaces of masonry moisture details explicit before a wall is built. That is genuinely valuable, because a coordinated moisture detail can make interfaces, intent, and responsibility explicit. But a model is a coordination tool, not a guarantee: it does not, by itself, make a wall watertight in the field.
What this reference is (and is not)
This page is a new coordination reference, written for this publication. It is not an official report of the former Building Information Modeling for Masonry (BIM-M) initiative, and it does not restore or republish that program’s historical documents. Where those historical downloadable reports are concerned, we track them separately and explain their status on the historical resource library page rather than rehosting files here.
The aim is narrow and practical: to connect the moisture guidance on this site to the coordination questions a project team can answer with a model, using the flashing detail as the worked example.
What BIM coordination adds
The National BIM Standard—United States describes its purpose as advancing the whole life cycle of the built environment by organizing and classifying electronic object data, so that owners, designers, suppliers, constructors, and facility managers can communicate through a shared structure. Applied to masonry moisture details, that shared structure is the point: it can make explicit what the detail is, who is responsible for each part, and how it meets the systems around it. A drained cavity wall, for instance, only works if flashing, weeps, and end dams form one continuous path — a classic interface problem that a coordinated model surfaces early.
A conceptual detail schedule
The table below is an illustrative, generic way to structure a masonry moisture detail in coordination — not a project specification and not tied to any product or dimension.
| Element | Coordination intent | Interface to confirm |
|---|---|---|
| Base flashing | Continuous collection surface | Laps, terminations, tie-in to backup |
| Weep openings | Drainage outlet above flashing | Kept open; located at collection line |
| End dams | Stop water at flashing ends | Turn-ups at openings and terminations |
| Discharge | Water leaves the assembly | Outward path clear of obstruction |
| Responsibility | Ownership of each part is named | No gap between trades at the interface |
Coordination checkpoints
- Intent is recorded. The detail’s purpose — a continuous collect-and-discharge path — is captured, not assumed.
- Responsibility is assigned. Each part of the path has a named owner, so nothing falls through the gap between trades.
- Discharge is verified. Collected water has a clear, unobstructed way out of the assembly.
- Field inspection is planned. The model points to what must actually be checked on site — laps sealed, weeps clear, end dams formed.
Limits
A model organizes information and communication; it does not pour, lap, or seal anything. Coordination reduces the chance of an interface being missed, but the wall is only as good as its construction and inspection. Treat this reference as a way to ask better questions before building — then verify the real detail, as described in masonry wall flashing, on the actual job.
Sources
Primary technical and preservation sources consulted for this article. Each was read at the URL below and checked on 2026-09-07. Links open the publishers' own pages; listing a source is not an endorsement of any product referenced there.
- National BIM Standard — United States, Version 4 (NBIMS-US V4) — National Institute of Building Sciences. https://nibs.org/nbims/v4/
- Flashing Strategies for Concrete Masonry Walls (TEK 19-04A) — Concrete Masonry & Hardscapes Association. https://www.cmha.org/resource/tek-19-04a/