Past Performance Narratives That Win Federal Contracts

Why Past Performance Can Make or Break Your Proposal Score

Despite that weight, past performance is consistently the weakest section in most proposals. Companies list contracts they have completed and consider the section done. That approach leaves significant score points on the table every single time.

The Core Principle: Relevance Over Prestige

Your biggest contract is not necessarily your best past performance reference. Evaluators are looking for relevance, defined in most solicitations across three dimensions:

• Scope: Similar type of work (network security, professional staffing, construction management, software development)
• Scale: Similar dollar value or contract size, usually within an order of magnitude
• Complexity: Similar technical, programmatic, or management challenges

One practical step: before you select your references, map each candidate contract against the PWS or SOW task areas. Build a simple matrix with task areas as columns and candidate references as rows. The reference that checks the most boxes goes first.

The STAR-R Formula for Past Performance Narratives

Structure each past performance narrative using STAR-R. This is not a creativity exercise. It is a scoring tool.

• S: Situation. What was the agency's challenge or requirement? Two to three sentences that frame the context an evaluator needs to understand why the work was difficult or consequential.
• T: Task. What was your specific scope of work? Two to three sentences covering contract type, dollar value, period of performance, and your role (prime or sub).
• A: Action. What did you actually do? Four to five sentences covering methodologies, tools, team composition, and any notable decisions or pivots. This is where you differentiate execution from mere presence.
• R: Result. What were the measurable outcomes? Two to three sentences with hard numbers: on-time delivery, cost savings, uptime percentages, ticket volumes, user satisfaction scores.
• R: Relevance. Explicitly state why this reference applies to the current solicitation. Two sentences, no more. Connect the dots directly to the PWS task areas or evaluation criteria language.

That final R is what most companies skip entirely. Evaluators are reading dozens of proposals under time pressure. They will not infer the connection between your DOL helpdesk contract and the current USDA IT support requirement. You must make that connection explicit, in writing, in the narrative itself.

Before and After: The Same Contract, Two Very Different Scores

Before: How Most Companies Write It

"Acme IT provided IT support services to the Department of Labor from 2022 to 2024. We managed the helpdesk and network infrastructure. The contract was performed on time and within budget."

This narrative contains zero verifiable data, no contract number, no CPARS reference, no metrics, and no relevance statement. An evaluator has no basis to rate it above "Neutral."

After: Using STAR-R

Every claim in that narrative is verifiable. The contract number lets an evaluator pull the record. The CPARS rating is on file. The metrics are specific enough to be credible. The relevance statement uses language that mirrors a typical PWS.

Essential Elements to Include in Every Reference Block

Before the STAR-R narrative, include a structured header block. Many agencies provide a template; if they do not, use this format:

• Contract number: Gives evaluators an independent verification path through PPIRS or direct agency lookup.
• Agency name, office, and POC with phone and email: Evaluators may call your reference directly. Make it frictionless. A bad phone number signals carelessness.
• Contract value (total and any options exercised): Demonstrates scale comparability to the current requirement.
• Period of performance: Most solicitations limit past performance to the last three to five years. Confirm your references fall within the window.
• Your role: Prime contractor carries more weight than subcontractor. If you were a sub, specify your percentage of work and which task areas you performed.
• CPARS ratings by category: List each rated category (Technical, Schedule, Cost Control, Management, Small Business Subcontracting) and the rating received. "Satisfactory" or above in all categories is a baseline. "Very Good" or "Outstanding" is a differentiator.
• Contract type: FFP, T&M, Cost-Plus. Relevant because it signals the risk environment you operated in.

Handling Weak or Missing Past Performance

New contractors face the classic chicken-and-egg problem: you need past performance to win contracts, but you need contracts to build past performance. Here is how experienced capture managers handle it:

• Use commercial past performance. FAR 15.305(a)(2) explicitly allows agencies to consider commercial contracts. A HIPAA-compliant managed services contract for a hospital network is directly relevant to a federal health IT requirement. Frame it using the same STAR-R structure and include a commercial client POC.
• Be direct about the gap. Many solicitations instruct evaluators to rate offerors with no past performance as "Neutral," not "Unacceptable." Acknowledge the gap, present your commercial references and key personnel records, and include a brief risk mitigation narrative. Honesty paired with mitigation consistently outperforms silence followed by an evaluator's discovery.

CPARS: Manage It Proactively, Not Reactively

The Contractor Performance Assessment Reporting System (CPARS) is the federal government's official past performance database, and it feeds directly into PPIRS (the Past Performance Information Retrieval System), which has been integrated into SAM.gov as the Contractor Performance Assessment Reporting System repository that evaluators consult during source selection. Most contractors treat CPARS as something that happens to them. Winning contractors treat it as an asset to manage.

• Request your records regularly. Contact the Contracting Officer on each active and recently completed contract. Know what is in your file before a proposal deadline forces you to find out.
• Respond to ratings you disagree with. You have 14 calendar days to submit a contractor comment after a rating is finalized. A well-written, factual rebuttal becomes part of the permanent record that evaluators see.
• Quote Outstanding and Exceptional ratings directly. Copy the exact language from a CPARS narrative into your proposal. "The contractor consistently exceeded performance standards and proactively identified cost savings" carries far more credibility than anything you write about yourself.
• Cultivate the relationship before the rating. Send monthly performance summaries to your COR. Flag issues early and document resolutions. Contracting Officers who see a contractor managing proactively write better CPARS narratives, because you have given them the material to do so.

A single "Outstanding" CPARS rating, quoted verbatim, is worth more in a proposal than a full page of self-promotional text. It is a third-party attestation from the federal government itself.