Common Misconceptions about Value Engineering (VE)

Amin Terouhid, Ph.D., CVS

 

Executive Takeaway: Industry practitioners sometimes mischaracterize Value Engineering (VE) as an aggressive, late-stage cost-cutting tool deployed only when a project faces budget overruns. In practice, treating VE as an exercise in price-slashing degrades the actual value that VE exercises provide and the main purposes it serves. VE is a function-oriented methodology used by a multidisciplinary team aimed at improving the value of a project, product, process, service or organization [1]. Correcting these misconceptions is essential for those who seek to maximize returns on their investments and enhance the value of their projects, products, processes, services, or organization.

Key Misconceptions

  1. Misconception: “Value Engineering Is Just a Fancy Term for Cost-Cutting”

When a capital project exceeds its baseline estimate, project managers often announce a “Value Engineering phase.” In practice, this phase usually degenerates into a reactive exercise where designers, contractors, and owners meet to slash line items, eliminate scope, or downgrade finish standards to meet an immediate budget cap. Because these budget-clearing drills are labeled as “VE,” industry professionals have come to assume that value engineering is simply a euphemism for cheapening a design.

Value Engineering, however, as established by international standards bodies such as SAVE International, does not begin with a dollar target; it begins with an analysis of Function [1]. Function analysis forces project teams to strip away specific physical solutions and ask fundamental questions: What must this asset or system actually do?

Traditional cost-cutting focuses strictly on reducing upfront capital expenditures (CapEx) by removing components. VE, by contrast, identifies alternative, often innovative ways to fulfill the required function at equal or superior performance levels.

When a team simply removes scope or specifies inferior materials without re-evaluating the underlying function, they are not performing VE. Instead, they are executing an unvetted scope concession that often compromises the project’s core intent.

  1. Misconception: “VE Inherently Compromises Project Quality”

Designers, architects, and end-users sometimes resist VE proposals because they operate under the assumption that “value” is a code word for compromise. Such a narrative suggests that any modification proposed during a VE workshop will inevitably result in a second-tier facility: thinner walls, less reliable equipment, degraded architectural aesthetics, or shortened asset service life. This misconception stems from a fundamental misunderstanding of the mathematical definition of Value, which is performance achieved based on the resources used. In a formal value study, value is defined as the quotient of functional performance divided by resource expenditure. This formulation underscores how effectively a design transforms invested assets into results. As such, value can be enhanced in several ways that have nothing to do with sacrificing quality. Examples include:

  • Increasing Performance while holding Resources constant: Introducing higher-efficiency equipment or a more flexible layout for the same capital investment.
  • Maintaining Performance while reducing Resources: Fulfilling the exact technical and operational requirements through an alternative layout or modular construction technique that requires less material and labor.
  • Significantly increasing Performance with a minor increase in Resources: Investing slightly more capital upfront to eliminate a chronic operational bottleneck, which yields significant long-term reliability gains.

VE actively protects baseline performance standards. For example, if an alternative proposal reduces safety margins, degrades required capacity, or accelerates material failure rates, it fails the fundamental test of functional equivalence.

  1. Misconception: “Value Engineering Is a Late-Stage Emergency Intervention”

On some capital programs, VE is treated as an emergency brake, a process invoked only at 90% design completion or after construction bids come in significantly over budget. The team rushes through a high-pressure workshop to identify immediate design rollbacks so the project can move forward to award or groundbreaking.

Treating VE as a late-stage rescue mechanism severely diminishes its effectiveness. The ability to influence total project value follows an exponential decay curve across the project lifecycle, while the cost of implementing changes increases dramatically over time. Therefore, when VE is delayed until the end of design:

  • Redesign Costs Multiply: Architectural and engineering revisions require extensive rework of calculated drawings, calculations, and specification packages, which erodes the net financial gains of proposed changes.
  • Schedule Delays Cascade: Re-evaluating major systems late in the design phase may cause disruptions.

To capture maximum strategic value, owners must deploy Value Engineering during the conceptual and schematic phases—when fundamental decisions regarding footprint, structural framing, system selection, and spatial relationships are still fluid.

  1. Misconception: “VE Focuses Purely on Initial Construction Costs (CapEx)”

