BIM in Singapore: CORENET X, IFC, Coordination and Digital Submission Guide
Singapore’s CORENET X portal is the one-stop digital shopfront for building works approvals. This guide summarises official phased dates, IFC+SG BIM submissions, coordination implications, and where firms should verify requirements on government sites.
Singapore’s building works approvals are moving through CORENET X, the one-stop digital shopfront co-led by the Building and Construction Authority (BCA) and the Urban Redevelopment Authority (URA). This guide is a reading aid for architecture, engineering and construction teams who need to connect BIM production — including IFC exchange and coordination — to official digital submission facts. It is not a substitute for circulars, the CORENET X Code of Practice, or legal advice. Where this article states dates and thresholds, they are taken from official public materials. If a seller or a blog adds extra local “BIM laws,” ignore them until you see them on a government site.
CORENET X is described by the agencies as a one-stop integrated digital shopfront for approval of building works. It is intended to move an agency-centric journey toward a customer-centric one, with a redesigned regulatory approval process. Official communications describe streamlining many approval touchpoints across regulatory agencies into key gateways under Regulatory Approval for Building Works (RABW). Co-leading agencies are BCA and URA, alongside other agencies named in the circulars (including NParks, SCDF, LTA, PUB, NEA and SLA, with HDB and JTC as public sector developers, and GovTech support). For the full agency list and the process description, use the circular, not a paraphrase in a meeting.
Industry support listed in official outreach has included a CORENET X Code of Practice, a Good Practices Guidebook, training, a training environment, and mentions of Productivity Solutions Grant support for BIM software and IFC+SG courses. Those schemes have their own eligibility rules. This article does not expand them beyond noting that official pages are the source.
Official phased mandatory dates
URA circular URA/PB/2025/07-DCG (10 September 2025), published as a reminder consolidating earlier information, sets out the phased mandatory submission timeline. The same dates appear on the CORENET X portal messaging.
1 October 2025: Mandatory CORENET X submission for all new projects with gross floor area (GFA) at or above 30,000 square metres.
1 October 2026: Mandatory CORENET X submission for all new projects, regardless of GFA.
1 October 2027: Mandatory onboarding to CORENET X for all ongoing projects. Official footnotes describe ongoing projects in relation to equivalent clearances for Design Gateway (for example Provisional Permission, DC clearances). Read the circular’s footnote rather than inventing which live sites are in or out.
Projects below a given threshold before their mandatory date have been encouraged in official text to familiarise themselves early. Voluntary or assisted onboarding has been part of the transition story. Do not treat encouragement as a substitute for the mandatory dates that apply to your category.
If your project sits near a GFA threshold, the definition of GFA and of “new project” is an official question, not a BIM modeller’s guess. Ask the qualified person and the agencies’ published definitions.
BIM submissions, GFA 5,000 m2, and IFC+SG
Official CORENET X implementation material states that requirements for BIM submissions remain unchanged and only apply to projects with new GFA at or above 5,000 square metres. This article does not add extra BIM-submission triggers.
All BIM submissions made through CORENET X are required to adopt the openBIM Industry Foundation Classes standard with Singapore local addition, referred to in official text as IFC+SG (also discussed in industry and agency materials as IFC-SG). IFC is the international openBIM standard developed by buildingSMART International and is also an ISO 16739-series standard. IFC+SG is an addition to that open standard to cater for local regulatory needs. Native Revit or other native files are not described in those circulars as the CORENET X BIM submission format.
A related official point in URA circular material on implementation is that BIM submission in IFC-SG format is described as mandatory for new erections or major addition and alteration (A&A) projects with new GFA of 5,000 m2 or more. Read the circular you are relying on for the exact project types. Do not extend that sentence to every small works job.
Official communications also distinguish CORENET X portal onboarding (the shopfront for submissions generally) from BIM submission (the model-based IFC+SG package where BIM submission applies). A project can be required to use the portal because of the 2025–2027 dates above, while BIM submission remains tied to the 5,000 m2 new GFA rule as officially stated. Do not collapse those two facts into “every CORENET X job needs a full BIM model.”
What this means for coordination and production
If your project requires BIM submission, your production pipeline must include IFC export, mapping to required IFC entities and Singapore property sets using official mapping resources, and validation in the tools the portal provides (official materials refer to model checking on the submission path). That is extra to ordinary project clash detection. A Navisworks clash-free native model is not automatically an IFC+SG-valid submission.
The BIM Execution Plan should name: whether CORENET X is in scope, whether BIM submission is in scope under the 5,000 m2 rule, the IFC+SG mapping responsibility, software versions, and who runs the official checker. Freelancers should not be asked to “guarantee approval.” They can be asked to follow the published mapping and to fix checker reports you assign to them.
Coordination among architecture, structure and Mechanical, Electrical and Plumbing (MEP) still matters because a submission model that cannot be internally consistent will fail checks or fail the project later. Use ordinary coordination and clash detection. Do not skip project coordination because a regulatory checker exists; they are different tests.
How to brief a specialist without inventing rules
Write: project GFA, whether it is new or ongoing, which mandatory date applies, whether new GFA is at or above 5,000 m2 for BIM submission, Revit (or other) version, and that mapping must follow official IFC+SG files. Attach the circulars. Forbid extra “local BIM codes” that are not in those documents.
It will not list additional GFA thresholds. It will not invent fire, parking, or planning rules as BIM rules. It will not say CORENET X replaces QP responsibility. It will not say 4D/5D is mandatory. It will not say every renovation needs Scan to BIM for submission. It will not quote unofficial “pass rates.”
Quality checklist for a Singapore digital-submission BIM package (process, not extra law)
Current circulars read (date-stamped in the BEP)
Portal date category identified (2025 / 2026 / 2027 as applicable)
BIM submission in/out under official 5,000 m2 new GFA rule
IFC+SG mapping owner named if BIM submission is in
Native coordination still run
Official checker reports assigned
No guarantee-of-approval language in the specialist contract
Authoring native, exporting IFC+SG, and not mixing the jobs
Most Singapore building teams still author in tools such as Revit. CORENET X BIM submission, where it applies, is described officially as openBIM IFC with Singapore addition. That means a production pipeline with two quality gates: native coordination quality, and export/mapping quality. A specialist who is excellent at native clash grouping may still fail an official model check because property sets are missing. A specialist who can fill property sets may still export geometry that no longer matches the coordinated native file. Buy both gates or accept the gap in writing.
Keep native clash detection. The official checker is not your hanger coordination meeting. The official checker is not your room schedule for a client. Use clash detection for construction risk and the official tools for the submission path.
Do not submit a design-option playground. Freeze a submission model version, name it, and map that version. If architecture changes after freeze, that is a new submission decision, not a quiet overwrite.
Mapping files, entities and the temptation to invent parameters
Official CORENET X resources include mapping guidance and related code of practice material. Follow those files. Do not create a parallel parameter named something that “sounds SG” and hope. Do not copy a friend of a friend’s shared-parameter file from 2023 without checking it against the current official pack. Dates matter; circulars get updated. The BEP should record which official mapping pack and which Code of Practice edition were used.
IFC schema version and Model View Definition matters in any IFC pipeline. Use what the official documentation currently requires, not what a freelancer’s exporter defaults to. Test a small model first: one storey, a few types, a known room, a known duct. Then scale. Marketplace Milestone A should be that small model through the official checker, not a whole tower export on the night before a deadline.
People, portal accounts and the limit of a marketplace specialist
Portal onboarding, company accounts, and Qualified Person roles are organisational and professional issues. A freelance modeller can prepare files and fix checker items assigned to modelling. They cannot become your QP by downloading Revit. Write the RACI: who uploads, who accepts comments from agencies, who interprets a planning condition, who remaps IFC. If the RACI is blank, the specialist will be asked to do all of it at 2 a.m. and it will still not be valid.
Training: official outreach has pointed to courses and a training environment. Sending a freelancer to public training may be worthwhile; it is not a substitute for reading the circular that applies to your GFA and your new-versus-ongoing status.
Coordination implications unique to a submission freeze
A submission freeze can disagree with a construction model that is still moving. Some teams branch a “regulatory” model. Branching needs a rule for which fixes flow back. If a checker demands a property on a wall type, that fix should usually return to the native library. If a checker demands a simplification that would hurt hangers, do not “simplify” the construction model; fix the export view. The BEP should say that construction coordination remains the construction model’s job.
MEP in IFC is historically easy to damage in export (systems, spaces, connectors). Budget an MEP export test even if architecture passed. Do not assume one discipline’s success is another’s.
What buyers should attach to a BIMProSG brief in Singapore
The circular PDF (or a link to the URA/BCA page), the project’s GFA statement from the qualified team, whether BIM submission applies under the official 5,000 m2 new GFA rule, the authoring software version, and whether the specialist is mapping, modelling, or only fixing checker reports. Do not attach a rumour slide from a seminar as if it were a circular. Seminar slides go out of date; circulars are the reference.
Gateway thinking without inventing extra gates
Official CORENET X communications describe a redesigned process with key gateways under Regulatory Approval for Building Works. Your project team should read those gateway descriptions in the Code of Practice and circulars. This article will not invent additional gateways, rename them, or assign unofficial BIM LOD numbers to them. If a seminar slide shows extra steps, check them against the current official PDF before you put them in a freelancer’s brief.
What you can put in a brief without inventing law: we will freeze a model for this official gateway; we will export IFC+SG using the official mapping pack dated X; we will run the official checker; we will assign checker items to named roles. That is production planning against official documents.
Assisted onboarding and voluntary periods
Agencies have described voluntary adoption, pilots, and assisted onboarding as part of the transition. Those programmes have their own sign-up paths on official sites. A marketplace specialist cannot enrol your company in an agency programme by modelling faster. If you are before your mandatory date, official text has encouraged familiarisation. Use the training environment if it is offered. Do not treat a training upload as a live statutory submission.
OpenBIM literacy on the team
Someone on the buyer side must understand IFC well enough to see whether an export dropped rooms or systems. If nobody does, hire that as a small review package, separate from modelling. Otherwise you will approve a native NWD and fail an official check a week later. BIMProSG can host both packages. They should not be the same milestone unless the same person is truly doing both.
buildingSMART’s IFC is international. IFC+SG is the local addition for regulatory needs as official text states. Training a team only on native Revit worksharing is necessary but not sufficient when BIM submission applies.
Coordination still uses English, grids and meetings
Digital submission does not remove clash meetings. It does not remove hanger decisions. It does not remove gravity. Teams that pause coordination to “focus on CORENET” often return to a construction model that has drifted. Keep the Friday native federation. Branch the submission export. That is process, not extra regulation.
Briefing language that stays inside official facts
Safe: cite the three dates, the 30,000 m2 new-project threshold in 2025, all new projects in 2026, ongoing onboarding in 2027, BIM submission remaining for new GFA ≥ 5,000 m2, IFC+SG for those BIM submissions through CORENET X. Unsafe: extra GFA numbers, unofficial LOD mandates, fake pass rates, “AI will auto-approve.” Paste the safe list into project postings. Point to https://info.corenet.gov.sg and https://www.ura.gov.sg.
Keeping submission and construction models from poisoning each other
A construction model will contain hangers and temporary objects that a regulatory export may not want. Use view/export filters or a branch. Do not delete hangers from the construction model to satisfy an export. Do not add fake walls that help a checker but lie to site. Official mapping should be satisfied by correct properties and entities, not by theatrical geometry. If a checker item seems to demand theatrical geometry, raise it through official enquiry channels, not through a silent model lie.
GFA statements belong to the qualified team
Modellers should not calculate statutory GFA to decide whether BIM submission applies. They should receive the project’s stated category from the qualified persons and the circulars. If someone asks a freelancer “is our GFA over 5,000?”, the freelancer should point back to the design team. This article’s thresholds are for reading official dates, not for substituting a GFA calculation.
After 1 October 2026 and 2027
Plan staffing for portal literacy, not only for modelling peaks. Ongoing-project onboarding in 2027 needs a reading of the footnote on Design Gateway equivalent clearances. Put a reminder in the BEP to re-read the portal before those dates in case circulars are updated. This article is a snapshot against the cited public circulars; the PDFs win later.
CTA: work from circulars, then hire production support
Download the current CORENET X material, then hire or post a package that matches those facts. BIMProSG is a marketplace, not an agency. For modelling and IFC help, also see Revit modeling and CAD to BIM if your sources are drawings.
FAQ
Does a 4,000 m2 new project need BIM submission? Official material says BIM submission requirements remain for projects with new GFA ≥ 5,000 m2. A 4,000 m2 project may still fall under CORENET X portal mandatory dates depending on year and whether it is a new project. Read the dates above and the circular; do not treat this FAQ as a ruling.
Is Revit banned? Official BIM submission format through CORENET X is IFC+SG. Teams may still author in Revit and export. Confirm export mapping.
When is a small project on the portal? From 1 October 2026, mandatory CORENET X submission for all new projects regardless of GFA, per the circular table. Until then, the 1 October 2025 mandate is for new projects ≥ 30,000 m2 GFA.
What is an “ongoing” project in 2027? See the circular footnote on Design Gateway equivalent clearances. Do not guess from this article alone.
Can a freelancer submit on our behalf? Submission authority follows professional and portal account rules. A modeller can prepare files; QP and account roles are official.
Where do we ask questions? Official channels include the CORENET X site and the enquiry path published by the agencies (circulars have pointed to go.gov.sg links). Use those, not a forum rumour.
Does IFC+SG replace clash detection? No. Different purpose.
Sources and reference notes
Primary sources: CORENET X portal https://info.corenet.gov.sg ; URA circular “CORENET X : MANDATORY SUBMISSIONS STARTING FROM 1 OCTOBER 2025 (FOR NEW PROJECTS ≥ 30,000 SQM GROSS FLOOR AREA)” (URA/PB/2025/07-DCG, 10 September 2025) at https://www.ura.gov.sg/Corporate/Guidelines/Circulars/dc25-07 ; related URA circulars on CORENET X implementation (including dc25-01 as listed on URA’s site); BCA circular PDFs linked from the CORENET X document library describing IFC+SG and the unchanged BIM submission GFA ≥ 5,000 m2 statement. buildingSMART / ISO 16739 for IFC as an international standard. Always download the current PDF. If this article and a circular disagree, the circular wins.
Image brief
A simple timeline graphic: 1 Oct 2025 (≥ 30,000 m2 new), 1 Oct 2026 (all new), 1 Oct 2027 (ongoing onboarding), plus a separate callout: BIM submission still tied to new GFA ≥ 5,000 m2. Caption sources as BCA/URA. No fake “compliance score” UI.