The CORENET X Code of Practice is the document that tells you how a multi-agency regulatory submission is actually supposed to be prepared. It is not a BIM standard and it is not a software manual. It sits between the two: it explains how project teams should organise information so that seven regulatory agencies can review one set of models across the key submission gateways.
If your team is preparing for the CORENET X e-submission process, this is the document your workflow has to answer to. Here is what it covers and what it means in practice.
What the CORENET X Code of Practice is
BCA describes the Code of Practice (COP) as a document “intended to help industry practitioners in understanding how to prepare multi-agency regulatory submissions across the key submission gateways in CORENET X”. Two words in that sentence carry most of the weight.
Multi-agency. Under the previous regime, a project team prepared a submission for each agency in turn. CORENET X inverts that: one coordinated submission is reviewed by BCA, LTA, NEA, NParks, PUB, SCDF and URA together. The COP exists because a model that satisfies one agency’s reading is not automatically legible to the other six.
Gateways. Submissions are no longer a continuous trickle of applications. They are grouped into defined milestones, and the COP sets out what must be in place at each one.
The COP also addresses the unglamorous project-collaboration problems that sink coordinated submissions — multi-disciplinary project set-up, geo-referencing, and the modelling conventions that vary from firm to firm. These are exactly the issues that do not show up until three consultants’ models are federated and nothing lines up.
The 3-Gateway Process and the Direct Submission Process
CORENET X provides two routes. Most building works follow the 3-Gateway Process. A Direct Submission Process (DSP) exists for submissions that do not warrant the full gateway sequence.
Within the gateway route, the COP documents requirements at each of the key submission gateways:
- Pre-Submission Consultation — engagement with agencies before the formal sequence begins
- Design Gateway — the coordinated design submission
- Piling Gateway — where piling works require separate clearance
- Construction Gateway — approval to proceed with construction
- Independent Submissions — items that sit outside the main sequence
- Completion Gateway — the closing submission for the project
Separate provisions cover Conservation, External Works, Part-ST Submissions and Infrastructure Works, which do not map cleanly onto the standard building-works sequence.
The practical consequence is that your BIM programme now has fixed checkpoints. A model that is “mostly there” at the Design Gateway is not a model that passes it. This is the single biggest change in how teams have to plan their modelling effort, and it is why the BIM Execution Plan has become a live delivery document rather than a formality.
How the Code of Practice relates to IFC+SG
The COP and the IFC+SG resources answer different questions, and teams regularly conflate them.
- The Code of Practice tells you what a submission must contain and when it is due.
- IFC+SG tells you how the model must be structured so the agencies’ systems can read it.
BCA states that the COP “complements” the IFC+SG materials, which provide the technical templates and help resources for generating IFC+SG models from proprietary BIM authoring tools. In other words: satisfying the COP without a valid IFC+SG export gets you nowhere, and a clean IFC+SG export submitted at the wrong gateway with the wrong content gets you nowhere either.
If IFC+SG is new to your team, start with what IFC+SG is and why Singapore created it, then work through the common validation errors before you attempt a live submission.
The disclaimer that matters
The COP carries a caveat that is easy to skim past and expensive to ignore. BCA states that the document “details the envisaged end state of CORENET X”, that CORENET X is developed through Agile methodology, and that features and requirements “will be developed progressively” with enhancements released in phases.
It then says plainly: “For the exact implementation date, please refer to official circulars.” And: the COP “does not substitute Handbooks, Circulars or other regulatory publications” of the agencies.
Read that as an instruction, not boilerplate. The COP describes where CORENET X is going. The circulars tell you what is mandatory today. Teams that plan against the COP alone end up preparing for requirements that have not commenced, or missing threshold changes that have. The current position on thresholds is set out in our note on CORENET X versus CORENET 2.0.
What this changes for project teams
Three practical shifts follow from the COP, and they land on different people.
For the QP: coordination is no longer something that happens before submission. It is the submission. A federated model that has not been checked across disciplines will surface as agency comments, and those comments now arrive at a gateway rather than in a rolling correspondence.
For the BIM manager: project set-up decisions made in week one — geo-referencing, shared coordinates, naming, discipline split — determine whether the federated model works at the Design Gateway. These are cheap to get right at the start and very expensive to correct later.
For the contractor: the Construction and Completion Gateways mean model information has to survive into delivery and handover. A model that was built purely to clear design approval will not carry the information those later gateways ask for.
Where to start
If you are onboarding a project now, the sequence that works is: confirm which process and thresholds apply to your project from the current circulars; set the BEP and project set-up against the gateway your team hits first; and validate an IFC+SG export early, on a partial model, rather than discovering structural problems the week a gateway is due.
Our CORENET X submission checklist covers what to have ready before the first gateway, and the full CORENET X requirements guide goes deeper on model content.
Frequently asked questions
What is the CORENET X Code of Practice?
It is BCA’s guidance document explaining how industry practitioners should prepare multi-agency regulatory submissions across the key submission gateways in CORENET X. It covers submission content, gateway requirements and recommended BIM collaboration practices, and it complements the IFC+SG technical resources rather than replacing them.
What is CORENET X?
CORENET X is Singapore’s regulatory approval process for building works, replacing the earlier agency-by-agency model with a single coordinated, multi-agency submission built around BIM. Seven agencies — BCA, LTA, NEA, NParks, PUB, SCDF and URA — review the same submission package at defined gateways.
What are the steps in the CORENET X submission workflow?
For building works following the 3-Gateway Process: Pre-Submission Consultation, then the Design Gateway, the Piling Gateway where applicable, the Construction Gateway, and finally the Completion Gateway. Independent Submissions handle items outside that sequence, and a Direct Submission Process exists for submissions that do not require the full gateway route.
Does the Code of Practice tell me when CORENET X becomes mandatory for my project?
No. The COP states explicitly that for exact implementation dates you should refer to official circulars, and that it does not substitute handbooks, circulars or other regulatory publications. Thresholds and commencement dates are set by circular, not by the COP.
Do I need IFC+SG to comply with the Code of Practice?
For projects where BIM submission is mandatory, yes — the COP governs what and when, while IFC+SG governs how the model is structured for agency systems to read. The two work together, and a submission needs both to succeed.
Need help with a CORENET X submission?
Beyond+ prepares IFC+SG models and coordinates multi-discipline submissions for Singapore projects. Tell us your project size, stage and gateway, and we will tell you what is actually required.
Talk to Beyond+ Our BIM services →This article summarises publicly available guidance for general information. It is not a substitute for the Code of Practice, agency handbooks or circulars. Always verify current requirements against the official publications of BCA, LTA, NEA, NParks, PUB, SCDF and URA for your specific project.