Glossary
Preconstruction vs Construction
Last updated
Definition
Preconstruction and construction are the two distinct phases of a general contractor's involvement on a project, separated by contract award. Preconstruction covers everything that happens before the contractor is under contract to build, including business development, bid preparation, estimating, sub solicitation, proposal writing, and the negotiation that leads to award. Construction covers the work that happens once the contract is signed, including procurement, scheduling, field operations, project controls, and closeout. The two phases are run by different teams in many firms, with the preconstruction department leading the bid effort and handing the project to the operations team at award.
Context
The structural separation between preconstruction and construction reflects the fact that the two phases involve different work, different rhythms, and different skill sets. Preconstruction is a sales and documentation operation. Its output is a bid response that wins work at acceptable margin. Construction is an execution and management operation. Its output is a finished project delivered on schedule, on budget, and to the contract specifications.
Most general contractors above a certain size run a dedicated preconstruction department, often led by a Director of Preconstruction or a VP of Estimating. The department typically includes estimators who work the takeoffs and pricing, proposal writers or marketing staff who handle the qualitative content, and business development personnel who manage the relationships with owners, architects, and developers that bring opportunities into the firm. Smaller firms collapse the function into the same people who later run the project, which works at low bid volume and breaks down as the firm grows or as bid volume increases.
The handoff between the two phases is one of the points where projects most commonly run into trouble. The preconstruction team has spent weeks or months developing a deep understanding of the bid documents, the owner’s expectations, the sub pricing assumptions, and the schedule logic that supports the price. The operations team inheriting the project has to build that understanding from scratch unless the handoff is structured deliberately. Firms that run smooth handoffs typically formalize the process through bid-to-build meetings, written turnover documents, and continued involvement from the lead estimator into the early weeks of construction.
Components
The preconstruction phase typically includes the following activities:
- Business development and opportunity identification. Tracking solicitation feeds, maintaining relationships with owners and design firms, attending pre-bid meetings, and deciding which opportunities the firm will bid on.
- Bid go/no-go decisions.Evaluating each opportunity against the firm’s capacity, the strategic fit, the competitive landscape, and the expected probability of award before committing the resources to bid.
- Quantity takeoffs and estimating. Reading the drawings and specifications, performing quantity takeoffs by trade or system, applying current unit pricing, and building up the cost estimate to a complete bid number.
- Sub solicitation and scope leveling. Distributing scope packages to subcontractors, collecting sub bids, leveling the bids to ensure scope completeness and fair comparison, and selecting the subs whose pricing will support the prime bid.
- Proposal preparation. Producing the proposal narrative, the compliance matrix, the indexed drawing set, and the action checklist of contractor-supplied items required for submission. This is the documentation work that turns the pricing effort into a bid response the owner can evaluate.
- Pre-bid coordination. Attending mandatory and discretionary pre-bid meetings, submitting requests for information through the channels the solicitation specifies, and incorporating addenda into the bid response as they are issued.
- Final review and submission. The pre-submission review where the proposal narrative, the compliance matrix, and the action checklist are reconciled against the solicitation, and the bid package is submitted in the format and on the schedule the owner has specified.
The construction phase, which begins at contract execution, includes:
- Project mobilization. Setting up the field office, establishing the project team, executing subcontracts and purchase orders, and securing the bonds, insurance, and permits required to start work.
- Procurement and submittal management. Issuing material orders, processing shop drawings and product data through the submittal review cycle, and managing long-lead items that drive the schedule.
- Field operations. Running the daily construction work, coordinating trades, managing safety and quality, and resolving the field issues that arise during execution.
- Project controls.Tracking cost against budget, schedule against baseline, and contract changes through the change order process. The project controls function feeds the firm’s internal reporting and the owner-facing reporting the contract requires.
- Closeout.Punch list completion, final inspections, owner training, warranty documentation, and the final accounting that closes the project on the firm’s books.
Common Mistakes
- Treating preconstruction as a cost center rather than a margin lever. The preconstruction phase is where margin is set, both through the pricing decisions and through the qualitative positioning that determines whether the firm wins the bids it wants to win. A firm that staffs preconstruction lean to control overhead ends up with thin proposals, missed bids, and a pipeline that does not support the operations side.
- Letting construction-phase staff carry preconstruction work as overflow. Asking project managers and superintendents to write proposals during construction-phase downtime produces preconstruction output that reflects construction-phase priorities rather than bid-stage requirements. The proposal narrative reads as operational instead of evaluative, and the time the operations staff spend on bid work is time they are not spending on the projects they are running.
- Skipping the bid-to-build handoff. The preconstruction team holds context that the operations team needs at the start of the project. Firms that do not formalize the handoff lose that context, which shows up later as scope misunderstandings, budget surprises, and avoidable schedule problems in the early weeks of construction.
- Confusing preconstruction services with the preconstruction phase of a hard-bid project. Some delivery methods, particularly Construction Manager at Risk and design-build, include a paid preconstruction services phase where the contractor works alongside the design team during design development. That phase is contractually different from the bid-stage preconstruction work on a design-bid-build project, and conflating the two produces confused conversations about what the firm is being asked to do.
- Underestimating the bid volume the preconstruction department can sustain. Each estimator on the team has a realistic ceiling on the number of bids they can prepare in a given period without quality degrading. A department that consistently runs above that ceiling produces lower-quality bids, declines opportunities it should be pursuing, or both. The capacity question is structural, not an effort problem.
How ScalaBid Handles This
The ScalaBid service sits within the preconstruction phase of the contractor’s work, specifically on the documentation side of bid preparation. Each ScalaBid Submission Packageis delivered inside the 72-hour engagement window. The contractor’s preconstruction team continues to handle the strategic decisions that belong with the firm: which opportunities to pursue, how to price the work, which subs to select, what positioning to emphasize, and what the final bid number should be. The Submission Package is what the team works from during the documentation production stretch, which removes the assembly burden from the estimators and lets the preconstruction department run more bids at the same staffing level. Firms that hit the capacity ceiling described above commonly find that the binding constraint is documentation production rather than estimating capacity, and this is the constraint the package is built to relieve.