A CORENET X submission is not a document upload — it is a coordinated BIM submission that seven agencies review together. That changes what “ready to submit” means. This CORENET X submission checklist covers what a project team should have in place before each gateway, from model readiness to IFC+SG export, so regulatory approval does not stall on avoidable rework.
First: Does CORENET X Apply to Your Project Yet?
Check the timeline before anything else. CORENET X became mandatory on 1 October 2025 for new projects of 30,000 sqm GFA or more. From 1 October 2026 it covers all new projects with GFA of 5,000 sqm and above. Projects below that threshold are not required to onboard and may continue through CORENET 2.0 for now (per URA circular DC26-08 / BCA APPBCA-2026-12, 23 July 2026, which revised the earlier DC25-07 plan). If your project falls outside these windows it may still submit under CORENET 2.0 — our CORENET X vs CORENET 2.0 comparison explains the differences in detail, and the full CORENET X requirements and timeline guide covers the mandate and gateway structure end to end.
Before You Start: Team and Onboarding
- Confirm who submits — the Qualified Person submits the coordinated package, but every discipline contributes a model. Agree responsibilities early.
- Read the CORENET X Code of Practice — it defines the submission process, model requirements, and what each gateway expects.
- Complete onboarding for the project team — make sure the people exporting and uploading actually know the portal and the requirements, not just the modelling software.
- Plan submissions into the programme — a coordinated BIM submission takes preparation time that drawing-based submissions never needed. Treat each gateway as a milestone with lead time, not a formality at the end of a phase.
Model Readiness Checklist
- One coordinated model set — architectural, structural, and MEP models federated and clash-managed before submission, not assembled at the deadline.
- Correct IFC classification — elements mapped to the right IFC entities; modelled-as-something-else workarounds fail validation.
- Regulatory parameters populated — the Singapore-specific attributes agencies check must live in the BIM model, not on annotation.
- Spaces and zones defined as data — much of the review reads spatial information, not geometry.
- IFC+SG export configured and tested — validate the exported IFC models before upload, not after a rejection. See our guide to common IFC-SG validation errors for what typically fails.
The Gateways: What Each One Needs
CORENET X consolidates approvals into coordinated gateway submissions, with agencies — BCA, URA, SCDF, PUB, LTA, NEA, NParks — reviewing the same model and returning a single coordinated response.
- Design Gateway — the coordinated design submission, covering what building plan and planning clearances previously handled separately. The model must already be cross-discipline coordinated; this is where most preparation effort concentrates.
- Piling Gateway — an optional early gateway that lets piling and related works start ahead of full design clearance, when the project needs the programme head start.
- Construction Gateway — the clearance to proceed with main construction works, with the model updated to reflect the approved design.
- Completion Gateway — the final phase: as-built models and the submissions supporting occupation and completion certification.
Submissions that do not need multi-agency coordination follow the Direct Submission Process (DSP) instead of a gateway — but the main project approvals run through the gateways above.
The Condensed Checklist
- Timeline checked — which mandate window applies
- QP and discipline responsibilities agreed
- Code of Practice requirements reviewed for the current gateway
- Models federated, coordinated, and clash-managed
- IFC classification and regulatory parameters verified
- Spaces and zones complete as data
- IFC+SG export validated before upload
- Gateway lead time in the programme
Frequently Asked Questions
When did CORENET X become mandatory?
From 1 October 2025 for new projects of 30,000 sqm GFA or more, extending from 1 October 2026 to all new projects with GFA of 5,000 sqm and above. Projects below 5,000 sqm GFA are not required to onboard (URA circular DC26-08 / BCA APPBCA-2026-12, 23 July 2026).
What format does a CORENET X submission use?
IFC+SG — Singapore’s localisation of the openBIM IFC standard. Our IFC-SG explainer covers how it works.
Who reviews the submission?
The relevant regulatory agencies review the coordinated submission together and coordinate their comments into a single response — that is the core change from CORENET 2.0’s agency-by-agency clearance.
Preparing a submission and want the model checked before the gateway does it for you? Beyond+ supports readiness review, IFC+SG preparation, and the full submission process — see our CORENET X BIM e-submission support.
Before you work through this checklist, confirm whether CORENET X applies to your project at all — the 5,000m² threshold from 1 October 2026 decides that. The Code of Practice sets out what each gateway expects.