Financial management on capital projects is often structured in silos: the project management team is evaluated solely on delivering the asset within the initial construction budget (CapEx), while the facility operations team inherits the ongoing operational costs (OpEx). Because of this split, VE workshops frequently fall into the trap of evaluating alternatives based exclusively on upfront installation prices.

Evaluating capital decisions solely on initial contract pricing creates a distorted picture of asset economics. A lower upfront purchase price frequently conceals costs such as higher energy consumption, complex maintenance requirements, or expensive replacement parts. It is important to note, however, that VE evaluates proposals through the lens of Total Cost of Ownership (TCO) by assessing complete asset lifecycles and factoring in the time value of money.

  1. Misconception: “The Design Team Can Facilitate Its Own VE Process”

Project owners looking to streamline administrative overhead often ask their primary design firm to lead the internal VE review. The rationale seems straightforward: the original engineers and architects understand the facility requirements better than anyone else, so they should be best positioned to optimize it. This approach overlooks two critical human and organizational factors: confirmation bias and disciplinary isolation.

  • Confirmation Bias: Design teams often invest hundreds of hours developing specific technical solutions. Expecting them to objectively critique their own assumptions, challenge their own design choices, or propose alternatives that render their previous work obsolete is unreasonable.
  • Siloed Perspectives: Designers often lack real-world insights into daily facility maintenance, constructability bottlenecks, current supply chain realities, and specialized trade labor availability.

A VE workshop requires independent process leadership provided by a certified facilitator (such as a Certified Value Specialist) [1]. An independent facilitator brings no emotional attachment to the baseline design, enforces strict adherence to the formal VE Job Plan, encourages cross-disciplinary debate, and ensures that facility operators, cost estimators, and contractors have an equal voice in shaping project outcomes.

Conclusion

In conclusion, VE is not a late-stage emergency exercise, a superficial cost-slashing exercise, or a compromise on project quality, nor is it a self-assessment best left to original design teams or limited to upfront CapEx line items. Far more effective than these reactive, price-focused missteps, VE is a function-oriented methodology used by a multidisciplinary team aimed at improving the value of a project, product, process, service, or organization. By deploying a multidisciplinary team early in the design phase, VE aims to optimize the true performance-to-resource ratio, to preserve or enhance functions and enhance the overall value provided by the project, product, process, service, or organization.

References

  • [1] SAVE International. Value Methodology Standard and Body of Knowledge.
  • [2] Federal Highway Administration (FHWA). Value Engineering Policy and Job Plan Guidelines.

 

Value Methodology for Capital Asset Owners: An Effective Approach for Enhancing the Value

Amin Terouhid, Ph.D., CVS

 

Executive Takeaway: Value Engineering (VE), when deployed as an owner-driven, function-oriented discipline, serves as a primary engine for enhancing value. Rather than functioning as a late-stage cost-cutting exercise, systematic Value Methodology aligns early design parameters with long-term operational objectives, regulatory demands, and user expectations.

Function Analysis and Overall Project Value

For owners of capital infrastructure, project success extends far beyond budget adherence; value is defined by factors such as the alignment of functional performance, operational reliability, asset adaptability, and stakeholder satisfaction. Traditional project reviews often make the mistake of narrowing their focus strictly to capital expenditure (CapEx) line items, which may adversely affect function, compound operational complexity, or compromise the service life of the project in the process.

VE shifts this dynamic by elevating the conversation from what a project costs to what a project achieves.

Two of the core considerations that establish the foundation for value-driven capital asset ownership include:

  • Function: Analyze the project to understand and clarify the required function of the project.  In accordance with SAVE International standards, functional analysis empowers owners to eliminate unnecessary design friction, improve user experience, and reallocate project resources toward high-impact performance drivers [1].
  • Performance: Criteria governing functional execution, including operational capacity, system redundancy, safety margins, environmental sustainability, and target service life.

Maximizing Project Value

