Use the estimate to answer a specific budget question
Before asking for an early cost figure, identify the decision it needs to support. A developer may be testing whether a proposed building area is feasible. An architect may need to compare two envelope systems. An owner may be deciding whether to phase a renovation. Those questions call for different scope boundaries and levels of detail.
A preliminary estimate should state which construction costs it covers and which project costs sit outside it. Land, design fees, permits, financing, owner equipment, and other non-construction items should not be assumed included simply because the document has a grand total.
What information can support an early estimate?
Complete construction documents are not essential for an initial budget, but the estimator still needs a defined basis. Location, approximate area, building use, proposed systems, quality expectations, and schedule help describe what is being estimated. Sketches and design narratives should be dated so a later update can be compared with the same starting point.
- Project location and approximate gross area
- New construction, addition, renovation, or phased occupied work
- Known structural, enclosure, finish, and building-system choices
- Available concept drawings, narratives, surveys, and existing-condition information
- Pricing date, planned construction period, and owner budget boundaries
- Options to compare and decisions that remain open
Conceptual, schematic, and detailed estimates
At an early concept stage, the available information may support area-based or system-based allowances rather than measured components. Schematic drawings can support more defined geometry and assemblies. As details and specifications develop, the estimator can replace broader assumptions with measured scope and project-specific quotations.
The label alone does not establish reliability. Ask what documents were used, how the quantities were developed, what pricing basis applies, and which items are still allowances. A detailed-looking spreadsheet does not remove uncertainty from an undefined building system.
A simple example of comparing budget updates
Consider a fictional cost plan with a $400,000 base construction allowance and a separately identified $40,000 allowance for unresolved scope. Its subtotal is $440,000 before any additional agreed contingency, escalation, owner costs, or fees. These figures are invented to show organization; they are not market rates or a project quotation.
Suppose the next design review changes the base construction scope to $430,000 and resolves the undefined scope at $35,000. The comparable subtotal becomes $465,000. The $25,000 increase is explained by a $30,000 rise in base scope and a $5,000 reduction in the separate allowance. Recording both movements is more useful than reporting only that the total increased.
Keep allowances, contingency, and escalation distinct
An allowance provides a stated basis for scope that is known but not yet sufficiently defined. Contingency addresses uncertainty and risk within the agreed cost plan. Escalation addresses expected price movement over time. Define the purpose, basis, and inclusion of each rather than hiding them in one unexplained markup.
Do not copy an accuracy percentage or contingency rate from an unrelated project and treat it as a promise. The available documents, scope uncertainty, procurement strategy, and market conditions determine what the estimate can reasonably support. The estimator should explain those limits in the basis of estimate.
When should a preliminary estimate be updated?
Update when the project changes materially: added area, a different structural or MEP system, revised finish selections, new site information, phasing, or a changed procurement schedule. Keep a record of what changed between design issues and distinguish scope movement from a change in pricing assumptions.
Before final bidding, review the coordinated drawing set, current specifications, addenda, supplier coverage, and contractor-specific costs. A preliminary budget can inform that process, but it should not be presented as a completed trade bid when its scope is still conceptual.
Further reading
GSA describes how estimates develop as project scope and design become clearer in its guidance on developing and managing project costs. Its agency-specific estimate ranges are not a guarantee for a One Estimating assignment.