BIM Execution Plan Template for Singapore Projects: Free Download (CORENET X Ready)

Before the first model gets opened, someone needs to answer: who models what, to what level of detail, in what software, and how does it all get submitted? That's the BEP. In Singapore, CORENET X has made this more pressing — BCA now requires submissions in IFC+SG (Singapore's own file format) at fixed project gateways. Getting these answers documented early isn't optional — it's the difference between a project that runs smoothly and one that scrambles at every submission date.

What is a BEP?

A BIM Execution Plan is a project-specific document that defines how Building Information Modelling (BIM) will be delivered — who models what, to what Level of Detail (LOD), when, in what software, and how models get coordinated and submitted. It's typically the supply chain's formal response to the client's Employer's Information Requirements (EIR). When no EIR exists (which still happens on many Singapore projects), the BEP is prepared proactively by the lead consultant or contractor to align the team regardless.

The BEP governs the full delivery setup: software stack and version control, roles and responsibilities across all disciplines, shared project folder (Common Data Environment, or CDE) structure and access, file naming conventions, and the submission workflow for CORENET X. It's not a document you file and forget — it gets updated at each project phase as team membership, scope, and requirements evolve.

Think of it as the project's BIM constitution. Everything from clash detection cadence to LOD expectations to who clicks "submit" in the CORENET X portal should be traceable back to it.

Built for Singapore Projects

A generic BEP template won't cut it here. Singapore has its own regulatory requirements and submission infrastructure that don't exist in other markets — and if your BEP doesn't address them explicitly, you'll find out the hard way at submission time.

CORENET X is not like other BIM submission systems. Singapore's BCA requires project teams to submit BIM models through CORENET X at three gateways: Design, Construction, and Completion. Each gateway requires models in IFC+SG format — not standard IFC, not Revit native files. If your BEP doesn't document the IFC+SG export and validation workflow from the start, teams often prepare generic BIM models and then scramble to convert and fix them under submission deadlines.

SVY21 coordinates are mandatory. Singapore uses its own national coordinate system (SVY21). Models submitted to CORENET X must be georeferenced correctly — wrong coordinates will fail BCA validation. This needs to be set up at the project's first modelling session, not retrofitted at submission time. The BEP is where that requirement gets documented and assigned.

BCA has specific LOD and data requirements by submission stage. What property data needs to be in the model, and to what Level of Detail, is defined by BCA's CORENET X Code of Practice — not just by the design team's preferences. A Singapore BEP needs to map these requirements to specific disciplines and phases so no one is surprised at gateway.

The Singapore BIM Guide V2.0 sets the baseline. Most international BEP templates reference ISO 19650. Singapore projects also need to reference the Singapore BIM Guide V2.0, which sets local standards for model content, file naming, and CDE structure. A BEP that only cites ISO 19650 may miss Singapore-specific requirements that BCA or the client will expect.

Multi-party projects need explicit role assignment. Singapore's construction market often involves multiple consultants, a main contractor, and specialist sub-contractors — each working in different software on different parts of the model. Without a Singapore-specific BEP that assigns CORENET X submission responsibilities explicitly, it's common for everyone to assume someone else is handling it.

The template available below is built around these requirements. It's not a generic ISO 19650 document adapted for Singapore — it's written for Singapore projects from the ground up.

Who Owns the BEP?

The BEP is a living document. Ownership shifts as the project moves through its phases, and the template is designed to reflect that.

Design phase: The lead consultant — architect or engineer, depending on the project type — owns the BEP. They set the LOD progression, nominate the software stack, configure the CDE, and define the clash detection and coordination workflow. Sub-consultants are expected to comply. The BEP at this stage is detailed enough to govern design coordination and the CORENET X design-stage submission.

Construction and handover: As the main contractor comes on board, BIM ownership often transfers. The main contractor takes over BEP maintenance — managing sub-contractor model compliance, coordinating trade clashes, running the CORENET X submissions at construction and completion stages, and delivering the as-built model. The consultant models don't disappear; they become reference inputs for the contractor's coordination workflow.

Template Section 9.2.1 has a decision table for assigning the BIM Manager role by contract type — design-and-build, traditional procurement, or main contractor-led BIM. It's worth filling this in explicitly at project kick-off to avoid ownership disputes later.

Why It Matters

Seven reasons — all grounded in what actually goes wrong on Singapore projects when the BEP is missing or treated as a formality.