The capacity to enhance project value changes dramatically throughout the delivery lifecycle. During early concept phases, owners possess maximum flexibility to optimize facility configuration, streamline operational workflows, and integrate innovative design solutions. As design matures and solidifies, opportunity shifts toward constructability enhancements, installation quality, and risk reduction.

To maximize long-term project outcomes, owners must integrate structured VE milestones across key project stages:

  1. Conceptual & Planning Phase

During initial project formulation, value studies refine project vision, align multi-stakeholder priorities, right-size facility footprints, and optimize system architecture. Intervening at this stage establishes an adaptable project framework, which can reduce design rework and establish clear performance criteria before design is solidified.

  1. Schematic & Detailed Design Phase

During design development, the VE framework evaluates discipline-specific assemblies (e.g., structural framing systems, MEP redundancy, building envelope performance, and spatial flow). In this phase, the focus shifts to enhancing operational functionality, improving maintainability, standardizing systems, and optimizing construction sequencing.

  1. Construction & Execution Phase

During construction, value methodology transitions to formal Value Engineering Change Proposals (VECPs). At this stage, contractors propose field-level innovations, advanced material technologies, or constructability improvements. Owners maintain rigorous technical oversight to ensure that construction innovations improve field execution without compromising specified quality or long-term durability.

Methodological Framework

To yield results, capital owners are recommended to adhere to a standardized, multi-phase value methodology. As recognized by SAVE International and the Federal Highway Administration (FHWA), the VE Job Plan provides a disciplined structure for objective project enhancement [1, 2]. Each stage of the Job Plan fulfills a distinct function:

  1. Information Phase: Gathers baseline requirements, stakeholder goals, operational constraints, design models, and risk registers to establish a complete project picture.
  2. Function Analysis Phase: Maps required performance outputs using active verb/measurable noun pairs, uncovering areas where design complexity does not contribute to core project goals.
  3. Creativity Phase: Conducts multidisciplinary brainstorming to generate innovative design concepts, technological substitutions, and operational improvements.
  4. Evaluation Phase: Screens potential ideas against owner-defined value criteria, such as operational reliability, safety, and maintainability.
  5. Development Phase: Models viable VE alternatives into engineering proposals, supported by performance calculations, constructability reviews, and lifecycle impact assessments.
  6. Presentation & Action Phase: Submits formal recommendations to executive leadership and key stakeholders for final review and implementation.

Conclusion

Ultimately, embedding Value Engineering (VE) as a governance discipline transforms capital asset ownership from a reactive management exercise into a proactive value-creation strategy. By leveraging decisions in function analysis and conducting the workshop process through the structured VE Job Plan, owners ensure that resources spent serve a defined objective. Rather than compromising quality through superficial cost-cutting, the VE methodology aims to balance upfront execution with long-term performance, durability, and operational adaptability. Integrating VE milestones from early planning through construction by strategies such as enforcing multidisciplinary collaboration and conducting VE workshops can help capital projects better fulfill their strategic intent, minimize lifecycle costs, and increase the overall value the provides.

References

  • [1] SAVE International. Value Methodology Standard and Body of Knowledge.
  • [2] Federal Highway Administration (FHWA). Value Engineering Policy and Job Plan Guidelines.
  • [3] U.S. Government Accountability Office (GAO). GAO Schedule Assessment Guide & Cost Assessment Guide: Best Practices for Project Management (GAO-16-89G / GAO-20-195G).

 

Value Engineering and Constructability Reviews: How to Coordinate Two Complementary Services

Amin Terouhid, Ph.D., CVS

 

Executive takeaway. Value engineering (VE) and constructability reviews address somewhat different questions, but their findings often intersect. VE evaluates whether project, process, or system functions can be delivered with better overall value. Constructability review, on the other hand, evaluates whether the design can be built safely, efficiently, and as intended. Coordinating these services gives owners broader insight while preserving separate objectives, methods, and records.

Different questions, complementary results

Value engineering (VE) is a structured, multidisciplinary process that analyzes project functions and develops VE alternatives or design suggestions to improve value. A function states what the project must accomplish, and performance describes how well that function must be delivered to be able to demonstrate performance in areas such as capacity, safety, reliability, maintainability, and code requirements. Resources typically include money, time, labor, equipment, materials, and energy. SAVE International’s Value Methodology uses function analysis to examine the relationship between function, performance, and resources. [1]

