Call Us/Whatsapp Us: +65 8385 9933 | Email: aman@amanengineering.com.sg for inquiry and free quotation

CORENET X Migration: Singapore Teams’ 2026 Readiness Checklist

BIM coordinator checking a building model

Projects with a gross floor area of 30,000 square meters or more must already submit through CORENET X as of October 1, 2025, and every new project at 5,000 square meters or above joins them from October 1, 2026. The immediate action for any project team is to confirm the project’s GFA category, secure Corppass or Singpass for Business access, and register for the training environment before a submission deadline forces the issue.

TL;DR:

  • All ongoing projects, regardless of size, must onboard by October 1, 2027; projects already mid submission may finish in CORENET 2.0, subject to BCA confirmation.
  • Projects below 5,000 square meters can adopt voluntarily, giving teams a full submission cycle to learn the gateways before requirements apply.
  • Mandatory submissions require coordinated IFC+SG discipline models with prescribed parameters; run schema validation and the Automated Model Checker on draft exports to catch errors early.
  • Agencies issue one consolidated response per gateway, so a single unresolved query can block clearance; assign a Submission Coordinator to track agency responses.
  • Corppass or Singpass for Business access must be authorized for specific staff, so request permissions weeks before submission rather than days.
Com
amanengineering.com.sg
Prepare Your Team for CORENET X
Aman Engineering Consultancy supports statutory submissions, BIM and regulatory approvals for construction projects in Singapore.

Explore engineering services

Table of Contents

What CORENET X Is and How It Changes Submissions

CORENET X is the Building and Construction Authority’s successor to CORENET 2.0, structured around the Regulatory Approval for Building Works (RABW) framework rather than a patchwork of agency-specific portals. Instead of routing separate 2D drawings to separate agencies, we now submit a coordinated, federated BIM model through gateways that multiple agencies review together. Mandatory BIM submissions must use the openBIM IFC+SG standard, Singapore’s localized Industry Foundation Classes schema, which standardizes how building elements and their data are described across disciplines.

The portal itself brings several changes that affect daily workflow:

  • A built-in BIM viewer replaces separate desktop software for agency reviewers checking submitted models.
  • The Automated Model Checker (AMC) runs schema and quality checks before a submission reaches a human reviewer.
  • A shared collaboration space lets structural, architectural, and M&E teams exchange issues through BIM Collaboration Format (BCF) files rather than email threads.

Mandatory Timeline and Who Is Affected

The rollout follows three fixed dates set out in the BCA implementation circular:

  • October 1, 2025: mandatory for new projects with GFA at or above 30,000 square meters.
  • October 1, 2026: mandatory for new projects with GFA at or above 5,000 square meters, effectively covering all new projects at this threshold.
  • October 1, 2027: all ongoing projects, regardless of size, must onboard to CORENET X.

Projects below 5,000 square meters can still choose to submit voluntarily ahead of the mandatory date, and the URA circular DC23-01 confirms that smaller projects may use the openBIM IFC+SG standard on a voluntary basis before it becomes compulsory for them. Early adoption gives a project team a full submission cycle to learn the gateway process without a regulatory deadline bearing down. Projects already mid-submission under CORENET 2.0 at a threshold date are generally allowed to complete that submission on the old system, but teams should confirm their specific transition arrangement with BCA rather than assume continuity.

Submission Requirements: IFC+SG, Model Content, and File Workflows

Meeting CORENET X requirements means treating the BIM model, not the drawing set, as the primary submission artifact. The CORENET X Code of Practice sets out what a compliant IFC+SG export must contain and how disciplines should structure their models.

  1. Export every mandatory discipline model in IFC+SG format, with the parameters and minimum dimensions the Code of Practice specifies populated against each object.
  2. Decide what belongs in the coordinated federated model versus what can go into an independent submission; space provision for M&E equipment is typically mandatory in the model, while granular equipment specification details can often follow later as an independent submission.
  3. Follow the naming and unit conventions in the Code of Practice consistently across disciplines so the federated model assembles without manual rework.
  4. Run the model through IFC schema validation and the Automated Model Checker before formal submission, resolving flagged items through BCF exchanges with the relevant discipline lead.

Simplified geometry is acceptable in many cases. A tree, for instance, can be modeled as a simplified “lollipop” shape as long as the required IFC+SG parameters and minimum dimensions are present, which keeps file sizes manageable without sacrificing the data agencies need.

Pro Tip: Run the Automated Model Checker on a draft export well before your internal deadline. Catching a missing parameter early costs an hour; catching it after formal submission can cost a full review cycle.

RABW Gateways and the Joint Submission Workflow

CORENET X organizes regulatory approval into three sequential gateways, and a project cannot advance to the next one until the current gateway clears. The Code of Practice describes how agencies coordinate their review within each stage:

  • Design Gateway: covers the core design submission and is mandatory for every project moving through RABW.
  • Piling Gateway: an optional gateway for projects with piling works that need early structural clearance ahead of the main construction package.
  • Construction Gateway: covers the detailed construction submission, including the cross-disciplinary coordination elements each discipline must contribute.
  • Independent submissions: certain discipline-specific items, such as detailed M&E equipment specifications, can still be submitted outside the main gateway package once the coordinated items are cleared.

Agencies review their respective disciplines within each gateway but issue a consolidated response, which means one agency’s outstanding query can hold up clearance for the whole gateway. A named Submission Coordinator, working alongside the qualified person for each discipline, becomes the practical point of contact for tracking which agency has or has not responded.

