Writing a Strong Past Performance Narrative That Wins Government Contracts

Why Past Performance Is a Scored Evaluation Factor

Federal acquisitions over the simplified acquisition threshold almost always include past performance as a rated evaluation factor, and the Federal Acquisition Regulation (FAR) 15.305(a)(2) requires agencies to assess the quality and relevance of a contractor's prior work. Evaluators use the Contractor Performance Assessment Reporting System (CPARS), references, and the narrative you submit to form that judgment. Your narrative is your chance to frame the context that raw CPARS ratings cannot tell on their own.

For small businesses, past performance can feel like a catch-22: you need it to win, but you need wins to have it. The good news is that FAR 15.305(a)(2)(iv) allows agencies to consider a lack of relevant past performance as neutral rather than negative, and you can sometimes cite work performed by a teaming partner, a key subcontractor, or even predecessor work done by staff at a previous employer when disclosed properly. Understanding these rules before you write saves you from underselling legitimate experience.

• FAR 15.305(a)(2) governs past performance evaluation in negotiated acquisitions.
• CPARS ratings are official government records; your narrative supplements them.
• Neutral past performance is not automatic disqualification - verify agency-specific guidance in each solicitation.
• Teaming partner and subcontractor past performance may be permissible; read the solicitation instructions carefully.

The Anatomy of One Past Performance Entry

Most solicitations ask for three to five reference entries, each covering a specific contract. A single entry typically needs to answer five questions in a logical order: What was the contract (scope, dollar value, period of performance, agency or client)? Why is it relevant to the work being bid? What did your team actually do and how? What were the measurable outcomes? And how did the relationship with the customer go, including any problems and how you resolved them?

Think of each entry as a short case study, not a job description. A job description says what you were responsible for. A case study says what you changed, improved, or delivered. The difference matters because evaluators are looking for evidence of performance, not potential. Concrete numbers, named deliverables, and specific timelines carry far more weight than adjectives like 'comprehensive' or 'innovative.'

1. Step 1 - State the contract facts up frontOpen each entry with the contract number (if unclassified and allowed), ordering agency or commercial client, contract type (FFP, T&M, CPFF), dollar value, period of performance, and your role (prime or sub). This gives evaluators immediate context and demonstrates you understand government contracting structures.
2. Step 2 - Map the work to the solicitation requirementsExplicitly state which tasks or requirements in the current solicitation this reference supports. Do not make evaluators guess. Phrases like 'This effort directly supports the requirements in Section C, paragraph 3.2...' signal that you read the solicitation and chose references deliberately.
3. Step 3 - Describe the actual work with specificsName the tools, methods, team size, and deliverables. Avoid vague language. Instead of 'provided IT support,' write 'maintained 99.7% uptime across 14 geographically dispersed sites serving 3,400 end users under a 4-hour response SLA.'
4. Step 4 - Quantify outcomesResults speak louder than tasks. Use percentages, dollar amounts saved, schedule metrics, and quality indicators wherever your records support it. If you reduced processing time by 30% or delivered all 12 contract deliverables on time with zero CORs, say so.
5. Step 5 - Address problems and corrective actions honestlyIf your CPARS record includes any less-than-satisfactory ratings or a problem arose during performance, address it directly. Evaluators read CPARS before they read your narrative. A brief, factual explanation of what happened, what you changed, and what the outcome was often turns a vulnerability into evidence of maturity and accountability.

Relevance and Recency: The Two Filters Evaluators Apply

Every solicitation defines relevance differently, so read the evaluation criteria section before selecting references. A common framing is that relevant work shares similar scope, complexity, dollar magnitude, and mission area. If the RFP asks for recent and relevant work within three years and a dollar threshold, contracts outside that window or below that size may receive little or no credit regardless of quality.

Recency rules are usually stated explicitly, often as work performed within the past three to five years. If your best reference is older, consider whether a subcontractor or teaming partner has more recent comparable work. When you do cite an older contract, note briefly why it is still technically applicable, such as specialized equipment or a regulated environment that has not changed significantly. Do not pretend recency criteria do not exist; evaluators will notice.

A Concrete Example: IT Services Narrative Entry