Although VE and constructability reviews address somewhat different questions, their findings often intersect. A constructability review is a systematic examination of design documents by people with relevant construction knowledge. It considers whether the work can be safely built with available access, equipment, labor, materials, sequencing, temporary works, and site controls. The review may also identify incomplete details, conflicts between drawings and specifications, difficult interfaces, unclear bid requirements, and obstacles to inspection or maintenance. USACE describes constructability reviews as evaluating project and contract features for ease of successful and safe execution.

The distinction is practical. For example, VE may ask whether another structural system can transfer the required loads with better life-cycle value. Constructability review, on the other hand, may ask whether the selected system can be fabricated, delivered, erected, connected, inspected, and protected under actual project conditions. Either review may identify cost or schedule benefits, but neither should be reduced to informal cost cutting or routine drawing coordination. The following table compares the primary questions, the main lens through which these types of studies assess the project, and their typical output:

 

Comparison

VE Study

Constructability Review

Primary question

What must the project do, and how can value improve?

Can the design be built safely and efficiently?

Main lens

Function, performance, resources, and life-cycle value

Access, sequencing, means and methods, interfaces, and field conditions

Typical output

Developed design suggestions and VE alternatives with evaluation and recommendations

Comments, risk items, design clarifications, and practical corrections

Overlap occurs when a constructability observation reveals a value opportunity. Limited crane access, for example, may prompt a different assembly strategy. Conversely, a VE alternative may introduce new construction risks that require a closer review. The two services should exchange information, but each finding should retain its origin and evaluation criteria. They have different focus areas.

Coordinate the reviews through one decision process

The owner typically begins with a common information package, consisting of the owner’s project requirements, drawings, specifications, cost estimate, schedule, site and utility information, permit conditions, risk register, and/or major procurement assumptions. The owner’s project requirements define the outcomes and performance the completed facility must achieve.

A qualified VE facilitator leads the structured VE Job Plan, including information, function analysis, idea generation, evaluation, development, and presentation. SAVE International and FHWA describe these phases as an organized process for developing and presenting alternatives. The constructability lead coordinates discipline reviews and consolidates comments on execution, safety, access, sequencing, interfaces, and document completeness. Designers explain the design basis and evaluate changes, and the owner accepts, rejects, or defers recommendations. [1, 2]

A shared issue log can prevent duplication. Each item should record its source, affected requirement, discipline, cost and schedule implications, responsible evaluator, decision, and required follow-up. Similar comments may be combined, but a constructability correction should not be reported as a VE saving unless it has undergone functional and value evaluation. Likewise, a VE alternative should not be recommended for implementation until its constructability has been verified.

Recommendations for owners

Owners are recommended to define separate scopes and deliverables; schedule coordination early enough to influence design; include design, construction, operations, estimating, scheduling, safety, and procurement knowledge; use one controlled issue log; verify VE alternatives for constructability before approval; evaluate constructability ideas through VE when they change function, performance, or life-cycle economics; and document final decisions and assigned actions.

Coordinating the reviews supports that balance by avoiding solutions that appear economical but are difficult to build, operate, or maintain. The objective is not to maximize the number of comments or VE alternatives. Instead, the objective is to produce practical and reasonable VE alternatives or constructability recommendations that are practical, buildable, preserve required functions, meet performance criteria, use resources responsibly, and reduce avoidable project risk.

References

[1] SAVE International. About the Value Methodology.

[2] Federal Highway Administration. The Value Engineering Process and Job Plan.

From Value Engineering Workshop to Implemented Value: Closing the Value Engineering Follow-Through Gap

Amin Terouhid, Ph.D., CVS

Maryam Mirhadi, Ph.D., VMA

 

Executive takeaway. A value engineering (VE) workshop produces VE alternatives or design suggestions, but value remains unrealized until the project team acts. Owners should make timely decisions, assign responsibility, incorporate accepted VE alternatives or design suggestions into the design, and verify the work. Structured follow-through connects VE workshop to project delivery.

