When a project is over budget, cutting cost may be necessary. That doesn’t make every cut value engineering.
Originally published August 2012. Updated October 2026 to reflect current owner-side value engineering and capital project practices.
“Every time we are asked to do ‘Value Engineering,’ it is to lower the cost.”
That was a familiar complaint in design and construction, and there was some truth behind it.
A project comes in over budget. The team is told to value engineer it. Everyone starts looking for things to remove, substitute or downgrade until the estimate reaches the target.
There is nothing inherently wrong with reducing scope or cost when a project exceeds its budget. Owners have budgets, and projects have to live within them.
But that is not necessarily value engineering.
True value engineering asks a different question:
Can we achieve the required function or outcome in a better way?
Sometimes the answer reduces first cost. Sometimes it reduces operating or life-cycle cost. Sometimes it improves constructability, reliability, schedule or maintainability. And sometimes the better-value solution costs more initially because it produces greater value over the life of the asset.
That is very different from going down a list and asking:
“What can we eliminate?”
Value Is More Than First Cost
Value engineering is a process for evaluating alternatives against the functions and objectives a project is intended to deliver.
Design concepts, specifications, construction techniques, materials, building systems and operating requirements can all be examined for opportunities to improve value.
The important distinction is that lower cost and greater value are not automatically the same thing.
A less-expensive piece of equipment may have a shorter useful life or greater maintenance requirements. A material substitution may save money during construction but increase replacement costs later. Eliminating infrastructure may solve today’s budget problem while limiting an owner’s ability to expand or modify the building in the future.
The construction estimate captures only part of that decision.
Look Beyond the Initial Construction Cost
Life-cycle cost analysis can help compare alternatives over an appropriate period rather than looking solely at the initial purchase or construction cost.
Depending on the decision, an owner may need to consider:
- initial capital cost;
- operating and energy costs;
- maintenance requirements;
- expected useful life;
- replacement cost;
- constructability;
- schedule impact;
- reliability;
- availability of parts and service;
- future flexibility; and
- risk.
Not every decision requires an elaborate financial model. But the criteria should reflect what matters to the owner.
A product that costs less today but requires substantially more maintenance may not represent better value. Neither does eliminating something that will predictably have to be added back in a future capital project.
Establish What the Owner Values
Value cannot be evaluated intelligently until the project team understands the owner’s priorities.
One owner may place a premium on first cost because capital is constrained. Another may prioritize operating cost because the organization expects to own the building for decades. A mission-critical operation may place reliability and redundancy ahead of both.
Schedule may dominate another project because opening six months earlier has greater business value than the construction savings being considered.
That is why value engineering should not begin with a list of things to cut.
It should begin with an understanding of what the project is supposed to accomplish and which outcomes the owner is trying to protect.
Once those priorities are understood, alternatives can be compared against them.
Cost Cutting May Still Be Necessary
Sometimes the project simply costs more than the owner can afford.
At that point, scope may have to change.
That is a legitimate project decision.
But there is value in calling the exercise what it is.
If a conference room is eliminated, a finish is downgraded or future capacity is removed because the project must meet an approved budget, the owner should understand both the immediate savings and the consequence of the decision.
The question should not stop at:
“How much does this save?”
It should also include:
“What are we giving up?”
That distinction becomes especially important when dozens of individual reductions are being considered across a large project. Each item may appear reasonable on its own while their cumulative effect materially changes what the owner ultimately receives.
Value Engineering Requires an Owner’s Perspective
Value engineering works best when the project team evaluates alternatives against explicit owner criteria rather than treating the construction estimate as the only measure of value.
That may require participation from designers, engineers, contractors, operators, facilities personnel, procurement and other stakeholders who understand different parts of the decision.
But someone still has to keep the owner’s objectives at the center of the exercise.
The owner’s job is to know which exercise the team is actually performing.
If the project is over budget and scope has to be removed, say so. That’s a legitimate project decision.
If the team is performing value engineering, alternatives should be evaluated against the functions and outcomes the owner needs—not simply ranked by how much they reduce today’s construction estimate.
Cost reduction asks, “What can we cut?”
Value engineering asks, “Is there a better way to achieve what we need?”
Those are not the same question.
About the Author: Richard Neuman advises organizations on capital planning, project governance, and complex capital programs. He has overseen more than $2 billion in capital investments across commercial real estate, healthcare, utilities, industrial, broadcast, and development projects.
He writes candidly from an owner-side perspective about the executive decisions and organizational dynamics that shape capital project outcomes.
Leading a major capital program or facing a complex capital decision?
Contact Richard.
Subscribe for insights on capital planning, project governance, and the executive decisions that shape project outcomes long before construction begins.

To me, V/E should apply the principle of “pay me now or pay me later”. I can spec a cheaper tile or carpet, but it will most likely will require replacement sooner then a more costly version. So, did I apply V/E by using the cheaper product, I think not.
I think Richard missed the fundamental basis of Value Engineering by proposing that it should derive essentially from a Life Cycle Cost Analysis . That reasoning is fundamentally flawed because Value Engineering is not about cost but about Value.
Agreed that the determination of value is intrisincally linked to cost, but there it ends. We should not see cost as a synonym for value or see cost as an interchangeable term with value. These are two different matters.
It is not Life Cycle Cost Analysis that should drive Vaiue Engineering therefore. It is Value Management and this starts with the strategic definition of Value on the particular project – with input from project sponsor; project owner & stakeholders.
The process of determining what is (& of) value to a particular project and the prioritisation of these (into a value tree) is absolutely essential to the value engineering exercise (I would suggest) every project should be subjected to – regardless of whether it seems affordable as originally proposed or not.
I am proposing that value management and value engineering should be an integral part of the delivery of any project and this needs to be integrated into the project life cycle – i.e from project inception, through project planning & execution. It is a valuable project control tool, not a ‘add-on’!
The concept of Value Engineering is about optimising value cost effectively and in that sense it may in fact result in spending a little bit more to augment value however defined for a particular project- if deemed desirable. Value Engineering is definitely not a cost-cutting exercise (Richard is on the money on this) but a value optmisation exercise.
To be clear, a Life Cycle Cost Analysis may infact not be necessary if the long term costs are of relatively low value on the value tree.
To conclude, Value Engineering is a tool of value management. The latter is about value optimisation and starts with a definition of value for a particular project.
Great article and as a real estate developer it is ofter difficult to build a financial model that meets the lender’s underwriting so we jump in and use the term VE when in essence it is simply cutting the construction budget with disregard to the future value of achieving operating efficiencies, reducing load factors and improving the functionality to meet future growth patterns. We are more concerned about debt coverage ratios and IRR in order to meet financing requirements. Lenders should learn to appreciate VE from a long-term perspective on future value and cash flows.