Writing Persuasive Past Performance Sections for Winning Proposals#

Past performance is often the deciding factor in government contract competitions. While your technical approach and pricing matter, evaluators want confidence that you've successfully delivered similar work before. A well-crafted past performance section transforms your company's history into a compelling narrative that directly addresses the customer's concerns and requirements.

This guide walks you through the strategic approach to writing past performance sections that resonate with evaluators and strengthen your proposal's overall competitiveness.

Why Past Performance Matters in Government Proposals#

Federal procurement regulations, particularly in FAR Part 15 (Contracting by Negotiation), emphasize past performance as a critical evaluation factor. Contracting officers use past performance to assess:

Your ability to deliver on schedule
Quality of work and adherence to specifications
Management capability and team stability
Customer satisfaction and relationship management
Financial stability and resource availability
Handling of challenges and problem resolution

Unlike technical proposals that describe what you will do, past performance demonstrates what you have done. This concrete evidence carries substantial weight because it reduces the customer's perceived risk.

Understanding the Evaluation Framework#

Before writing, understand how evaluators assess past performance:

The Past Performance Questionnaire (PPQ)#

Many solicitations include a PPQ requiring specific information about similar projects. These questions typically ask for:

Project title and description
Contract value and duration
Customer name and contact information
Relevance to the current opportunity
Specific accomplishments and outcomes

Answer PPQ questions with precision. Vague or incomplete responses signal weak past performance.

Relevance Scoring#

Evaluators assess how closely your past projects match the current requirement. A $50 million defense logistics contract carries more weight for a logistics RFP than a $2 million commercial supply agreement. Similarly, recent performance (within the last 3-5 years) typically scores higher than older projects.

The Customer Reference Check#

Evaluators often contact references listed in your past performance section. They ask pointed questions about your performance, reliability, and any issues encountered. This reality should drive your narrative strategy.

Selecting the Right Projects#

Prioritize Relevance Over Quantity#

Don't list every contract you've ever won. Instead, strategically select 3-5 projects that most closely align with the current opportunity's scope, scale, and complexity.

For a $10 million cybersecurity services contract, three highly relevant $8-12 million projects outweigh ten smaller, tangentially related contracts.

Match Key Evaluation Criteria#

Review the RFP's evaluation criteria and past performance questions. Your selected projects should demonstrate capability in:

Similar technical scope
Comparable contract value and duration
Same or similar customer type (federal, commercial, state/local)
Relevant team composition
Applicable certifications or clearances

Consider Recency#

Government evaluators prefer recent performance. Ideally, your examples should be from the last 3-5 years. If your most relevant work is older, include at least one recent project to demonstrate ongoing capability.

Crafting the Narrative#

Start with a Compelling Opening#

Your opening sentence should immediately connect the past project to the current opportunity:

Weak: "We completed a software development project for a federal agency."

Strong: "We successfully delivered a real-time data analytics platform for the Department of Transportation, processing 500+ million daily transactions with 99.99% uptime—directly paralleling the mission-critical requirements of this RFP."

Tell a Results-Focused Story#

Structure each past performance narrative around this framework:

The Challenge: What problem did the customer face?
Your Solution: What specific approach did you take?
The Results: What quantifiable outcomes did you achieve?
The Relevance: How does this directly apply to the current opportunity?

Example narrative:

The Department of Homeland Security needed to consolidate disparate data systems across 12 regional offices while maintaining security compliance. Our team designed and implemented an integrated cloud-based platform using microservices architecture. We delivered the project 2 months ahead of schedule within budget, achieving a 40% reduction in data processing time and enabling real-time intelligence sharing. This experience directly prepares us to architect the distributed system architecture required in your current RFP.

Quantify Everything Possible#

Evaluators remember numbers. Replace vague language with specific metrics:

Vague: "We delivered the project successfully and the customer was satisfied."

Specific: "We delivered the project 3 weeks ahead of schedule, 8% under budget, with zero critical defects and a customer satisfaction score of 4.8/5.0."

Quantifiable achievements include:

Schedule performance (% ahead/on-time delivery)
Budget performance (% under/at budget)
Quality metrics (defect rates, uptime percentages, compliance rates)
Scope achievements (features delivered, users served, transactions processed)
Customer satisfaction (survey scores, retention, contract renewals)
Team metrics (staff retention, security clearances, certifications)

Addressing Common Past Performance Challenges#

Limited Directly Relevant Experience#

If you lack exact matches, emphasize transferable experience:

Highlight projects with similar technical approaches, even if the application differs
Emphasize team experience across multiple similar projects
Explain how you've successfully adapted capabilities to new domains
Include subcontractor experience when appropriate

Past Performance Gaps#

If you're new to an area or haven't worked recently in the required field:

Lead with the most relevant experience you have
Emphasize recent capability building and team development
Highlight key personnel with strong track records
Consider strategic partnerships or subcontracting relationships
Explain your approach to risk mitigation