The workshop is a decision point, not the finish line

Value engineering (VE) is a structured, multidisciplinary process that uses function analysis to improve the relationship between required performance and the resources needed to achieve the intended functions and enhance the value of a project, process, or organization. SAVE International describes value as the relationship between function performance and resources. [1]

A VE recommendation is a developed proposal supported by assumptions, advantages, disadvantages, cost and schedule effects, risks, and implementation steps. Acceptance is the owner’s documented decision to proceed. However, implementation occurs when the VE alternative or design suggestion is, in fact, incorporated into design, approvals, procurement, construction, and operating requirements. Because these are separate stages, a VE workshop is not considered an achieved saving or enhanced value.

Create an accountable path from recommendation to completion

Before the VE workshop closes, the facilitator and project manager typically establish a VE action register, which is a register that tracks each VE alternative or design suggestion through closeout. Each entry should identify the affected function, required performance, cost and schedule basis, reviews, documents, decision authority, action owner, due date, dependencies, and final disposition. The decision authority may accept or reject the proposal; the action owner completes the assigned follow-up. A deferred item should state what remains necessary and when it will be reconsidered.

The VE report should provide enough technical, cost, and schedule information for a decision. FHWA’s VE process includes developing VE alternatives or design suggestions, presenting recommendations, and preparing an implementation plan. Its Job Plan supports both the study and implementation. FHWA also cautions against overstating or double-counting estimated savings. [2]

 

 

Convert an accepted VE alternative or design suggestion into controlled changes

Change control is the formal process for reviewing, approving, recording, and communicating a change to the project baseline. The baseline is the approved scope, cost, and schedule used to measure change. After accepting a recommendation, the project manager should identify affected drawings, specifications, calculations, estimates, schedules, risk records, permits, procurement packages, contracts, commissioning plans, and operating information. Commissioning verifies that systems are installed, tested, and operating as required. The designer must confirm continued compliance with owner requirements, codes, permits, and professional responsibilities.

If the established change management requirements are properly followed, an accepted VE alternative or design suggestion should be formally incorporated into the change management process. The proposed change should be appropriately reviewed, approved, documented, and incorporated into the design in accordance with the applicable change control procedures. This is what is meant by converting an accepted VE alternative or design suggestion into a “controlled change”: the recommendation does not simply become part of the design informally but is implemented through the established change management process to ensure proper authorization, documentation, coordination, and traceability.

 

Verify value and retain the lesson

Verification determines whether the completed VE alternative or design suggestion preserved the required functions, met the performance criteria, used the expected resources, and improved life-cycle value. Supporting evidence may include approved design revisions, procurement records, inspection and test results, commissioning data, schedule updates, cost records, maintenance requirements, and user feedback. For applicable Federal-aid highway projects, current federal rules require State transportation agencies to incorporate approved VE recommendations into the plans, specifications, and estimates before construction authorization and to monitor and report implementation. [3]

Although those requirements apply only within the regulation’s scope, the management practice is useful: distinguish among proposed, accepted, incorporated, completed, and verified recommendations. Close an item only when evidence is available. Record rejected VE alternatives or design suggestions, and reasons so later teams can understand the decision and avoid repeating the analysis.

Recommended owner actions

 

It is recommended that owners identify decision authority and action owners before the VE workshop; align response dates with design and procurement milestones; maintain one action register linked to change control; perform technical, cost, schedule, risk, permit, and operational reviews in proportion to the change; update affected baselines and contract documents; verify function and performance; and report achieved results separately from the VE workshop. The facilitator may support tracking, but project leadership remains responsible for decisions and implementation. Owners should make timely decisions, assign responsibility, incorporate accepted VE alternatives or design suggestions into the design, and verify the work. Structured follow-through connects VE workshop to project delivery.

References

[1] SAVE International. About the Value Methodology.

[2] Federal Highway Administration. The Value Engineering Process and Job Plan.

[3] Electronic Code of Federal Regulations. 23 CFR 627.7, VE Programs.