Suppose your company is bidding on a DHS help desk services contract, and you want to cite a prior GSA IT support contract. A weak entry reads: 'Our company provided IT support services to GSA from 2023 to 2025. We resolved tickets quickly and received good customer satisfaction scores.' An evaluator learns almost nothing actionable from that.

A strong version reads: 'Under Contract No. GS-XXXXX-XX, a firm-fixed-price task order valued at $4.2 million, our team operated a Tier 1 and Tier 2 help desk for GSA's Regional Offices from January 2023 through December 2025. We supported approximately 2,800 users across six regions, maintained a first-call resolution rate of 78% against a 70% contractual target, and closed 98.4% of Priority 1 tickets within the four-hour SLA. This directly mirrors the scope outlined in Section C.3 of the current solicitation, including multi-site user support, ITSM tool administration (ServiceNow), and Federal reporting requirements. Our final CPARS rating was Exceptional in Quality and Very Good in Schedule.' That entry earns its space.

Formatting Within Page Limits

Most RFPs impose a page limit on past performance volumes, often one to two pages per reference. Work within that constraint from the beginning rather than editing down at the end, which typically cuts the specifics that matter most. Use a consistent structure for each entry so evaluators can find what they need quickly. A simple table at the top of each entry covering the factual contract data, followed by narrative paragraphs for relevance, performance, and outcomes, is a format that works across many agencies and does not waste space.

Graphics, if allowed, should earn their page count. A one-row table of key metrics can convey in four lines what would take a paragraph to explain. However, do not use graphics to pad thin substance. If you cannot fill the entry with real accomplishments, choose a different reference or acknowledge limited past performance and lean on your key personnel qualifications and management approach instead.

Building a Living Library of Past Performance Records

The biggest mistake small businesses make is trying to write past performance narratives from memory during proposal crunch time. By then, project managers have moved on, contract numbers are buried in emails, and performance metrics were never centrally recorded. The solution is to create a simple internal repository, even a shared folder with a template, where each project lead documents outcomes as work is completed.

At a minimum, capture the contract number, agency, dollar value, period of performance, a summary of scope, key metrics achieved (schedule, cost, quality indicators), any notable customer commendations, and the COR or COTR name and contact information. Update it quarterly. When a proposal is due, you pull from a menu of pre-documented references rather than starting from scratch. This discipline is especially valuable when pursuing multiple opportunities simultaneously, which is common as a company grows.

• Document contract facts immediately at award, not at closeout.
• Record metrics monthly during performance so you have a data trail.
• Save written customer commendations and positive email exchanges with COR contacts.
• Note any issues and corrective actions taken in real time so you can narrate them accurately later.
• Review and update the library quarterly as a standard business practice.

Common Mistakes That Hurt Past Performance Scores

Selecting references because you feel good about the relationship rather than because they are objectively relevant is one of the most common and costly errors. Evaluators are assessing similarity of work, not the warmth of the customer relationship. A reference where your team did something adjacent to the current requirement scores lower than one where the scope overlaps directly, even if the adjacent reference was a bigger win.

Another frequent mistake is failing to disclose a negative CPARS rating and hoping evaluators will not find it. They will, because they check. Proactively addressing a problem, explaining root cause, and demonstrating the corrective action you implemented shows professionalism. Silence reads as either unawareness or evasion, neither of which inspires confidence. A third error is submitting references that are too old, too small, or from commercial clients without noting how the work is analogous to federal contracting demands. Read the solicitation criteria, match your references to them precisely, and explain any gap honestly.

Using Decision-Support Tools During Capture and Proposal Development

Identifying which opportunities are worth pursuing, and therefore which past performance references to prepare, is a capture management decision that comes before the writing starts. Tools that help you monitor and filter SAM.gov opportunities by NAICS code, set-aside type, and agency can reduce the time spent on pre-solicitation research and give your team more runway to develop strong narrative content.

CaptureIQ is designed to support that earlier stage of the process by surfacing relevant opportunities and helping teams organize pursuit decisions. All proposal content, including past performance narratives, is reviewed and authorized by the humans on your team before submission. The platform does not auto-submit proposals or generate narrative text on your behalf; it creates space for your writers and capture managers to do their work more efficiently by reducing the administrative load of opportunity monitoring.