Last reviewed on May 12, 2026.
Why past performance carries the weight it does
On most federal source selections, past performance is one of two or three top-weighted non-price evaluation factors. The reasoning is straightforward: contracting officers cannot test execution capability during evaluation, so they look at how the bidder has performed before. A firm with an exceptional track record on similar work is a safer bet than one promising to do it well for the first time.
Past performance evaluation has two distinct mechanics: the CPARS rating (which the government produces) and the past-performance proposal volume (which the bidder produces and which references those CPARS records and supplements them with reference contacts). This page is about how to build, manage, and deploy the past-performance portfolio — not the CPARS rating mechanics, which are covered separately.
What evaluators actually look at
The past-performance evaluation section of most Section M's lists three to five things the evaluator weighs:
- Recency. Typically within the past three to five years. Older work is given less weight or none.
- Relevance. Similarity in scope, complexity, dollar value, contract type, and customer environment. A small civilian contract is not strongly relevant to a large classified DoD pursuit.
- Quality of performance. CPARS ratings, customer references, and any documented issues.
- Scale. Whether the bidder has performed work of similar size. A firm whose largest project is $2M will have a hard time citing relevance for a $50M task order.
- Customer environment. Same agency, same classification level, same regulatory regime — all add weight.
The two failure modes are over-citing (every solicitation gets the same eight contracts, regardless of fit) and under-citing (omitting contracts that would have been relevant). Both reduce competitiveness.
Building the portfolio: what counts and what doesn't
The portfolio should be cataloged in a structured form before any specific pursuit needs it. For each contract, capture:
- Customer agency, sub-organization, and contracting officer
- Contract number, vehicle (Schedule, GWAC, agency-specific IDIQ), and contract type
- Period of performance and current status (in progress, completed, option exercised)
- Original ceiling, current obligations, and burn rate
- Scope summary in 100–150 words written in customer language
- Specific task areas the contract covered, with the labor categories used
- Quantitative outcomes — cycle times, defect rates, throughput, savings — with the source data they came from
- CPARS ratings by element (technical, cost, schedule, management, small business)
- Current customer reference: name, title, email, phone, with permission status logged
- Any documented issues, including how they were resolved
Subcontract work counts, but with caveats. Some solicitations specifically request only prime contract experience; others accept subcontract experience with explanation. Capture the prime contractor's identity, the dollar value of your subcontract portion, and a clear description of which scope you performed.
The new-contractor problem
Firms with no past performance face a real problem on most federal pursuits. The standard solutions, ranked roughly by effectiveness:
- Subcontract first. Build past performance as a subcontractor on a larger prime's contract. Document the work in writing with the prime so you can cite it later.
- Cite key personnel experience. When the firm has no relevant contracts but the proposed staff do, many evaluation schemes allow citing the individual's experience under a prior employer with a clear note that it was experience-of-personnel rather than experience-of-firm.
- Cite commercial past performance. For relevant commercial work where the buyer can serve as a reference. Less weight than federal work but better than nothing.
- Joint venture with a firm that has past performance. Under an SBA mentor-protégé JV, the JV can present the past performance of either parent.
- Cite team member past performance. Subcontractors listed in the proposal can offer their past performance, with appropriate weight.
None of these substitute for actual contract experience. The first three years of any new firm are mostly about building citable past performance, which is why most successful entrants start as subs.
Citing past performance in proposals
The past-performance volume is one of the most templated parts of a proposal — and one of the most-misused. Common section structure:
- Header data. Contract number, vehicle, contract type, value, period of performance, customer organization, and contracting officer details.
- Scope summary. A short narrative describing what the firm did on the contract, written to track to the current solicitation's scope.
- Relevance matrix. A two-column table mapping the current solicitation's requirements to elements of the cited contract. This is where you tell the evaluator why this example matters.
- Outcomes. Quantitative results — measurable improvements, awards, customer recognition. Tie each to a specific source.
- Customer reference. Current contact details with the customer's permission confirmed.
The relevance matrix is the section that wins or loses past-performance scores. It forces the writer to make the connection explicit instead of asking the evaluator to do the work. A weak past-performance section assumes the evaluator will read the scope summary and infer relevance; a strong one removes the inference.
Handling a negative CPARS rating
Even well-run firms get the occasional Marginal or Unsatisfactory rating. How you handle it matters more than the rating itself. The standard process:
- Engage during the rating period, not at the end. The single best way to avoid a bad rating is regular customer communication during performance. Issues you've already addressed are less likely to surface in a rating.
- Use the 14-day comment window. When a draft CPARS rating is issued, the contractor has a window to provide comments and supporting documentation. Use it. Comments become part of the permanent record alongside the rating.
- Request discussion. If there is a material disagreement, request a discussion with the rating official. Many initial ratings shift when context is added.
- Address the rating in future proposals. Rather than hoping evaluators miss a negative rating, cite the contract, acknowledge the issue, describe what you did to address it, and reference the post-issue performance. Evaluators respect transparency.
- Build mitigating context into the portfolio. A single Marginal rating among many Exceptional ratings is far less damaging than the same rating standing alone. Robust portfolios survive individual bad ratings.
A genuinely Unsatisfactory rating is harder. The contractor remains eligible to bid but should expect close evaluation scrutiny on future pursuits and may want to consider whether to bid on similar work until performance is demonstrated elsewhere.
Maintaining the portfolio over time
- Refresh quarterly. Update completed-contract status, new outcome data, and CPARS rating changes.
- Re-confirm references annually. Customer reference contacts move agencies and change roles constantly. A reference contact who has retired is worse than no reference.
- Sunset old contracts. Once a contract is more than five years old, move it out of the "primary citation" pool. It may still be useful as supplemental context but should not anchor a proposal.
- Document subcontractor performance you observed. If you served as a prime, the past performance of your subs is also an asset for future teaming.
- Capture customer compliments as you go. An email from a contracting officer praising specific work is past-performance evidence. File it with the contract record.
Common mistakes
- Generic past performance write-ups. Reusing the same scope summary across all proposals. Evaluators read it as "this firm doesn't really see how this contract maps to my requirement."
- Citing contracts that are too old. If the solicitation says "within the past three years," contracts from five years ago will score zero even if they were the firm's most impressive work.
- Outcomes without sources. "Reduced cycle time by 40%" is unverifiable. "Reduced cycle time from 14 to 8 business days as reported in the Q3 2024 program review" is.
- Missing reference confirmation. Calling references' contacts cold during evaluation and getting a "this person no longer works here" message destroys the citation.
- Treating subcontract experience as equivalent to prime experience. When the solicitation distinguishes them, the distinction matters. Be clear which is which.
- Hiding negative CPARS ratings. Evaluators have access to CPARS. Pretending a rating doesn't exist signals worse than addressing it.