PVA
All insights

Contracts & Bidding Owner-side insight

Shared Savings Clauses: What Owners Should Ask For

A shared-savings promise is only useful when the contract defines the comparison, accounting rules, scope protections, and process for verifying the result.

By Sam CastelanPublished Updated 8 min read

Define savings before sharing them

A contract that mentions shared savings may sound straightforward, but the phrase is incomplete without a defined calculation. Owners need to know what baseline is used, which costs count, which scope must remain, what deductions apply, who verifies the calculation, and when the accounting occurs. Without these details, parties can use the same phrase to mean different things.

Start by locating every reference to savings, incentives, contingency, buyout, allowances, and final reconciliation. Read the provisions together with the estimate, schedule of values, scope exhibits, change procedure, and payment terms. A definition in one section may conflict with language elsewhere. Ask qualified counsel to review the agreement's operation as a whole and under the applicable jurisdiction.

Do not treat a projected underrun, budget movement, or subcontractor quote difference as automatically earned savings. Establish what the owner contracted to receive and what was priced at the relevant baseline. Then decide which changes to that baseline count and which must be treated separately. An owner-side GMP review can connect the commercial formula to the estimate and contract documents.

Set a verifiable baseline

The baseline is the reference point against which savings are calculated. It may be a GMP, an approved estimate, a defined target, or another agreed amount. The parties should identify the exact version, date, scope, and included assumptions. If the baseline shifts without a documented method, the calculation can become difficult to reproduce.

Preserve the documents behind the baseline

Specify the documents that establish the baseline. Include the accepted estimate and scope, allowances, contingency treatment, general conditions, fee, alternates, owner purchases, and any identified exclusions. State whether the baseline is adjusted for approved scope changes, design development, schedule revisions, or other defined events. Preserve the original and revised versions rather than replacing the first estimate with a later number.

Consider a hypothetical project where a package is omitted from the original estimate and later added by the owner. If the baseline does not say how that addition is treated, a savings calculation could compare unlike scopes. The parties should agree whether the baseline changes, whether the added package is handled outside the incentive formula, and how the change is documented. This is a decision to resolve in advance, not a reported project outcome.

Ask whether the baseline includes amounts that are not available for savings, such as owner-held reserves or specific allowances. If an estimate line is a provisional amount, the parties should define how its reconciliation affects the incentive. A stated starting value is not enough if components remain unclassified.

Specify what counts as savings

Write down which cost categories enter the calculation. Potential questions include trade buyout differences, unused allowances, contingency balances, procurement credits, approved substitutions, scope reductions, cost underruns, and changes in general conditions or duration. The agreement may treat each differently. Avoid relying on a general reference to “actual cost below the GMP.”

Protect the owner's required scope and performance. A lower amount resulting from omitted work, reduced quality, deferred maintenance, or a substitution that does not meet the program should not be treated as equivalent to an efficiency while delivering the agreed requirements. Define acceptance criteria for substitutions and identify who approves them. Require that savings calculations distinguish authorized scope changes from delivery efficiencies.

Address credits and recoveries explicitly. If a supplier issues a rebate, credit, refund, or other adjustment, determine who receives it and when it is recorded. Define how taxes, freight, warranties, and related costs are treated. If a subcontractor's price changes after award, state which records support the final amount and how unresolved claims affect the calculation.

Clarify whether savings are calculated on committed costs, paid costs, forecast final cost, or another measure. A signed subcontract is not always the same as final cost if allowances, pending changes, or claims remain. Agree how open items are handled at interim calculation and closeout. Ask whether any amount is held until obligations are resolved.

Define deductions and calculation order

A shared-savings formula needs a transparent sequence. Identify the starting baseline, adjustments, eligible actual costs, permitted deductions, and resulting amount before applying any sharing percentage or allocation. The contract should make clear how each term is defined and how rounding, taxes, and timing are handled.

List costs that may be deducted and the evidence required. These could include agreed project costs associated with achieving an approved change, but the categories should be specific to the agreement. Determine whether contractor fee, insurance, bonds, general conditions, or other charges are already included in the baseline or separately accounted for. Avoid double-counting a cost in both the baseline and deductions.

Specify whether the contractor's share applies to all eligible savings or only savings beyond a threshold. If a threshold or target is used, define the reference and how changes affect it. Explain whether losses or overruns in one package offset savings in another. Clarify how the formula works if the project finishes above the baseline, if the scope changes materially, or if the agreement terminates early.

