If your project has a Gross Floor Area of 5,000 square meters or more, BIM submission through CORENET X is mandatory, following IFC+SG and the standards set by BCA and URA. Smaller projects may still opt in voluntarily. The immediate step for any qualified person preparing a submission is to run the IFC+SG validator on the model and confirm its geo-referencing before anything goes near the portal.
TL;DR:
- Projects with a GFA of 5,000 square meters or more must submit BIM models in IFC+SG format via CORENET X, with geo-referencing to SVY21 and SHD.
- The preparatory validation process should include discipline-level checks, federation testing, and a review of mandatory Singapore property sets before submission.
- Part ST submissions are available for projects exceeding 40,000 square meters GFA when structural details are phased, but early coordination on sequencing is essential.
- Incomplete federation, inconsistent geo-referencing, or missing agency data fields are the main reasons for submission rejections, which can often be avoided with dedicated project ownership.
- Specialist firms are recommended to manage BIM modeling, validation, and submission processes to minimize resubmission cycles and ensure compliance.
Table of Contents
- Quick CORENET X submission checklist before you file
- Who must submit and when: thresholds and Part ST exceptions
- What goes into your CORENET X submission package
- IFC+SG modeling essentials: SGPsets and geo-referencing
- Understanding the RABW gateways: DG, PG, and CG reviews
- Validation sequence and the portal errors that stall approvals
- Why projects get sent back for resubmission
- How AECTechnicalSG supports compliant CORENET X submissions
- What the CORENET X rollout gets right, and where teams still stumble
- Submission support that gets your project through the gateways
- FAQ
- Sources
Quick CORENET X submission checklist before you file
A short readiness check before formal submission catches most of the errors that cause written directions or outright rejection. Qualified persons preparing a Construction Gateway package should work through the following before uploading anything.
- Confirm whether the project meets the mandatory GFA threshold as specified in official guidelines and note the applicable rollout date for your submission type.
- Prepare a federated model with the required discipline exports (architectural, structural, and M&E) in IFC+SG format.
- Run discipline-level validators, then the official CORENET X Model Checker, before formal submission.
- Assemble 2D supplements, calculation reports, and a cover letter that explains any items not modeled in 3D.
- Where thresholds or scope are unclear, use pre-submission consultation or explore waiver routes rather than guessing.
Who must submit and when: thresholds and Part ST exceptions
The current mandatory threshold applies to new building projects with a GFA of 5,000 square meters or greater, following the lowering of the original 30,000 square meter threshold introduced in the October 2025 rollout, according to URA’s circular. Projects that onboarded under the earlier, higher threshold remain a useful reference point for teams comparing submission scope across phases.
- The Qualified Person and lead consultant bear responsibility for coordinating and submitting the federated model, not individual discipline consultants acting alone.
- Projects exceeding 40,000 square meters GFA, subject to additional block and length criteria, may qualify for Part ST submissions under BCA’s refined CORENET X process, allowing structural detail to be filed in stages.
- Part ST still requires a coordinated carcass model at the first Construction Gateway, so sequencing and AC/ACO endorsements need early planning.
- Projects below the mandatory threshold can submit voluntarily, which often shortens review cycles and builds internal BIM capability ahead of future mandates.
Readers working through broader authority coordination may find our architecture planning guide for 2026 compliance useful for understanding how gateway timing interacts with other statutory submissions.
What goes into your CORENET X submission package
The Construction Gateway package is a mix of modeled and non-modeled content, and knowing which is which saves a great deal of rework.
- Include federated architectural, structural, and M&E discipline models covering fixed installations relevant to multidisciplinary coordination.
- Provide detailed equipment schedules, specialist calculations, and similar items as 2D documents or calculation reports rather than forcing them into the model, since CORENET X guidance treats these as independent submissions where 3D adds no regulatory value.
- State explicitly in the submission cover letter which items are 2D only, so reviewers are not left searching the model for content that was never meant to be there.
- Apply consistent naming conventions across discipline and area divisions, and maintain clear revision tracking so agencies can trace changes between submission cycles.
- Prepare supplementary documents agencies routinely check, including structural calculations, fire safety schedules, and M&E coordination notes, and cross-reference them against the model rather than duplicating data inconsistently.
Our structural design approval guide covers the structural side of this package in more depth, particularly around AC/ACO endorsement sequencing.
IFC+SG modeling essentials: SGPsets and geo-referencing
IFC+SG is not the same as a generic IFC4 export, and treating it as one is a common source of rejected files.
- Use the official IFC+SG mapping and configuration files rather than relying on default exporter settings from your authoring software.
- Populate the required Singapore Property Sets, known as SGPsets, using the official Excel mapping file to confirm every mandatory field is present.
- Geo-reference the model to SVY21 (EPSG:3414) coordinates and the Singapore Height Datum, since URA’s best practice guidance notes that incorrect coordinates block the Automated Model Checker from matching against agency geodata.
- Check classification codes, level definitions, coordinate transforms, and property values before exporting, then validate the file locally rather than discovering errors on the portal.
Pro Tip: Run a full internal federation and validation pass that mimics the portal’s checks before you submit, since catching a coordinate mismatch internally costs far less time than resubmitting after a portal rejection.
Understanding the RABW gateways: DG, PG, and CG reviews
CORENET X structures review around three gateways, and knowing what each one checks helps teams stage their deliverables correctly instead of front loading everything into one submission.
- The Design Gateway reviews design parameters and key multi-agency parameters early, before detailed coordination begins.
- The Planning Gateway handles planning and statutory clearances, primarily from URA and related agencies, confirming the project can proceed on its intended footprint and use.
- The Construction Gateway reviews the coordinated federated model alongside detailed approvals from BCA for building plan and structural work, and from LTA, NEA, PUB, or SCDF where their scopes apply.
- Independent submissions remain available for agency-specific items outside the coordinated model, and pre-submission consultation or escalation through the CORENET X Code of Practice process can resolve conflicts before they reach formal review.
Validation sequence and the portal errors that stall approvals
A disciplined validation order prevents most of the rejections that otherwise cost a submission cycle.
- Run discipline-level validators on architectural, structural, and M&E models independently before attempting federation.
- Perform a federation or merge check across all disciplines to catch clashes and inconsistent coordinate systems.
- Submit the federated model through the CORENET X Model Checker, which includes an openBIM viewer to confirm renderability before agency processing begins.
Common portal errors worth checking first: geo-referencing mismatches against SVY21 and SHD, missing mandatory SGPset properties, and rendering failures caused by non-standard exports. The onboarding checklist and portal user manual, referenced in CORENET X’s AMA resources, walk through fixes for each.
Portal tools exist specifically to catch these issues before an agency sees the file. The Model Checker and openBIM viewer let teams confirm model quality and renderability ahead of formal processing, which is the single most effective way to avoid a failed first pass.
Why projects get sent back for resubmission
Most resubmissions trace back to a small set of recurring causes rather than genuinely novel problems.
- Incomplete federation, where one discipline model is missing or out of date relative to the others.
- Coordinate errors from inconsistent SVY21 or SHD referencing across discipline models.
- Missing agency-specific data fields that an SGPset mapping step should have caught earlier.
Pro Tip: Assign one team member ownership of the federation and validation step on every project, since diffuse responsibility is the most common reason coordinate and SGPset errors slip through.
When a staged submission or 2D supplement is genuinely necessary, document the justification in the cover letter rather than leaving reviewers to infer it. Where thresholds or scope remain genuinely ambiguous, escalate through the Code of Practice’s waiver process or the IACC rather than submitting speculatively.
How AECTechnicalSG supports compliant CORENET X submissions
Specialist firms provide BIM modeling, IFC+SG mapping, and endorsement services alongside full submission management for Singapore authorities. Typical workflows run discipline models through federation and validation checks before formal filing, reducing the risk of resubmission cycles that stall projects. For developers managing authority submissions alongside the BIM requirements, our project submission requirements guide covers the wider compliance picture. Projects of the scale seen in developments like the Hougang Central GLS site illustrate how multidisciplinary coordination scales with GFA, which is exactly where federation errors tend to surface first.
What the CORENET X rollout gets right, and where teams still stumble
The shift CORENET X represents is less about software and more about sequencing. Coordination that used to happen informally during agency review now has to happen before submission, and teams that treat the Model Checker as a formality rather than a genuine gate are the ones who get sent back. The conventional advice, which focuses heavily on software selection and exporter settings, underestimates how much of the failure rate comes from process ownership rather than tooling.
The CORENET X overview materials are explicit that responsibility for de-confliction has moved upstream to project teams. That means the real priority for a QP is not finding a better IFC exporter, it is assigning a single owner for federation and validation early, before discipline models diverge in ways that are expensive to reconcile later. Teams that treat geo-referencing and SGPset population as a final checklist item, rather than a design-stage discipline, consistently pay for it in resubmission cycles.
— Aman
Submission support that gets your project through the gateways
Consultancies manage the full CORENET X submission path, from BIM modeling and IFC+SG mapping through endorsement and liaison with Singapore authorities. Projects navigating Part ST sequencing or multidisciplinary coordination issues benefit from a single consultancy handling both the engineering and the authority submission.
Visit our services page to request a scoped technical review of your submission package, or explore PE endorsement and authority submission support if you need end-to-end coverage from design checks through final CORENET X filing.
FAQ
What is BIM in Singapore’s CORENET X context?
BIM in Singapore refers to building information modeling submitted through the CORENET X portal using the IFC+SG format, which includes Singapore-specific property sets and geo-referencing requirements. It replaces older paper and 2D-only submission routes for projects meeting the mandatory GFA threshold.
What are the BIM requirements in construction projects?
Projects with a GFA of 5,000 square meters or more must submit a federated BIM model in IFC+SG format through CORENET X, covering architectural, structural, and M&E disciplines. The model must be geo-referenced to SVY21 and the Singapore Height Datum and validated through the CORENET X Model Checker before formal review.
How much does a BIM course cost in Singapore?
Course pricing is not publicly listed in a single consistent source, and costs vary by provider and course length. Readers researching training should check directly with training providers rather than relying on a single quoted figure.
What is the average salary for a BIM engineer in Singapore?
Salary figures for BIM engineers are not consistently published by an official source, so no reliable figure can be cited here. Readers researching compensation should consult current job listings or industry recruiters for up to date ranges.