BIMINAM AS BUILT INFORMATION MEETING, 12-06-2026
Date: 12 June 2026
Duration: 2 Hours 15 Minutes
Meeting Summary
The meeting focused on reviewing and refining the draft As Built Information Definition document, with particular attention given to legal requirements, information handover obligations, minimum information standards, and information management principles.
A significant discussion centred on the application of Regulation 38 and whether fire safety information must be provided following fit-out works. It was highlighted that Regulation 38 applies to the erection or extension of a building but may not apply where works are limited to a separate fit-out package. Participants acknowledged that this creates a potential gap in information handover requirements and reinforces the importance of clearly defined contractual obligations.
The group agreed that project contracts should explicitly specify the information required at handover, as legislation alone may not guarantee the provision of all necessary operational, safety, and asset information. Members noted that clients often rely on contractual arrangements to ensure the receipt of complete and usable as-built information.
Updates to the draft document were reviewed, including revisions based on comments received from previous meetings. The group generally supported the proposed minimum information requirements and agreed that the document should remain practical and applicable across organisations with different levels of digital capability.
A detailed discussion was held regarding the use of the term “data format.” Several participants felt that the term could be interpreted inconsistently and suggested focusing instead on information content and end-user requirements. The group agreed that information requirements should be driven by operational needs and that terminology should be clear and unambiguous.
Members also questioned references to ISO 19650 interoperability, noting that ISO 19650 primarily provides a framework for information management processes rather than technical interoperability standards. It was suggested that broader information management principles or frameworks may be more appropriate references within the document.
The meeting further explored the role of change control in as-built information. Participants agreed that the information handed over should accurately reflect the final constructed asset. While maintaining an audit trail of changes during design and construction was considered valuable, there was recognition that long-term operational change management extends beyond the immediate scope of the as-built information requirements being developed.
Key Actions and Outcomes
- Review and amend wording relating to data format and information content requirements.
- Reconsider references to ISO 19650 and explore broader information management frameworks.
- Ensure information requirements remain achievable for organisations with varying levels of digital maturity.
- Clarify the role of change control within the scope of as-built information.
- Continue refining the minimum information requirements before progressing to guidance on information delivery, validation, and lifecycle management.
Conclusion
The meeting reinforced the need for a clear, practical, and client-focused definition of as-built information. The group agreed that the document should support effective information handover, address gaps between legal and contractual requirements, and provide a foundation for reliable building information throughout the asset lifecycle.