There is a moment on every capital project where the work transitions from planning to building. A package gets released. A contractor mobilizes. The schedule clock starts in earnest.

That moment is almost always treated as a beginning. It is actually a deadline — and most projects miss it without knowing they missed it.

The preconstruction handoff is the single highest-leverage point in a capital program. It is also the most consistently underdeveloped. What follows is the failure mode in its generic form, stripped of any identifying detail, because the pattern repeats across project types, owner organizations, and delivery models with enough consistency to be treated as a rule.

What the Handoff Is Supposed to Do

A preconstruction handoff gate exists to answer one question: is this project ready to build?

Not ready to start. Not ready to mobilize. Ready to build — meaning the information, decisions, and commitments required to execute the work without stopping are in place before the work begins.

That distinction matters because mobilization and construction readiness are not the same thing. A contractor can mobilize on a project that is not ready to build. They will show up, set up the trailer, run the first few weeks of work on whatever is available, and then slow down or stop when the gaps surface. By the time the gaps are visible in the schedule, the project is already behind.

The handoff gate is supposed to prevent that. In practice, it usually does not.

The Failure Mode

The most common version of this failure looks like this:

The project team has been working hard. Design is substantially complete — or described as substantially complete. Procurement is underway. The schedule shows a start date, and the start date is real. Everyone is ready to go.

What is missing is not effort. What is missing is a structured accounting of what is not done.

Design packages that are "substantially complete" often contain open items that are not tracked anywhere. Procurement commitments that are "underway" often have lead times that have not been mapped against the construction sequence. Long-lead equipment that was identified early has sometimes slipped in its delivery date without that slip being reflected in the baseline schedule.

None of this is visible at the gate review because the gate review is not structured to surface it. It is structured to confirm that the major milestones have been hit. The major milestones have been hit. The project proceeds.

The gaps surface in the field, three to six weeks into construction, when the crew needs something that is not there.

Why This Is Predictable

The preconstruction handoff failure is not a people problem. The teams involved are typically competent and working in good faith. It is a structure problem.

Specifically, it is the result of three structural conditions that appear together on most capital programs:

The gate criteria are milestone-based, not readiness-based. A milestone-based gate asks whether a deliverable exists. A readiness-based gate asks whether the deliverable is sufficient to support the next phase of work. "IFC drawings issued" is a milestone. "IFC drawings issued with no open RFIs on the critical path scope" is a readiness criterion. The first is easy to check. The second requires someone to actually look.

The handoff package is assembled by the team that produced it. This is not a criticism — it is a structural reality. The team closest to the work is best positioned to compile the package. They are also least positioned to identify what is missing, because what is missing is, by definition, not in front of them. A handoff package assembled without an independent review of completeness will reflect what the team knows, not what the project needs.

Schedule risk is carried implicitly. On most projects, the risks that are formally tracked are the risks that have been explicitly identified. The risks that are not tracked are the ones that have not been named. Procurement lead times that are tight but not impossible, design open items that are minor but not closed, equipment deliveries that are on schedule but with no float — these are not tracked as risks because they have not crossed a threshold. They are carried implicitly in the schedule, and they surface as surprises.

What the Gate Actually Needs to Contain

A preconstruction handoff gate that functions as a readiness check rather than a milestone confirmation needs to answer five questions explicitly:

1. What is not done, and does it matter?

Every open item in design, procurement, and permitting should be listed, categorized by impact on the construction sequence, and assigned an owner and a close date. The question is not whether open items exist — they always do. The question is whether any open item sits on the critical path or near-critical path, and whether the close date is before the work sequence that depends on it.

2. What is the procurement exposure?

For every major equipment and material category, the handoff package should show the committed delivery date, the required-on-site date based on the construction sequence, and the float between them. If the float is negative, that is a schedule risk that needs to be named and owned before construction starts, not discovered after.

3. Where are the decision dependencies?

Some construction work cannot proceed until a decision is made — a design choice, an owner approval, a regulatory determination. Those decisions should be identified, the work sequences that depend on them should be mapped, and the decision timeline should be confirmed against the construction schedule. A decision that is expected in week four of construction but required in week two is a schedule risk.

4. What does the contractor not know yet?

This is the question that is most often skipped. The contractor has been given a package. What is in the package that is ambiguous, incomplete, or likely to generate RFIs? A structured pre-construction RFI review — where the owner's team and the contractor's team walk through the package looking for gaps before construction starts — surfaces issues that would otherwise surface as field RFIs, with all the schedule and cost impact that entails.

5. What is the recovery plan if the first four answers are unsatisfactory?

A gate review that can only approve or delay is a gate review that will almost always approve, because delay has a visible cost and proceeding has a deferred cost. A gate review that includes a conditional approval path — proceed with these specific mitigations in place by this specific date — gives the team a mechanism to move forward without pretending the gaps do not exist.

The Hyperscale Version of This Problem

On hyperscale data center programs, the preconstruction handoff problem takes a specific form that is worth naming separately.

The schedule compression that defines hyperscale delivery means that the float between design completion and construction start is often near zero. There is no buffer to absorb a handoff that is 90% ready. The project needs to be ready to build on day one of construction, because there is no week three to catch up.

This creates pressure to declare readiness before readiness exists. The pressure is real and the business reasons for it are legitimate. The answer is not to resist the pressure — it is to make the gaps visible early enough that they can be closed before the gate, rather than discovered after it.

That requires starting the readiness assessment earlier than feels necessary, when the project still has time to respond to what it finds.

The Checklist Is Not the Point

There are preconstruction handoff checklists available from every major owner organization, program management firm, and industry association. Most of them are good. None of them are the point.

The point is the conversation the checklist forces. A checklist item that says "procurement status confirmed" is only useful if someone in the room is willing to say "confirmed against what, exactly?" and keep asking until the answer is specific.

The gate is a forcing function for that conversation. The checklist is a prompt. The readiness is in the answers.

---

The Preconstruction Handoff Checklist referenced in the curriculum is a working version of the framework described here — structured around the five questions above, formatted for use in a gate review, and genericized for use across project types. It is available to subscribers.