Value engineering without losing the client brief
Admin · 22 October 2026
Illustrative image. Photo by Daniel McCullough on Unsplash. Unsplash License.
A value engineering discussion can improve a project when it asks how to deliver the required outcome more effectively. It becomes less useful when the exercise consists of removing visible costs without examining the functions those costs support. A cheaper component, smaller space or simplified detail may be appropriate, but the decision needs to account for what the client will receive and the work required to make the alternative viable.
For project managers and design teams, the starting point is the brief. Identify the requirement behind the proposed change before comparing solutions. The client may need a particular operational capability rather than a particular product. That distinction creates room for useful alternatives while protecting outcomes that would otherwise disappear during a rushed review of the cost plan.
Define the purpose of the exercise
Agree what the review is trying to achieve and which constraints apply. The project may need to address an affordability gap, simplify delivery or improve maintainability. These objectives can lead to different choices. Avoid mixing them into a general instruction to find savings without specifying what performance must be retained and who can approve a change to the requirements.
Set the baseline against which proposals will be assessed. Identify the current scope, estimate and design information, including their maturity and assumptions. Without a common reference, different participants may calculate savings against different versions of the project. Record any known exclusions so that a proposal is not credited with removing a cost that was never included.
Understand the function before the solution
Ask what each element is intended to do for the user or the building. A finish may need to withstand a particular cleaning regime; a circulation allowance may support equipment movement; a system arrangement may preserve access for maintenance. The relevant specialists and operators should explain these needs. Their input helps the team distinguish a genuine requirement from a solution adopted early without further examination.
Where the brief is ambiguous, resolve that ambiguity before accepting a substitution. Terms such as robust or flexible do not provide a reliable comparison unless the team understands what they mean in use. Document the criteria that an alternative must satisfy and the evidence needed to demonstrate suitability. This gives suppliers and designers a clear problem to solve.
Invite proposals with enough information
A proposal should identify the change, the affected scope and the reason it is expected to improve value. Ask for supporting information proportionate to the decision. This may include a technical comparison, an outline sequence or a supplier statement. A suggestion made in a workshop can be worth exploring, but it should not enter the approved savings total before its implications are understood.
Name the person responsible for developing each proposal and the contributors required. Some alternatives cross several disciplines and procurement packages. If no one owns the complete assessment, each participant may evaluate only their own portion. Set a decision date that allows investigation before the proposal conflicts with information releases, orders or work already committed.
Compare complete consequences
Look beyond the purchase price of the changed item. Identify consequential design work, supporting components, installation arrangements and any effects on testing or handover. A substitution may reduce one package while increasing another. Keep those movements visible so that the project assesses the combined result rather than celebrating a saving that has simply moved elsewhere.
Consider a hypothetical office project where an alternative partition system has a lower supply price. The comparison should examine the required performance, interfaces, installation sequence and effect on doors or services as relevant. The alternative may still be attractive. The point is to establish its suitability and total project effect before treating the initial price difference as a confirmed benefit.
Include the operator in the assessment
Ask how the proposed change affects cleaning, maintenance, replacement and everyday use. The operator may identify consequences that are difficult to see in a design workshop. Where an alternative requires different support arrangements or specialist servicing, record that information and obtain the appropriate review. Do not assume that the party buying the work will also bear every consequence of operating it.
Any claim about future savings needs a stated basis. Identify the assumptions, time period and information source, and distinguish estimates from verified results. Where dependable data is unavailable, describe the uncertainty rather than inventing a payback period. The decision maker can then weigh the evidence appropriately instead of receiving a precise-looking comparison built on unsupported expectations.
Assess time and delivery commitments
Check whether the alternative changes lead times, approvals or the sequence of work. A technically suitable proposal can be impractical if it arrives after manufacture has started or requires a review that the programme has not allowed. Ask the planning and procurement teams to identify the relevant commitments. Record what is reversible, what requires further agreement and what has already been completed.
Distinguish the time needed to investigate from the time needed to implement. A proposal may appear simple but require updated drawings, coordination and communication across several parties. Include those actions in the assessment. If the project cannot complete them before the affected work, the decision should address that constraint explicitly rather than relying on an instruction to accelerate without a credible plan.
Keep a clear proposal register
Use statuses that distinguish an idea, an assessed option, an approved change and an implemented change. Record the estimated benefit separately from any agreed commercial adjustment. This prevents a management report from adding speculative proposals to confirmed outcomes. The register should make it easy to see which decisions are ready and which still depend on evidence or agreement.
Retain rejected proposals with a short explanation. They can be useful if circumstances change, but should not repeatedly return to the agenda without new information. Link accepted proposals to the relevant requirement and affected documents. This preserves the reasoning and helps later teams understand the trade-off that the client actually approved.
Use the proper approval route
The APM overview of change control provides general context for assessing proposed changes to an approved baseline. For a construction project, the authority to alter requirements, instruct work and agree commercial consequences depends on its actual arrangements. A workshop recommendation should not be treated as completing all those steps.
Make the approval specific. State the alternative accepted, the evidence reviewed and any conditions. If the client agrees to change an operational requirement, record that change to the brief rather than leaving the original requirement apparently intact. Where the proposal preserves the requirement, retain the evidence showing how it will do so. Both cases need a traceable decision.
Verify implementation and learn from the result
Assign responsibility for updating the information and communicating the decision to affected parties. Confirm that procurement, site delivery and handover records reflect the approved arrangement. An alternative is not fully implemented because its name appears in meeting minutes. Track the work needed to translate the decision into the actual project, including any revised acceptance evidence.
After delivery, review whether the expected benefit was achieved and whether any unanticipated consequence appeared. Keep the conclusion proportionate to the evidence available. The lesson may concern the alternative itself or the timing and quality of the assessment. A useful value engineering process leaves the project with a better-supported solution and a clearer understanding of the client’s priorities, rather than a list of savings detached from the asset ultimately delivered.
Keep responsibility for the benefits record with a named person. They should reconcile approved proposals with the current scope and estimate, flagging any double counting or benefit that remains dependent on an unresolved commercial agreement.
