Why Projects Lose Control During Preconstruction
Short answer
Projects lose control during preconstruction when scope, design, cost, schedule and owner decisions are not managed as one connected process. Control is maintained by documenting requirements, tracking assumptions and decisions, reconciling estimates and using milestones to confirm readiness before the project advances.
Preconstruction is where a project is either de-risked or quietly set up to fail. The failure mode is almost always the same: design advances faster than pricing, and nobody reconciles the two until a bid comes back thirty percent high.
Scope drifts before it is priced
Each design iteration adds detail. Unless someone maintains a scope of record, the estimate is always pricing a building that no longer exists.
Allowances hide decisions
An allowance is a deferred decision with a number attached. Track them as open items, not as line items.
The decision log is the control
Most owners have a budget and a schedule. Fewer have a written record of what was decided, by whom, and on what date. That record is what prevents relitigating the same choice in month nine.
Reconcile at gates, not at bid
Set phase gates — concept, schematic, design development, construction documents — and require a reconciled estimate at each. A surprise at the fourth gate is manageable. A surprise at bid is a redesign.
What Loss of Control Looks Like Before Construction
A project can appear active while key decisions remain unsettled. Drawings advance, estimates arrive and consultants meet, but the owner may still lack a confirmed scope, decision schedule or record of accepted assumptions. That disconnect often surfaces later as redesign, delayed approvals or bids that cannot be compared fairly.
Control does not mean eliminating every unknown. It means identifying open issues, assigning responsibility and understanding how each decision affects cost, schedule, permitting and procurement.
How Owners Can Restore Control
Start with a written project brief that states the intended use, scope, quality expectations, budget boundaries and target schedule. Then maintain a decision log, risk register and milestone schedule so unresolved matters remain visible to the owner and project team.
Require drawings, estimates and schedules to use the same scope assumptions. When one document changes, the related cost, timing and permitting effects should be reviewed before the team proceeds.
Why Early Estimates Can Create False Confidence
An early estimate is only as reliable as the information behind it. If design documents are incomplete, the estimate will depend on allowances, exclusions and assumptions. Those items are not inherently a problem, but they must be stated clearly and tracked as the design develops.
Owners lose visibility when estimate updates change format, include different scopes or bury prior assumptions. Each update should reconcile against the previous version and explain what changed because of design development, market input or a revised project decision.
The Owner Decisions That Cannot Be Deferred
Preconstruction depends on timely owner direction. Decisions about program, finishes, equipment, operating requirements and contracting approach affect the work of architects, engineers, estimators and permitting authorities. Leaving these matters open can force the team to design around assumptions that later prove incorrect.
A decision schedule should identify what must be decided, who provides the information and when direction is required. It should also show the consequence of a missed date, such as redesign, delayed pricing or a shifted permit submission.
How Control Is Lost in Preconstruction
Projects commonly lose control when design, budget and schedule move on separate tracks. The design team may advance details without current cost feedback, while the estimate may rely on a scope the owner has not formally approved.
Another warning sign is unclear authority. If consultants, contractors and owner representatives do not know who can approve a change, decisions may be delayed or made without a complete view of the consequences.
Set a Clear Basis for Design
The owner should establish a written basis for design before the team develops detailed documents. It should define the project goals, intended use, site constraints, required spaces, quality expectations and known approval requirements.
This document becomes the reference point for reviewing design proposals and requested changes. When priorities conflict, the team can return to an agreed set of requirements rather than relying on meeting notes or individual recollections.
Set Decision Rights Before Design Starts
A project can have an owner, architect, contractor and consultants in place and still lack a workable decision structure. Before design begins, identify who can approve scope, budget, schedule, contracts and design changes. Separate the person providing input from the person making the final call, and name a backup when the decision-maker is unavailable.
Create a decision log that records the issue, available options, cost and schedule effects, required decision date and final direction. Unresolved decisions should be escalated before they delay design or procurement. This is especially important when ownership includes multiple investors, family members, association board members or lenders with separate approval rights.
Build the Budget Around Total Project Cost
The preconstruction budget should include more than the contractor’s work. Track design and consultant fees, surveys and testing, permitting and utility charges, owner-furnished items, insurance, financing costs, temporary operations, escalation assumptions and appropriate contingencies. Keep construction contingency, design contingency and owner reserve separate so the team can see what each allowance is intended to cover.
At each design milestone, reconcile the estimate against the approved scope rather than simply comparing one estimate with the last. Identify what is included, excluded, carried as an allowance or still undefined. If the budget is over target, assign specific scope decisions with owners and deadlines; broad instructions to “value engineer” usually postpone the same problem.
Map the Approval Path for the Actual Jurisdiction
Do not treat “Charleston” as one permitting environment. A property may fall under the City of Charleston, Charleston County, Mount Pleasant, Sullivan’s Island, Isle of Palms, Folly Beach or another authority, each with its own submittal process and review sequence. Historic district review, architectural review boards, zoning relief and association approval may also apply before or alongside building permits.
Site conditions can add separate coordination for floodplain requirements, stormwater, tree protection, wetlands, septic, utility service, encroachments or work near state-maintained roads. Confirm jurisdiction, required reviews, submission dependencies and meeting calendars early. The schedule should show what can proceed in parallel and what must be approved before design, bidding or construction can advance.
Use a Gate Before Pricing and Construction
Before releasing documents for pricing, confirm that the scope is sufficiently defined, major systems are coordinated, owner selections are tracked and jurisdictional requirements are reflected in the drawings. Review constructability, long-lead items, access and staging, temporary protection, utility constraints and any occupied-site requirements. List remaining assumptions and assign responsibility for closing each one.
Before authorizing construction, reconcile the contract sum to the total project budget and confirm the baseline schedule, allowances, alternates, insurance, permit status and procurement plan. Also establish change-order authority, submittal and RFI workflows, reporting cadence and payment review procedures. If an item is intentionally deferred, document its cost exposure, schedule consequence and decision deadline rather than allowing it to remain an informal open issue.
Common questions
- Who should maintain the preconstruction decision log?
- One person should be responsible for keeping the log current, distributing it and recording final direction. The owner should confirm who has approval authority and which decisions require input from designers, contractors or other consultants.
- When is a project ready to move from design into construction?
- The project should have an approved scope, coordinated documents, a current cost forecast and a schedule that reflects permitting and procurement needs. Remaining assumptions and risks should be visible, assigned and accepted by the owner.
- What should an owner ask for at each design milestone?
- Ask for the current drawing set, estimate, milestone schedule, decision log and list of major risks or exclusions. These materials should use consistent assumptions and explain changes since the prior review.