Ask the estimator or cost professional to test the formula using simple hypothetical cases before execution. For example, examine how the clause would work when an allowance is unused, when a substitution is approved, or when a scope addition offsets a buyout difference. The exercise is for identifying ambiguity, not forecasting savings. Counsel should review the wording and any consequences.

Make records and review rights usable

The owner needs access to information sufficient to reproduce the calculation. Identify the records to be provided, such as estimates, trade bids, subcontract agreements, purchase orders, invoices, credits, change logs, cost reports, and final cost summaries. Define when records are submitted, how long they are retained, and who may inspect them.

Set a consistent reporting format. Show baseline, approved adjustments, commitments, incurred cost, forecast cost, pending changes, contingency use, allowance reconciliation, credits, and calculated savings separately. Require a trail from each total to underlying documentation. The report should identify estimates as estimates and actual commitments as commitments.

Define the review and dispute path

Clarify the review process. Who prepares the calculation? Who checks it? What period does the owner have to ask questions? What happens if records are incomplete or the parties disagree? Specify a path for resolving a calculation dispute, including any independent review mechanism if the parties choose one. Have qualified counsel assess the language, confidentiality terms, and record rights for the agreement and jurisdiction.

The timing of access matters. Waiting until final closeout to discover that buyout records or credits are missing may make verification difficult. Consider interim reporting at defined project milestones, while recognizing that final figures can depend on closeout, claims, and warranty obligations. State when a provisional calculation may be made and how it is adjusted later.

Connect savings to owner decisions

The clause should distinguish owner-directed changes from contractor-led savings opportunities. Establish how proposed alternatives are reviewed for design intent, code requirements, operations, durability, schedule, warranties, and total installed scope. The owner should know when a decision is required and what information is needed to make it.

Do not let the incentive drive decisions that transfer costs to operations or future maintenance. A substitution should be evaluated against the performance requirements and lifecycle responsibilities relevant to the project. If specialist design input is needed, identify who provides it and how the review fits the schedule. An incentive formula is not a substitute for technical approval.

Clarify who may authorize a change and whether approval must be written before implementation, subject to the contract's emergency provisions. Define how the proposed change affects the baseline, cost report, schedule, and savings calculation. This avoids asking the owner to approve a concept without knowing its commercial treatment.

Coordinate the formula with the procurement plan, especially where early purchase decisions or quote expirations may affect cost. Coordinate it with bid comparisons as well. If package scope was not normalized, a buyout difference may reflect a coverage difference rather than a genuine saving. Bid leveling can help create a comparable scope record before award.

Resolve edge cases before signature

Read the formula against plausible scenarios. What happens if the owner changes the program? What if a design revision adds required scope? How are schedule extensions treated? Do savings from one trade offset unresolved cost growth elsewhere? What if the contractor makes a purchase without required approval? How are unused contingency and allowances accounted for? What records establish the final amount?

Also review the interaction with termination, default, dispute, audit, and final-payment provisions. The incentive may be calculated at a different time from other final accounts. Identify whether the parties can verify it if the contract ends early or a claim remains unresolved. These are legal and commercial questions for counsel and the project team.

Maintain a plain-language summary for the owner decision-makers. It should explain the baseline, eligible savings, deductions, share calculation, reporting package, review window, and closeout. Compare the summary to the executed agreement so that it does not promise terms the contract does not contain. General guidance cannot determine whether particular wording is enforceable.

Frequently asked questions

Does a shared-savings clause guarantee the owner savings?

No. It describes an allocation method if the contract's defined conditions are met. The baseline, included scope, cost records, deductions, changes, and verification process determine how it operates. It does not guarantee a project outcome.

Should unused contingency automatically count as savings?

Not automatically. The agreement should define who owns each contingency, what it may fund, how authorized use is reported, and how unused balances are treated. Owner-held reserves and contractor-controlled amounts may have different treatment.

Who should verify the shared-savings calculation?

The agreement should identify who prepares and reviews the calculation and what records support it. The owner may use a qualified cost professional or other agreed reviewer, while counsel advises on review and dispute provisions in the specific contract.

About the author

Sam Castelan

Chief Consultancy Officer (Senior Architect, Master Planner, MBA, MPL, MPA)

Brings development, master planning, and value engineering experience.

Meet the PVA team

Keep reading

A second set of eyes

Your next project decision deserves a closer look.

Scope and commercial terms are agreed in writing.

Request a project review
Confidential fit discussionRequest a project review