General

The BoD is a separate document containing specifications and description of how the Design Team expects to fulfil the requirements in the OPR.

If you haven't read the article about the OPR, you can read it here.

The Design Team must describe how they intend to resolve each individual OPR item. The description is an early verification and expectation alignment of the OPR item between the Design Team and the Cx Team.

The BoD systems and structures the Design Team’s thoughts and plans, so that the Cx Team can verify at an early stage that the Design Team has adhered to the OPR.

Developing the Basis of Design

The BoD is not a standardized document in construction projects, and there are many Design Teams who have not worked with the BoD before.

There may, therefore, be a risk that the Design Team’s work with the BoD does not meet the Cx Team’s expectations and therefore does not provide the necessary value for the Cx process

The Cx Team must, therefore assist, and support the Design Team in making BoD responses

How to structure the BoD document

The BoD should be constructed in the same format as the OPR, as this allows reuse of the structure from the OPR

This is an advantage, as the Design Team has to prepare a BoD for each individual OPR item.

The BoD must, as a minimum, include the following information:

• Reference to the OPR item to be answered.
• Description and explanation of how the requirement is expected to be resolved in the project.
• The name of the responsible person from the Design Team for the BoD response.
• Date of the BoD response.

Who can approve a BoD response?

It is for the Cx Team to check and approve the Design Team’s replies in the BoD. Each BoD response must be reviewed and either approved or rejected by the Cx Team

If a response is rejected, the Cx Team must describe why the BoD response is rejected, and the Design Team must review and update the BoD response.

Examples of OPR item and BoD response

The examples below show how a BoD response can be performed.