As Built Information Group Meetings 26-06-2026

BIMINAM AS BUILT INFORMATION MEETING, 26-06-2026

Meeting Summary

Date: 26 June 2026
Duration: 1 Hour 30 Minutes


Meeting Objective

The meeting continued the review of the As Built Information Guidance Document, focusing on refining terminology, improving document structure, and ensuring the guidance clearly defines the minimum information required to support the safe operation, maintenance, and management of buildings throughout their lifecycle. The group reviewed updated draft sections, resolved comments from previous meetings, and agreed several changes to improve clarity and consistency.


Key Discussion Points

  1. Defining the Target Audience

The group discussed who the guidance is ultimately intended for. It was agreed that the document should primarily support building operators, owners, facilities managers, and maintenance teams, rather than contractors alone. The guidance should focus on providing practical information that enables buildings to be safely operated and maintained throughout their lifecycle.


  1. Improving Terminology

Members reviewed several key terms used throughout the document.

Key recommendations included:

  • Replacing the generic term "management" with more accurate wording.
  • Using "building operators" as the primary term wherever possible.
  • Recognising that larger projects may involve owners, asset managers, facilities managers, operators, and maintenance teams with different responsibilities.
  • Including clear definitions of these terms within the project glossary.

The group agreed that consistent terminology would improve understanding and reduce ambiguity.


  1. Clarifying the Meaning of Building Information

A detailed discussion focused on defining exactly what Building Information should include.

The guidance should clearly state that Building Information covers:

  • Structural information
  • Building fabric
  • Mechanical and electrical systems
  • Plant and equipment
  • Supporting infrastructure
  • Utilities and associated services
  • Handover documentation
  • Information required for safe operation and maintenance throughout the building lifecycle

Members agreed this definition should appear both within the document and the glossary.


  1. Reviewing Minimum Information Requirements

The group continued reviewing the section defining the minimum level of information expected for building handover.

Discussion focused on ensuring the guidance:

  • Meets legal and regulatory requirements.
  • Provides practical information rather than excessive documentation.
  • Clearly explains what information must always be provided.
  • Supports future building operation rather than simply project completion.

  1. Revising "Best Practice" Wording

Considerable discussion centred around the phrase "tending towards best practice."

Several members felt the wording was too vague and open to interpretation.

Suggestions included:

  • Removing the phrase entirely.
  • Referring instead to recognised industry standards and codes.
  • Using stronger wording that establishes clear expectations.
  • Avoiding language that weakens the purpose of the guidance.

The general agreement was to produce clearer, more direct wording throughout the document.


  1. Metadata and Information Quality

Members discussed the requirement for verified and validated metadata.

Although metadata requirements have not yet been fully defined, the group agreed that:

  • Metadata requirements should eventually be standardised.
  • The glossary should explain what metadata means.
  • Contributors should understand the level of information expected without creating unnecessary complexity.

  1. Practical Industry Feedback

New member Taylor Hammond shared practical experience from reviewing O&M manuals and as-built documentation on live projects.

Key observations included:

  • Information received at handover is often incomplete or inconsistent.
  • Better document organisation would improve long-term usability.
  • Guidance should reflect the practical challenges experienced by those responsible for maintaining completed buildings.

The group welcomed this practical industry perspective.


  1. Document Development Approach

Anthony Taylor reminded members that the objective is to produce a practical industry guidance document rather than attempting to achieve perfection in the first release.

The group agreed to:

  • Continue reviewing the document section-by-section.
  • Resolve comments as they arise.
  • Produce an Executive Summary once the draft is complete.
  • Publish the document for wider industry consultation before finalisation.

Key Decisions

  • Confirmed building operators and operations & maintenance teams as the primary audience.
  • Agreed to improve terminology throughout the document.
  • Clarified that Building Information covers the entire asset lifecycle, not simply construction information.
  • Agreed to strengthen wording around best practice and regulatory expectations.
  • Confirmed that important definitions will be added to the glossary.
  • Continued progressing the draft towards an industry consultation version.

Key Takeaways

The meeting further strengthened the draft guidance by improving terminology, clarifying responsibilities, and reinforcing the importance of providing complete, practical, and lifecycle-focused building information. The group emphasised that successful As Built Information should support safe building operation long after construction is complete. Future meetings will continue refining the document, with particular attention given to glossary definitions, metadata requirements, and preparing the guidance for wider industry review.