FAR 15.404-1 keeps price analysis, cost analysis, and cost realism separate

Start with the analysis object

FAR 15.404-1 states that the objective of proposal analysis is a fair and reasonable final agreed-to price and assigns responsibility for evaluating offered-price reasonableness to the contracting officer. It says price analysis examines a proposed price without evaluating separate cost elements and proposed profit. It describes comparisons that may include competing proposed prices, valid historical prices adjusted for material differences, market or catalog information, independent estimates, parametric methods, and data from the offeror.

A contractor-facing record should therefore identify the exact item, quantity, unit, period, place, delivery, terms, option, assumption, escalation basis, source price, comparison date, adjustment, and proposal version. A historical price is not comparable merely because the item name matches. Terms, quantities, market conditions, configuration, performance, and time can change the basis. Preserve the difference instead of compressing it into one benchmark.

Keep cost elements and allowability distinct

The regulation describes cost analysis as review and evaluation of separate cost elements and profit or fee, including judgment about what performance should cost under reasonable economy and efficiency. It lists techniques such as examining proposed labor, material, indirect rates, trends, prior actuals, estimates, and technical inputs. That analysis is different from comparing an overall price, and it is also different from the later determination of whether an incurred cost is allowable under a contract.

Preserve the work breakdown, basis of estimate, quantities, hours and labor mix, rates and effective periods, material and subcontract basis, escalation, indirect structure, contingency, assumptions, estimating method and calibration, technical owner, accounting source, reconciliation, approvals, and unresolved data. Proposed, evaluated, negotiated, budgeted, incurred, billed, paid, and allowable remain separate states and may have different evidence and authorities.

Read realism as an evaluation construct

FAR 15.404-1 describes cost realism as an independent review of proposed cost elements to assess whether they are realistic for the work, reflect a clear understanding of requirements, and align with the offeror's proposed methods and materials. For cost-reimbursement contracts it describes a probable cost that may differ from proposed cost and is used for evaluation. The regulation also addresses limited use in certain fixed-price contexts and keeps evaluation tied to solicitation criteria.

Do not turn a model output, government probable-cost adjustment, audit observation, negotiation position, or competitor inference into the contractor's operating forecast. Preserve what the solicitation required, which proposal version and cost elements were analyzed, the documented questions and responses, what the government communicated through authorized channels, and what was finally negotiated or awarded. Only the contracting officer or another authorized government role can communicate the government's conclusion.

Keep the FAR source and decision boundary visible

The newly registered Acquisition.gov source establishes the text of FAR 15.404-1 in the FAC 2026-01 baseline, effective March 13, 2026. It establishes federal proposal-analysis concepts and contracting-officer responsibilities; it does not establish which data a particular solicitation requires, the government's analysis of an offer, a request for certified data, negotiation position, price reasonableness, cost realism, responsibility, award, or contract outcome.

GovCon Market Brief reviewed the official page on August 26, 2026. The March effective date is contextual and does not imply a material regulatory change since the August 25 run. Contractors should map one pricing record from solicitation and amendments through basis of estimate, price and cost support, internal challenge, submission, authorized questions, negotiation, final proposal revision, award baseline, accounting handoff, and retention with qualified contracting, pricing, finance, legal, and technical review.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

GovCon Market Brief will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.