IFC submission standards in Singapore are defined by IFC+SG, the Singapore-specific extension of the IFC4 Reference View, which governs how BIM models are structured, populated with regulatory data and exported for CORENET X. For new projects with a gross floor area (GFA) of 5,000 m² and above, IFC+SG is the mandatory submission format. This article sets out the thresholds, data structure, coordinate requirements, package contents and validation steps that Qualified Persons and project teams must address before lodging a model.
TL;DR
- IFC+SG is the extended IFC format that carries Singapore regulatory data. It is the format supported for CORENET X submissions.
- Submission through CORENET X Gateway Processes has been mandatory since 1 October 2026 for new projects with GFA of 5,000 m² and above. Smaller projects may use 2D format or lightweight BIM.
- Models must be geo-referenced to SVY21 (EPSG: 3414) and the Singapore Height Datum, and must embed the IFC+SG properties defined in the Excel Mapping File.
- All new gateway submissions from 1 January 2027 must adopt COP Edition 4.0.
- Validate every model, discipline by discipline and as a federated whole, before formal submission.
Table of Contents
- What IFC and IFC+SG mean for a CORENET X submission
- Which projects must submit in IFC+SG
- The IFC+SG data structure
- Geo-referencing and coordinate standards
- Discipline models, federation and the submission package
- Validating the model before submission
- Pre-submission checklist
- Our perspective
- How Aman Engineering supports CORENET X submissions
- FAQ
- Sources
What IFC and IFC+SG mean for a CORENET X submission
Industry Foundation Classes (IFC) is an open, vendor-neutral schema for exchanging building information. Singapore does not accept native files from proprietary authoring software. According to the CORENET X support centre, the format supported for submissions is the IFC4 Reference View, which includes local regulatory requirements called IFC+SG. IFC+SG is the extended version of IFC and introduces new representations for localised regulatory requirements.
The practical consequence is that a model is no longer only a geometric record. CORENET X describes IFC+SG as the definition of how BIM models are structured for submission, combining IFC with Singapore-specific information so that agencies can read, review and check model data. Each wall, door, space and other identified component must therefore carry the attributes that the relevant Code of Practice requires, in a form the agencies’ automated checks can interpret.
A team that treats IFC export as a final conversion step typically discovers missing parameters late. A team that treats IFC+SG as a modelling specification from the first design stage avoids rework. Our guide to BIM submission standards in Singapore covers the wider submission context.

