CORENET X Code of Practice (COP)

IMPORTANT

COP Fourth Edition – Transition Arrangements

EFFECTIVE DATE 1 January 2027

1. Ongoing Submissions

Projects already submitted and undergoing review, including resubmissions following Written Directions (WD), may continue using their existing COP edition until approval for that gateway is obtained.

2. New Gateway Submissions

From 1 January 2027: All new gateway submissions, including projects moving to the next gateway (e.g. projects preparing for DG, or have already obtained DG and are preparing for first CG submission), are required to adopt COP Edition 4.0.

Previously approved models do not need to be updated unless required for the next gateway submission.

3. Amendment Submissions

From 1 January 2027: Amendment submissions are required to adopt COP Edition 4.0.

Previously approved models do not need to be updated unless they are affected by the amendment or required for agency review.

4. Part ST Submissions

  • CG submitted before 1 January 2027: Consultants may continue using their existing COP edition for the part ST submissions.
  • CG submitted from 1 January 2027: part ST required to adopt COP Edition 4.0.

Software Configuration Files

Software vendors are expected to release their updated configuration files by November 2026. This will give consultants approximately two months to prepare their models before the proposed effective date of 1 January 2027. Please refer to the CORENET X > BIM Authoring Tools page for the latest updates on software support and configuration files for COP Edition 4.0.

CORENET X

Code of Practice (COP)

Understanding CORENET X submission requirements

The CORENET X Code of Practice provides guidance on the requirements, processes and information needed for coordinated multi-agency regulatory submissions.

Explore Code of Practice

Feedback & Enquiries

About

Preamble

This Code of Practice (COP) is intended to help industry practitioners in understanding how to prepare multi-agency regulatory submissions across the key submission gateways in CORENET X.

This Code of Practice, where relevant, will include recommended procedures and good practices to address common Building Information Modelling (BIM) issues at general project collaboration level (e.g. multi-disciplinary project set-up, geo-referencing) and specific details that vary from firm to firm today.

This Code of Practice complements the , which provides technical templates and help resources from key proprietary BIM software for the generation of IFC+SG models.

Disclaimer

This Code of Practice details the envisaged end state of CORENET X. CORENET X is developed through Agile Methodology and hence, features and requirements mentioned in this COP will be developed progressively, and its technological enhancements will be made available in phases. For the exact implementation date, please refer to official circulars.

This Code of Practice does not substitute Handbooks, Circulars or other regulatory publications of our regulatory agencies. Readers should refer to the relevant Codes, Acts and Regulations on the compliance required for their projects, before referring to this Code of Practice on how to represent the compliance information in the CORENET X submission gateways.

Readers should consult relevant agencies if they need to determine the regulatory requirements to fulfil compliance.

How to use this Code of Practice

01
Section 1

Introduction to CORENET X

  • What is CORENET X?
  • What are the key aspects of CORENET X?
  • What is a user journey of CORENET X like?
02
Section 2

General Requirements

  • Which agency’s approvals are covered under CORENET X?
  • What do abbreviations like RABW and IFC-SG stand for?
  • What happens to the QP’s statutory obligations under CORENET X?
  • What is each project team submission like and maximum file size?
  • What is the model preparation process like?
Filter by
SECTION 3

Regulatory Agencies

  • RABW Requirements categorised by Regulatory Agencies

Key Gateways

  • RABW Requirements categorised by Key Gateways

Other Building Works

  • RABW Requirements for
    • External Works
    • Direct Submission Process
    • Conservation

Note: Each RABW requirement in Section 3 is complemented by IFC common components from the BIM Model (where relevant)

04
Section 4

Typical Components in a Project (“Identified Components”)

  • What does a BIM component need to contain / look like, in order to satisfy agency’s regulatory requirements?

Note: CORENET X is developed through Agile Methodology and sections / requirements in this COP will be updated progressively and its technological enhancements will be made available in phases.

Downloads

Latest Edition

Fourth Edition · September 2026

Annex

The Annex is a summary of changes vis-à-vis the 3.1 Edition of the COP

Download Annex
CORENET X Code of Practice Download COP ↗
Annex (Second Edition)

The Annex is a summary of changes vis-à-vis the First Edition of the COP

Download Annex ↗
CORENET X Code of Practice Download COP ↗
Annex (First Edition)

The Annex is a summary of changes vis-à-vis the First Edition of the COP

Download Annex ↗

Terms and Definitions

For the purpose of this Code of Practice, the following definitions shall apply:

8 terms

Abbreviation for “Regulatory Approval Process for Building Works”, and refers to the new process involving 3 key sequential submission gateways to all Agencies for one collective and coordinated approval at each gateway.

Major submission milestones in CORENET X, where the submission needs to comply with multiple agencies’ statutory requirements at each Gateway.

  • Multiple Agency requirements listed under each regulatory agency can be found here.
  • Multiple Key Gateway requirements listed under each gateway can be found here.

Similar to today, there are 3 supporting mechanisms will continue to complement the approval process:

  1. Pre-Submission Consultation

    Pre-submission consultation will continue to be available for industry to consult or seek clarification prior to submission.

  2. Waivers

    Where necessary, the industry may apply for waiver under the respective Act and Regulations and the respective agency will assess the applications accordingly.

  3. Escalation Mechanism

    Industry can table their case to seek resolution on inter-agency regulatory conflicts at the Inter-agency Coordinating Committee (IACC).

Combined Building Information Model that compiles multiple models from different disciplines or sections of the project into a single, complete model of the project.

  • Federated models support concurrent authorship of different aspects of the project by multiple parties.
  • Federated models also support multi-disciplinary coordination as models are geo-referenced to coordinates from the Singapore SVY21 coordinate system (EPSG: 3414) for Easing and Northing (x,y) and Singapore Height Datum (SHD) for Height (z).

New representations for local regulatory requirements, in the Industry Foundation Classes (IFC) openBIM standard. More information of the mapping and configuration files for IFC+SG can be found .

As long as relevant IFC+SG data requirements are embedded in the respective BIM components and minimum dimensions represented, BIM components do not need to replicate their real-life equivalent.

For example, trees can be represented as lollipop objects as long as the relevant IFC+SG parameters under the identified component 'Landscape Plants' are embedded in the tree object accordingly (e.g. “Girth”, “Height” and “Status” , etc.).

Lollipop tree representation

Besides BIM submissions in the IFC+SG format, CORENET X will be able to accept non-BIM submissions.

CORENET X will be able to accept non-BIM documentations that accompany each project team’s submission of IFC+SG models (e.g. design calculation reports, 2D supplementary drawings)

No matching terms found.