Writing a Past-Performance Volume That Actually Scores Well

The Problem Starts Before You Write a Word

A mid-size 8(a) firm loses a $4.2M IT services recompete. Their past performance volume listed six contracts, all relevant on paper. The SSEB narrative came back: "References provided limited insight into the offeror's specific role, outcomes achieved, or challenges overcome. Volume rated Acceptable." Acceptable on past performance against an incumbent rated Exceptional is a loss. The work was real. The write-up killed them.

This happens constantly. Capture managers treat the past performance volume as a compliance exercise: fill in the PPQs, attach the CPARS, hit page limit. Evaluators treat it as evidence. Those two mindsets produce very different documents.

Understand What Evaluators Are Actually Scoring

Before you draft a single sentence, pull the evaluation criteria from Section M and map every required element. Most RFPs score past performance on two axes: relevancy and quality. Some add a third: recency. Each axis has a defined standard in the solicitation, and each one requires a different kind of proof.

• Relevancy is about scope, magnitude, and complexity. A $500K help desk contract does not demonstrate relevancy for a $6M enterprise network operations requirement, even if the technical work overlaps. Match dollar thresholds, labor categories, and technical scope explicitly.
• Quality is about outcomes and ratings. CPARS ratings of Very Good or Exceptional, on-time delivery, zero cost overruns, specific performance metrics. Evaluators want to see the contractor performed well, not just that they performed.
• Recency is usually defined as work performed within three to five years of RFP release. Check the solicitation definition. Do not cite a contract that ended six years ago and assume the evaluator will overlook it.

Select References Strategically, Not Chronologically

Most teams default to their largest or most recent contracts. That is not always right. The correct selection criterion is: which references best mirror the PWS or SOW in this RFP?

Build a simple relevancy matrix before you finalize your reference list. Columns: contract value, period of performance, agency type (civilian, DoD, IC), primary NAICS, key technical requirements from the current RFP. Rows: your candidate references. Score each candidate against the current requirement. Pick the references with the highest overlap, not the highest dollar value.

If you are a small business pursuing a contract with a large business set-aside waiver, or teaming as a subcontractor, also consider whether you need to include subcontract performance. FAR 15.305(a)(2) allows offerors to submit performance of predecessor companies, key personnel, and subcontractors. Use that flexibility if your prime contract history has gaps.

The Anatomy of a Strong Past Performance Write-Up

Each reference narrative should follow a consistent structure. Here is a format that maps directly to what evaluators need to score:

1. Contract identification: Agency, contract number, NAICS, period of performance, total contract value (base plus all options), your role (prime or sub, and percentage of work if sub).
2. Scope summary: Two to three sentences describing what you actually did. Not what the program was. What your team delivered.
3. Relevancy bridge: Explicitly connect this reference to the current requirement. Use language from the RFP's PWS. If the RFP says "Tier II help desk support" and your reference included Tier II help desk support, say that. Do not make the evaluator infer the connection.
4. Performance evidence: This is where most write-ups fail. You need specific, quantified outcomes. Not "delivered on time" but "maintained 99.2% SLA compliance across 14,000 monthly tickets over a 36-month base period." Not "received positive feedback" but "rated Very Good in all six CPARS categories; contracting officer noted zero critical deficiencies in 48 months."
5. Challenge and resolution: One paragraph describing a specific problem that arose on the contract and how your team resolved it. This is optional in some solicitations but powerful when included. It shows operational maturity and distinguishes you from competitors who only report smooth performance.

Mining CPARS and Reference Quotes the Right Way

CPARS narratives are gold if you know how to use them. Log into the CPARS system and pull the full narrative text for every reference you plan to cite. Evaluators know what a CPARS report looks like. If you quote it accurately, it carries weight. If you paraphrase loosely, it looks like you are hiding something.

Pull direct quotes from the contracting officer's narrative. Phrases like "contractor proactively identified a schedule risk and implemented a mitigation plan that kept the program on track" or "technical staff demonstrated deep subject matter expertise during a critical system migration" are exactly the kind of language that supports an Exceptional quality rating. Put them in your write-up with attribution: "Per CPARS assessment dated [month/year], the Contracting Officer noted..."

Also coordinate with your references before submission. A PPQ (Past Performance Questionnaire) returned with generic ratings and no narrative comments is nearly useless. Call your POC. Walk them through the questions. Remind them of specific accomplishments. Ask them to write in concrete terms. A PPQ that says "contractor met all deliverables and we would use them again" is not the same as one that says "contractor reduced ticket resolution time by 22% in the first six months through process improvements they initiated without direction."

Common Mistakes That Drop Your Rating

These show up repeatedly in debriefs:

• Citing a contract where you were a sub but writing it as if you were the prime. Evaluators check. If the FPDS record shows a different prime, your credibility takes a hit.
• Listing a reference that ended more than five years ago without checking the RFP's recency definition. Some solicitations define recency as three years. Read Section M.
• Using the same generic narrative for every reference. If your relevancy bridge does not change from one reference to the next, you are not actually bridging anything.
• Submitting PPQs without following up. References get busy. A PPQ sitting in someone's inbox does not help you. Build in a two-week buffer and follow up twice.
• Ignoring the page limit math. If you have six references and a 15-page limit, you have roughly two pages per reference. Plan the structure before you write, not after.

When You Do Not Have Enough Relevant Past Performance

This is a real problem for companies moving into new agencies, new contract types, or higher dollar thresholds. Options include: teaming with a partner who has the relevant history and including their performance with clear role delineation; citing key personnel performance from prior employers (FAR 15.305 allows this in some contexts); or being transparent about the gap and compensating with a strong management approach volume that addresses risk mitigation directly.

Do not pad with marginally relevant references just to hit a number. An evaluator who rates three of your six references as Not Relevant will score you lower than a competitor who submitted three Highly Relevant references. Quality over quantity is not a cliche here. It is the scoring math.

Takeaway

A past performance volume earns an Exceptional rating when it does three things: selects references that mirror the current requirement by scope and magnitude, provides specific quantified evidence of quality rather than general assertions, and explicitly connects each reference to the RFP's evaluation criteria using the solicitation's own language. The work is in the preparation, not the writing. If you have not pulled CPARS narratives, briefed your references, and built a relevancy matrix before you open a Word document, you are already behind.

If you want a second set of eyes on your past performance strategy before your next submission, reach out to the IT Custom Solution team for a focused review session.