BIMINAM AS BUILT INFORMATION MEETING, 28-05-2026
Meeting Overview
- Continued development of an industry-wide definition for As Built Information.
- Focused on creating a definition that is applicable across construction, handover, asset management, operations and regulatory compliance.
- Explored how As Built Information relates to existing deliverables such as O&M Manuals, Health & Safety Files, Regulation 38 information and Golden Thread information.
Key Discussion Topics
- Whether As Built Information should be defined around:
- A project
- An asset
- A built asset
- The importance of creating a supporting glossary of terms to avoid ambiguity and industry-wide misunderstanding.
- Recognition that terms such as "asset" and "project" mean different things to different stakeholders and therefore require clear definitions.
Major Themes
- As Built Information should represent the authoritative record of what has been built or installed.
- The definition should focus on what information is needed, rather than how it is created or validated.
- The occupier, owner and facilities management perspective should be central to the definition.
- Information should enable safe operation and maintenance of the built environment long after the project team has left site.
Ongoing Debate
- Whether O&M Manuals should be considered:
- Separate from As Built Information; or
- Part of the overall As Built Information set.
- Discussion highlighted that many industry participants currently view:
- As-built drawings
- O&M Manuals
- Health & Safety Files
- Regulation 38 information
- Golden Thread information
- as separate deliverables.
- Others argued that from an operator's perspective these collectively form the information needed to manage the asset and should therefore be included within the As Built Information scope.
Proposed Future Work
- Create a visual model or Venn diagram showing the relationship between:
- As Built Information
- O&M Manuals
- Health & Safety Files
- Regulation 38 Information
- Golden Thread Information
- Develop a supporting glossary defining contentious terms such as:
- Asset
- Built Asset
- Project
- Information
- Verification
- Define minimum standards for:
- Validation
- Accuracy
- Evidence
- Digital formats
Key Conclusions
- Industry confusion around the meaning of "As Built" remains significant.
- Standardised terminology is essential before wider adoption can occur.
- Definitions must be understandable by designers, contractors, operators, asset owners and regulators.
- The group is moving towards defining As Built Information as a comprehensive information set that supports operation, maintenance, compliance and future decision-making.
- Future sessions will focus on validation requirements and minimum information standards.
Key Action Points
- Finalise the core definition of As Built Information.
- Produce a glossary of supporting terms.
- Develop a visual relationship model between major handover deliverables.
- Establish minimum validation, evidence and accuracy requirements.
- Align the definition with operational and asset management needs rather than purely project delivery requirements.
- Continue engagement with industry experts to ensure the definition can become an accepted industry standard.