Past performance that wins: relevance, recency and CPARS

Past performance is the Government's best predictor of how you will perform. FAR 15.304 requires agencies to evaluate it in negotiated competitive acquisitions expected to exceed the simplified acquisition threshold, unless the contracting officer documents why it is not appropriate, and FAR 15.305(a)(2) describes how: evaluators weigh the currency and relevance of the information, its source, its context and general trends in performance. Strong records do not speak for themselves. The proposals that win make relevance obvious and back every claim with evidence.

What evaluators look at#

• Relevance: how similar the referenced work is in scope, size, complexity and environment. Solicitations usually define relevance; mirror their terms.
• Recency: whether the work falls inside the window the solicitation sets, often measured back from the proposal due date.
• Quality: how well you performed, drawn from performance evaluations, questionnaires, interviews and other sources the agency has.
• Trends: improving or declining performance across contracts.

Many agencies express the result as a confidence assessment (for example, substantial, satisfactory, limited or no confidence) rather than adjectival ratings. An offeror with no relevant past performance record may not be evaluated favorably or unfavorably on past performance (FAR 15.305(a)(2)(iv)): it receives a neutral rating instead.

How CPARS feeds every future bid#

Agencies record contractor performance evaluations in CPARS under FAR Subpart 42.15. Evaluations are prepared at least annually and when work is completed, and they rate areas such as technical quality, cost control, schedule, management and small business subcontracting on a five-level scale from Exceptional to Unsatisfactory. Source selection teams use these records for future awards, for up to three years after the work is completed (six years for construction and architect-engineer contracts).

You get the chance to respond. The agency notifies you when an evaluation is ready, and you have up to 14 calendar days to submit comments, rebutting statements or additional information (FAR 42.1503). Disagreements are reviewed at a level above the contracting officer. CPARS evaluations are not released to the public, which also means you cannot read your competitors'.

Using your team's records#

You do not have to rely only on your own contracts. FAR 15.305(a)(2)(iii) says agencies should take into account past performance information about predecessor companies, key personnel with relevant experience, or subcontractors that will perform major or critical aspects of the requirement, when that information is relevant. For small business joint ventures on set-asides, SBA's rule requires the agency to consider work done individually by each joint venture partner as well as by the joint venture itself (13 CFR 125.8). Read Section L closely, because solicitations limit how many references each team member may submit and what counts.

Writing a reference that scores#

For each reference, include:

1. The facts: contract number, customer, contract type, period of performance, value and your role (prime, subcontractor or joint venture partner).
2. A relevance map: a short table that ties each element of the new requirement to what you did on this contract, using the solicitation's own terms.
3. Results with numbers: service levels met, cost savings, schedule performance, defects reduced or transitions completed.
4. Problems and fixes: if something went wrong, say what you changed. Evaluators often know already, and a candid answer builds confidence.
5. Customer contacts who are current, reachable and expecting the call or questionnaire.

Past performance checklist#

Common pitfalls#

• Choosing references by contract value alone. A smaller contract with a closer scope match is often more relevant than a large one.
• Claiming a teammate's work as your own. Identify who performed what; misattributed performance damages credibility.
• Letting CPARS comment windows pass. An unanswered marginal rating follows you to every competition.
• Ignoring subcontract work. Work you performed as a subcontractor can be relevant; document it with the prime's help.

How TeamingIndex helps#

• Every profile shows award history from USAspending.gov, so you can quickly see where a partner has performed and for which agencies. Sort partners by total obligations to find deep records in your market.
• Run a past performance analysis with the AI analyst to see which of your awards to cite for a target requirement (by recency, relevance, size and scope), how to write them up and what is missing. Verify every fact before it goes into a proposal.
• Add teammates whose records close your gaps with the Team Builder, and see positioning for recompetes for how past performance fits a challenger strategy.