Preliminary estimating helps a project team test budget, scope, and design direction before construction documents are ready. The method should match the information available: conceptual estimates use broad program and system assumptions, schematic estimates respond to early geometry and assemblies, and design-development estimates add detail as systems become defined.
One Estimating documents the basis of estimate, design information reviewed, location, pricing date, allowances, exclusions, and unresolved decisions. This allows each update to be compared against the previous stage instead of presenting an unexplained total.
What is included
- Document and design-stage review
- Basis-of-estimate narrative
- System, assembly, area, or elemental cost development
- Allowances for undefined scope when appropriate
- Option and alternate comparison when requested
Choose the method to match the design stage
An early concept cannot support the same line-item certainty as a coordinated construction-document set. Conceptual estimates rely more on program, gross area, systems, analogous assemblies, and explicit allowances. As drawings develop, broad assumptions can be replaced with measured quantities and defined products.
Stating the estimate class in plain language prevents false confidence. The deliverable explains which inputs are firm, which are inferred, and which remain allowances or exclusions.
Managing changes between estimates
Budget movement can result from added area, system changes, specification upgrades, schedule, escalation, market conditions, or simple scope clarification. A disciplined update separates those drivers where the documents allow it.
Project teams get the most value when each estimate uses a controlled design issue and records decisions made since the previous review. That creates a cost history the team can discuss with the design rather than only comparing totals.
Location, escalation, and uncertainty
Early estimates still need a project location and pricing date. Labor conditions, taxes, freight, material availability, access, and schedule can influence a concept before detailed quantities exist.
Contingency and escalation are not interchangeable. Contingency addresses defined categories of uncertainty; escalation addresses expected cost movement over time. We include or exclude them only as agreed and identify the basis used.
Common scope and estimating risks
- Presenting an early estimate without a basis or design-stage qualifier
- Using detailed-looking unit costs for undefined systems
- Failing to track owner scope and alternates between updates
- Combining contingency and escalation without explanation