FAR 15.406-3—Documenting the negotiation.
Plain-English Summary
FAR 15.406-3 tells the contracting officer how to document a negotiated acquisition in the contract file, usually through a price negotiation memorandum (PNM) or similar record. It covers the purpose of the negotiation, the acquisition description and identifiers, the names and roles of the negotiators, the status of contractor systems that affected the negotiation, and how certified cost or pricing data were handled. It also requires a summary of the contractor’s proposal, field pricing assistance, the Government’s negotiation objective, the negotiated position, the key facts and considerations behind prenegotiation objectives and the final agreement, any significant direction from Congress or higher-level officials, the basis for profit or fee objectives and outcomes, and the documentation supporting a fair and reasonable price. In practice, this section is the audit trail for how the Government reached the negotiated price and terms, especially in actions where cost analysis, price analysis, or defective certified cost or pricing data are involved. It also ensures that field pricing offices receive the final negotiation record so their support can improve future acquisitions.
Key Rules
Document the agreement
The contracting officer must record the principal elements of the negotiated agreement in the contract file. A PNM or similar memorandum should capture the essential facts, decisions, and rationale behind the final negotiated outcome.
Identify the acquisition and negotiators
The documentation must state the purpose of the negotiation, describe the acquisition, include identifying numbers such as the RFP number, and list the name, position, and organization of each Government and contractor representative who participated.
Address contractor system status
The record must note the current status of contractor systems such as purchasing, estimating, accounting, and compensation, but only to the extent those systems affected and were considered in the negotiation. This helps explain how the Government evaluated the contractor’s pricing environment and controls.
Explain certified cost or pricing data treatment
If certified cost or pricing data were not required above the threshold, the file must state the exception used and the basis for it. If the data were required, the file must explain how the contracting officer relied on the data, any inaccuracies or omissions found, the corrective actions taken, the effect on price, or whether an exception later applied and the data were therefore not treated as certified cost or pricing data.
Summarize proposals and analyses
The documentation must summarize the contractor’s proposal, field pricing assistance recommendations, any variances from those recommendations, the Government’s negotiation objective, and the negotiated position. If the price determination is based on cost analysis, the summary must address each major cost element; if based on price analysis, it must identify the source and type of data used.
Explain key drivers and differences
The file must identify the most significant facts or considerations that controlled the prenegotiation objective and the negotiated agreement, including an explanation of any major differences between the two positions. This is the core rationale for why the final deal was reached.
Capture external direction impacts
If direction from Congress, other agencies, or higher-level officials significantly affected the action, the documentation must discuss and quantify that impact. The rule applies when the direction comes from officials outside the normal award and review chain for the specific contract action.
Document profit, fee, and fair price
The memorandum must state the basis for the prenegotiation profit or fee objective and the negotiated profit or fee, and it must document the basis for finding the price fair and reasonable. This ties the profit/fee analysis and overall pricing conclusion to the final award decision.
Share field pricing results
When field pricing assistance was used, the contracting officer must send a copy of the negotiation documentation to the supporting office(s). If appropriate, the contracting officer should separately provide feedback on how advisory field support could be improved.
Responsibilities
Contracting Officer
Prepare and place in the contract file a complete negotiation record covering all required elements, including the purpose, acquisition details, participants, contractor system status, certified cost or pricing data treatment, proposal and analysis summary, key facts, external direction, profit or fee basis, and fair and reasonable pricing determination.
Contracting Officer
Explain any significant variances between field pricing recommendations, prenegotiation objectives, and the final negotiated position, and document the effect of defective or inapplicable certified cost or pricing data when relevant.
Contracting Officer
Forward the negotiation documentation to any office that provided field pricing assistance and, when appropriate, provide separate feedback on how that support could be made more effective.
Field Pricing Assistance Office(s)
Provide advisory support during the negotiation process and receive the final negotiation documentation so the office can understand how its recommendations were used and improve future support.
Contractor
Participate in the negotiation through its representatives and, when certified cost or pricing data are required, submit data that are accurate, complete, and current unless an exception applies.
Agency/Higher-Level Officials
If their direction materially affects the negotiation, ensure that such direction is identifiable and can be discussed and quantified in the contract file documentation.
Practical Implications
This section is about defensible pricing records: if the file does not show how the Government reached the negotiated price, the award is harder to defend in audits, protests, claims, or defective pricing reviews.
The most common mistake is writing a generic PNM that lists conclusions without explaining the reasoning, especially the link between proposal data, analysis, negotiation objectives, and the final price.
Another frequent gap is failing to document how certified cost or pricing data were used, or failing to explain why an exception applied; that omission can create problems under Truthful Cost or Pricing Data requirements.
Contracting officers should be especially careful to record major differences between prenegotiation objectives and the final agreement, because those differences are often what reviewers focus on first.
When field pricing support is involved, sending the final memo back to the support office is not just administrative housekeeping; it helps improve future pricing advice and creates a complete record of how the support was used.
Official Regulatory Text
(a) The contracting officer shall document in the contract file the principal elements of the negotiated agreement. The documentation ( e.g., price negotiation memorandum (PNM)) shall include the following: (1) The purpose of the negotiation. (2) A description of the acquisition, including appropriate identifying numbers ( e.g., RFP No.). (3) The name, position, and organization of each person representing the contractor and the Government in the negotiation. (4) The current status of any contractor systems ( e.g., purchasing, estimating, accounting, and compensation) to the extent they affected and were considered in the negotiation. (5) If certified cost or pricing data were not required in the case of any price negotiation exceeding the certified cost or pricing data threshold, the exception used and the basis for it. (6) If certified cost or pricing data were required, the extent to which the contracting officer- (i) Relied on the certified cost or pricing data submitted and used them in negotiating the price; (ii) Recognized as inaccurate, incomplete, or noncurrent any certified cost or pricing data submitted; the action taken by the contracting officer and the contractor as a result; and the effect of the defective data on the price negotiated; or (iii) Determined that an exception applied after the data were submitted and, therefore, considered not to be certified cost or pricing data. (7) A summary of the contractor’s proposal, any field pricing assistance recommendations, including the reasons for any pertinent variances from them, the Government’s negotiation objective, and the negotiated position. Where the determination of a fair and reasonable price is based on cost analysis, the summary shall address each major cost element. When determination of a fair and reasonable price is based on price analysis, the summary shall include the source and type of data used to support the determination. (8) The most significant facts or considerations controlling the establishment of the prenegotiation objectives and the negotiated agreement including an explanation of any significant differences between the two positions. (9) To the extent such direction has a significant effect on the action, a discussion and quantification of the impact of direction given by Congress, other agencies, and higher-level officials ( i.e., officials who would not normally exercise authority during the award and review process for the instant contract action). (10) The basis for the profit or fee prenegotiation objective and the profit or fee negotiated. (11) Documentation of fair and reasonable pricing. (b) Whenever field pricing assistance has been obtained, the contracting officer shall forward a copy of the negotiation documentation to the office(s) providing assistance. When appropriate, information on how advisory field support can be made more effective should be provided separately.