Past Performance in Federal Proposals: What Evaluators Actually Score

Past performance is one of the most consistently misunderstood evaluation factors in federal proposals. Offerors list their largest contracts and assume the volume reads as capability. It does not. Evaluators score past performance on relevance, recency, and demonstrated outcomes — and a reference that fails on any of those dimensions can drag down an otherwise strong proposal.

Relevance is the primary filter

The first question an evaluator asks of a past-performance reference is: "Is this work like the work I am buying?" A reference must demonstrate similarity in scope, technical area, contract type, customer mission, and complexity. A massive reference in an unrelated domain is less valuable than a smaller reference that mirrors the solicitation's scope. Select references for relevance first; magnitude is a tiebreaker, not the lead.

Recency is a quiet gate

Most solicitations specify a recency window for past performance — commonly three to five years. A reference outside the window, however strong, may be excluded from evaluation. Maintain a living past-performance library tagged by recency, scope, customer, and contract type, so the references you select are always inside the window. Assembling relevant, recent references under proposal deadline is a failure mode that produces weak sections.

Specificity converts to score

The reference that reads "provided IT services" scores lower than the one that reads "delivered a 24/7 Tier-1/Tier-2 help desk supporting 3,200 users across four sites for [agency], sustaining 98% first-call resolution and zero SLA defaults over a 36-month period of performance, with a final award fee rating of 'very good'." Specificity — scope, scale, customer, duration, outcomes, and any rating — is what converts a reference from a claim into evidence.

Address risk proactively

If a reference carries a known issue — a cure notice, a terminated contract, a dispute — address it in the narrative. A reference with an honest, specific explanation of a resolved issue often scores better than a reference with a gap the evaluator must investigate. Silence on a known issue reads as evasion; a direct, factual explanation reads as competence.

Build the library once

The past-performance section is the easiest section to do well — if the library exists before the proposal. A structured, tagged library of references with scope, scale, outcomes, recency, and contract specifics lets the proposal team select the strongest, most relevant references in hours rather than reconstructing them under deadline. That library is a capture asset, not a proposal artifact.