Negative Past Performance Events#

If you've had performance issues, address them directly in your proposal narrative:

Acknowledge the issue briefly and factually
Explain root causes and contributing factors
Describe corrective actions implemented
Demonstrate how those lessons improved your processes
Show success in subsequent similar projects

Example: "While our initial implementation timeline on Project X extended 4 months due to unexpected legacy system integration challenges, we implemented comprehensive change management processes and delivered the remaining 80% of the project ahead of schedule. We've successfully applied these lessons to five subsequent integration projects, all delivered on or ahead of schedule."

Structuring the Section for Maximum Impact#

Use a Consistent Format#

For each past performance example, use this structure:

Project Title

Contract Value: $X million
Duration: MM/YYYY – MM/YYYY
Customer: [Name], [Location]
Customer POC: [Name], [Title], [Contact]

Relevance to Current RFP: [2-3 sentences connecting this project to current requirements]

Project Description: [2-3 paragraphs covering challenge, solution, and results]

Key Accomplishments: [3-5 bullet points with quantified results]

Create Visual Hierarchy#

Use formatting strategically:

Bold key metrics and accomplishments
Use bullet points for achievements
Include small tables comparing past performance to current requirements
Add a one-page summary table comparing all past performance examples

Align with Technical Proposal#

Reference your past performance section in your technical approach. When describing your methodology, reference the successful application of that same methodology in past projects. This creates a cohesive narrative.

Preparing Supporting Documentation#

Customer References#

Provide current contact information for decision-makers who can speak authoritatively about your performance. Ideal references include:

Project Managers
Contracting Officers
Technical Leads
Program Directors

Brief your references before proposal submission. Share relevant proposal excerpts so they understand what claims you're making.

Letters of Reference#

Consider including optional letters of commendation from past customers. These carry significant weight if they:

Speak to specific accomplishments
Address evaluation criteria from the current RFP
Quantify results and customer satisfaction
Come from senior-level decision-makers

Documentation#

Maintain organized files containing:

Final project reports
Customer acceptance documentation
Performance metrics and dashboards
Award letters or commendations
Lessons learned documents

Best Practices and Common Mistakes#

Do's:#

Be specific and concrete – Use project names, dates, and metrics
Demonstrate relevance – Explicitly connect each project to current RFP requirements
Highlight team continuity – Show that key personnel from past projects will work on this one
Address customer concerns – If the RFP emphasizes schedule reliability, emphasize your on-time delivery record
Use customer language – Mirror terminology and priorities from the solicitation
Update regularly – Maintain current past performance data as projects complete

Don'ts:#

Exaggerate or misrepresent – Evaluators verify claims through reference checks
List irrelevant projects – One highly relevant project beats five marginally related ones
Use generic descriptions – Avoid boilerplate language that could apply to any company
Forget the customer perspective – Write about what matters to them, not what's easiest for you to describe
Omit challenges – Perfect projects seem unrealistic; acknowledge obstacles and how you overcame them
Neglect recent performance – Include at least one project from the last 2 years

Leveraging Past Performance Across Proposal Sections#

In Your Executive Summary#

Open with a strong past performance statement:

"[Company] brings proven expertise in [relevant domain], having successfully delivered [X] similar projects totaling $[Y] million in contract value over the past [Z] years, with 100% on-time delivery and zero critical defects."

In Your Technical Approach#

Reference past performance when describing your methodology:

"We employ the phased implementation approach successfully used on the [Project Name] engagement for [Customer], which resulted in [specific outcome]. This proven methodology directly applies to your requirements."

In Your Management Approach#

Tie past performance to your team and processes:

"Our Project Manager, [Name], led the [Project Name] team of [X] personnel, delivering [specific achievement]. That same team composition and proven processes will execute this contract."

Preparing Your Past Performance Database#

Develop a searchable database of all your company's completed contracts that includes:

Project title and description
Contract value and duration
Customer name and contact information
Key personnel involved
Technical scope and deliverables
Performance metrics and outcomes
Lessons learned
Relevant certifications or compliance achievements
Customer satisfaction ratings

This database becomes invaluable when responding to multiple RFPs. You can quickly identify relevant projects and extract information for proposal narratives.

Conclusion#

Past performance sections succeed when they tell a compelling, results-focused story that directly addresses evaluator concerns and demonstrates your capability to succeed on the current contract. Success requires strategic project selection, specific quantified achievements, clear relevance to current requirements, and honest acknowledgment of challenges overcome.

Invest time in developing strong past performance narratives, maintaining current documentation, and cultivating customer relationships. These efforts pay dividends across multiple proposals and significantly improve your win rates in competitive government contracting environments.

Remember: evaluators choose contractors based on proven ability to deliver. Your past performance section is where you prove you've earned that trust.