When do we need to submit a model for audit under 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

Models are usually submitted at the end of each project stage:

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

At these points, the model is checked against the agreed Level of Information Need and stage-specific requirements before it is authorized and accepted.

2.2 Coordination gateways

When a model will be used as a reference for other disciplines or for multidisciplinary coordination, a review is normally required before it is shared. For example:

• 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

Models are often formally reviewed when the appointing party must make important decisions, such as:

• 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.

3. ISO 19650 certification audits - when are models reviewed?

If your organization goes for ISO 19650 certification with a third-party body, your models are also reviewed as evidence of how you apply the standard in real projects.

• Stage 1 audit - mainly head office: policies, procedures, templates, CDE setup.
• Stage 2 audit - project-based: the auditor looks at a live or recent project including models and information records.
• Ongoing surveillance audits - periodic sampling of projects and models to confirm continued compliance.
• Recertification audits - every few years, including project evidence and model reviews again.

The timing and choice of projects are agreed in your audit plan with the certification body.

4. How Plannerly supports the full ISO 19650 audit lifecycle

The sections below describe typical problems teams face at each step and how Plannerly helps turn ISO 19650 theory into a practical, auditable workflow.

4.1 Defining clear information requirements (OIR, AIR, PIR, EIR)

Common problem: Projects start with vague or inconsistent information requirements. Later, nobody agrees what "good enough" looks like when the model is audited.

How Plannerly helps:

• Provides structured templates for OIR, AIR, EIR, BEP and other ISO 19650 documents.
  Learn more: What is ISO 19650?
• Supports consistent information requirement definitions across projects so every model audit is against clear criteria.
  Training library: Learn ISO 19650
• Keeps full version history, so you can see exactly which requirements applied at each stage.

4.2 Agreeing requirements and creating a true contract

Common problem: Requirements are "approved" in email threads and static PDFs. Months later, nobody can see which version was actually agreed when the model is checked.

How Plannerly helps:

• Turns requirements and BEPs into live collaborative documents, not scattered PDFs.
  Product overview: https://plannerly.com/
• Supports e-signature workflows so agreements become a real contract, with clear approval records.
• Tracks who approved what and when, providing strong evidence at audit time.

4.3 Translating requirements into delivery plans (MIDP / TIDP)

Common problem: MIDPs and TIDPs are created in spreadsheets that quickly go out of date, making it hard to show who was responsible for each deliverable at each stage.

How Plannerly helps:

• Uses the Scope module to break requirements into clear tasks and work packages.
• Generates a structured MIDP/TIDP directly from the agreed scope, reducing errors.
• Connects tasks to responsible parties and milestones, making audit responsibilities transparent.
  Learn more about Plannerly workflows: Learn ISO 19650

4.4 Uploading, versioning and submitting model deliverables

Common problem: Models and PDFs are stored in multiple locations, with inconsistent naming and no single source of truth. When an audit or handover comes, nobody is quite sure which file is the "real" deliverable.

How Plannerly helps:

• Provides a central File Manager where models and documents are uploaded, tagged and permissioned.
  Product overview: https://plannerly.com/
• Links files directly to specific tasks and milestones so each submission is clearly documented.
• Supports ACC and other CDE integrations for smoother model synchronization.

4.5 Automating model verification and compliance checking

Common problem: Manually checking models for naming conventions, parameters, LOI, COBie or IDS rules is slow, inconsistent and difficult to prove at audit time.

How Plannerly helps:

• The Verify module turns your agreed requirements into automated model checking rules.
• Checks can cover naming, parameters, property sets, LOI, COBie fields, IDS and more.
  Overview: Learn ISO 19650
• Produces clear pass/fail reports that can be shared with clients or auditors as evidence.

4.6 Submitting the model at audit milestones - with full traceability

Common problem: When an auditor or client asks "Which model version did we accept, under which BEP and which requirements?", it can take hours or days to pull together evidence from different systems.

How Plannerly helps:

• Keeps everything connected in one place: requirements → agreements → scope → tasks → files → checks → reports.
• Allows you to generate audit-ready exports for internal or external reviews.
• Helps you demonstrate a consistent, ISO 19650 aligned process to certification bodies.
  Course for organizations: ISO 19650 for Companies

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

You submit a BIM model for audit under ISO 19650 when:

• 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.

ISO 19650 does not dictate calendar dates. Your EIR, MIDP and TIDPs define when models are audited. Plannerly helps make those audits simpler, faster and far more transparent.

6. Free BIM + ISO 19650 training to learn the full workflow

If you want to build a complete, audit-ready workflow using Plannerly and ISO 19650, start with the free and low-cost training programs here:

• Level 1 - BIM Management Basics: https://plannerly.com/courses/basic/
• Level 2 - Advanced BIM Workflows: https://plannerly.com/courses/advanced/
• Level 3 - ISO 19650 Expert: https://plannerly.com/courses/expert/
• ISO 19650 for Companies: https://plannerly.com/courses/iso19650/
• Training hub - all courses: https://plannerly.com/training/