A constructability review is a schedule decision disguised as a design task

Constructability review asks a question the design process does not: can this be built, in this sequence, in this space, with the access and the trades available.

It is a review of buildability and sequence, not of design adequacy, and it is normally scheduled where it is least useful. On many projects it happens after the design is coordinated and issued for tender — sometimes after a contractor is appointed — at which point the findings arrive as change rather than as improvement.

What the review looks for

The questions are narrow and practical, and they are mostly about space and order.

Can the components physically be installed in the sequence the design implies. Is there room to lift, land, and connect each major item, with the crane or hoist available, from a position that exists on the site.

Does anything have to be installed before something else that is nominally later in the program. Large plant frequently has to be placed before the enclosure around it is complete, which is a sequencing constraint the design does not state.

Is there working space at each connection, for the trade that has to make it, with the tools that trade uses. Is there access for the temporary works that the permanent works require.

Can the work be executed in packages that a real market will bid, with interfaces at boundaries that a subcontract can be written around.

Are the tolerances achievable in combination. Individually reasonable tolerances on adjacent elements can produce a joint that cannot be made.

None of these is a design error in the conventional sense. The design may be entirely compliant and still be difficult, slow, or expensive to build, and difficulty converts directly into program.

Why timing determines the value

The findings of a constructability review are the same whenever it is run. What changes is what can be done with them.

Before coordination, a sequencing or access finding is a drawing revision. The design team incorporates it, and the cost is design hours.

After coordination but before tender, the same finding is a redesign with knock-on effects across disciplines. More expensive, still manageable, and still cheaper than the alternative.

After tender, the finding is a variation. The contractor has priced the design as issued, and any change to it is instructed and paid for at construction rates with a program impact attached.

After construction has started, the finding is either a variation or an acceptance that the work will be built the hard way — slower, with more labor, and with a claim behind it.

The review costs the same at every point. What it returns falls by an order of magnitude at each stage, and it is usually scheduled at the third one.

Who should conduct it

The reviewer needs recent experience of building comparable work. That is a different qualification from designing it, and it is the reason a design team's internal review is not a substitute — a design team reviews against the specification and the code, which is its job.

Three sources are usable. A contractor engaged for pre-construction services, which is the strongest option where the delivery model permits it. An independent reviewer with relevant construction experience, retained by the owner. Or the owner's own construction staff, where the organization builds regularly enough to have them.

What matters is that the reviewer is looking at means and sequence, and that the findings are directed at the design team as comments to be dispositioned rather than at the owner as observations.

Keeping the boundary clear

One caution. A constructability review examines whether a design can be built; it does not select or direct the means, methods, or sequences a contractor will use, and it does not relieve the design team of responsibility for the design or the contractor of responsibility for execution and site safety. Those obligations stay where the contracts put them.

Handled that way, the review is an owner-side risk reduction: it tests whether the documents the project is about to buy from describe something a competent contractor can build efficiently. Handled loosely — as an instruction on how to build — it transfers responsibility the owner should not want.

What to do with the findings

Every finding should be dispositioned: incorporated, rejected with a stated reason, or accepted as a known difficulty with an allowance in the estimate and the program.

That last category is the one projects skip. A known constructability difficulty that has been priced and programmed is a managed condition. The same difficulty, identified and then left in the report, becomes a surprise during construction — with the review document sitting in the project file as evidence that it was foreseen.