Which projects must submit in IFC+SG
The applicable format depends on the size of the project and the date submissions commenced. The Urban Redevelopment Authority’s circular on the CORENET X implementation plan states that from 1 October 2026, submission via CORENET X Gateway Processes is mandatory for all new projects with GFA of 5,000 m² and above. Projects of that size that commenced submissions in CORENET 2 by 30 September 2026 may continue in CORENET 2 for now.
| Project situation | Submission requirement |
|---|---|
| New project, GFA of 5,000 m² and above | CORENET X Gateway Processes, with IFC+SG models mandatory |
| New project, GFA below 5,000 m² | 2D format or lightweight BIM may be used |
| GFA of 5,000 m² and above, submissions commenced in CORENET 2 by 30 September 2026 | May continue in CORENET 2 for now |
| Any new gateway submission from 1 January 2027 | COP Edition 4.0 must be adopted |
The format rule is confirmed on the URA CORENET X page: IFC+SG is mandatory for projects with GFA of 5,000 m² and above, while projects below that threshold may use 2D format or lightweight BIM.
The Code of Practice transition in 2027
The CORENET X Code of Practice page specifies that from 1 January 2027, all new gateway submissions, including projects moving to the next gateway, are required to adopt COP Edition 4.0. Previously approved models do not need to be updated unless required for the next gateway submission. Teams with projects approaching a subsequent gateway in early 2027 should therefore confirm which edition governs the model they intend to lodge. Our CORENET X migration readiness checklist sets out the preparation steps.
Who may lodge the submission
Only Qualified Persons (QPs) with a valid Practising Certificate, such as registered Architects, Professional Engineers and Registered Surveyors, can submit a Development Application via CORENET X, as stated by URA. Developers and contractors should accordingly plan the appointment of QPs and the model delivery schedule together.
The IFC+SG data structure
IFC+SG stores regulatory information in two kinds of property sets. CORENET X documentation explains that standard IFC Psets, such as Pset_WallCommon, Pset_DoorCommon and Pset_SpaceCommon, are used alongside Singapore-specific SGPsets, such as SGPset_Wall, SGPset_Door and SGPset_Space.
The controlling reference is the IFC+SG Excel Mapping File. The version dated 22 September 2026 defines the IFC entities, SGPsets, properties and controlled values required for submission. It is intended to be used with the Code of Practice and the Glossary of Identified Components to check data completeness before IFC export.
In practice, the mapping file governs four decisions:
- Which BIM components are identified components for the gateway being submitted.
- Which IFC entity each component must be exported as.
- Which Psets and SGPsets, and which properties within them, must be populated.
- Which values are controlled, meaning the entry must match a permitted value rather than free text.
Because the mapping file is revised, the version used for modelling should be recorded in the BIM Execution Plan and checked again before each gateway.
Geometry need not imitate reality
The Code of Practice allows a pragmatic approach to representation. As CORENET X explains, components do not need to replicate their real-life equivalent as long as the relevant IFC+SG data requirements are embedded and minimum dimensions are represented. Trees, for example, can be modelled as lollipop objects if parameters such as Girth, Height and Status are embedded. Modelling effort should be directed to data accuracy and required dimensions, not to visual fidelity.
Geo-referencing and coordinate standards
Submitted models must be positioned in real-world coordinates. CORENET X guidance states that models should be assigned Singapore SVY21 coordinates (EPSG: 3414) for Easting and Northing (x,y), with elevation levels or height (z) based on the Singapore Height Datum (SHD).
The common failure points are these:
- Models authored on a local project origin and never transformed to SVY21.
- Disciplines using different base points, so that the federated model does not align.
- Level values expressed relative to a project datum instead of SHD.
- Site and survey models that use a different coordinate reference system from the building models.
The corrective step is to agree the coordinate setup at project initiation, publish it in the BIM Execution Plan, and have every discipline verify its origin against the shared reference before the first coordination exchange.
Discipline models, federation and the submission package
Separate discipline models are accepted. The CORENET X guidance confirms that models from different disciplines can be submitted separately and that the Collaboration Platform federates them. A federated model, as defined in the Code of Practice, compiles multiple models from different disciplines or project sections into a single, complete project model, supporting concurrent authorship and multidisciplinary coordination. Federated models are geo-referenced to SVY21 and SHD in the same manner as individual models.
The total size of all models in a single submission should not exceed 2 GB, according to the Code of Practice webinar materials. Large projects should plan model splitting by discipline or zone, and remove unneeded geometry and unused library content before export.
Typical package contents
The typical submission package for a Construction Gateway submission includes the items below.
| Item | Notes |
|---|---|
| Architecture IFC+SG model | Geo-referenced |
| C&S Engineering IFC+SG model | Geo-referenced |
| M&E Engineering IFC+SG model | Geo-referenced |
| 2D drawings | Accompany the models |
| Design calculation reports | Supporting document |
| Other supporting documents | For example B-Score BDAS forms, Site Investigation reports and Pollution Control Study reports |
The contents of each gateway differ, so the package should be confirmed against the current CORENET X guidance for the gateway concerned. For the broader process on electronic plans, see our CORENET X submission guide for electronic building plans.
Validating the model before submission
Validation is the step that most directly determines whether a submission proceeds without avoidable clarifications. Three layers apply.
Authoring-side checks. The CORENET X third-party application listing describes an IFC+SG validator that extracts all elements from the model and checks whether IFC+SG parameters have been added to the corresponding BIM components. This helps QPs identify parameters missed when mapping data into the proprietary BIM model.
IFC file checks. A web-based validator, as described on the CORENET X authoring tools page, automatically checks IFC files against CORENET X requirements before submission, identifies missing or incorrect IFC+SG information, and supports validation of federated models across multiple disciplines.
Agency-side checks. The Automated Model Checker (AMC) is a rules-based engine that lets practitioners validate BIM models for quality and regulatory compliance before actual submission. According to the CORENET X Connect briefing, Agency Processing Officers review AMC-generated results after formal submission and before issuing response letters. The same briefing states that agencies will collaborate to respond to industry collectively within 20 working days.

