Past Performance Reference Forms: How to Write Them So Evaluators Actually Score You High

Past performance is one of the highest-weighted evaluation factors in most federal source selections — often 25-40% of the total score. And the documents that evaluators actually read to assess your past performance are the past performance reference forms you submit: usually a Past Performance Questionnaire (PPQ), sometimes the CPARS narrative, sometimes a custom solicitation-specific form.

Most contractors approach these forms as administrative paperwork. That's a missed opportunity. Past performance forms that are written strategically — that connect prior work to the new requirement, quantify outcomes, and surface differentiators — score significantly higher than forms that just list scope and dates.

What evaluators actually do with reference forms

When a source selection team evaluates your past performance, they're trying to answer three questions:

1. Is this prior work relevant? Does it match the scope, magnitude, and complexity of the new requirement?
2. Did you perform well on it? What's the documented quality, schedule, and customer satisfaction record?
3. How confident are we that you'll perform well on the new contract? This is the actual rating decision.

The reference form is the primary evidence for all three. If the form is sparse, generic, or poorly aligned with the new requirement, the evaluator has to do the work of inferring relevance — and inference always defaults to the safer (lower) score.

The structural elements of a strong past performance reference

1. The relevance bridge

The single most important element of a past performance reference is the explicit connection between the prior work and the new requirement. Don't make the evaluator hunt for it. State it directly.

Example: "This contract required network engineering, IT security, and cloud migration services for a 5,000-user federal customer — directly aligned with the requirements of [the new RFP] for IT modernization services at the Department of [X]."

Include a relevance crosswalk if the solicitation allows it: a table mapping the new requirement's scope elements to specific work performed under the prior contract.

2. The magnitude data

Evaluators apply a magnitude test (dollar value, contract complexity, period of performance). Make these data points easy to find:

• Contract value (and annual value if multi-year)
• Period of performance
• Number of personnel deployed
• Number of locations
• Customer organization size and mission

If the new RFP is $25M annually, your $4M reference is weak even if the work was directly relevant. If you have a stronger reference, lead with that one. If your strongest reference is sub-magnitude, address it explicitly: "While this contract is smaller than the new requirement, it included [specific element] at the magnitude relevant to the new work — managing X locations / Y users / Z systems."

3. The quantified outcomes

This is where most reference forms fall flat. Generic statements like "the contractor performed satisfactorily" or "all milestones were met" are forgettable. Quantified outcomes that demonstrate value are memorable.

Strong outcome language:

• "Reduced incident response time from 4 hours to 27 minutes through implementation of [specific approach]"
• "Maintained 99.7% system availability over the 36-month period of performance"
• "Completed migration 6 weeks ahead of contract schedule, generating $1.2M in cost avoidance for the customer"
• "Achieved 100% retention of cleared personnel through year three"

Weak outcome language:

• "Performed all required tasks"
• "Met all contractual obligations"
• "Customer was satisfied"

The difference is significant. Quantified outcomes get cited in evaluator notes and source selection decision documents. Generic statements get scored as unremarkable.

4. The third-party validation

Wherever possible, use third-party validation language. Customer comments, CPARS quotes, award citations, and program success metrics are stronger than self-assessments.

Strong: "Per CPARS evaluation dated March 2025, the customer rated quality 'Exceptional' and noted 'the contractor's proactive risk identification has prevented multiple potential schedule slips.'"

Weak: "We are proud of the high-quality work performed on this contract."

If you have CPARS records, mine them aggressively for usable evaluator language. See our CPARS guide for how to build CPARS into your past performance strategy.

5. The challenge-and-resolution narrative

Evaluators are skeptical of references that describe nothing but smooth sailing. Real federal contracts have challenges — surge requirements, scope changes, technical surprises, personnel transitions. References that honestly describe a challenge and how the contractor resolved it score higher than references that pretend nothing ever went wrong.

Example structure: "During the second year of performance, the customer requested a 40% surge in cybersecurity assessment volume to support a new mission requirement. The contractor responded by deploying [X resources] within [Y days], maintaining quality standards while delivering all assessments on revised schedule. Customer cited this responsiveness in the FY[X] CPARS as evidence of contractor flexibility under pressure."

Writing the PPQ that the customer will actually sign

If the solicitation requires a Past Performance Questionnaire, the typical workflow is: you fill out as much as you can, send it to your customer for verification and signature, the customer adds their evaluation comments, and you submit the completed form.

Practical tips:

• Pre-fill aggressively. Don't ask the customer to write narratives — pre-fill the form with the strongest possible language and let them edit.
• Send the form well in advance. Customers need at least 5-10 business days to review and sign. Some have approval chains that take longer. If the proposal is due in 14 days and you haven't sent the PPQ yet, you have a problem.
• Provide context. Send the customer a short cover note explaining what the new RFP is for and why their reference matters. They're more likely to provide strong language when they understand the strategic context.
• Make it easy to sign. Provide signature blocks, instructions for return, and your timeline. "Please review and sign by [date]; I'd appreciate any edits or additions you'd like to make."

The relevance crosswalk

For complex solicitations, a relevance crosswalk is one of the highest-leverage moves you can make. It's a table mapping each major scope element of the new requirement to specific work performed under the prior contract.

The crosswalk does the work for the evaluator. Instead of inferring relevance, they see it laid out explicitly. Sources selection decision documents frequently cite relevance crosswalks as evidence supporting strong past performance ratings.

Common past performance reference mistakes

Picking the wrong references. The instinct is to use your three largest contracts. The right move is to use the three contracts most relevant to the new requirement — even if they're smaller. Magnitude matters, but relevance matters more.

Using stale references. Most solicitations require references from the past 3-5 years. References older than that get heavily discounted or excluded entirely. Track your reference portfolio and refresh it as work ages out.

Generic narrative language. "Performed admirably," "to customer satisfaction," "all requirements met." These phrases produce middle-of-the-pack scores. Specific, quantified, third-party-validated language produces strong scores.

Skipping the relevance bridge. Don't make the evaluator infer the connection between your prior work and the new requirement. State it directly.

Submitting incomplete forms. A PPQ with blank fields, missing customer signatures, or missing data points reads as either contractor sloppiness or customer reluctance. Both hurt your score.

The customer relationship dimension

Strong past performance references are downstream of strong customer relationships. The contractors who get the strongest PPQ language are the ones whose customers are genuinely glad to provide it — usually because the contractor stayed in touch, delivered on commitments, and made the customer's life easier over time.

If your past performance references require pulling teeth out of customers who haven't heard from you in two years, that's a relationship management problem, not a paperwork problem. Fix it before the next bid cycle.

Bottom line

Past performance reference forms are not paperwork. They're evidence — the primary documentary evidence evaluators use to score one of the highest-weighted factors in your proposal. Treating them strategically (with relevance bridges, quantified outcomes, third-party validation, and challenge-resolution narratives) materially improves your scores.

Combined with disciplined CPARS management during contract performance and proactive customer relationships throughout the contract lifecycle, your past performance portfolio becomes a compounding asset that wins more contracts each year.

For more on the proposal mechanics that surround past performance, see our guides on government proposal compliance matrix template, how to read Section M like a winning capture manager, and CPARS explained for government contractors.