Why The Gap Between Planning And Building Causes So Many Problems
Commercial construction projects rarely fail because of one bad decision. They fail because of small gaps between phases: what gets promised at estimating, what gets planned in preconstruction, and what actually happens once crews are on site.
Each phase often has different people running it. Estimators build the number. Planners build the schedule. Procurement buys the materials. Site teams build the thing. When those groups work in isolation, details get lost in the handoff. A material substitution made during procurement might not reach the person managing client expectations. A schedule assumption made in preconstruction might not survive contact with the actual site conditions.
This is one reason some construction leaders choose to stay involved across the whole life of a project rather than handing it off phase by phase. Craig Plescia is one example of an executive whose leadership role spans preconstruction through completion, with experience across office, hospitality, restaurant, data center, mixed-use, and life-science projects. That range matters because each of those project types carries its own risks, and staying close to the work across sectors builds judgment that a narrower focus cannot.
What Hands-On Involvement Actually Looks Like
Executive involvement does not mean doing every job on site. It means staying close enough to the details that nothing gets decided in a vacuum. A few areas where this tends to matter most:
Estimating. Numbers built without input from someone who understands execution risk tend to be optimistic. An executive who has run projects knows where costs hide: in site conditions, in trade coordination, in permitting timelines that never move as fast as anyone hopes.
Procurement. Material decisions made purely on cost can create delays later if lead times or substitutions were not checked against the schedule. Someone with a full view of the project can catch that before it becomes a problem, not after.
Client Communication. Clients do not experience a project in phases. They experience one relationship. When the person setting expectations early is the same person accountable for delivering later, there is less room for the message to drift.
On-Site Execution. Plans change once work starts. Ground conditions differ from drawings. Trades run into sequencing conflicts nobody predicted. A leader who understands the original plan can make faster, better-informed calls when reality does not match it.
Why This Matters More On Complex Projects Than Simple Ones
A small, single-use building can often tolerate some disconnect between phases. The scope is narrow enough that problems stay contained.
Complex commercial projects do not have that cushion. A life-science building has mechanical and infrastructure requirements that a restaurant build-out does not. A data center has power and cooling needs that a mixed-use residential project never touches. Hospitality work often runs on a public-facing timeline that cannot slip without real cost. Office projects usually involve a tenant with its own move-in date driving everything else.
Working across all of these project types, as Craig Plescia's background shows, means carrying lessons from one sector into another. A scheduling risk learned on a data center project can inform how a hospitality project gets planned. A procurement lesson from a life-science build can shape how a mixed-use project handles long-lead materials. That kind of pattern recognition is hard to build if a leader only ever sees one type of project, or only ever sees one phase of it.
The Cost Of Losing Continuity
When leadership is not continuous across a project, the most common failure point is not a single dramatic mistake. It is a slow accumulation of small ones: a scope assumption from early planning that never got updated, a client conversation that promised something procurement could not actually deliver, a schedule built without input from the people who would have to execute it.
By the time these gaps surface, they are expensive to fix. A schedule slip discovered mid-construction costs far more to correct than the same issue caught during preconstruction. A client expectation set incorrectly at the start is harder to walk back once work is underway.
Hands-on leadership does not eliminate every risk. Complex projects always carry some. But it closes the distance between where a decision gets made and where its consequences land. That distance is where most preventable problems live.
What This Means For Anyone Hiring For A Complex Project
If you are evaluating a construction partner for a project with real complexity, whether that is a mixed-use development, a life-science facility, or a hospitality build with a hard opening date, it is worth asking a direct question: who is involved from estimating through completion, and does that person actually stay on the project the whole way?
Some firms rotate different people through different phases. That can work fine on simpler jobs. On complex ones, ask how information gets passed between phases, and who is accountable for making sure nothing gets lost in the handoff.
The answer will not show up in a proposal document. It shows up in how a firm talks about its own process, and in whether the same names appear across preconstruction, procurement, and execution, or whether each phase gets a different owner.
Continuity does not guarantee a smooth project. Nothing does. But it removes one of the more common reasons complex projects run into trouble: not a lack of skill in any one phase, but a lack of connection between them
