Reading an Incumbent CPARS Record to Find Their Weaknesses

The Record Is Already Public. Most Bidders Ignore It.

A mid-size IT services firm wins a $14M network operations contract. Three years later, their CPARS record shows two "Satisfactory" ratings on schedule and a single narrative note: "Contractor experienced recurring delays in monthly status report delivery, requiring Government intervention on four occasions." The incumbent re-competes. A competitor reads that sentence, builds a proposal section around disciplined reporting cadence, and wins.

That is not a hypothetical. It is the basic mechanics of past performance intelligence done correctly. CPARS records are official Government assessments, written by Contracting Officer Representatives (CORs) and Contracting Officers, stored in the Contractor Performance Assessment Reporting System, and accessible through FAPIIS (Federal Awardee Performance and Integrity Information System) and USASpending.gov. They are not marketing copy. They are candid, structured evaluations that follow a defined rating scale: Exceptional, Very Good, Satisfactory, Marginal, Unsatisfactory. Every rating below "Exceptional" represents a gap the incumbent could not close.

Where to Pull the Records

Start with three sources in this order:

1. FAPIIS.gov: Covers contracts at or above the simplified acquisition threshold (currently $10,000 for CPARS applicability; CPARS is generally required for contracts exceeding the simplified acquisition threshold of $250,000, but the threshold language should be stated precisely). Includes CPARS assessments, terminations for default, administrative agreements, and suspension or debarment actions. Search by UEI (the DUNS number has been retired and replaced by the Unique Entity Identifier; SAM.gov and FAPIIS now use UEI only) or company name.
2. USASpending.gov: Use the "Awards" search to find the incumbent's contract history under the relevant NAICS code or PSC. Cross-reference award IDs against FAPIIS records.
3. SAM.gov Past Performance module: Some records are visible here, particularly for contracts where the contractor has shared their record publicly or the agency has posted it.

For IDIQ task orders, CPARS are often written at the task order level, not just the base contract. Pull every order you can find. A contractor might hold a "Very Good" at the IDIQ level but carry a "Marginal" on a specific delivery order, which is the more operationally relevant data point.

The Rating Scale Is Only the Starting Point

Capture managers who stop at the adjectival rating miss the real intelligence. The narrative fields are where the vulnerabilities live. CPARS forms include structured comment blocks for each evaluation area: Technical/Quality, Schedule, Cost Control, Management/Business Relations, and Small Business Subcontracting (when applicable). Each block can contain several hundred words of Government-authored assessment.

Look for these specific patterns in the narrative text:

• Hedged praise: Phrases like "generally met requirements" or "performance was acceptable" are bureaucratic signals that the contractor cleared the bar but did not exceed it. In a best-value source selection, that is exploitable.
• Passive-voice problem statements: "Issues were identified" or "corrections were required" indicate the Government had to intervene. Count how many times intervention language appears across multiple periods of performance.
• Staffing references: Any mention of key personnel turnover, subcontractor performance problems, or "transition challenges" is a direct line to a proposal discriminator. If the incumbent lost their program manager mid-contract, write your staffing stability plan explicitly around that risk.
• Repeated Satisfactory ratings in the same category: A contractor who earns "Satisfactory" on Cost Control across three consecutive evaluation periods is telling you they do not manage cost proactively. That is a proposal theme, not just a data point.

Building a Weakness Matrix

Organize what you find into a simple matrix before you write a single proposal word. Columns: Evaluation Area, Rating, Narrative Signal, Proposed Discriminator. Rows: each CPARS record you reviewed. This gives the capture team a structured view of where the incumbent is consistently weak versus where a single bad period may have been an anomaly.

Distinguish between systemic weaknesses and isolated incidents. A single "Marginal" on schedule during a period that included a major scope change is not the same as three consecutive "Satisfactory" ratings on schedule across unrelated contracts. The former may be explainable; the latter is a pattern the Source Selection Evaluation Board (SSEB) will likely have already noticed.

If the solicitation uses a Past Performance Questionnaire (PPQ) or asks offerors to submit references, the Government evaluators are doing the same analysis you are. Your proposal needs to show the SSEB that you already understand the incumbent's performance gaps and have built your technical approach to close them.

Connecting CPARS Intelligence to Proposal Sections

Past performance intelligence should drive three sections of your proposal, not just the past performance volume.

Technical Approach: If the incumbent's CPARS shows recurring schedule slippage, your technical approach should include a named schedule management methodology (Integrated Master Schedule, two-week look-ahead meetings, whatever fits the contract type) with specific process steps. Do not just claim you will meet deadlines. Describe the mechanism.

Management Approach: If the record shows key personnel churn, your management volume should address retention directly. Compensation structure, named alternates, transition protocols. FAR 52.237-3 (Continuity of Services) -- note that this clause applies to contracts for essential services and requires contractors to furnish a plan for continuity of services; verify it is actually included in the specific RFP before citing it, as it is not universally applicable may already be in the RFP; if so, tie your staffing plan explicitly to that clause.

Past Performance Volume: Select your own references to contrast with the incumbent's documented weaknesses. If they have a cost control problem, lead with a reference where you delivered under budget and include a CPARS quote (with permission, or from your own record) that uses the word "Exceptional" in the Cost Control field. Let the evaluator draw the comparison without you making it explicitly.

What CPARS Cannot Tell You

CPARS records have blind spots. Contracts below the simplified acquisition threshold (currently $250,000) may not have formal CPARS. Some agencies are inconsistent about completing assessments on time, so a gap in the record does not always mean clean performance. Classified contracts will not appear. And CPARS reflects the COR's perspective, which may not capture every operational nuance.

Supplement CPARS with agency-specific sources: Inspector General reports, GAO bid protest decisions (which sometimes contain detailed findings about contractor performance), and news coverage of program delays. If the incumbent's program was the subject of a congressional inquiry or an IG audit, that information is often more candid than any CPARS narrative.

Also check SAM.gov for any active exclusions or administrative agreements. A contractor operating under a compliance agreement has a documented integrity issue that may be relevant to the responsibility determination under FAR 9.104-1.

Practical Limits and Ethical Boundaries

Everything described here uses publicly available Government records. There is no gray area in accessing FAPIIS or USASpending.gov. The ethical line is in how you use the information. Citing a competitor's CPARS weakness in your proposal without connecting it to a genuine capability of your own is a red flag to evaluators. The goal is to build a stronger technical and management narrative, not to write a critique of the incumbent.

Some proposal teams make the mistake of referencing the incumbent by name in their proposal. Do not. Frame every discriminator as a positive capability statement about your firm. The SSEB will make the comparison themselves.

For capture teams building this analysis at scale, our services at IT Custom Solution LLC include structured past performance research and competitive intelligence support that feeds directly into proposal development workflows.

Takeaway

Pull the incumbent's CPARS before you write the first word of your technical approach. Map every rating below "Exceptional" to a specific narrative signal. Build your proposal discriminators around the gaps you find. The record is public, the methodology is straightforward, and most of your competitors are not doing it systematically. That is the margin.

If you want to walk through this process against a live opportunity you are tracking, reach out for a brief consult with the IT Custom Solution team. No commitment required, just a focused conversation about your capture situation.