Past Performance in Federal Proposals: Narratives, CPARS & Strategy

1885 words GovCon ProposalEngine

Past performance is the evaluation factor where your proposal stops being a writing exercise and becomes a record of what your company has actually delivered. Source selection teams do not read your narrative in isolation. They read it next to your CPARS reports, the questionnaires your references return, and whatever the evaluator already knows about your firm from prior contracts.

That means a well-written narrative cannot rescue a weak record, and a strong record can still lose points if your write-up does not make relevance obvious. This guide covers how evaluators apply the factor, how to choose references, how to write the narrative, and how to manage CPARS and questionnaires before a solicitation lands on your desk.

How Evaluators Actually Use Past Performance

Under FAR 15.304 and 15.305, past performance is an evaluation factor in most negotiated procurements. The agency assesses how relevant and recent each reference is and how well the work was performed, then assigns a confidence rating. Read the solicitation's Section M closely, because the rating labels and definitions vary by agency and even by office.

Two mechanics catch offerors off guard. First, evaluators can use information beyond what you submit, including CPARS records and their own knowledge of your performance. You are not controlling the evidence set. Second, an offeror with no relevant record may not be rated favorably or unfavorably; it receives a neutral or unknown confidence rating. Neutral is not a win, but it is not a loss either, and it changes how you should allocate effort.

Watch for solicitations that split corporate experience from past performance. Corporate experience asks what you have done; past performance asks how well you did it. They may be separate factors with separate page limits, and mixing the two weakens both.

Relevance and Recency: Choosing the Right References

Relevance is usually judged on three dimensions: size (dollar value), scope (type of work) and complexity. Recency windows are set in the solicitation, commonly the last 3 to 5 years. A reference that is perfectly relevant but outside the window is usually worth less than a slightly less similar contract performed last year.

Build a shortlist before you write anything. For each candidate contract, score it against the solicitation's own language, not your gut sense of similarity.

DimensionWhat to checkExample
SizeContract value relative to the new requirementA $4M task order against a $40M ceiling is a weak size match
ScopeSame type of work, same labor categoriesCybersecurity assessment work for a civilian agency when the RFP asks for the same
ComplexityNumber of sites, stakeholders, clearances, integration pointsMulti-site rollout with classified components versus a single-office deployment
RecencyPerformance within the solicitation's windowCheck whether the window runs from contract end or period of performance

Agencies may also consider past performance of predecessor companies, key personnel and subcontractors that will perform major parts of the work. If your prime record is thin but your proposed program manager ran a nearly identical contract elsewhere, say so explicitly and supply the reference. Do not assume the evaluator will connect the dots.

Choose references you can actually reach. A perfect contract with an unresponsive reference produces a late or missing questionnaire, which reads worse than a modest but well-documented one.

Writing the Narrative

Most past performance narratives fail for the same reason: they describe the contract instead of answering the evaluator's question, which is "will this happen again on my program?" The structure below answers that question in a predictable order, and it works whether you have half a page or two pages per reference.

  1. Contract facts block. Contract number, customer and agency, period of performance, dollar value, contract type, your role (prime or sub), and the reference's name, title, phone and email.
  2. Relevance statement. One or two sentences tying this contract to the new requirement on the solicitation's own terms. Name the size, scope and complexity matches.
  3. Challenge. The specific problem or risk on the contract. Be concrete. "Legacy system cutover with a fixed statutory deadline" beats "challenging environment."
  4. Action. What your team did, in sequence, with enough detail that the evaluator can see the work being performed by the people you are proposing now.
  5. Measurable result. Schedule, cost, quality and mission outcomes, stated in numbers you can defend if asked.
  6. Customer recognition. Awards, commendations, or a documented statement of satisfaction. If you have none, omit this block rather than padding it.

Writing tips that hold up under evaluation

  • Put the most relevant reference first. Evaluators read in order and form impressions early.
  • Use the same nouns the solicitation uses. If Section M says "relevance," write "relevance," not "similarity."
  • Attribute results to the people you are proposing, not to the company in general.
  • Keep the facts block identical across references so the evaluator can compare quickly.
  • Have someone outside the program read it cold. If they cannot state the relevance in one sentence, rewrite the relevance statement.

If you are producing narratives across many opportunities, a disciplined GovCon proposal writing guide and a consistent template will save more time than any single drafting sprint. Teams using AI and RFP automation to pull contract facts and draft first passes should still review every number against the source record.

CPARS: Managing the Record Before You Need It

CPARS is the Contractor Performance Assessment Reporting System. Ratings run Exceptional, Very Good, Satisfactory, Marginal, Unsatisfactory, and evaluation areas include quality, schedule, cost control, management, small business subcontracting and regulatory compliance. Those ratings are what many evaluators see first, before your narrative.

