BIM Execution Plan (BEP): What It Is, What to Include and Why Projects Need One
A BIM Execution Plan (BEP) records how a project will use BIM: purposes, responsibilities, software, naming, Level of Development, coordination and deliverables. This guide explains what to include and how to keep a BEP usable.
A BIM Execution Plan (BEP) is the project’s written agreement for how building information modelling will be used: for what purposes, by whom, in which software, at which Level of Development, with which naming, coordinates, exchanges and quality checks. If the plan is only a copied template with another project’s name, it is not a plan. If the plan is twenty pages nobody opens, it is not a plan. A usable BIM Execution Plan (BEP) is short enough to be followed on a Friday publish and specific enough that a freelancer can model without guessing your origin.
This guide explains what a BEP is, what to include, how it relates to ISO 19650 without turning into theatre, and why even a two-week outsourced package needs one. Expand the acronym on first use in every buyer conversation: BIM Execution Plan. Read this with LOD, coordination, and outsourcing. If you need someone to draft or implement a BEP, post a project or hire a specialist on BIMProSG.
What a BIM Execution Plan is — and is not
A BIM Execution Plan (BEP) is an operating document. It tells authors how to name a file, where north is, which Revit version to use, when to publish, what a clash cycle includes, and who may accept a residual issue. It is not a marketing brochure about “digital twins.” It is not a substitute for a design contract. It is not automatically a legal BIM standard for a whole country.
Pre-appointment and post-appointment language appears in ISO 19650-related practice: a supplier may explain how they will meet information requirements, then a project BEP becomes the shared way of working. On a small marketplace job, that can be two pages. On a hospital, it can be a longer controlled document. Length should follow risk, not a page-count habit.
If you outsource without a BEP, the specialist will import habits from their last job: their worksets, their level names, their idea of LOD 300. You may like those habits. You may not. Either way they will not be yours unless you write them down.
Why projects need one even when everyone “knows BIM”
Everyone knows BIM until two models miss by a building length. Everyone knows BIM until Mechanical, Electrical and Plumbing (MEP) uses different level names from architecture. Everyone knows BIM until a freelancer upgrades Revit and your office cannot open the file. The BEP exists because memory is not a coordinate system.
Clients who will later ask for quantities, 4D, as-builts, or a regulatory IFC export are asking for decisions that must be made at the start: classification, element coding, parameter mapping. A BEP that postpones those decisions “until we need them” often postpones them until they are expensive. See and .
Singapore projects that will use CORENET X should not hide that in a footnote. Portal onboarding and IFC+SG mapping, where they apply, belong in the purposes and exchange sections. They still must follow official rules, not a freelancer’s folklore. See BIM in Singapore.
What to include: a practical contents list
Project and purposes. Building type, location, and the uses of BIM: coordination, drawings, fabrication, quantities, handover, submission. If a use is not listed, it is out of scope until you change the BEP.
People and responsibility matrix. Who authors architecture, structure, MEP. Who coordinates. Who accepts residuals. Who answers RFIs. Marketplace specialists named as roles, not as “help.”
Software and versions. Revit year, Navisworks, Recap, IFC schema as needed. Plugin policy: no undeclared plugins.
Coordinates, units, north. The origin story. Shared coordinates method. Who publishes. What to do if a consultant already published wrongly.
Naming. Files, levels, grids, types, views, issues. Examples, not only principles.
Level of Development table. By system, not a slogan. Level of Development versus Level of Detail distinguished. Link to the LOD article.
Folder and exchange events. When files are due, in what container, native and/or IFC. Cut-off times.
Clash matrix and meeting cadence. Or a pointer to a one-page matrix. See clash detection.
Revision and change. How drawing issues map to model updates. What is a new package.
Security. Who may download a point cloud of an occupied building. Subcontracting rules.
Handover. What the last milestone contains: native files, purge policy, parameter fills, as-built rule.
You do not need a chapter for each if the project is a single typical floor. You do need a sentence for each that could otherwise explode.
How to keep a BEP alive
Put it next to the publish folder. Version it. When a decision is made in a clash meeting (“we accept 15 mm grazing on insulation versus tray”), write it into the BEP or into a residual register the BEP points to. A BEP that is only updated at kickoff will be ignored by week six.
Do not paste entire ISO clauses if nobody will apply them. Do map: “information exchange on Fridays 3 pm, native RVT plus NWD, named as …” That is ISO-shaped behaviour without costume.
Freelancers should receive the BEP with the brief, not after they have modelled in the wrong version. Paying to rebuild a file because the BEP arrived late is a buyer-side cost. See hiring.
Common BEP failures
Copied hospital BEP on a house. No origin diagram. LOD 500 promised at concept. Clash matrix that says “all vs all.” Software versions omitted. Marketplace specialist not named, so they never see the document. Twenty pages of software screenshots and two sentences of responsibility. A BEP stored only in a proposal PDF that nobody can edit.
A BEP that tries to redesign the building (“all ducts shall be 200 mm below beams”) without the engineer’s agreement is a specification pretending to be a BIM plan. Keep design in design documents; keep information rules in the BEP.
Outsourcing and the BEP
On BIMProSG, attach the BEP to the project posting or to the service order notes. Milestone one can be “BEP confirmation plus sample zone.” If you have no BEP, buy a short one as a deliverable from a coordinator, then buy modelling. Do not buy modelling first and a BEP later unless you enjoy paying twice.
Protected payments should reference BEP clauses in the acceptance test: “file named per section 4, Revit 2024, shared coordinates per section 5, LOD table per appendix A.” That is how a BEP becomes commercial rather than decorative.
Quality checklist for a usable BEP
Purposes listed
Roles listed including reviewers
Software versions listed
Origin explained with a diagram or a grid reference
Naming examples
LOD by system
Publish calendar
Clash matrix or pointer
Change rule
Security sentence
Short enough that a new freelancer reads it
Pre-appointment versus post-appointment: keeping ISO language usable
ISO 19650-style practice often distinguishes what a supplier says they will do before they are appointed from the shared project BIM Execution Plan (BEP) after they are appointed. On a marketplace job this can be light: the proposal restates software, LOD, and naming; the project BEP then locks origin and Friday cut-off. On a hospital it can be heavy: information requirements, container structures, and formal exchange events. Use the weight that matches the risk. Copying the heavy version onto a family-creation package will ensure nobody reads it.
A freelancer’s proposal should not contradict the BEP they have not yet seen. Send the BEP, or a draft, with the invitation to bid. If you cannot, the first milestone is the BEP confirmation. Paying for a week of modelling in Revit 2025 when the office is on 2023 is a BEP failure that looks like a software failure.
Language to prefer: verbs and examples. “Publish federated NWD every Friday 15:00 SGT named Project_Discipline_YYYYMMDD.” Language to avoid: “The team shall endeavour to leverage BIM to world-class standards.” The second sentence cannot be used in a milestone test.
Origin, shared coordinates and the one diagram that saves the job
A BEP without an origin story will produce at least one model in the wrong place. The diagram can be ugly: a grid bubble, a survey mark, a statement of units, and who is allowed to publish coordinates. If a consultant already published a wrong origin, the BEP must say whether we relocate them or we all move. Freelancers arriving mid-job need that paragraph more than they need a logo page.
Units live here too. Millimetres versus metres, and the civil ground coordinate system versus the building internal origin. Mixed civil and building files are a classic BEP omission. If site is out of scope, say that the building origin is internal only and must not be “corrected” to a random map.
True north versus project north should be a sentence, not a debate in week eight. Rotate in the BEP, not in a modeller’s preference.
Naming examples beat naming principles
“Files shall be named logically” is not a rule. “AR_B1_L03_ARCH_2024.rvt” with a legend of tokens is a rule. Issue IDs, view names, workset names, and type names all need examples. A specialist who invents parallel names is not creative; they are non-compliant. A buyer who never examples names is inviting that invention.
Level names deserve a table: storey, elevation, and the string that must appear in every discipline file. “Level 2” versus “Lvl 2” versus “Second Floor” is a coordination bug that clash software cannot fix. Put the table in an appendix that is one page.
Clash, quality and change clauses that commercial teams can use
The clash clause should point to a matrix and a grouping rule, not to “zero clashes.” The quality clause should list checks: origin, warnings, sample schedule, overlay. The change clause should define a revision packet and a pause when RFIs stall. These three clauses are the ones marketplace disputes actually use. If they are missing, you will argue about feelings.
Security and subcontracting: whether the freelancer may pass a point cloud to another person, where files may live, and what happens at the end of the appointment (delete, return, archive). Occupied buildings and Scan to BIM make this non-optional.
Handover clause: native files, tested IFC if needed, purge policy, parameter fills, and a how-to-continue note. Without it, the last invoice is a file the client cannot open after a version upgrade.
Who maintains the BEP when people change
Assign an owner. When the owner goes on leave, assign a deputy. A BEP with no owner is a PDF. Updates should be dated. A changelog of BEP decisions (origin freeze, insulation clash tolerance, plugin ban) is more useful than a restyled cover. Freelancers should receive the current version with the folder path, not a kickoff slide from six months ago.
If two documents conflict — specification versus BEP versus a WhatsApp instruction — the BEP should say which document wins for information rules, and that design intent still lives in the design appointment. WhatsApp should not win.
Appendices that people actually open
A BEP appendix can be a one-page clash matrix, a one-page LOD table, a one-page naming sheet, and a one-page origin diagram. Those four pages do more than a forty-page narrative. Put the narrative only where it explains a decision. Screenshots of software ribbons go out of date with the next version; do not make them the plan.
Hyperlinks to official Singapore circulars belong in an appendix if CORENET X is in scope, with the date you downloaded them. Do not paste entire circulars into the BEP; they will not be updated when the agencies update.
Language for mixed native and IFC teams
If some consultants only receive IFC, the BEP must name the export setup, the frequency, and the known limitations (what usually drops). A native-only BEP on a mixed team is a plan for half the people. Test the export as a BEP obligation, not as a surprise in week ten.
Templates and the BEP
The company Revit template is part of the execution plan even if it is a separate file. The BEP should say which template, which version, and who may change it. A freelancer using a different template because it “feels faster” will misalign line styles and shared parameters. That is a BEP breach, not a style preference.
Small projects: the one-page BEP
For a house or a single shop fit-out: software version, origin, naming of one model, LOD sentence, deliverable list, and reviewer name. That is a BEP. Do not skip it because the job is small. Small jobs still federate wrongly. BIMProSG packages should attach even this one pager.
Changing the BEP mid-job
Changes need a date, an owner, and a note of which live files must be updated. Changing level names in week nine is a real cost. If the client insists, it is a revision packet. The BEP should say so, so the commercial team is not surprised.
BEP and design change control
When a client instruction changes a plant room, the BEP’s change clause should say how the model update is requested, how clash is re-run, and how drawings are reissued. If that clause is missing, each instruction becomes a unique argument. Marketplace extras should point at the clause: this instruction is packet N+1.
BEP for Scan to BIM packages
Include scan coordinate system, who registers, unseen rule, and whether the cloud stays with the client. A modelling-only BEP that ignores the cloud will lose the evidence. Point to the Scan to BIM article for method and keep the sentences in the BEP short.
BEP for 4D/5D
Include the code list location, the programme revision rule, and the grain of linking. Without that, 4D specialists invent codes that estimators do not recognise.
Reading the BEP on day one of a hire
A BIMProSG specialist should quote the origin sentence and the software version back in their kickoff note. If they cannot find those sentences, the BEP is too long or too vague. Fix the document before they model.
BEP and plugins
List allowed plugins. Ban undeclared ones. A file that requires a paid plugin the client does not own is not delivered. If a plugin is essential, the client must buy it or the specialist must remove the dependency before the last milestone.
BEP sign-off
Someone named must accept the BEP. A document in a folder with no acceptor is a draft. On a marketplace job, the client’s reviewer accepts it as Milestone 0 or 1. Specialists then follow it. Arguments about taste after that are either change control or non-compliance.
One-sentence origin and one-sentence version
If a reader cannot find the origin and the Revit version in thirty seconds, rewrite the first page. Everything else can be appendix. Marketplace specialists will follow what they can find. They will not follow what is buried under a history of BIM in general.
Print the origin diagram. Stick it in the project folder README. The PDF BEP that nobody opens will not save a wrong coordinate. The diagram might.
Is a BEP mandatory by law? Not globally. Some clients and some public processes require information plans. Singapore digital submission has official documents (Code of Practice and related guides) that are not the same object as your project BEP, though your BEP should not contradict them if they apply. Read official sources.
Who writes it? The lead consultant or the client’s BIM manager, often with trade input. A freelancer can draft; the project must adopt.
BEP versus BIM protocol versus EIR? Different documents in different frameworks: employer’s information requirements, BIM protocol in contracts, execution plan for operations. Do not merge them into one unread PDF unless the project is tiny and everyone agrees.
How often to update? When software, origin, LOD, or roles change, and after decisions that affect all authors.
Can we use a template? Yes, if you delete what is not true. A filled lie is worse than a short truth.
Does a house project need one? A one-pager: version, origin, naming, LOD, deliverable. Still yes.
What if specialists refuse the BEP? Do not hire them for that project. They are applying for a different job.
Sources and reference notes
ISO 19650-1 and 19650-2 describe concepts and information management using BIM. National annexes and client templates vary. AIA and other bodies have published BIM protocol documents in some markets. BIMForum LOD Specification is often referenced from a BEP’s LOD table. buildingSMART IFC is an exchange schema a BEP may name. For Singapore, CORENET X Code of Practice and Good Practices Guidebook are official resources via https://info.corenet.gov.sg and URA/BCA circulars via https://www.ura.gov.sg. This article is not those documents.
Image brief
A one-page BEP contents diagram with purposes, people, software, coordinates, LOD, clash, handover. Secondary: a responsibility matrix. Avoid a stack of unread binders.