Most small businesses lose federal contracts before the technical evaluators ever read their approach. They lose in the past performance section. The evaluators score it low because the narratives are vague, poorly formatted, or miss what the RFP actually asked for.
Past performance is typically worth 15–30% of the evaluation in competitively negotiated acquisitions under FAR Part 15. On a $2M contract, that scoring weight is the difference between winning and a debriefing call.
This guide covers what goes into each narrative, how relevance is scored, and what to do when your CPARS record has a problem.
The standard six-part structure
Most solicitations specify a format. Follow it exactly. When they don't specify, use this structure. Evaluators are reading dozens of submissions, and they are looking for specific data points. Make it easy to find them.
Customer name and point of contact. Include the agency name, the contracting office, the COR or COTR name, and a phone number or email that still works. Evaluators verify references. A dead phone number is a failed verification.
Contract number and type. Include the full contract number (e.g., HHS-2022-AHRQ-OD-0001). List whether it was a firm-fixed-price, cost-plus, T&M, or IDIQ task order. Contract type signals complexity and risk management experience.
Contract value and period of performance. Give the total contract value and the dates (start through end, or start through present if ongoing). If it was a base period with options, list the base value and total value with all options exercised.
Scope description. Two to four sentences describing what you actually did. Be specific. Not "provided IT services" — "provided help desk support for 1,200 end users across three VA medical centers, managing a 4-hour SLA for Priority 1 tickets." The scope description is where relevance is established.
Relevance to the current requirement. Many companies skip this. Don't. Directly map your prior scope to the work in the solicitation. If the RFP is for cybersecurity assessments at civilian agencies, and your past contract involved FISMA audits at HHS, say that explicitly. Evaluators should not have to guess why your experience qualifies.
Outcomes and metrics. What did you deliver? Quantify it. On-time delivery rate, cost performance (final cost vs. budget), survey scores, awards received, option years exercised. If the agency exercised all options, say so. Option exercise is a strong proxy for customer satisfaction in evaluations.
How evaluators score relevance
Relevance is scored before quality. If an evaluator decides your past contract is not relevant, the narrative gets minimal credit regardless of how well you performed.
FAR 15.305(a)(2) directs agencies to assess "the currency and relevance of the information." Most solicitations break relevance into two or three categories. A typical structure:
- Very Relevant: Similar scope, complexity, and magnitude to the current requirement
- Relevant: Some similarity in scope or complexity
- Not Relevant: Little or no similarity
"Magnitude" usually refers to contract value. If the solicitation is for a $3M services contract and your reference is a $50K pilot, an evaluator may score it "Relevant" at best, even if the work is identical in nature. Check whether the RFP specifies a dollar threshold for relevance. Some explicitly state it: "References must have a value of at least $500K."
Recency matters equally. Most solicitations require references completed within three to five years. A 2019 contract submitted for a 2025 proposal is often outside the window, depending on when the period ended.
On size and complexity: if you are a small business bidding on a $5M contract for the first time, your $800K reference doing similar work is still relevant. Be direct about that in your narrative. Frame the trajectory. The evaluator has discretion, and a clear argument for relevance is better than hoping they connect the dots.
Where companies lose points
Describing inputs, not outcomes. "We managed a team of six and provided weekly status reports" is an input. "We reduced ticket resolution time by 23% over the base year and received an Outstanding CPARS rating" is an outcome.
Omitting adverse information that the evaluator will find anyway. CPARS records are visible to federal evaluators. If you had a rough performance period, disclose it and address it rather than leaving a gap that looks worse than the reality.
Copying the scope description directly from the prior contract's PWS. It reads like a form. Write in plain language describing what your company actually did, who you worked with, and what it took to deliver.
Submitting references with no institutional memory. If your COR left the agency two years ago and the backup contact is also gone, the evaluator cannot verify the reference. Try to confirm contact information before the proposal goes out.
Handling adverse CPARS ratings
CPARS (Contractor Performance Assessment Reporting System) is the federal database where agencies record contractor performance. Ratings run from Exceptional to Unsatisfactory. Every entry is visible to evaluators on future proposals.
If you have a "Marginal" or "Unsatisfactory" rating, you cannot hide it. Evaluators will see it.
The standard approach is to address it directly in a brief section within the past performance volume, or in the narrative for that specific reference. Here is what that looks like in practice:
Acknowledge what happened without being defensive. State the specific issue (schedule slip, quality problem, personnel turnover). Explain what caused it. Then describe what you changed: the new QA process, the project management software you adopted, the staffing redundancy you built in. If possible, show improved performance on a subsequent contract.
One adverse rating does not disqualify you if you show that it was a correctable problem and that you corrected it. What does hurt you is an adverse rating with no explanation, or multiple adverse ratings suggesting a pattern.
You have the right to respond to CPARS ratings within the system itself. If you disagree with a rating, submit a formal contractor response in CPARS before your next proposal cycle. Evaluators see contractor responses alongside agency ratings, and a well-reasoned response can mitigate the impact.
Teaming considerations
If you are submitting as part of a team or a mentor-protégé joint venture, past performance rules get complicated. The SBA's All Small Mentor-Protégé Program allows protégés to use mentor past performance in proposals — but only in specific ways and only for certain set-aside types. Under FAR 15.305(a)(2)(iii), agencies may consider past performance of key subcontractors.
Check the specific RFP language. Some solicitations explicitly allow teaming partner references; others require all references to be for work performed by the prime contractor. Submitting a subcontractor reference when the RFP prohibits it will not just fail to earn points — it may raise a concern about proposal compliance.
Action steps
- Pull your CPARS records now, before your next proposal. Log in at cpars.gov and review every rating from the past five years. If any are Marginal or Unsatisfactory and you have not filed a contractor response, file one before your next submission.
- Build a past performance library with a one-page summary for each reference contract. Include all six data fields, a verified POC, and two to three outcome metrics. Update it quarterly.
- Read Section L (instructions) and Section M (evaluation criteria) of each RFP for explicit relevance thresholds before selecting which references to submit. Submitting three highly relevant references beats submitting five marginally relevant ones.