Project Readiness Checklist: Step-by-Step Pre-Submission Actions

A structured lead-in reduces the chance that a single missing authorization or malformed export derails a gateway submission. We recommend working through these steps in sequence rather than in parallel wherever dependencies exist:

  1. Set up Corppass or Singpass for Business access for the firm and have the Corppass administrator authorize the specific staff who need the CORENET X Industry Portal service. Do this weeks, not days, before any submission is due.
  2. Register the project team for the CORENET X training environment and, where useful, request assisted onboarding to walk through the portal with BCA support before a live submission.
  3. Allocate roles clearly: a qualified person per discipline, a Submission Coordinator, and a BIM coordinator responsible for model federation and QA.
  4. Map out gateway deliverables against your project program, scheduling model federation and QA checkpoints ahead of each gateway rather than immediately before it.
  5. Run BIM QA in sequence: confirm export settings, run local IFC validators, federate the models, run them through the Automated Model Checker, and resolve every BCF item before formal submission.
  6. Confirm supporting documents are in the correct format, including site investigation data in both PDF and AGS formats and design calculations with annexes, and check payment arrangements for the submission.

Pro Tip: Treat the training environment as a dress rehearsal, not an optional extra. Teams that run a full mock submission before their first live gateway consistently surface formatting issues that would otherwise appear as AMC failures.

Common Pitfalls and How to Avoid Last-Minute Delays

Most CORENET X delays trace back to a small set of avoidable mistakes rather than genuine technical complexity. Key updates to CORENET X draw on lessons from pilot projects showing that teams new to IFC+SG often need more time than expected at the Design Gateway for clash detection and parameter population, which argues for budgeting extra coordination time rather than compressing it.

  • Underestimating multidisciplinary coordination time and leaving clash resolution to the final days before a gateway deadline.
  • Requesting Corppass or Singpass authorization too late, which delays the formal declaration step even when the model itself is ready.
  • Submitting IFC exports with missing IFC+SG parameters, which triggers Automated Model Checker or schema failures and forces a resubmission cycle.
  • Treating gateway preparation as strictly sequential when some Piling and Construction Gateway items can be prepared concurrently without risk.

Using a voluntary early submission, even on a smaller project below the mandatory threshold, gives a team real experience with these failure points before a hard deadline is on the line.

How Aman Engineering Consultancy Supports CORENET X Migration

We prepare IFC+SG models, run 3D BIM coordination across structural, architectural, and M&E disciplines, and manage statutory submission coordination through the RABW gateways on behalf of property developers and construction firms. We have experience coordinating submissions across multiple agencies, giving us familiarity with how agencies review gateway packages in practice. Before reaching out, have your project’s GFA, current model formats, and target gateway schedule ready so we can scope the work accurately.

How Aman Engineering Consultancy Supports CORENET X Migration — overview diagram

A Practitioner’s View on the CORENET X Transition

The firms that move through CORENET X with the least friction are the ones that treat training and voluntary early submissions as preparation, not paperwork. A project that resolves its clash detection and parameter gaps at a small, low-stakes submission avoids repeating those mistakes at the Design Gateway of a 30,000 square meter project. CORENET X rewards the teams that coordinate disciplines upfront rather than at the review stage.

— Aman

Get Help With Your CORENET X Readiness Review

Moving a project onto CORENET X touches model preparation, statutory coordination, and gateway sequencing all at once, and getting any one of those wrong costs time at the worst possible stage of a project. We offer 3D BIM model preparation built around IFC+SG export requirements, alongside statutory submission coordination through Authority Approvals for teams managing Design, Piling, and Construction Gateway packages.

Com

If your project sits near the 5,000 or 30,000 square meter thresholds, or your ongoing project needs to onboard before October 2027, contact us for a CORENET X readiness review and we will map out your gateway schedule, model preparation needs, and submission coordination plan before your deadline arrives.

FAQ

What is CORENET X and how is it different from CORENET 2.0?

CORENET X is Singapore’s current regulatory submission portal, built around the Regulatory Approval for Building Works (RABW) framework with three sequential gateways instead of separate agency submissions. It requires coordinated, federated BIM models in the openBIM IFC+SG standard for mandatory projects, rather than the largely drawing-based submissions used under CORENET 2.0.

When does my project need to migrate to CORENET X?

Your project must submit through CORENET X from October 1, 2025 if its GFA is 30,000 square meters or more, and from October 1, 2026 if its GFA is 5,000 square meters or more. All ongoing projects, regardless of size, must onboard by October 1, 2027.

What is IFC+SG and why does it matter for submissions?

IFC+SG is Singapore’s localized version of the Industry Foundation Classes openBIM schema, and it is the mandatory format for BIM submissions on qualifying projects. It standardizes how building elements and their data are described so agencies can review a single coordinated model instead of separate discipline drawings.

What happens if my IFC model fails the Automated Model Checker?

The Automated Model Checker flags schema errors or missing IFC+SG parameters and returns them as BCF issues for the responsible discipline to resolve before resubmission. Running the checker on a draft export ahead of the formal deadline, as we recommend to project teams, avoids discovering these issues during a live submission window.

Can my firm help prepare models and manage the submission for us?

Yes. We prepare IFC+SG compliant 3D BIM models and coordinate statutory submissions through the RABW gateways, drawing on our experience coordinating approvals across multiple Singapore government agencies.

Sources

Leave a Reply