A larger share of architectural risk than ever now resides in exported information.

The weak link is often not the model itself but what leaves it: room data sheets, quantity take-offs, IFCs, area schedules, carbon inputs, and coordination files. These outputs go into pricing, procurement, permit review, and technical coordination. Once circulated, they can carry more authority in practice than they were originally intended to have.

Most offices scrutinise geometry, drawings, and discipline content more thoroughly than they do the purpose and status of exported data. A technically accurate model can still create risks if a secondary output is reused as if it were fully verified and ready for another purpose.

The key takeaway is straightforward: tighten control over four aspects- what leaves the office, its purpose, who checked it, and where the reliance limit is documented.

Three forces are driving this problem forward.

First, model-based delivery is now common enough that digital outputs quickly move between teams, consultants, contractors, clients, and authorities.

Second, contract language has had to evolve. In the UK, the CIC BIM Protocol was established to define how model-based information should be delivered and managed throughout project stages. Sweden is now facing similar pressure through Boverket’s BIM initiatives and the contractual discussions around AB 25.

Third, automated compliance checking makes it harder to conceal poor information. Software increasingly tests BIM data against permit rules, codes, and project requirements, enhancing the importance of structured, traceable, and verifiable data.

In summary, these forces place more project importance on exported information. The model itself may remain unchanged, but the risk arises when an output is used for an unintended purpose.

This week’s market signals are tied to spikes in online search, reflecting what architects are currently grappling with.

Online search interest in architect liability for building safety certification, along with rising professional indemnity costs, indicates that this issue is already a commercial concern rather than just a theoretical one. Firms are exploring where responsibility lies once digital information takes on operational significance.

A common worry is why BIM models fail to meet building code compliance: models are often pushed into review and validation processes, where missing or poorly organised data can quickly become costly.

Interest in embodied carbon calculation within BIM models and lifecycle carbon assessments for building permits indicates a similar trend. Environmental data is becoming more integrated into permitting and compliance processes, increasing the importance of accurate information management.

Research on structural safety under performance-based codes indicates that an increasing number of decisions now rely on well-defined assumptions, recorded parameters, and traceable information trails.

The pressure on firms is coming from the same direction across liability, code checking, carbon reporting, and insurance: model-derived information is moving further through the project than many internal controls were designed to handle. That has practical consequences. Offices need to enforce stronger discipline around information release, not just improve modelling. A firm may know who checked the drawing set but still lack clear answers to four more critical questions.

What exactly left the office? What was it issued for? Who verified the high-risk fields? How far was that reliance allowed to travel?

This week’s Deep Dive explores that problem through contracts, BIM governance, and internal QA. The focus is narrow and practical: the point where information leaves the model and begins doing work that the office never clearly assigned to it.

[Read the full analysis: When model data outruns the contract]

See you next week!

-Johan

[email protected]

architectonic.io