Because the officers review the AMC results, a model that has already passed the same checks internally enters review with its data issues resolved. The Code of Practice is also complemented by the IFC+SG Resource Kit, which provides technical templates and help resources from key proprietary BIM software for generating IFC+SG models. Our review of top BIM tools for Singapore projects addresses tool selection.
Pre-submission checklist
- Confirm applicability. Check GFA against the 5,000 m² threshold and confirm the submission commencement position against the URA circular.
- Fix the governing documents. Record the Code of Practice edition, the Excel Mapping File version and the Glossary of Identified Components version in the BIM Execution Plan.
- Set coordinates. Establish SVY21 (EPSG: 3414) and SHD for all disciplines at the outset.
- Map before modelling. Add IFC+SG parameters to components as they are created, not at export.
- Export per discipline. Produce separate Architecture, C&S and M&E IFC models where that suits the workflow.
- Validate each file and the federation. Resolve missing parameters, incorrect controlled values and alignment errors.
- Check file size. Keep the combined total within 2 GB.
- Assemble supporting documents. Include 2D drawings, calculation reports and any gateway-specific reports.
- Have the QP lodge. Submission is restricted to QPs with a valid Practising Certificate.
For a structured quality process, our 7-phase BIM model QA checklist and the CORENET X requirements checklist for 5,000+ sqm projects expand on these steps.
Our perspective
Our experience of statutory submissions is that delay originates in data, not in drawings. A model that is geometrically complete but missing controlled values or correct coordinates will generate clarifications regardless of how well the design has been coordinated.
For that reason we treat IFC+SG compliance as part of the design process. The mapping file is read at project initiation, the coordinate setup is agreed across disciplines before the first exchange, and each discipline model is validated before it joins the federated model. Our multidisciplinary PE team and single-point statutory coordination are designed to keep that discipline consistent across Architecture, C&S and M&E.
We also regard the gateway sequence as a programme matter. With COP Edition 4.0 applying to all new gateway submissions from 1 January 2027, teams benefit from a coordinator who tracks edition changes and authority requirements across BCA, URA, SCDF and the other agencies in one place. Our stated authority clearance rate of 99% reflects this emphasis on transparent requirements and early verification.
Aman
How Aman Engineering supports CORENET X submissions
Aman Engineering Consultancy provides authority approvals, PE endorsements and 3D BIM services for developers, construction firms and building owners in Singapore. Our team coordinates statutory submissions across the relevant agencies, and our BIM capability covers model production and shop drawings for multidisciplinary projects.

To discuss a project, review our 3D BIM services or contact us through the Aman Engineering Consultancy website.
FAQ
What is the difference between IFC and IFC+SG?
IFC is the open international schema for exchanging building data. IFC+SG is its extended Singapore version, which adds representations for local regulatory requirements. CORENET X supports the IFC4 Reference View including IFC+SG, as stated by the CORENET X support centre.
Is IFC+SG mandatory for every project?
No. IFC+SG is mandatory for projects with GFA of 5,000 m² and above. Projects below that threshold may use 2D format or lightweight BIM, according to the URA CORENET X page. Confirm the position for the specific project and gateway before submission.
Can each discipline submit its own model?
Yes. Separate discipline models can be submitted and the Collaboration Platform federates them into a single project model. Every model must still use the same SVY21 and SHD reference so that the federated model aligns.
Which coordinate system must models use?
Models must use Singapore SVY21 (EPSG: 3414) for Easting and Northing and the Singapore Height Datum for height, as set out in the CORENET X model setup guidance.
How long do agencies take to respond?
Agencies have stated that they will respond to industry collectively within 20 working days for CORENET X submissions, per the CORENET X Connect briefing. Our guide to the BCA building plan clearance timeline discusses programme planning.
Sources
- CORENET X: What is IFC+SG
- CORENET X support: IFC format supported in submissions
- URA circular DC26-08: Updates to CORENET X implementation plan
- URA: CORENET X
- CORENET X: Code of Practice
- CORENET X: IFC+SG Data Structure
- CORENET X: IFC+SG Excel Mapping File
- CORENET X: About the Code of Practice
- CORENET X: Checking levels (z coordinates)
- CORENET X: Code of Practice webinar, 15 June 2023
- CORENET X: Typical submission package
- CORENET X: Third-party apps
- CORENET X: Modelling and authoring tools
- CORENET X Connect: Prepare for mandatory implementation