When to bring a contractor into the design

Bring the contractor into the conversation when you need to test the design against the budget, existing conditions or opening date. That can be during concept design. I would agree on what that first review needs to answer, then make the review more detailed as the drawings develop and the team has better information to work from.

At concept, test the program and the major assumptions

Early input should help the owner and design team understand what is driving the project. The builder can review the proposed use of the space, the existing conditions visible on a site walk and the construction approach that the concept implies.

A budget range at this stage needs its assumptions written down. Identify the information used, what remains unknown and the items that could materially change the range. That gives the owner a way to compare the design with the available budget and decide which investigations deserve attention first.

The same applies to the schedule. Discuss the intended sequence, the information needed to develop it and the long lead items already apparent. Avoid treating an early timeline as a fully coordinated construction schedule when major decisions and existing conditions remain open.

During design development, resolve the details that drive cost

As the design develops, the review can become more specific. Read the disciplines together and identify details that affect how the work will be installed. A ceiling layout, for example, may need coordination with ductwork, access panels, lighting and the depth available above the finished ceiling.

The builder's comments should explain the issue and its effect on cost, time or constructability. The design team remains responsible for the design response. A useful review gives the architect enough information to resolve the question while keeping the intended result in view.

The same ceiling review can identify selections that need to be made while the layout is still being developed. A custom fixture may affect the ceiling detail, electrical preparation and installation access. Review its requirements and expected delivery with the design team, including whether an alternate would change the appearance or performance.

Carry those answers into the estimate and schedule. If the plan depends on releasing the fixture early, identify the information and owner authorization needed for that release. The procurement discussion belongs alongside the design decision it depends on, so the owner can assess the choice while there is still room to change it.

Before bidding, establish a common scope for the trades

As the documents become more complete, review the scope boundaries between trades and between the contractor and owner suppliers. Confirm the drawing revisions being priced and identify allowances, exclusions and open decisions in a consistent format.

That information helps the team compare proposals. Two totals are difficult to evaluate when one includes a package that another excludes or when each bidder has assumed a different method of access. The comparison should show what each proposal covers and what information is still required.

A preconstruction engagement can also leave the owner better prepared for competitive bidding. The reviewed scope, estimate and assumptions become a basis for questioning other proposals. The owner can assess the work included alongside the proposed price and schedule.

Define what the preconstruction engagement will produce

Ask for a scope of services tied to the stage of design. The deliverables may include a budget with its assumptions, a schedule, a procurement study, a risk register, a site logistics plan and recommendations for changes that could save cost or time.

Each deliverable should have enough detail to support the next decision. A risk register should explain the condition, its potential effect, who is investigating it and when the answer is needed. A recommendation to change a material should identify what the owner gains and what changes in the design or operation.

Agree on the review meetings and how revisions will be handled as the design advances. Identify which version reflects the current direction and what changed since the previous review, so a decision made in design development reaches the estimate and the documents being priced. The scope of the engagement needs to cover those updates as well as the first set of deliverables.

Bring the project information you have to the first meeting

The first conversation can begin with the available drawings, the property or site information, the intended use, the budget expectations and the date the owner is working toward. Identify the design team and the decisions already made. If the project is still being defined, explain which questions need to be answered first. Ask the contractor to describe the proposed review and the information needed from the team. The response should connect the scope of preconstruction to the decisions in front of the owner, with a clear description of the work to be done.

Our preconstruction services describe those deliverables in more detail.