Most GovCon proposal teams treat past performance as a compliance checkbox. List the contracts, hit the page limit, submit. Evaluators notice. A past-performance volume that reads like a project summary sheet tells the government exactly nothing about whether you can execute on their specific requirement. The difference between a score of 6 and a score of 9 on this factor is almost never about which projects you list — it's about how you translate project history into credible, relevant evidence.
Why Generic Narratives Fail Evaluators
Federal Source Selection Evaluation Boards (SSEBs) read dozens of proposals for the same requirement. They are looking for evidence — specific, verifiable, and directly relevant to the performance work statement in front of them. What they consistently find instead are paragraphs describing scope, team size, and contract value, with no connection to what the solicitation actually requires.
The fundamental problem is perspective. Most companies write past performance from their own vantage point: what they did, how big the project was, what technologies they used. Evaluators need the government's vantage point: what outcome did the contractor produce, how similar was that environment to ours, and what happened when things went wrong?
Insight
GAO protest decisions consistently cite a single failure pattern in losing past-performance volumes: the narrative describes work performed but does not demonstrate relevance to the new requirement. Relevance is your responsibility to establish — evaluators will not infer it.
The Three Questions Every Narrative Must Answer
Before writing a single word, your past-performance team should confirm that each reference answers three fundamental evaluator questions. If your narrative cannot answer all three clearly, the reference is either the wrong choice or requires more development work before submission.
- 1Is this work relevant to what we are asking you to do? Relevancy is determined by scope, complexity, and contract type — not dollar value or recency alone. A $2M delivery order that mirrors the technical complexity of a $40M IDIQ is often more relevant than the larger contract with a different mission.
- 2Can you prove the work was done well? Proof means more than "completed on schedule." It means contractor performance assessment reports (CPARs), customer references, quantified outcomes, and documented performance against defined metrics.
- 3What happened when it was hard? The best past-performance references are not the perfect projects — they are the ones where something went sideways and the contractor responded with skill, transparency, and results. Evaluators are deeply skeptical of narratives with no adversity.
Relevancy Mapping: The Most Underused Technique in Proposals
Relevancy mapping is the practice of explicitly connecting each element of your past-performance reference to specific requirements in the PWS, SOW, or QASP. Most teams skip this step. They assume evaluators will draw the connection themselves. They will not — or if they do, they will draw a weaker connection than you would.
The mechanics are straightforward. Take each reference and create an internal matrix before writing the narrative. On one axis, list the technical requirements, management requirements, and performance objectives from the solicitation. On the other axis, list what your reference contract actually required. Then map them explicitly. Where the mapping is strong, lean into it with specific language. Where it is weak, either find a better reference or be honest about the similarity with a bridge statement.
Example
Bridge statement example: "While this contract supported a civilian agency environment rather than a DoD classified network, the security compliance framework — FedRAMP High, FISMA Moderate — and the 24/7 NOC staffing requirements are directly analogous to the performance environment described in Section C of the solicitation."
Quantification Without Overselling
Numbers make narratives credible. But there is a right way and a wrong way to quantify. The wrong way is to attach large numbers to activities that do not matter to evaluators: "supported 5,000 end users," "managed a $180M contract vehicle," "delivered over 2 million lines of code." These figures are common, unverifiable without context, and ignored by experienced evaluators.
The right approach is to quantify outcomes that track directly to what the solicitation is trying to achieve. If the PWS requires 99.5% system availability, cite your actual uptime across the reference period. If the requirement is rapid position filling for cleared personnel, cite your average time-to-fill for clearance-required roles. If the contract is cost-type with earned-value requirements, cite your CPI and SPI variance range. Evaluators know what metrics matter in their domain — you should prove you know too.
Outcome metrics by contract type
| Requirement Type | Weak Metric | Strong Metric |
|---|---|---|
| IT Operations | Managed 200 servers | 99.97% uptime across 36-month base period; zero P1 SLA breaches |
| Staffing / Cleared Personnel | Placed 80 cleared professionals | Avg 22-day time-to-fill for TS/SCI roles vs. 45-day industry benchmark |
| Program Management | Managed $40M contract | Delivered at 0.98 CPI / 1.02 SPI across 24-month period of performance |
| Proposal / Capture Support | Supported 12 proposals | 9 of 12 resulted in award; $340M total contract value won |
The Narrative Structure That Scores
A high-scoring past-performance narrative follows a consistent structure. The specifics vary by solicitation requirements and page limits, but the underlying logic is the same across most federal acquisitions.
1. Reference Header (Contract Basics)
State the contract number, agency, period of performance, contract value, and type (FFP, CPFF, T&M). Include the NAICS code if space allows. This is not where you make your case — it is where you establish the foundation that evaluators will use to verify or request CPARs.
2. Relevancy Paragraph
Write one to two paragraphs that explicitly connect this reference to the current requirement. Do not wait for evaluators to draw this connection. Use the language of the solicitation — mirror the PWS terms, not your marketing copy. If the solicitation uses "Agile delivery methodology," use that phrase in your relevancy paragraph if it applies.
3. Performance Evidence
This is the weight-bearing section. Describe what you delivered in outcome terms, with quantification. Reference your CPAR ratings if they are Exceptional or Very Good. If you have a customer quote from a reference check or prior debrief, this is the right place for it.
4. Challenges and Recovery
Describe one significant challenge you faced during the period of performance and exactly how you handled it. Be specific. "We identified a six-week schedule risk in month four due to a subcontractor delay. We escalated immediately to the COR, presented three mitigation options with cost and schedule impact modeled for each, and implemented the approved path — recovering five of six weeks by period-of-performance end." This paragraph alone is often what separates Outstanding from Very Good in evaluator scoring.
5. Point of Contact
Provide a verified, reachable government POC. Stale contacts — retired contracting officers, email addresses that bounce — are a direct source of downgraded or unratable past-performance assessments. Call the POC before submission. Confirm they are still reachable and that they remember the engagement positively.
Common Mistakes and How to Fix Them
- Using marketing language instead of performance language. "World-class delivery team" tells evaluators nothing. "Maintained 99.94% SLA compliance across a 36-month base period on a mission-critical DoD network" tells them everything.
- Submitting the maximum number of references regardless of relevancy. More references does not mean more evidence — irrelevant references dilute the quality of your volume and waste evaluator reading time. Choose fewer, stronger references.
- Failing to verify POC availability before submission. This is the single most preventable cause of non-ratable past performance. Call the POC. Send a heads-up email. Confirm the contract number they should reference if contacted.
- Letting the contracts team own this section alone. Your strongest past-performance narratives require input from the program manager, the contracting officer's representative relationship, and the delivery team that lived through the challenges. This is not a documentation exercise — it is an evidence-building exercise.
- Copy-pasting from prior proposals. Evaluators who have reviewed your past submissions will notice. More importantly, prior proposals were written for different solicitations with different relevancy requirements. Every narrative should be freshly mapped to the current PWS.
“Your strongest past-performance reference is not your biggest contract — it's the one that most closely mirrors the specific performance environment the government is trying to recreate.”
A Note on Subcontractor and Teaming Partner Performance
When including references for work performed by teaming partners or subcontractors, be explicit about the work split. Evaluators are trained to identify narratives that claim full-team performance when the prime had a minor role. If your teaming partner performed 80% of the relevant work on a reference contract, disclose this and explain your oversight and integration role. Attempting to claim full credit creates credibility risk across your entire volume.
Tip
Before final submission: assign one person to call every reference POC and confirm reachability. This takes two hours and is the highest-ROI activity in your final stretch. A single non-ratable reference in a competitive acquisition can be the difference between award and protest.
Key Takeaways
- Relevancy must be explicitly stated — evaluators will not infer it from scope descriptions.
- Quantify outcomes that mirror what the solicitation is trying to achieve, not vanity metrics.
- The challenges-and-recovery paragraph often determines whether a reference scores Outstanding vs. Very Good.
- Verify every POC before submission. Non-ratable references have ended competitive proposals.
- Fewer, stronger, more-relevant references outperform a maximum-count volume every time.
About the author
Umer Paul
Co-Founder & Managing Director, Hiregenyx
Umer leads recruitment and proposal delivery at Hiregenyx with a practical focus on hiring velocity, compliance readiness, and evaluator-focused proposal quality. He co-founded Hiregenyx to close the gap between proposal pursuit and talent execution in US federal and commercial markets.