ISO 19650 Company Compliance (with Checklist)

This video explains the final steps of audit preparation for ISO 19650 certification, covering how to organise documentation, finalise the compliance checklist, understand the two audit stages, and book the audit with confidence. The written guide below covers how to gather and centralise compliance materials in the Docs module, how to move checklist items to a verified status as gaps are fully resolved, what auditors assess during the stage 1 documentation review and the stage 2 live project implementation review, how to prepare evidence of actual use rather than theoretical processes, and how the Plannerly team supports the final readiness review before the audit is scheduled.

How the final audit preparation phase brings everything together for certification

Getting to the audit preparation phase means your team has already done the hard work. The readiness check identified where your processes stood. The gap analysis report documented what needed to change. The get audit ready phase closed those gaps through process customisation, team training, and structured progress tracking. Now, the final step is to prepare for the audit itself by organising your documentation, confirming that every checklist item is genuinely resolved, and understanding what the auditor will assess across both stages of the certification process.

The first priority is making sure your documentation is complete, centralised, and audit-ready. Every process, policy, and piece of evidence that supports your compliance should be stored in the Docs module as a structured smart document rather than scattered across email threads, shared drives, or local files. This includes your BIM Execution Plan, your Master Information Delivery Plan, your responsibility matrix, training records, standard operating procedures, and any other materials that demonstrate how your organisation manages information in line with ISO 19650. Using templates from the Plannerly library ensures consistency and alignment with the standard, while the File Manager keeps everything version-controlled and accessible to the people who need it.

With documentation in order, the next step is to finalise the compliance checklist in the Scope module. During the get audit ready phase, your team has been working through identified gaps and updating statuses as each one is addressed. Before the audit, every resolved item should be moved to a verified status, confirming that the gap has not just been worked on but has been fully resolved and checked. This distinction matters because the auditor needs to see that your organisation has a verification process, not just a list of completed tasks. Each verified item should have supporting evidence attached, comments documenting what was done and why, and a clear audit trail showing the journey from identified gap to resolution. The grid, timeline, and Kanban views make it easy to confirm at a glance that all items have been addressed and nothing remains outstanding.

Understanding what the auditor will assess is essential for preparing effectively. ISO 19650 certification typically involves two stages. Stage 1 is a documentation assessment where the auditor reviews your processes, systems, and procedures on paper. They are looking for evidence that your organisation has documented its information management approach, that the approach aligns with the requirements of the standard, and that the documentation is complete, consistent, and accessible. This is where your centralised Docs module, your completed checklist with verified statuses, and your gap analysis report become the primary evidence. Stage 2 is a live project implementation review. Here, the auditor moves beyond documentation and looks at how your processes work in practice on a real project. They want to see evidence that your team is actually following the documented workflows, that information is being managed according to the standard, and that the tools and systems described in your documentation are being used as intended. This means having a live project where the full BIM workflow is in operation, with real data in the Scope module, real documents being tracked, and real verification happening through the Verify module.

The difference between stage 1 and stage 2 is the difference between describing what you do and proving that you do it. Many teams find stage 1 relatively straightforward if their documentation is thorough. Stage 2 requires more preparation because it exposes any disconnect between documented processes and actual practice. This is why the get audit ready phase emphasises team training so heavily: every team member needs to understand and follow the workflows, not just the information manager or BIM lead. If the auditor finds areas where processes are documented but not followed, or where the documentation does not match what is happening on the project, these are raised as non-conformities that need to be addressed before certification can be granted.

Before booking the audit, the Plannerly team offers a final readiness review for teams on the supported programme. This review checks that your documentation is complete, your checklist is fully verified, your gap analysis report reflects the current state, and your live project demonstrates genuine implementation. Once both you and the Plannerly team are confident that everything is in place, you can book the audit with a certification assessor and move into the final stage of the certification journey.

