Incomplete Design Set: Budget or Bid?

Key takeaways

• An incomplete design set should usually be priced as a budget or design-development estimate, not as a final bid.
• A written basis of estimate is what keeps an early budget number from being mistaken for a complete scope price.
• Measure the scope that is defined, and carry the rest as explicit assumptions or allowances.
• Early vendor input matters most on scopes that can materially affect cost, procurement, or package strategy.
• Every estimate update should show the change from the prior issue so scope growth is visible.

If the design set is still incomplete, treat the number as a budget or design-development estimate rather than a final bid. The estimate should be issued with a written basis of estimate, clear assumptions and allowances, targeted vendor input, and a defined update path as the documents advance.

An incomplete design set should be priced as a budget or design-development estimate

An early design estimate is meant to support decisions, scope alignment, and planning. It is not the same as a later bid built from a more complete document set.

The first question is not the price. The first question is how the number will be used.

Common uses include:

• Budget pricing for feasibility or owner review
• A design-development checkpoint to show cost movement as the documents develop
• A preliminary carry on fast-track work where package planning or early procurement starts before the full set is complete

Those uses require different estimate language. A budget estimate can rely on broader assumptions. A preliminary carry needs tighter scope notes so an early number does not get treated like a final commitment.

AACE estimate classification guidance separates early design estimating from later-stage estimates with more complete definition. The estimate label should match the level of design information available.

The basis of estimate is the main deliverable

At this stage, the basis of estimate matters as much as the number. Without it, the estimate is easy to misread and hard to update.

A sound basis of estimate should identify:

• The drawing set, specification sections, and addenda reviewed
• The estimate date and pricing date
• The estimate purpose, such as budget pricing, design-development review, or preliminary bid carry
• The level of document development by discipline when architectural, structural, civil, and MEP information are not equally complete
• The measurement method used for major scopes
• The assumptions behind quantities or assemblies that are not fully shown
• The allowances carried for undefined items
• The exclusions, deferred scopes, or owner-furnished items reflected in the number
• The schedule, phasing, access, or sequencing assumptions that affect cost
• The procurement assumptions for long-lead or specification-sensitive items
• The RFIs or clarifications that still need answers

The basis should also explain how the estimate was built. Some scopes may be taken directly from drawings. Others may be carried by assembly, system, or vendor input where design detail is still limited.

For a general contractor, the basis should show which bid packages are reasonably defined and which remain conceptual. For a trade contractor, it should show what is included in the trade scope and what is still pending design, vendor selection, delegated details, or coordination.

Tribuild Consultancy is a multi-trade estimating, preconstruction, and project-administration company.

Measure defined scope and state the rest

The practical approach is simple: measure what is reasonably shown, and state the rest plainly. Forcing detailed takeoff from incomplete information creates false precision.

Measure the major cost drivers that are actually visible

Early estimates are strongest when they focus on scope that is shown well enough to influence the project total in a meaningful way.

Examples include:

• Gross building area and major program areas
• Site paving, retaining, or underground utility runs when civil intent is sufficiently developed
• Structural framing concepts, slab areas, and foundation types when the basis is shown
• Exterior wall area, glazing scope, and roofing area
• Core interior build-out scope such as partition types or ceiling areas when plans support it
• Major equipment counts from schedules or narratives

Carry incomplete detail as assumptions or allowances

Where branch distribution, supports, trims, accessories, or finish transitions are not fully defined, system-level carries are more reliable than pretending the detail is complete.

Examples include:

• A drywall estimator may quantify primary partition types and carry specialty backing, acoustical sealant intensity, or detail-driven conditions as stated assumptions or allowances
• A mechanical estimator may quantify listed equipment and major duct mains while carrying final branch routing, controls coordination, or terminal density by assumption
• An electrical estimator may count major service equipment and fixture intent while carrying final device layout, homeruns, or specialty systems by allowance until the design is clearer
• A general contractor may carry specialties, toilet accessories, or final hardware sets by allowance when room layouts are developed but product selection is still open

Keep assumptions and allowances separate

An assumption is the condition used to price the work. An allowance is a cost carry for scope that is not defined enough to price directly.

State both clearly. If an assumption changes, the estimate should change. If an allowance is replaced by defined scope, the estimate should be reconciled and updated.

When the documents conflict or leave a true scope gap, log it early. Unresolved issues may require an RFI or clarification from the responsible party.

Vendor input should focus on scope that can move cost or procurement

Early vendor outreach matters most on scopes that can materially affect cost, schedule, or package strategy. You do not need full quote coverage on every trade to improve an early estimate.

Prioritize outreach when:

• The scope is a major cost driver
• The item has a long lead time
• The package includes delegated design or heavy coordination
• The specification leaves multiple product paths open
• Freight, access, or phasing could materially affect installation cost
• The estimate depends on a major equipment or system decision

Typical scopes for early market input may include:

• Structural steel, joists, and deck
• Curtain wall and glazing systems
• Roofing assemblies
• Major HVAC equipment
• Switchgear, generators, and distribution equipment
• Elevators and other equipment packages
• Specification-sensitive finish packages

The goal is to understand the vendor's pricing basis, pending items, major exclusions, lead-time concerns, and product choices that could materially change the estimate.

Update the estimate whenever the documents materially change

An early estimate is not finished when it is issued. It needs a defined update path tied to document development, addenda, procurement decisions, and scope clarifications.

Each update should do three things:

• Replace broad carries with direct quantities where the drawings now support takeoff
• Reconcile prior assumptions and allowances against newly defined scope
• Show the delta from the previous estimate issue so scope growth and pricing movement are visible

That update discipline matters on negotiated work, design-assist work, and fast-track projects. An early budget number can drift into an accidental commitment if the documents keep changing but the estimate record does not.

The estimate should make uncertainty visible

A useful early estimate makes the known scope, the assumed scope, the pending questions, and the next review point visible. That is more valuable than presenting a detailed number that the documents do not support.

Contractors who treat early estimating as a connected workflow, drawing review, scope interpretation, vendor input, proposal language, and estimate updates, put themselves in a stronger position when the design advances into bid, procurement, and project administration.

If you want to review one upcoming project or one estimating workflow, Tribuild Consultancy can discuss a multi-trade estimating requirement.

Sources

• https://tribuildconsultancy.com
• https://web.aacei.org/resources/publications/recommended-practices