AEC definitions

What Is Value Engineering in Construction?

Last reviewed: September 2026

Value engineering is a structured review of a design to deliver the function the owner actually needs at a lower life-cycle cost. Done during design, it can change systems before they are detailed. Used as a nickname for cuts after pricing, it often deletes scope instead.

Also called
VE
Question it asks
What function is required, and what else can perform it
Best timing
Design development, before details and specs lock
Who proposes
Designers, estimators, and builders with a pricing role
Must update
Drawings, specifications, and the estimate together
Weak form
Late deletions after the set is already coordinated

Definition

Value Engineering (VE)

Value, in this method, is function divided by cost. A VE study names the function of an assembly, asks what else could perform it, and prices the alternatives, including operating cost when the owner will live with the choice. The classic timing is design development, when systems are chosen and details are not yet drawn. Contractors on CM-at-risk and design-build teams submit VE ideas against the estimate. Accepting an idea is a design change: drawings and specifications both move. A VE log that only says "cheapen the facade" without a function and a spec edit is a cost-cutting list.

In depth

Start with the function, not the line item

A curtain wall’s function might be daylight, thermal performance, and a corporate image, not "curtain wall." A VE alternative might be a punched window and a spandrel if those functions survive. If the image was the function the owner funded, the alternative fails even if it is cheaper. Writing the function down keeps the study from becoming a hunt for the most expensive spec section.

Life-cycle cost belongs in the same note. A cheaper roof that fails sooner, or a mechanical system with higher energy use, can be a worse value. First-cost VE that ignores the owner’s operating budget solves the bid and harms the building. Say which cost the owner asked you to optimize.

Timing decides whether the idea is real

During schematic design and design development, a structural system or an HVAC concept can change with redrawing measured in days. At 90% CD, the same idea redraws coordinated details, specifications, and possibly the code path. After bids, it is a change order or a VE alternate the bidders priced. Teams that "do VE" the week before the bid set is issued are negotiating scope reduction under a more respectable name.

The estimate has to be mature enough to prove a saving. VE against a schematic allowance is a guess. VE against a 60% estimate, with quantities, can be accepted or killed with a number. That is why the 60% gate and the DD estimate are the practical windows.

An accepted idea has to land in the documents

Each accepted item needs an author, a drawing list, and a specification section. "Delete the access floor, save $400,000" is not done until the plans, the details, and the spec section agree, and the estimate drops by that scope only once. Orphan details of the deleted system are how the submittal phase buys it anyway.

Rejected ideas should stay on the log with a reason. Owners reopen cost conversations. A rejected VE item with no record gets redesigned twice. The log is also the defense when a contractor later proposes, as a substitution, an idea the owner already declined.

Contractor proposals need a design decision

Builders see means the drawings do not show: a repetitive detail, a specified product with a long lead, a wall type that is slow. Those proposals are valuable and they are still design changes if they alter performance or appearance. The architect or engineer of record has to accept them. A contractor-accepted VE item that never hits the sealed documents is a field change with no stamp.

Shared-savings clauses on GMP jobs can pay the contractor for accepted ideas. That is an incentive, not a transfer of design responsibility. The owner should see the cost basis. A saving measured from an inflated estimate is not a saving.

Examples

Value Engineering (VE) on a real project

  • 01

    A DD study replaces a custom exterior panel with a standard rainscreen after the owner agrees the function is durability, not a unique profile.

  • 02

    A 90% "VE" list deletes casework scope so the bid hits a number, and the documents have to be revised before issue.

  • 03

    A CM proposes an alternate chiller. The mechanical engineer accepts it and edits the schedule and the specification.

FAQ

Frequently asked questions

Value engineering is a review of design choices aimed at providing the owner’s required function at a lower cost, often including operating cost. It works by comparing alternatives before the documents are fully detailed.

During schematic design and design development, and at a 60% estimate when quantities exist. Late VE, after the set is coordinated or after bids, is usually scope reduction and costs more to document.

Value engineering keeps the required function and changes the way it is delivered. Cost cutting removes function or quality to hit a number. The labels get swapped on live projects, which is why the function and the spec edit should be written down.

The owner decides whether the function and the saving are acceptable. The architect or engineer of record has to agree the alternative meets the design and the code, and then revise the documents. A contractor can propose an idea and cannot seal it.
Accelerating the design and construction of the built world.

Unlock the value of your institutional knowledge—organized, connected, and grounded in your team's critical workflows with Nomic.

Start for free
What Is Value Engineering in Construction? | Nomic