Past Performance Information Retrieval: Turning CPARS Narratives into a Proposal Asset

A contracting officer marks your firm Exceptional in Quality on a $4.2M IDIQ task order. The assessing official writes two paragraphs about your team's on-time delivery rate and a specific corrective action you executed without being asked. That narrative sits in CPARS for three years. When your proposal manager pulls together the Past Performance volume for the next competitive RFP, she spends four hours hunting through old emails and SharePoint folders trying to reconstruct what that CO actually said. She finds a screenshot. It is cropped. The dollar value is missing.

That is not a hypothetical. It is the standard operating condition for most small businesses competing on multiple vehicles simultaneously. The fix is not complicated, but it requires treating CPARS retrieval as a deliberate capture activity rather than a last-minute proposal task.

What Lives in CPARS and Why It Matters

The Contractor Performance Assessment Reporting System (CPARS) generates Contractor Performance Assessment Reports (CPARs) on contracts above the simplified acquisition threshold for most service and supply contracts, and above $750,000 for construction and architect-engineer services, per FAR 42.1502. Each report scores your firm across five standard dimensions: Quality, Schedule, Cost Control, Management, and Small Business Subcontracting (when applicable). The assessing official adds narrative. You get to respond. Both the rating and the narrative become part of the official record that source selection officials (SSOs) pull when evaluating past performance under FAR 15.305(a)(2).

The narrative is the asset most firms underuse. Ratings are a single adjective: Exceptional, Very Good, Satisfactory, Marginal, or Unsatisfactory. The narrative is where a CO writes things like: "The contractor proactively identified a supply chain delay six weeks before it would have impacted delivery and presented three mitigation options to the COR. The selected option resulted in zero schedule slip." That sentence, properly extracted and cited, is worth more in a proposal than a generic claim about your project management methodology.

The Retrieval Problem

CPARS access is role-based. Your firm's Focal Point (the designated company representative in the system) can view finalized reports. But access lapses when Focal Points change, companies restructure, or staff turn over. Many small businesses discover they cannot retrieve their own records when a proposal is already in flight.

Before you start any retrieval effort, confirm the following:

• Who is your current CPARS Focal Point? Is their account active?
• Do you have finalized reports for every contract above the applicable threshold in the past three years (the standard lookback window in most RFPs)?
• Have you responded to every assessment? Unanswered assessments with negative narratives look worse than responded ones.
• Do your subcontractors have their own CPARS records you may need to reference for a teaming arrangement?

If your Focal Point account is inactive, reactivation requires contacting the CPARS help desk and going through your Contracting Officer. Budget a week minimum. Do not wait until Section L of an RFP tells you past performance volumes are due in 14 days.

Building a CPARS Library Before the RFP Drops

The most effective capture teams maintain a living past performance library that is updated on a rolling basis, not assembled under deadline pressure. Here is a practical structure:

Step 1: Export and Archive Every Finalized Report

Log into CPARS quarterly. Download finalized reports as PDFs. Store them in a version-controlled folder organized by contract number, agency, and period of performance. Include the contract value, NAICS code, and the name of the assessing official in the folder metadata. That last item matters because some RFPs ask you to list the evaluating official as a reference.

Step 2: Extract Quotable Narrative Segments

Read every narrative and pull sentences or short paragraphs that speak to specific performance outcomes. Tag each extract by theme: schedule adherence, quality control, cost management, small business utilization, surge response, cybersecurity compliance, or whatever categories align with the types of work you pursue. A simple spreadsheet works. Columns: Contract Number, Agency, Period of Performance, Rating, Narrative Extract, Theme Tag, Dollar Value, NAICS Code.

This extract library becomes your proposal team's reference file. When a Section L asks you to describe your approach to schedule management, your writer can pull three verbatim CO statements that corroborate the narrative rather than writing generic claims.

Step 3: Draft and File Your Contractor Comments

FAR 42.1503 gives you 30 calendar days to submit a contractor comment on any CPARS assessment. Most small businesses either skip this step or treat it as a dispute mechanism only when ratings are negative. That is a missed opportunity. Even on Exceptional ratings, a well-written contractor comment can add context: the contract scope, the number of personnel deployed, the specific technical challenges overcome. That comment becomes part of the official record and shows up when an SSO pulls the report.

Draft a standard comment template for positive assessments. Keep it factual and brief: three to five sentences that add scope context the CO may not have captured. File it within the 14-day window every time.

Using CPARS Narratives in the Proposal

FAR 15.305(a)(2) requires source selection officials to assess the relevance and quality of past performance. Relevance is about contract similarity (scope, complexity, dollar value, customer type). Quality is where your CPARS narratives do the work.

When you cite a past performance example in a proposal, structure the reference this way:

1. Contract identification: Agency, contract number, period of performance, total value.
2. Scope summary: Two to three sentences describing what you did, sized to match the RFP requirement.
3. CPARS rating: State the official rating and the dimension (e.g., Exceptional in Quality, Very Good in Schedule).
4. Narrative evidence: Quote or closely paraphrase the CO narrative. Use quotation marks and attribute it to the assessing official's CPARS record. This is not bragging; it is documented government testimony.
5. Relevance bridge: One sentence connecting that performance to the specific PWS or SOW requirement in the current RFP.

Evaluators reading past performance volumes are often fatigued by contractor self-assessment. A direct quote from a CO carries a credibility weight that your own prose cannot match. Use it deliberately and sparingly. Two or three strong quoted extracts per past performance example is enough. More starts to look like padding.

When You Do Not Have Enough CPARS Coverage

Some RFPs allow you to supplement CPARS records with other past performance sources: customer satisfaction surveys, letters of commendation, or references from subcontract performance. FAR 15.305(a)(2) and many agency supplements explicitly permit this. If your CPARS record is thin because your firm is newer or recently crossed the threshold, document what you do have and supplement with written references from CORs or prime contractors who can speak to your performance on the same dimensions CPARS uses.

For a brief conversation about structuring your past performance strategy, the team at IT Custom Solution can walk through your current CPARS coverage and help identify gaps before your next competitive pursuit.

The Operational Takeaway

Treat CPARS retrieval as a standing capture task, not a proposal emergency. Confirm your Focal Point access today. Export every finalized report this quarter. Build a tagged extract library from the narratives. File contractor comments within 14 days of every assessment. When the RFP drops, your past performance volume should be 60 percent assembled before you open Section L. That is the difference between a volume that quotes government testimony and one that quotes yourself.

Winrove, a product of IT Custom Solution LLC, includes past performance tracking and reuse workflows built for exactly this kind of capture discipline. Plans start at $49/mo at winrove.com.