Constructability review in preconstruction: turn buildability issues into estimate decisions

Use constructability review to test access, sequencing and physical execution before pricing. Record the cost consequences of unresolved design interfaces.

Guide7 min read

Published

Tower crane above steel reinforcement

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.

Book a demo
On this page
  1. Freeze the basis before testing the work
  2. Walk the installation, not just the finished geometry
  3. Worked example: rooftop unit replacement
  4. Keep a decision register through bid day
  5. Hand the review to the delivery team
  6. Apply the same review questions to project documents

A constructability review checks whether the documented design can be built through workable access, sequencing and trade interfaces. USACE’s BCOES guidance provides one formal example of reviewing executable solicitation requirements alongside the estimate; its agency-specific process is not a universal contract rule.

A constructability review tests whether the work shown can be executed under the access, sequence and conditions assumed in the estimate. For a GC pricing a commercial project, the useful output is a decision: resolve the issue, carry a defined method and cost, or identify the unresolved exposure in the bid basis. A list of design comments alone does not tell the chief estimator what to carry.

Start with the design and restrictions available at a named cutoff. Walk the work in installation order with an estimator, superintendent and relevant trade input. Record the source, the person responsible for the next answer, the schedule effect and the estimate treatment. The review is a preconstruction judgment, not an engineering approval, a site verification or a guarantee that every field condition is known.

The National Institutes of Health design requirements manual, in its agency-specific constructability review, identifies restricted access, complex phasing, incompatible systems and incomplete documents among potential obstacles. Its review obligations apply to its own projects; they are a useful prompt for a GC, not a universal contract requirement.

Freeze the basis before testing the work

List the drawing and specification revisions, addenda, site information, proposed schedule and owner restrictions used in the review. Distinguish an issued requirement from a proposal assumption and an unverified field condition. Assign someone to check subsequent addenda against the log and estimate before bid submission.

At conceptual design, the same question may only support a stated assumption and a range or allowance, depending on the agreement. As details mature, replace that basis with quantities, trade input and a defined method. See conceptual construction estimating for how to preserve the assumptions behind an early number.

A GC in a hard-bid procurement should use the specified question and addendum process for ambiguities. A proposed qualification may not be accepted, and a private assumption does not change the contract documents. In a negotiated preconstruction assignment, the team may have a different opportunity to test alternatives with the owner and designer. Check the actual procurement and contract terms in either case.

Walk the installation, not just the finished geometry

Pick a work area and follow material, equipment and crews from delivery to completed installation. Use the drawings, specifications, schedule, site information and proposed means together. To read between the drawings, compare the details across disciplines and ask what has to happen between them.

  • Access and handling: Can the component reach its final position through the available opening and along the proposed route? Check staging, lifting equipment, floor loading, delivery windows and the space needed to assemble or maintain equipment. Obtain qualified review where loads or lift design require it.
  • Sequence and occupancy: What must be installed, inspected, energized or removed first? Test work windows, shutdowns, curing, protection and restoration against the schedule and owner restrictions. Identify repeated mobilizations rather than assuming one continuous operation.
  • Temporary works and services: Identify temporary support, weather protection, barriers, access equipment and utilities, including who designs, supplies, maintains and removes them. For example, review temporary construction power as a separate capacity, distribution and responsibility decision, not simply an assumed trade inclusion.
  • Tolerances and interfaces: Compare the space needed to install, fasten, inspect and adjust adjoining systems. Ask which trade sets the controlling elevation or opening, who measures existing conditions, and who pays for corrective work if assumptions do not hold. Confirm applicable tolerances with the project documents and responsible specialists rather than inventing a universal clearance.

A model can help expose spatial conflicts, but constructability can be reviewed on drawings and in the field without one. If a model is available, carry unresolved access, sequence and temporary-work assumptions into the coordination plan, with an owner and due date. BIM coordination vs. clash detection explains why identifying a modeled collision is only part of resolving the interface.

Worked example: rooftop unit replacement

Consider an illustrative occupied commercial building. The drawings show a replacement rooftop unit, while the proposed estimate assumes a single crane pick and uninterrupted access to the roof. The team has not verified the delivery route, crane location or shutdown window. No cost or schedule below is a benchmark.

The superintendent sketches the route and asks a crane subcontractor for a preliminary method and price. The mechanical bidder confirms the unit's shipping dimensions and whether it can be separated. The structural engineer is asked to evaluate the proposed loading where necessary; the owner is asked to confirm access and shutdown restrictions through the authorized project channel. Until those answers arrive, the one-pick plan is an assumption, not a verified method.

