Generate a complete, professional BIM Execution Plan (BEP) document — the foundational agreement that governs how Building Information Modeling will be implemented on a project.
A BIM Execution Plan (BEP) is a formal document that establishes BIM standards, workflows, and responsibilities for a project. Required by ISO 19650 and most public clients, it defines the software stack, file naming conventions, Level of Development (LOD) matrix, coordination schedule, and deliverable requirements.
Project Information (name, number, phase, standards); Team Roles (BIM Manager, coordinators, discipline leads); Software & Standards (Revit version, IFC export, naming convention); LOD Matrix (22 element categories × 5 phases, LOD 100–500); Workset Structure (discipline-based workset naming); Clash Detection Schedule (frequency, software, responsibility matrix); Deliverables Schedule (milestones, formats, submission dates).
Level of Development defines how much geometry and data a model element contains. LOD 100: conceptual massing. LOD 200: approximate geometry. LOD 300: precise geometry for coordination. LOD 350: connectors and interfaces for handoff. LOD 400: fabrication-ready detail. LOD 500: as-built verified. The BEP LOD matrix specifies the required LOD per element category per project phase.
Work through each of the 7 sections in order. The right panel previews your complete BEP document in real time. Click Copy to copy the formatted document, or Print to generate a PDF. The generated BEP is ready for project team submission and owner review.
A BIM Execution Plan (BEP) is a project-level document that defines how BIM will be implemented — covering software, standards, workflows, LOD requirements, and team responsibilities. It is required by ISO 19650 (international BIM standard), US General Services Administration (GSA), UK PAS 1192 projects, and most public infrastructure clients. On private projects, owners increasingly require a BEP as part of BIM contract requirements to ensure coordination quality and data handover standards.
A Pre-Contract BEP (employer's information requirements) is issued by the client before project award to describe what BIM information they require and when. It is a procurement tool. A Post-Contract BEP is produced by the appointed party (design team or contractor) after award, confirming how they will deliver the BIM requirements. This builder generates a Post-Contract BEP — the working document that governs day-to-day BIM practice on the project.
A well-structured Revit project typically has 5–10 discipline worksets: one per major discipline (Architecture, Structure, MEP — or split into Mechanical, Electrical, Plumbing), plus shared worksets for Site, Levels & Grids, and Linked Models. Avoid creating worksets per floor or per team member — these proliferate and slow model performance. The key principle is that worksets should reflect ownership and visibility needs, not just organizational hierarchy.
Industry best practice is weekly clash detection for active design phases, with formal coordination meetings bi-weekly. The clash detection cycle: model submission (Monday/Tuesday) → automated clash detection run → clash report distribution → team triage and assignment (Wednesday) → resolution deadline (following Monday). Critical clashes (structural penetrations, life safety systems) should be flagged for immediate resolution regardless of the cycle schedule. Use Navisworks Manage or BIM 360 Clash Detection for automated runs.
The UK BS EN ISO 19650 naming convention is widely adopted: [Organization]-[Project]-[Zone]-[Level]-[Type]-[Role]-[Number]-[Revision]. Example: ARCH-PROJ01-ZZ-M1-DR-A-0001-P01.rvt. US projects commonly use a simplified format: [Discipline]-[Building]-[Level]-[Revision]. The BEP must specify the exact convention, abbreviation tables, and revision status codes (S0 work-in-progress, S1 suitable for coordination, S2 suitable for information, S3 suitable for construction) used on the project.