Past performance sections carry 30-40% of evaluation weight in most federal proposals. Select references using the MATCH framework (Magnitude, Agency type, Technical overlap, Complexity, History within 3–5 years), then lead each write-up with an opening hook, a challenge, your approach, and quantified outcomes. Technical approach is a promise – past performance is proof.
Most contractors treat past performance as a filing exercise. They pull three contracts from the last five years, write a paragraph about each one, and move on. Then they wonder why the score comes back mediocre.
Here’s the reality: evaluators are skeptical. They’ve read hundreds of proposals from contractors who all claim to be experienced, reliable, and mission-focused. Past performance is the one section where the buyer gets to check whether any of that is actually true. It’s the moment where your credibility gets tested against hard evidence — and evaluators know exactly what a weak write-up looks like. Past performance evaluation is governed by https://www.acquisition.gov/far/part-15, which establishes how agencies assess an offeror’s track record.
The contractors who win consistently understand that past performance isn’t just a compliance checkpoint. It’s your most powerful persuasion tool. Done right, it makes an evaluator think: “They’ve done this exact thing before. Why would we take a risk on anyone else?”
This is a guide on how to get there.
Why Is Past Performance Your Strongest Competitive Weapon in Government Proposals?
In competitive procurements, past performance routinely carries 30–40% of total evaluation weight. On some task order vehicles and IDIQ procurements, it’s even higher. Yet most proposal teams spend the bulk of their effort on technical approach — and then submit past performance write-ups that are thin, generic, and unconvincing.
That’s a strategic error. If a section carries 35% of the weight, it deserves 35% of your attention.
The deeper reason past performance matters is psychological. Technical approach is a promise. Past performance is proof. Evaluators know that any contractor can write a compelling management plan or a polished methodology section. What they can’t fake is a documented history of delivering results on similar work.
When your past performance section lands correctly, it shifts the evaluator’s frame from “Can they do this?” to “They’ve already done this.” That’s an entirely different conversation – and it’s where wins happen.
The corollary is also true: a weak past performance section, even alongside a strong technical approach, introduces doubt. Evaluators don’t want to be the person who approved an award to a contractor that then struggled. Solid past performance reduces their risk. That’s the job your write-ups need to do.
How Do You Select the Right Past Performance References Using the MATCH Framework?
The first decision – which contracts to submit – often determines the outcome before you write a single word. Relevance is not a nice-to-have. It’s the core criterion evaluators apply when scoring past performance.
Use the MATCH framework to evaluate your options:
Magnitude
Contract value should be in the same ballpark as the opportunity you’re pursuing. A rough rule: within 50% in either direction. If you’re bidding a $10M contract and your best reference is a $500K project, evaluators will question your capacity. If you’ve never run anything near this scale, that’s a gap to address – not hide.
The exception: if you’re a small business teaming with larger partners, your reference pool may skew smaller. In that case, use every available mechanism to demonstrate capacity – teaming partner past performance, key personnel history, and explicit statements about how your team structure scales.
Customer Type
Match your references to the type of buyer you’re bidding. If you’re responding to a government agency, a government reference demonstrates familiarity with procurement norms, compliance requirements, and the culture of public-sector delivery. If you’re bidding a commercial opportunity, commercial references in the same industry or market segment carry the most weight. Nonprofit, healthcare, and regulated-industry buyers each have their own evaluation cultures – a reference from a closely analogous environment signals that you understand the customer’s world.
Lead with the references that most closely mirror the customer type you’re bidding. If you don’t have a direct match, be explicit about why your experience still applies.
Technology
Aim for at least 70% technical overlap between your reference and the target opportunity. If the RFP calls for cloud migration work and your strongest reference was a help desk contract, you’re scoring a minimal relevance rating regardless of how well you performed. Map the PWS requirements directly against what you actually delivered in each reference. Where there’s overlap, name it specifically.
Complexity
Match the scope and challenge level of the work. Evaluators notice when contractors submit simple, low-risk contracts to support bids on complex, high-stakes programs. It raises the question: can they handle this? Submit references that required problem-solving, integration, coordination, or risk management – not just routine delivery.
History
Recency is a factor in evaluation. Contracts completed within the last three years carry the most weight. Three to five years back is still strong. Anything older than five years is treated skeptically, and evaluators may question whether your team, processes, or technology are still current. If your most relevant reference is six years old, consider whether you can supplement it with more recent work in adjacent areas, even if the match isn’t as strong.
When you evaluate your past performance portfolio against this framework, the right references usually become obvious. If they don’t — if nothing scores well across all five dimensions – that’s your cue to start developing new past performance today, before the next opportunity closes.
What Does a High-Scoring Past Performance Write-Up Look Like?
Once you’ve selected the right references, structure is everything. High-scoring past performance write-ups follow a consistent pattern. Here’s how to build one.
The Opening Hook
Your first sentence should immediately establish relevance. Don’t bury the lead.
Weak: “ABC Company has extensive experience providing IT support services to clients.”
Strong: “We delivered end-to-end cybersecurity operations – including SOC monitoring, incident response, and vulnerability management – under a $4.2M contract from 2021 to 2024.”
The strong version tells the evaluator three things instantly: what you did, who you did it for, and at what scale. They can see the relevance before they’ve read a full paragraph. That’s the goal.
Challenge and Context
After the hook, establish why the work was difficult. Every contract has challenges. Naming them demonstrates that you understand the complexity of delivery – and that you’ve operated under real pressure.
This doesn’t mean complaining or deflecting blame. It means being specific about the environment: aggressive timelines, legacy system constraints, high-security requirements, multi-stakeholder coordination, a transition from an incumbent, a major scope change mid-contract. Whatever was genuinely hard about the work, describe it briefly. This sets the stage for your approach and makes your outcomes more credible.
Your Approach
Describe what you actually did – not in generic terms, but in specific, technical language that demonstrates methodology. Evaluators are looking for evidence that you have a repeatable process, not just good luck.
If you followed a specific framework (ITIL, CMMI, Agile, NIST), name it. If you deployed specialized tools or techniques, mention them. If you coordinated across multiple subcontractors or customer partners, explain how. The goal is to give the evaluator enough detail to understand how you work, not just that the contract was completed.
Quantified Outcomes
This is where most contractors leave points on the table in their past performance sections. Vague outcome statements are nearly worthless. Specific metrics – tied to things that actually matter to customers – are persuasive.
Compare these:
Vague: “Provided excellent customer service and maintained strong relationships throughout the contract.”
Quantified: “Maintained 98.3% customer satisfaction across 1,200+ support tickets, with an average resolution time of 3.8 hours against a 4-hour SLA – exceeding the performance standard for 34 consecutive months.”
The second version is memorable. An evaluator can picture that performance. They can compare it against what they’re hoping for on the new contract. Numbers anchor the narrative in a way that adjectives never can.
Work backward from the contract’s performance standards: what were you measured against? What did you achieve? If you have formal performance ratings – CPARS for government contracts, client satisfaction scores, Net Promoter Scores, or independent audit results – reference them. If you delivered under budget, say by how much. If you beat a schedule milestone, name it. Every metric you can attach to outcomes strengthens the case.
The Relevance Statement
Don’t assume evaluators will connect the dots. Spell out explicitly how this past work applies to the current requirement. Reference specific PWS sections, task areas, or evaluation criteria by name if possible.
“The scope of this contract directly parallels the requirements outlined in the current RFP, which calls for [specific task]. Our experience managing [specific aspect] under a comparable environment positions our team to execute this requirement from day one.”
This closing statement does two things: it makes the relevance explicit (helpful to the evaluator), and it demonstrates that your team read the RFP carefully (also helpful to the evaluator).
How Do You Handle Past Performance Gaps in a Government Proposal?
No portfolio is perfect. Here’s how to handle the most common gaps without letting them sink your score.
Gap #1: You’re Small or New
Subcontracting history, teaming partner past performance, and key personnel experience are all legitimate sources of relevance. If your company hasn’t run contracts at this scale, but your program manager has managed $15M programs at a previous employer – say so. Many evaluation frameworks allow for this, and evaluators know that experience travels with people, not just corporate entities.
When teaming, make sure your prime-sub agreement clearly establishes which partner is responsible for which work – and make sure your past performance section reflects that division accurately. Don’t claim credit for work your partner did; do leverage their record where you’ll be genuinely responsible for similar delivery.
Gap #2: Wrong Customer Type
If your references are from a different sector than the one you’re bidding, lead with capability and complexity rather than customer match. Emphasize that the technical requirements, compliance environment, or operational constraints of your past work were comparable – even if the customer wasn’t.
Be honest about the difference: “While this reference is from a regulated healthcare environment rather than a commercial software context, the data security requirements, multi-stakeholder coordination, and change management complexity were directly comparable to those described in the current RFP.”
Acknowledging the gap while explaining the relevance is more credible than hoping evaluators won’t notice the mismatch.
Gap #3: Partial Match
If your reference checks some boxes but not all, highlight what does match and acknowledge what doesn’t. Evaluators score on overall relevance. A reference that’s a strong match on magnitude, technology, and complexity – even if the customer type is different – can still score well.
The key is to demonstrate that you understand the difference, and that you have a plan for bridging any gaps (additional key personnel, targeted subcontractors, a transition plan).
Gap #4: Confidential or Restricted Contracts
If some of your most relevant work is confidential, classified, or subject to NDA restrictions, you can still reference it – with appropriate redactions. Describe the scope in general terms (“a confidential financial services engagement”), the scale (“$8M, 36-month engagement”), the technical work type (“advanced data analytics and compliance reporting”), and the outcome (“exceeded all contractual performance standards”). You won’t score as high as you would with a fully documented reference, but you also don’t have to pretend the work didn’t happen.
Where Else Should You Use Past Performance Evidence in Your Proposal?
One of the most underused strategies in proposal writing is carrying past performance evidence into other sections of the proposal. Evaluators read the whole document. When they see consistent, specific evidence of relevant experience woven throughout, it reinforces the core message: you’ve done this before.
Technical Approach
When you introduce a technical methodology, support it with experience. “We’ve implemented this approach on [reference] and [reference], reducing deployment timelines by 22% compared to baseline projections.” That single sentence does more to make your technical approach credible than three paragraphs of methodology description.
Risk and Mitigation
Every risk you name should have a corresponding mitigation that references prior experience managing that risk. “We’ve managed similar integration risks on [reference], where we established a dedicated integration testing environment that eliminated three critical defects before production deployment.” Experience-backed mitigations are significantly more persuasive than theoretical ones.
Key Personnel
When you introduce program managers, technical leads, or other key personnel, briefly reference the relevant past performance they bring. “Ms. [Name] served as Program Manager for [Reference], where she led the team that achieved [outcome].” This connects the past performance record to the actual humans who will execute the new contract – which is exactly what evaluators are trying to assess.
What’s on Your Reference Preparation Checklist Before Proposal Submission?
Your write-ups are only half the battle. The reference check – where evaluators contact your past customers – is equally important, and most contractors don’t prepare for it.
Contact your references before you submit. This is not optional. You should know whether your past customer is willing to provide a positive reference, and you should give them a heads-up that they may be contacted. An evaluator who reaches a reference that has no idea the contractor is bidding a new contract is not a good look.
Prepare your reference on what evaluators will ask. Performance questionnaires cover quality, schedule, cost control, management, and often small business utilization. Walk your reference through what they’ll be asked. This isn’t coaching them to lie – it’s ensuring they have the information to answer accurately.
Provide a one-pager on the opportunity. Give your reference a brief summary of what you’re bidding: the customer, the scope, the scale, the key technical areas. Help them draw the connection between the work you did for them and the work you’re proposing to do. They’ll give a more relevant, more confident reference as a result.
Maintain a live past performance library. Don’t start from scratch every proposal. Keep a running database of past performance summaries — one for each completed or active contract – that includes the key metrics, client contact information, scope summary, and relevance tags. When a new RFP comes in, you can pull the right references in minutes rather than days. (For more on building that system, see [How to Build a Proposal Content Library](/blog/proposal-library-system-reusable-content).)
Why Is Past Performance Proof – Not Just Paperwork?
“Technical approach is a promise. Past performance is proof. Evaluators know that any contractor can write a compelling management plan or a polished methodology section. What they can’t fake is a documented history of delivering results on similar work.”
Past performance is not a compliance exercise. It’s your most credible proof point – the section of the proposal where you stop making promises and start showing receipts.
The contractors who consistently score well on past performance share a few characteristics: they select references that match the opportunity, they structure their write-ups around specific outcomes rather than general claims, they quantify results wherever they can, and they prepare their references before the proposal goes out.
None of this is complicated. But it requires discipline, preparation, and a genuine commitment to treating past performance as the persuasion opportunity it is – not just the paperwork it feels like.
Your evaluators have seen hundreds of proposals. The ones that stick are the ones that make them think: “These people have done this. Exactly this. And they did it well.” That’s the bar. Write to that standard.
Written by Tom B. “We build AI-powered RFP response software”.
Leave a Reply