The Journey

With the project environment established, the focus shifts to developing and maintaining the BIM model throughout the project's lifecycle. Unlike the initial project setup, this stage is continuously evolving, with every design revision, coordination meeting and technical decision influencing the model.

As modelling progresses, changes are introduced from multiple sources. Architectural revisions, structural updates, MEP coordination, fire strategy amendments, package responsibility changes and client decisions all require careful review before being incorporated into the model. Some elements are revised, others are removed entirely, while new details, build-ups and bespoke solutions are developed to reflect the latest approved information.

Every modelling decision must be validated against the project's drawings, specifications, design intent and coordination outcomes. The model becomes a live representation of the project, requiring constant comparison with previous revisions to ensure obsolete information is removed and new requirements are accurately integrated without compromising coordination.

Building the Digital Model

Modelling is never carried out in isolation. While developing my package in Revit, I routinely work with Revizto and Navisworks on a second screen to monitor the latest published models from other disciplines. By comparing these against the linked models within my Revit environment, I can quickly identify discrepancies, newly introduced clashes or design changes before progressing further. This continuous cross-checking ensures my package remains aligned with the most up-to-date project information and significantly reduces coordination issues during model reviews

To improve consistency and productivity, repetitive workflows are enhanced through custom Dynamo automation. For example, when developing drylining packages from the architect's design intent, I developed a script that automatically extracts all relevant walls or ceilings from a linked architectural model and imports them in bulk into the project. This provides a structured starting point before extending the walls slab-to-slab, adding critical studs and developing the package into a fully coordinated, buildable solution. Similar workflows have been developed to improve model validation, parameter management, naming compliance and information consistency. More of these automation tools and the reasoning behind them are explored in the Automation & Digital Workflows section.

Throughout this stage, modelling and coordination happen simultaneously. Every update is an opportunity to identify potential issues before they reach site, improve buildability and strengthen collaboration between disciplines. By the end of this phase, the model has developed into a coordinated, information-rich digital representation, ready for publication and the next cycle of project coordination.

Once the latest models have been published, the coordination process begins. This is where the project becomes highly collaborative, bringing together architects, structural engineers, MEP consultants, specialist subcontractors and the wider design team to identify, assess and resolve coordination issues before they reach site.

Using platforms such as Revizto, Navisworks and regular coordination meetings, I review clashes, design comments and General Correspondence (GCs) raised against my package. However, coordination is far more than identifying clashes—it is about understanding why they exist and determining the most appropriate solution without compromising the design intent, buildability or programme.

Coordination & Issue Resolution

Not every clash is the same and every issue must be carefully assessed before any changes are made. Some clashes are purely geometric, while others are driven by buildability, fire strategy, system interfaces or installation sequencing. These often require discussions with specialist subcontractors, internal technical workshops or even consultation with manufacturers to validate a proposed detail before it can be incorporated into the model.

A good example is the development of a three-sided opening within a shaft wall. Although a solution may appear suitable within the BIM model, it cannot be implemented until it has been reviewed and accepted by the relevant system manufacturer to ensure it complies with the tested system and performance requirements.

Other coordination issues relate to architectural intent rather than construction. Changes affecting visibility, room finishes, ceiling layouts or aesthetics often require close collaboration with the architect to ensure the proposed solution satisfies both the design requirements and the project's functional needs.

Before implementing any modification, I verify that it is fully supported by the latest project information. Almost every change introduced into the model should be traceable to an updated drawing, a design instruction, an answered RFI, a General Correspondence (GC) or another formally issued document such as INSTRUCTIONS

Maintaining this audit trail ensures the model remains accurate, accountable and aligned with the approved design.

Coordination is rarely a linear process. Resolving one issue frequently creates new interfaces with other disciplines, requiring further reviews, technical discussions and validation before a final solution is agreed. This cycle continues throughout the project until the package reaches a coordinated, buildable solution that satisfies both the design intent and construction requirements.

Throughout this process, my objective extends beyond eliminating clashes. I focus on improving buildability, reducing construction risk, maintaining design intent and delivering solutions that can be confidently constructed on site.

More chapters are on the way ...........

Get in touch

Address

London, UK

Contacts

07990700594

khalilsenhadjicad@gmail.com