Skip to article
Preconstruction

The bid handoff meeting should explain the gaps, not just the number

Use a bid-to-operations handoff to expose scope gaps, qualifications and unresolved interfaces before buyout and mobilization.

Two colleagues at a table reviewing a large set of floor plans in a site office, with binders, hard hats and a schedule whiteboard behind them.
Generated editorial illustration.

An estimator can explain exactly why the number works. A project manager can still inherit a job that does not.

The difference often sits in the qualifications: a scope assumption made to meet a deadline, an alternate carried in one trade but not another, or a responsibility that everyone expects someone else to own. These details deserve a deliberate handoff before buyout locks them into separate packages.

A useful bid handoff checklist preserves the basis of the price and turns unresolved assumptions into assigned work. It does not pretend that every gap can be solved in one meeting.

#Start with the version that was actually priced

Identify the drawing set, specification issue, addenda and clarifications used to prepare the bid. Keep a manifest, not just a folder called “latest.” If the contract set differs, identify what changed and who is reviewing the difference.

Ask each estimator to name the assumptions most likely to surprise operations. A quantity allowance, an excluded test or a restricted-hours assumption may matter more than a small rounding difference in the estimate.

The Construction Industry Institute's 1986 guideline Scope Definition and Control1, written for industrial projects, emphasizes the problems created by inadequate scope definition and the need to evaluate changes across affected areas. The interface exercise below is a practical way to bring that concern into a GC handoff.

#Review interfaces instead of reading trade names aloud

Use a simple responsibility matrix for items crossing package boundaries. Examples include penetrations and firestopping, temporary power, supports, access panels, testing, equipment startup, protection and final cleaning. These are examples to examine, not a claim that they belong to a particular trade on every project.

For each interface, record:

  • What the project documents require.
  • Where it is carried in the estimate.
  • Which proposed subcontract includes it.
  • Any conflicting qualification or exclusion.
  • Who must resolve the uncertainty and by when.

Do not resolve a disagreement by typing an assumed owner into the matrix. Mark it unresolved until the responsible team has aligned the scope with the contract documents and procurement approach.

#Keep commercial assumptions visible

A quote expiration, escalation allowance or lead-time qualification can change the buyout strategy. So can an assumption about site logistics, occupied work, shifts or owner-furnished equipment.

Walk through one hypothetical interface: equipment is owner-furnished, mechanical carries installation, and electrical carries connection. Who unloads it, inspects it on receipt, stores it, protects it and coordinates startup? The answer must come from the actual agreements. The handoff's job is to make sure the question does not disappear between the packages.

Where the answer affects cost or time, connect it to the pending-change or risk record. Keep an allowance distinct from a confirmed scope commitment. Do not count the same uncertainty in a trade allowance and again in a general contingency without explaining the treatment.

#Give operations a decision list

Finish with a short list ordered by when the decisions become difficult to reverse. A scope question that affects an imminent purchase deserves attention before a cosmetic clarification with several months of runway.

Assign ownership to a person, not “estimating” or “the team.” Include the source document and the current assumption so the person does not have to repeat the discovery work.

After buyout, revisit the high-risk interfaces against the executed packages. Mark which assumptions were confirmed, changed or remain open. This second pass matters because the subcontract ultimately signed may differ from the quote discussed at the handoff.

Try the matrix on one package that has several interfaces. Ask the incoming project manager to walk through the estimator's inclusions and exclusions against the documents that were actually priced, and to say how the package will be bought and installed.

Record each assumption that cannot be traced to a document as an open item, with an owner and a decision date. Keep the original estimate unchanged so the priced position stays distinct from later clarifications, and review the open items at the first buyout meeting.

For a smaller GC, this does not require an elaborate system. A clear matrix, the documents that were actually priced and a named owner for each open item are enough to start. The objective is to pass on the reasoning that produced the number, while there is still time to act on it.

For the broader approach to reviewing project records, see SP4N’s product overview.

Sources

  1. 1Scope Definition and Control (Construction Industry Institute Publication RS6-2, 1986)Construction Industry Institute
Share this
LinkedInPostEmail