For most design firms, the building information model has quietly become the center of the work product. It coordinates disciplines, drives documentation, and feeds fabrication and facilities management downstream. It is also, increasingly, something a contractor, a subcontractor, or a future owner relies on directly — and that reliance is where the professional liability conversation now lives. A model is not merely a faster way to draw. It is a representation others act on, and the law of professional liability has always followed reliance.
What Level of Development Actually Means
The level-of-development framework, codified in the BIMForum LOD Specification, is the industry's attempt to make model reliance precise. It grades each model element — not the model as a whole — on how far its geometry and information can be trusted. LOD 100 is conceptual; LOD 200 is approximate geometry; LOD 300 is precise geometry with accurate dimensions; LOD 350 adds the interfaces and connections needed for coordination; LOD 400 is detailed enough for fabrication; and LOD 500 reflects verified as-built conditions. The distinction that matters is that LOD describes reliability, not visual detail. An element can look finished on screen and still carry an LOD that says, in effect, do not scale this yet.
The AIA's digital practice documents translate that framework into contract language. E203, the Building Information Modeling and Digital Data Exhibit, establishes whether and how BIM will be used; G201 sets the digital data protocol; and G202, the Project BIM Protocol, assigns a model element author and an authorized level of development to each element at each project phase. Read together, they answer two questions that decide liability: who authored this element, and how far is anyone entitled to rely on it. When those answers are documented, a dispute has a map. When they are not, every party argues from its own assumption.
Where the Liability Opens
The exposure tends to appear in the space between what a model shows and what it promises. A contractor pulls dimensions off an element modeled at LOD 200 and builds to them as though it were LOD 400. A trade coordinates against a federated model and a clash that should have been caught in the model surfaces in the field. A question arises, late, about whether the model or the drawings govern when the two disagree. In each case the design firm's standard of care is measured against what it represented — and if the model is a contract document, errors carried in it are the firm's errors, reliance on them was foreseeable, and the old comfort that "the drawings control" may not survive a project that was run from the model.
Coverage does not always move in lockstep with that exposure. Most architects and engineers professional liability forms respond to a negligent act, error, or omission in professional services, and model preparation is squarely professional services. But firms should read the fine print for electronic-data and technology exclusions, and should confirm that a third party's reliance on a shared electronic model is treated as a covered professional service rather than carved into a cyber or media silo. The point is not to assume a gap, but to confirm there is none before a claim tests the question. A policy written with drawings and specifications in mind is not always read, by its own terms, to extend to a model that a dozen downstream parties opened and relied on.
Managing the Exposure
The discipline is almost entirely contractual and procedural. Define the authorized level of development for each element and phase in the BIM execution plan, and tie it to the G202 protocol rather than to an informal understanding. State the order of precedence between the model and the drawings so a conflict has an answer. Disclaim reliance beyond the stated LOD in plain language, so a downstream party cannot treat a coordination model as fabrication-ready. Preserve the model as an instrument of service with defined ownership and license terms. And coordinate the whole arrangement with the professional liability carrier, because the cleanest contract still benefits from a policy that is known to respond to it.
This is the judgment our 4-Step Strategic Process is built to support. Strategic Discovery maps how the firm actually uses BIM and who relies on its models downstream. Risk Assessment tests the contract language, the LOD assignments, and the policy's treatment of electronic deliverables against the way the project is really run. Solution Design closes the reliance and precedence gaps and confirms the coverage follows the exposure. Ongoing Optimization keeps the protocols and the policy aligned as the firm's technology and project mix evolve. The model has become the firm's most valuable instrument; the professional liability around it should be built with the same care the model is.
— Ryan Mefford, President & Risk Advisor