Mastering the Past Performance Information Retrieval System for Government Bids

What Happened to PPIRS (and Where Past Performance Lives Now)

A small business capture manager spent three hours searching the PPIRS portal for competitor past performance data before a $4M IT services bid, only to discover the system had been retired and migrated years earlier. That is a real scenario that plays out regularly, and it costs proposal teams time they do not have. If your understanding of the Past Performance Information Retrieval System is more than a few years old, this guide will correct the record and give you a practical workflow for using the current infrastructure to your advantage.

PPIRS: What It Was and What Replaced It

PPIRS was the federal government's centralized repository for contractor past performance evaluations. Contracting officers used it to pull Contractor Performance Assessment Reporting System (CPARS) ratings before making source selection decisions. In 2021, the General Services Administration consolidated PPIRS into SAM.gov as part of a broader effort to unify federal procurement data under a single platform. The PPIRS URL now redirects to SAM.gov, and all past performance data that lived in PPIRS migrated with it.

What did not change is the underlying data source: CPARS. Contracting officers still enter performance evaluations in CPARS, and those evaluations flow into SAM.gov where they are visible to authorized users. Understanding this pipeline, CPARS as the input and SAM.gov as the retrieval layer, is the foundation of any serious past performance strategy.

How the Current System Works End to End

CPARS: Where Evaluations Are Written

Under FAR 42.1502, contracting officers are required to prepare past performance evaluations for most contracts exceeding the simplified acquisition threshold. For construction and architect-engineer contracts the threshold is lower. Evaluations are entered directly into CPARS and cover performance areas including technical (quality of product or service), schedule, cost control, management or business relations, and small business subcontracting. The specific areas and number vary by contract type. Each area receives a rating: Exceptional, Very Good, Satisfactory, Marginal, or Unsatisfactory.

Critically, contractors have 14 days to review and comment on a CPARS evaluation, with up to 14 additional days to submit a formal response, before it is finalized. This is one of the most underused windows in federal contracting. A Satisfactory rating on a contract where you delivered early and under budget is worth contesting with documented evidence. A comment that reads "Contractor disputes the schedule rating; government acknowledged two government-caused delays in modification P00003" is far more useful than silence.

SAM.gov: Where You Access the Data

Registered entities can access their own past performance records through SAM.gov at no cost. Contracting officers and source selection officials have broader access to search across contractors. As a bidder, your primary use cases are:

• Auditing your own record before a proposal submission to catch errors or outdated information.
• Verifying that recently completed contracts have been evaluated and that evaluations are accurate.
• Confirming your CAGE code and entity registration are current, since an expired SAM registration can disqualify a bid regardless of past performance quality.

How Contracting Officers Actually Use Past Performance in Source Selection

FAR 15.305(a)(2) requires that source selection officials evaluate the relevance and quality of past performance when it is listed as an evaluation factor. "Relevance" is the word that matters most. A $500K janitorial contract does not demonstrate relevant past performance for a $10M cybersecurity IDIQ, even if the ratings were all Exceptional. Evaluators look for contracts that are similar in scope, complexity, dollar value, and technical requirements to the work being solicited.

Many RFPs define relevance explicitly. A solicitation might state: "Recent is defined as within the last five years. Relevant is defined as contracts with a total value of at least $1M involving network operations support for a federal civilian agency." Read that language carefully before selecting which references to include in your proposal. Submitting three marginally relevant contracts when you have one highly relevant one wastes evaluator attention and can actually lower your score.

Quality is assessed through the CPARS ratings themselves and through the narrative comments. A rating of Very Good with a comment like "Contractor proactively identified a critical path delay and proposed a recovery schedule that brought the project in on time" tells a story. A rating of Very Good with no comment tells the evaluator almost nothing beyond the number.

Building a Past Performance Record That Wins Evaluations

Start Before the Contract Ends

Most contractors treat past performance as a proposal problem. It is actually a contract execution problem. The habits you build during performance determine what your CPARS record looks like. Specifically:

