FAR 48.1—Subpart 48.1

General.

FAR 48.101 explains what value engineering is and sets out the two basic ways it can be used in federal contracting: a voluntary, incentive-based approach and a mandatory, Government-directed program approach. It defines value engineering as a formal technique for finding ways to perform more economically without reducing essential functions or characteristics, with the goal of lowering acquisition, operation, or support costs. The section also distinguishes between contractor-initiated value engineering change proposals (VECPs), where the contractor uses its own resources and may share in savings if the proposal is accepted, and Government-required value engineering programs, where the contractor is paid to perform a specified level of effort as a separate contract item. It further notes that no savings sharing is allowed in architect-engineer contracts, while other contracts with a program clause do allow sharing, but at a lower rate than the voluntary approach. In practice, this section matters because it frames how value engineering is structured, who bears the development cost, when the contractor can recover costs or earn a share of savings, and how agencies should target value engineering effort toward areas with meaningful savings potential.

Policies.

FAR 48.102 sets the government-wide policy framework for value engineering (VE) and value engineering change proposals (VECPs). It explains the agencies’ duty to maintain cost-effective VE procedures, give contractors a meaningful financial incentive, and include VE clauses in appropriate supply, service, architect-engineer, and construction contracts unless an exemption applies. It also addresses how agencies must process VECPs, how savings are shared, when subcontract VE clauses should be considered, and special rules for major system programs in civilian agencies and the Department of Defense. The section further clarifies that VE incentive payments are not profit or fee, that profit or fee generally should not be reduced because a VECP is accepted, and that profit/fee is excluded from savings calculations. In addition, it requires contracting officers to set sharing periods and sharing rates using prescribed factors and to document the rationale in the contract file. Finally, it imposes a mandatory VE program for architect-engineer services, but prohibits sharing of VE savings in those contracts, and requires agency procedures for funding and paying contractor shares of collateral and future contract savings. In practice, this section is the policy backbone for deciding when VE applies, how it is administered, and how contractors are rewarded for generating government savings.

Processing value engineering change proposals.

FAR 48.103 explains how value engineering change proposals (VECPs) are received, reviewed, decided, and documented once a contractor submits them under the Value Engineering clauses in FAR subpart 48.2. It covers the contractor’s submission instructions by reference to the clause, the contracting officer’s duty to promptly process and objectively evaluate the proposal, and the requirement to document the contract file with the reasons for acceptance or rejection. It also sets a 45-day decision deadline, requires written notice if more time is needed, and allows the contractor to withdraw an unaccepted VECP after the specified period. The section explains how an accepted VECP is implemented through a contract modification, how performance continues under the existing contract until that modification becomes effective, and how the Government may recover proportionate savings-share payments if accepted units are later rejected or not delivered. Finally, it identifies several Government determinations as unilateral and discretionary, including acceptance or rejection, collateral costs and savings, the applicable sharing rate under Alternate II, and the duration of the sharing period and contractor sharing rate. In practice, this section is important because it governs the speed, fairness, documentation, and financial consequences of VECP processing for both parties.

Sharing arrangements.

Relationship to other incentives.

FAR 48.105 explains how value engineering change proposals (VECPs) interact with other contract incentive structures, such as performance incentives, design-to-cost incentives, and similar award or target mechanisms. Its purpose is to prevent double counting: a contractor should be encouraged to propose cost-saving or performance-improving changes, but the same benefit should not be paid twice through both value engineering shares and another incentive already tied to the affected target. In practice, this means the government must preserve the original incentive targets when a VECP is accepted, rather than revising them upward or downward to reflect the VECP’s effect. The section also makes clear that only the portion of VECP benefit not already rewardable under another incentive may be paid under the value engineering clause. For contracting officers and contractors, this rule is important because it affects how savings are measured, how incentive formulas are applied, and whether a VECP produces additional compensation beyond the contract’s existing incentive structure.