How to prepare for the ISO 19650 certification audit step by step

  1. Centralise all compliance documentation – Gather every document that supports your compliance into the Docs module. This includes your BEP, MIDP, responsibility matrix, training records, standard operating procedures, and any evidence of process implementation. Use templates to ensure consistency and alignment with the standard.
  2. Review and verify every checklist item – Go through the compliance checklist and confirm that every previously identified gap has been resolved. Update the status of each item to verified, attach supporting evidence, and add comments documenting what was done to close each gap.
  3. Generate the final gap analysis report – Use the gap analysis report to produce an up-to-date summary showing all items as resolved. If you have auto-versioning configured, confirm that the latest version reflects your current compliance status.
  4. Prepare for stage 1: documentation assessment – Review your documentation from the auditor’s perspective. Check that every ISO 19650 requirement is covered by a documented process, that the documentation is accessible and well-organised, and that the gap analysis report provides a clear evidence trail from initial assessment through to resolution.
  5. Prepare for stage 2: live project review – Ensure that a live project is running with the full BIM workflow in operation. Confirm that information is being managed through the Scope module, documents are being tracked in Docs, and verification is happening through the Verify module. The auditor will want to see real data demonstrating actual use of the processes you have documented.
  6. Confirm team readiness – Verify that all team members have completed the relevant training programmes and can demonstrate their understanding of the workflows they are responsible for. The auditor may ask team members about their roles and how they use the tools and processes in practice.
  7. Complete the final readiness review – For teams on the supported programme, schedule a readiness review with the Plannerly team. This review checks documentation completeness, checklist verification, report accuracy, and live project implementation before you commit to booking the audit.
  8. Book the audit – Once the readiness review confirms that everything is in place, book the audit with a certification assessor. Provide them with access to your gap analysis report and compliance documentation so they can prepare for the assessment.

What you’ll learn

  • Documentation organisation for audit – How centralising all compliance materials in the Docs module with structured templates and version control creates a single, accessible source of evidence that the auditor can review efficiently and thoroughly.
  • Verified status and evidence trails – How moving checklist items from resolved to verified, with attached evidence and documented comments, demonstrates to the auditor that your organisation has a genuine verification process rather than just a task completion record.
  • Stage 1: documentation assessment – What the auditor evaluates during the first stage, including the completeness and consistency of your documented processes, your gap analysis report, and the alignment between your documentation and the requirements of the standard.
  • Stage 2: live project implementation – How the auditor assesses whether your documented processes are being followed in practice on a real project, why evidence of actual use matters more than theoretical compliance, and what a disconnect between documentation and practice means for certification.
  • Training as audit evidence – Why team training is not just a preparation activity but a critical piece of audit evidence, and how the auditor may assess whether team members understand and follow the workflows they are responsible for.
  • Final readiness review and booking – How the supported programme’s final readiness review helps identify any remaining gaps before the audit is booked, and how working with a certification assessor ensures the assessment process runs smoothly.

Common questions

What is the difference between stage 1 and stage 2 of the audit?

Stage 1 is a documentation assessment. The auditor reviews your processes, systems, and procedures on paper to confirm that they are documented, complete, and aligned with ISO 19650. Stage 2 is a live project implementation review where the auditor assesses whether those documented processes are actually being followed on a real project. Stage 1 checks what you say you do. Stage 2 checks what you actually do. Both stages need to be passed for certification to be granted.

What does the auditor look for during the live project review?

The auditor wants to see evidence that your team is managing information according to the workflows documented in your BEP, MIDP, and other compliance materials. This includes how information is created, shared, reviewed, and approved, how deliverables are tracked in the Scope module, how documents are maintained in the Docs module, and how verification is performed through the Verify module. They are looking for consistency between your documentation and your actual working practices.

What happens if the auditor finds non-conformities?

Non-conformities are areas where your processes do not meet the requirements of the standard or where there is a disconnect between your documentation and actual practice. Minor non-conformities can usually be addressed within a defined timeframe without requiring a full re-audit. Major non-conformities may require more significant changes and a follow-up assessment. The non-conformities lesson covers how to identify, address, and document these issues as part of your continuous improvement process.

How do I know when I am ready to book the audit?

You are ready when all items in the compliance checklist have been verified with evidence attached, your documentation is centralised and up to date in the Docs module, your gap analysis report shows all gaps as resolved, your team has completed the relevant training, and you have a live project demonstrating genuine implementation of your ISO 19650 workflows. The final readiness review with the Plannerly team provides an additional confirmation before you commit.

Explore further

0% Complete

Pin It on Pinterest