1. Identifies BIM goals upfront. Design coordination, construction sequencing, CORENET X compliance, FM handover — these require different models, different LOD, different data. Without agreed goals documented before work starts, teams model for the wrong purpose and the rework bill starts accumulating from week one.

2. Holds parties accountable. The responsibility matrix (RACI — Responsible, Accountable, Consulted, Informed) in the BEP assigns every major BIM activity — model authoring, clash review, IFC export, CDE management, submission sign-off — to a responsible party. When a sub-contractor misses a delivery deadline or a model fails validation, the resolution process starts with the document, not a group chat argument.

3. Controls BIM costs. The BEP defines what's in scope: does the contractor need a surveyor for progress tracking? Is 4D simulation required? Does the Mechanical, Electrical and Plumbing (MEP) model need to be LOD 400 or LOD 350? Scope creep on BIM deliverables is expensive, and it's almost always the result of undocumented assumptions. Locking scope in the BEP early keeps the budget predictable.

4. Prevents deliverable disputes. What counts as "as-built"? Does the FM handover model include equipment data? Is the contractor responsible for structural connection details or is that the engineer's scope? The BEP answers these before construction starts, so there's no argument at handover about what was included in the fee.

5. Defines the CDE and file structure early. Teams that agree on folder structure and naming conventions at project start spend far less time hunting for the right model version mid-project. Information chaos — coordinating against the wrong version, missing IFC files at submission — is almost always a file management problem. The BEP solves it before it starts.

6. Drives CORENET X readiness from day one. The BEP documents Singapore's BCA file format (IFC+SG) and the national coordinate system (SVY21) at project kick-off. That means the export process, validation steps, and submission responsibilities are assigned and understood before the first BCA submission checkpoint — not figured out at 11pm the night before submission.

7. Reduces rework from misaligned LOD expectations. Consultants and contractors often have different assumptions about who adds connection details, service penetrations, or slab edge conditions. The BEP's LOD matrix assigns responsibility by discipline and stage. Clarifying this early eliminates the rework that comes from discovering the assumption gap at coordination.

Key BIM Workflows

These are the four workflows that almost every Singapore project needs documented in the BEP. The template has dedicated sections for each.

Clash detection. Three review stages: soft clash (clearance envelopes, access zones, maintenance space), hard clash (elements physically overlapping), and sign-off checkpoint (all critical clashes resolved before model lock-off). The 8-test checklist covers Architecture vs Structure, Architecture vs MEP, Structure vs MEP, and MEP vs MEP by system. Without a defined process, clash detection becomes ad-hoc — different teams running different tests, no clear sign-off gate, locked-off models that still have critical clashes sitting in them.

CORENET X submission. The 6-step IFC+SG workflow:

1. Model QA
2. Export to IFC+SG using BCA-approved settings
3. Validate using Bimeco Validator (SVY21 coordinates, property completeness, file format compliance)
4. Resolve critical errors
5. Upload to CORENET X portal
6. Log the submission record in the CDE

The submission checkpoint is high-stakes — a failed validation delays the whole project. Documenting and assigning this process in the BEP means everyone knows the steps before they're under deadline pressure. For context on how CORENET X differs from CORENET 2, there's a separate article on the transition.

Model coordination meetings. Cadence (typically weekly during active design coordination, fortnightly during construction), attendance by discipline, and how clash reports are distributed and actioned. What gets reviewed at each meeting: clash report, delivery schedule status, and outstanding queries affecting models. Coordination meetings without a documented format tend to drift — the same clashes get raised every week without resolution.

CDE status workflow. Four stages, following project information stages as defined by ISO 19650 (the international standard for construction information management):

• WIP — work in progress, not for coordination
• SHARED — available for combined multi-discipline model review
• PUBLISHED — formally issued
• ARCHIVED — superseded

Teams that skip this structure end up coordinating against WIP models or issuing superseded drawings — both expensive mistakes.

Download the Template

Download BIM Execution Plan Template (PDF) — No registration required.

What's inside:

• 32 pages, 18 sections
• Appendices A–F with fill-in guides for BIM use cases, Level of Geometry matrix, modelling guidelines, and clash configuration
• CORENET X 6-step submission workflow
• ISO 19650-aligned shared folder structure and file naming convention
• Responsibility matrix (RACI) covering all project BIM roles
• 3-stage clash detection workflow with an 8-test checklist

For projects requiring CORENET X BIM submission support or full BIM management, we can customise the template for your specific team and programme.

Need the BEP filled in for your project? Send us an enquiry and we'll get back to you.