A structured, standards-compliant BIM coordination process from initial client requirements through to verified project delivery.
The workflow begins with a thorough analysis of the client's Employer's Information Requirements (EIR). This foundational document defines what information is needed, when it is needed, and in what format — establishing the information management framework for the entire project. Requirements are reviewed to understand BIM maturity expectations, software requirements, deliverable formats, and any project-specific constraints.
A BIM Execution Plan (BEP) is developed in response to the EIR, outlining how the BIM requirements will be met, which software will be used, who is responsible for what, and how information will flow between project contributors throughout the design and construction process.
Existing documentation — including legacy CAD drawings, survey data, geotechnical reports, and architectural plans — is collected, validated, and prepared for integration into the BIM environment. CAD files are cleaned, scaled, and oriented to a common coordinate system before being used as reference underlays for BIM model creation.
For renovation or extension projects, existing-conditions models may be created from available drawings and site survey data. Coordinate reference systems and project grid are established at this stage to ensure all discipline models are correctly georeferenced and can be federated without offset errors.
Discipline-specific BIM models are created or developed to the required Level of Development (LOD), following the BEP and project templates. Structural models — including frame, slab, foundation, and connection elements — are built in Revit and, where required, detailed further in Tekla Structures or Advance Steel for steel-intensive projects.
Models are developed with correct parameter data from the outset, enabling downstream use for quantity take-off, scheduling, and facilities management. Custom Revit families are created where standard library content does not meet project-specific requirements. Model health and naming convention compliance are checked at regular intervals against the established BIM standards.
Individual discipline models are federated into a single coordinated model using Autodesk Navisworks or BIM Collaborate Pro. Coordination meetings are conducted on a defined cycle — typically weekly — with discipline leads reviewing the federated model to identify spatial conflicts, coordination issues, and design discrepancies that require resolution.
A structured coordination process ensures that issues are assigned to the responsible party, tracked through to resolution, and formally closed before progressing. This iterative coordination loop is the core of effective multi-discipline BIM delivery — catching conflicts in the digital model rather than on the construction site.
Systematic clash detection is performed using Navisworks, with carefully defined clash rules targeting the most critical interface zones between disciplines: structural elements versus MEP services, architectural elements versus structural components, and MEP discipline-to-discipline clashes. Hard clashes, soft clashes (clearance violations), and workflow duplications are all identified and categorised by severity.
Clash reports are generated and distributed to discipline teams for resolution. Each clash is assigned a priority level, responsible party, and resolution deadline. Resolution actions are verified in the model before the clash is formally closed — maintaining a clean and accurate record of the coordination process throughout the project lifecycle.
Construction documentation is produced directly from the coordinated BIM models, ensuring consistency between the 3D model and 2D drawing deliverables. Plans, sections, elevations, and details are extracted from Revit using properly configured view templates, sheet sets, and drawing standards aligned with project requirements.
Quantities are extracted from the model to support cost planning and bill of materials production. Specifications and model-based schedules are coordinated with the drawing set, creating a fully integrated and consistent package of construction information that minimises risk of error during the construction phase.
A comprehensive quality control process is applied to all model deliverables before publication to the Common Data Environment (CDE). Model audits check for correct family usage, naming convention compliance, LOD consistency, missing parameters, and structural integrity of the model data. Quality checks are documented and any non-conformances are corrected before approval.
Compliance with the project's BIM Execution Plan and the employer's information requirements is verified at each information delivery milestone. This gate process ensures that only approved, validated information is published as Shared or Published status on the CDE — maintaining the integrity of the project information throughout the delivery lifecycle.
Final model deliverables are prepared, validated, and formally handed over to the client through the project's CDE. The deliverable package includes native Revit model files, IFC exports for interoperability, PDF drawing sets, quantity schedules, and a comprehensive model information guide. All files are named, structured, and documented in accordance with the EIR and project BIM standards.
For projects with an operational phase requirement, the model is prepared as an asset information model (AIM) — structured to support facilities management and building operations. Handover documentation confirms that all required information has been delivered, verified, and accepted by the client, formally closing the BIM delivery process.