CPARS evaluations need lifecycle-state evidence
FAR Subpart 42.15 separates an agency evaluation, the contractor's comments or rebuttal, review above the contracting officer, availability for source selection, and the finalized copy. A usable CPARS record must preserve which state a reader saw and every later addition.
Editorial figure by GovCon Market Brief. Source context: FAR Subpart 42.15 Contractor Performance Information.
Treat the agency evaluation as the first state
FAR 42.1503 requires the agency evaluation to reflect performance and to include ratings with supporting narratives. It also requires both negative and positive evaluations to be provided to the evaluated contractor. That initial agency work product is therefore an identifiable state, not the only artifact that will ever belong to the CPARS evaluation. Preserve its factor ratings, narrative text, evaluation period, authors, completion time, contractor-notification time, and the exact version shown for comment.
A downstream copy should identify whether it contains only the agency evaluation or also includes a contractor response and agency review. The evaluation identifier, evaluated entity or unit, covered award or order, performance period, interim or final designation, source version, retrieval time, and reader purpose should travel together. A PDF saved without state and retrieval context can look definitive even when the regulation still permits additional material to enter the record.
Preserve the contractor response as its own artifact
The regulation affords the contractor up to 14 calendar days from notification to submit comments, rebutting statements, or additional information. Those are not silent edits to the agency narrative. Retain the notification, response deadline, submitted artifact, submitter, submission time, referenced factor or narrative, attachments, and any acknowledgment. If nothing is submitted, preserve that fact and the elapsed window rather than inferring agreement with every statement.
Keep the agency's words and the contractor's words attributable. A rebuttal may challenge a fact, add context, or dispute the rating, but its receipt alone does not revise the agency conclusion. Conversely, a source-selection reader should not receive the agency text stripped of a contractor response that CPARS makes available. The operating record needs both artifacts and an explicit relationship between them without merging their authorship or meaning.
Expose review-pending and final states
FAR 42.1503 requires review at a level above the contracting officer to consider disagreements, while leaving the ultimate conclusion with the contracting agency. Capture the request for review, disputed points, reviewing official, materials considered, review comments, disposition time, any agency revision, and the resulting version. Do not turn the reviewer's participation into a contractor win or an automatic rating change; the source establishes a review mechanism and agency conclusion, not a predetermined result.
The timing rule creates an important state distinction. The regulation says evaluations and contractor-submitted information become available for source-selection use no later than 14 days after notification, with an indication when agency review is pending. CPARS is then updated with later contractor comments and later agency review. A retrieval layer should display that pending marker and later update rather than backdating the completed review or presenting the earlier retrieval as if it contained the later disposition.
Test one disputed evaluation across two retrievals
A buyer test should create a synthetic evaluation, notify the contractor, submit a rebuttal on day 13, leave the above-officer review pending after day 14, and retrieve the record for a permitted source-selection use. The first retrieval should show the agency evaluation, contractor response, state marker, and retrieval time. After the reviewing official acts, retrieve it again and verify that the later review and resulting evaluation state appear without overwriting what the first reader actually received.
GovCon Market Brief reviewed the newly registered FAR Subpart 42.15 page on September 17, 2026. It supports the stated evaluation, response, review, retention, availability, pending-review, and update sequence. It does not establish the contents or merits of any evaluation, the accuracy of a rating or rebuttal, the identity or access rights of any reader, the outcome of an agency review, the relevance weight assigned in a later source selection, or any award result.
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.