When do we need to submit a model for audit under ISO 19650?

This article explains when BIM models are submitted for audit on an ISO 19650 project, the typical milestones where model checks happen, and how Plannerly supports each step - from clear information requirements through to automated model verification.

TL;DR: ISO 19650 does not give one fixed date to "submit a model for audit". You submit models at agreed information exchange milestones (EIR, MIDP, TIDP), project gateways, and when certification bodies request project evidence. Plannerly helps make each of these submissions clear, traceable and audit ready.
Want a deeper ISO 19650 overview first?
Read the introduction to ISO 19650 and information management here: What is ISO 19650?

1. ISO 19650 basics - what does it say about model submission?

ISO 19650 defines a repeatable process for managing information, not a single calendar date to upload your BIM model. Instead, it defines two key steps where models are effectively "audited":

  • Submit for internal authorization - the delivery team checks and authorizes the information model before it is shared outside the delivery team.
  • Submit for external acceptance - the appointing party reviews and accepts the information model at a defined information exchange milestone.

These authorization and acceptance events are what many teams refer to as model audits. They happen at project-specific milestones that are defined in:

  • Exchange Information Requirements (EIR)
  • Master Information Delivery Plan (MIDP)
  • Task Information Delivery Plans (TIDPs)

2. Project milestones - when do we usually submit models for audit?

On a typical ISO 19650-aligned project, BIM model audits happen at predictable points. Your EIR and MIDP should clearly list these information exchange milestones. Common examples:

2.1 End of design or delivery stages

  • Concept design
  • Schematic design
  • Detailed design
  • Construction stages

2.2 Coordination gateways

  • Prior to clash detection sessions
  • Before issuing a federated model to the wider team
  • Before using the model for tender quantities or pricing

2.3 Client decision points

  • Design freeze or concept sign-off
  • Budget or funding approvals
  • Tender issue or award decisions

2.4 Handover and Asset Information Model (AIM)

Before final handover, models are checked against the Asset Information Requirements (AIR). The result becomes the Asset Information Model used for operations and maintenance.

5. Summary - when to submit a BIM model for audit

  • An information exchange milestone in your EIR or MIDP is due.
  • A project gateway or decision point requires trusted model information.
  • A handover or AIM delivery is required against the AIR.
  • An ISO 19650 certification body requests project evidence for Stage 2, surveillance or recertification audits.