From Tender to Handover: How a BIM Execution Plan Steers a Modeling Team

A BIM Execution Plan does its real work long before anyone opens Revit. On a typical job it begins as a response to the owner's Employer's Information Requirements, and it ends as the document every discipline checks when a model comes back for review. Following that path shows why the plan matters to a team that builds models for other people.

During tender, the bidding team writes a pre-contract BEP. It shows capability and explains the proposed approach at a high level, answering the client's requirements rather than fixing every detail. Once the contract is awarded, the lead contractor and the full team replace it with a post-contract plan. That version carries the responsibility matrix, the Master Information Delivery Plan, the Task Information Delivery Plans and the detailed quality assurance steps. ISO 19650 describes the same two stages as pre-appointment and post-appointment.

From that point the plan is a daily reference. Roles are fixed, so each model element has an owner. Information exchanges state which elements, which level of development and which level of information are due at each milestone. Collaboration procedures define file structure and the common data environment where everything is stored. Facility data requirements, often exchanged through COBie, tell the team what the owner needs later for operations.

For a provider that builds models for others, those exchange rules are the brief. The level of development and the file conventions written into the BEP decide what the team hands over and in what format, and the same plan records where the common data environment sits, including projects that coordinate through ACC in BIM workflows. A vague plan produces guesswork, and gaps then surface late, when fixing them costs more.

Verification closes the loop. The plan names the model checks, the clash-detection routines and the data-validation steps that must pass before a model is shared. A reviewer can then compare a delivered model against the plan line by line instead of relying on opinion.

The plan also has to keep moving. Best practice is to review it at the start of each major phase, such as schematic design, design development and construction, and whenever scope, key personnel or software changes. A BEP that is copied from another project and never revised quietly stops guiding anyone.

The full breakdown of components, the eight-step creation process and the common mistakes is covered in the BIM execution plan guide. Read it alongside your own project documents, and tailor any template to the job in front of you.

The practical test for any BEP is simple. A new team member should be able to open it and learn who owns what, which standards apply and what is due at the next milestone. If the plan cannot answer those three questions, it needs another revision before modeling continues.