• Document every deliverable acceptance in writing, including the date the government accepted it.
• Track any government-caused delays (GFE delays, slow approvals, scope changes) with dated correspondence. These become your evidence if a schedule rating is unfair.
• Request interim CPARS evaluations on long-duration contracts. FAR 42.1502 encourages annual evaluations on contracts exceeding one year. Do not wait for the final evaluation to discover a problem.
• Assign someone on your team to own the CPARS relationship with the contracting officer. This is not the PM's side task; it is a dedicated responsibility.

Respond to Every Evaluation

Even when a rating is positive, a contractor comment that reinforces the narrative is useful. If an evaluation says "Exceptional quality," your comment can add: "Contractor maintained a defect rate below 0.5% across 1,200 deliverables over 18 months, exceeding the contract quality standard of 2%." Now the evaluator reading your proposal has specific data, not just a label.

When a rating is inaccurate or unfair, use the 14-day comment window to dispute it with facts. Reference specific contract line items, modification numbers, and correspondence. Avoid emotional language. A comment that reads "Contractor respectfully disagrees with the Marginal schedule rating. Government-directed stop-work order (reference CO letter dated 14 March) accounts for 23 of the 30 days cited as delay" is professional and documentable.

Curate Your Reference Portfolio

Most solicitations ask for three to five past performance references. Treat this as a strategic selection, not a list of your biggest contracts. For each opportunity, map the evaluation criteria in the RFP to the contracts in your portfolio and select the references that best match on scope, dollar value, agency type, and technical complexity. A well-matched reference from a $800K contract will outscore a poorly matched reference from a $5M contract.

Maintain a living past performance matrix that captures for each completed contract: the contract number, agency, period of performance, total value, NAICS code, scope summary in two to three sentences, CPARS ratings by category, and the contracting officer's contact information. Update it within 30 days of contract closeout. When a proposal is due in 10 days, you will not have time to reconstruct this from memory.

Practical Workflow for Using SAM.gov Past Performance Data

1. Audit your record 60 days before a major proposal submission. Log into SAM.gov, pull your entity's past performance data, and verify that every completed contract you intend to reference has a finalized evaluation. Missing evaluations are common, especially on task orders under IDIQs.
2. Contact the contracting officer if an evaluation is missing. FAR 42.1502 requires evaluations; if one is absent, a polite email to the CO citing the FAR requirement is appropriate. Get it in writing.
3. Cross-reference your references against the RFP's relevance definition before finalizing your proposal section. If the RFP defines "recent" as three years and one of your references is 38 months old, flag it for your proposal manager.
4. Prepare a brief narrative for each reference that connects the past work to the current requirement. Do not assume the evaluator will make the connection. Spell it out: "This contract is relevant because it required the same FISMA Moderate boundary management and incident response procedures required under Section C.3.2 of this solicitation."
5. Verify subcontractor references separately. If you are including a teaming partner's past performance, confirm their SAM registration is active and their CPARS record is accessible. An expired registration on a key subcontractor's entity can create complications during evaluation.

Where Technology Fits in This Workflow

Manually tracking CPARS evaluations, mapping references to RFP criteria, and monitoring SAM.gov for new solicitations that match your portfolio is time-consuming. Tools like Winrove (built by IT Custom Solution LLC, plans starting at $49/month at winrove.com) can accelerate the research phase: identifying relevant opportunities, surfacing evaluation criteria language, and helping capture managers match their past performance portfolio to specific solicitation requirements before the proposal clock starts.

Technology does not replace the discipline of managing your CPARS record during contract execution. It does reduce the time between "RFP released" and "we have a compliant past performance section drafted."

The Practical Takeaway

Your past performance record is built on the job site, in the deliverable tracker, and in the 14-day CPARS comment window. By the time you are writing a proposal, the record is largely fixed. The contractors who consistently win on past performance factors are the ones who treat CPARS management as an ongoing program, not a proposal-week scramble. Start your next contract with a CPARS plan in place, and your proposal team will have something worth submitting.