The comment clock is short. After an assessing official issues an evaluation, the contractor has 14 days to comment before it becomes available to source selection officials, and 60 days in total to submit comments. A contractor can request review one level above the contracting officer. If you learn about a CPARS evaluation on day 45, you have lost most of your room to respond.

CPARS evaluations are kept for source selection use for 3 years after contract completion, 6 years for construction and architect-engineer contracts. A marginal rating from a contract that ended two years ago is still in front of evaluators today.

A working CPARS routine

  • Track every active contract's assessment due dates in the same system you use for proposal deadlines.
  • Assign one person to monitor CPARS notifications and escalate within 48 hours.
  • Draft your contractor comment as a factual record, not a rebuttal. Cite deliverables, dates and correspondence.
  • Request review one level above the contracting officer when the record is wrong, and do it early in the comment period.
  • Keep the final CPARS PDF in your past performance library the day it is finalized.

For a broader view of how the record feeds capture decisions, see the win strategy and capture management guide.

Past Performance Questionnaires

Past performance questionnaires are sent by the offeror to its customer references, who return them directly to the contracting officer. You do not control the content, and you usually do not see it before the evaluator does. What you control is whether it arrives on time and whether the reference knows what to write about.

Practical steps:

  • Confirm the reference's current contact information and willingness before you submit the proposal, not after.
  • Send the questionnaire early enough that the reference has room to complete it before the solicitation deadline.
  • Give the reference the contract facts: contract number, period of performance, your role, and the key outcomes. Do not tell them what rating to give.
  • Follow up once, politely, and tell the contracting officer if a reference goes silent so the record shows you tried.

Some agencies use their own questionnaire format. Read Section L for the exact instructions, and check the proposal compliance guide for how Section L and M requirements interact.

When You Have Thin or No Past Performance

New entrants, small businesses pivoting to a new agency, and firms pursuing a new scope all hit this wall. The neutral or unknown confidence rating under FAR 15.305 is your floor, not your ceiling. Several legitimate paths raise the record without overstating it.

  • Key personnel performance. Cite the relevant contracts your proposed PM, technical lead or chief engineer performed at prior employers, with references who will confirm it.
  • Subcontractor and teammate performance. If a major subcontractor will do substantial work, its past performance counts. Present it as the team's record, clearly labeled.
  • Predecessor companies. If your firm acquired or reorganized from an entity with relevant work, document the relationship and supply the references.
  • Adjacent relevance. A contract that is smaller or simpler but genuinely similar in scope is better than nothing, provided you explain the gap honestly.

Small businesses should also check whether the set-aside evaluation criteria differ; the small business set-aside guide covers how agencies apply the factors in those procurements. If your record is genuinely thin, spend your effort on technical and management volume quality rather than stretching a weak reference into a claim it cannot support.

Handling a Bad Rating

You will eventually have a marginal or unsatisfactory rating on the record, or a Satisfactory that undersells the work. How you handle it in the proposal matters more than whether it exists.

First, decide whether to disclose. If the solicitation requires all relevant references, omitting a bad one is a risk the evaluator may discover through CPARS. Second, if you disclose, pair the rating with context the evaluator can verify: what went wrong, what you changed, and evidence the fix worked on a later contract. A corrective narrative backed by a subsequent strong rating is credible. An excuse is not.

Third, use the CPARS process itself. If a rating is factually wrong, the comment window and the review one level above the contracting officer are your formal remedies. Do that work when the evaluation issues, not when a proposal is due.

Finally, brief your writers. Proposal staff who discover a bad CPARS record during color team review tend to write around it, which produces vague narratives that score poorly. Give them the facts and a plan.

Building a Past Performance Library

The teams that write strong past performance narratives fastest are not better writers. They maintain a library that already contains the raw material. Build one and update it after every contract closeout and every CPARS finalization.

Store, for each contract:

  • Contract facts: number, customer, agency, value, period of performance, contract type, role.
  • Final CPARS report and any contractor comments.
  • Two or three reference contacts, with the date each was last confirmed.
  • A one-page outcome summary with defensible metrics.
  • Relevance tags, such as the labor categories, technologies and agency types the work covers.

Tag entries so you can search by agency, scope and dollar value when a solicitation arrives. A library with good tags turns reference selection from a two-day scramble into an hour of filtering. Proposal operations teams that run this discipline across opportunities tend to produce more consistent narratives; the proposal operations guide covers the workflow side.

Two more habits pay off. First, capture outcome data at closeout, while the customer still remembers the numbers. Second, review the library quarterly and retire references that have aged out of common recency windows.

GovCon ProposalEngine drafts past performance sections from the write-ups in your own library and checks them against the solicitation requirements, so each narrative starts from a verified record.

Managing active bids? GovCon ProposalEngine uses AI to extract every compliance requirement, match your institutional knowledge base, and produce section-by-section proposal drafts in minutes.

Start Free Trial