Suppose the team prices a feasible working assumption at $18,000 for the crane and associated handling, with a possible second mobilization estimated at $7,000 if the shutdown cannot be completed in one window. These figures are illustrative only. The estimator carries the $18,000 once in the appropriate cost code, checks that the mechanical proposal excludes or includes the same lift, and records the $7,000 exposure separately for decision. It is not automatically added to contingency and also to the trade carry. The schedule owner tests the effect of a second mobilization on the turnover milestone.

If the owner confirms one available window and the crane method is accepted by the responsible parties, update the log and price to the supported method. If the answer is still outstanding at bid cutoff, seek a formal clarification and record the pricing basis and exposure for the bid decision. Whether a qualification, allowance or alternate can be submitted depends on the solicitation and agreement. If the assumption changes after bid, reconcile the affected lift, mechanical scope, access and schedule together.

Keep a decision register through bid day

Use a row for each issue, not a single general note that the job has access risk. The following is a reusable structure, populated with the example above.

FieldExample entry
Issue and sourceRoof lift route and single shutdown window; mechanical roof plan revision 2 and owner access notes
Working basisOne crane mobilization and one shutdown; both await confirmation
Next owner and deadlineEstimator requests access answer from owner through project channel before bid cutoff; superintendent obtains crane method
Cost and schedule$18,000 illustrative lift carry; possible $7,000 second mobilization exposure; check turnover milestone
Decision and statusOpen; avoid duplicate mechanical and GC lift carry; escalate if no answer by cutoff

Attach or reference the relevant drawing detail, specification section, question and response, proposal revision and estimate line. Record who owns the next action as well as who can authorize a design or access decision. A subcontractor's suggested method may inform the carry; it does not by itself revise design requirements or secure owner approval.

Before committing, classify each row as resolved, priced on an explicit basis, or open for an authorized decision. For a resolved item, record the answer and where the cost and schedule were updated. For a priced assumption, identify the trigger for revisiting it, the included amount and any separately stated exposure. For an open issue, name the decision-maker and deadline. Reconcile trade proposals, general conditions, allowances and contingency so the same cost is neither omitted nor counted twice. A contingency is not a substitute for describing the underlying uncertainty.

Hand the review to the delivery team

At estimate approval and again at buyout, transfer the current register with the bid basis, open questions, accepted responses, trade scope boundaries and estimate references to the project manager and superintendent. Assign dates to field verification and procurement decisions. Reopen a row when an addendum, selected subcontractor method or site finding changes its basis; record the resulting estimate and schedule decision rather than silently overwriting the original assumption.

The register helps teams see the conditions behind the price. It does not replace the designer's responsibility, required engineering, a site investigation, safety planning or the contract's formal change process.

Apply the same review questions to project documents

A company can use Piper Survey to apply its constructability questions to project documents, obtain source-supported answers where available and flag questions needing a human response. The team still checks physical execution, validates assumptions with the appropriate parties and decides what to price. Keep the document answer connected to the issue and estimate decision so a later revision can be assessed in context.

FAQ

When should a GC conduct a constructability review?

Begin with the design and information available for the estimate, then revisit material issues as documents and trade input develop. The useful level of detail depends on design maturity, site access and the procurement schedule. Record the cutoff and assumptions each time.

Does a constructability review replace BIM clash detection?

No. A model may help identify spatial conflicts, while the review also tests sequence, access, temporary work and assumptions that may not appear in a model. Issues from either process need an accountable owner and a decision.

What if an issue is unresolved at bid time?

Use the procurement's question process, price a documented basis where possible and escalate the remaining exposure to the bid decision-maker. Confirm whether the solicitation permits a qualification, allowance or alternate. Do not assume a private note alters contract obligations.

The CNYG-223M mortar-lift comparison shows this at the production-method level: Shore Parkway’s granite-repointing detail calls for one-inch layers, while Item 107 limits layers to half an inch and requires thumb-print hardness before the next layer. Resolving that difference gives the estimator an explicit placement-sequence assumption before carrying the unit rate.

For an adjacent-package example, the TxDOT Pond A scope review shows how to turn the overlap between two project descriptions into an estimate hold. Record the work assigned to 3B-1 and check the issued limits and handoff before carrying the remaining 3C-2 quantity.

ShareLinkedInX

Related reading

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow

See Piper on your project

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.