All Field Notes

Field Notes · 7 min read

Past performance citations that score, and the ones that quietly do not

Published May 26, 2026

  • Past Performance
  • Proposal Writing

Past performance is the section that small contractors most often write the way they wish it scored, instead of the way it actually scores. The government does not read past performance narratives as marketing copy. The government reads them as evidence packages, and the evaluation criteria in Section M tell you exactly what kind of evidence is in scope. Most past performance volumes are written as if Section M did not exist.

What past performance is being evaluated against

Three dimensions, in roughly this order.

Relevance. Is the work you did similar in scope, complexity, magnitude, and contract type to the work being procured? Section L will define each of those terms. Sometimes "magnitude" means dollar value within a band. Sometimes it means staffing level. Sometimes it means geographic footprint. Read the definition before you write the citation.

Recency. Was the work performed within the recency window? Three years is common. Five is common. Some agencies use a rolling window from the date of solicitation issuance. Cite the period of performance. Do not round.

Quality. Did the customer rate the performance well? This is where CPARS comes in for prime contracts, and where PPQs come in for subcontract work and commercial work. The narrative is supposed to give the evaluator the context to interpret the rating, not to substitute for it.

If your citation does not address all three dimensions explicitly, the evaluator has to do the work of inferring them. Evaluators do not infer in your favor.

The structure of a citation that scores

Every past performance citation should hit, in order.

  1. Customer and contract identification. Agency, contracting office, contract number, period of performance, total contract value, your role (prime or subcontractor), and the dollar value of your scope if you were a subcontractor.
  2. Relevance to the current solicitation. A direct, sentence-by-sentence mapping of the work performed to the work being procured. If the current RFP asks for help desk support in three time zones, your citation says "We provided help desk support across three time zones." Not "We provided customer support."
  3. The work performed. A factual description of the scope, the deliverables, the staffing model, the technical environment, and any constraints (clearance levels, security requirements, geographic dispersion).
  4. Quantified outcomes. Specific metrics. Tickets resolved per month. Uptime percentage. Cost savings. Schedule performance. Customer satisfaction scores. Numbers, not adjectives.
  5. CPARS or PPQ rating. The actual ratings, with dates. Do not paraphrase. If you got a Very Good in Quality, you say Very Good in Quality. If you got a Satisfactory, you say Satisfactory.
  6. Customer reference. A current name, title, phone number, and email for the COR or the equivalent. Verify it the week before submission.

Where it goes wrong

The most common pattern. The contractor writes a narrative that reads beautifully and never once mentions the actual scope of the current solicitation. The evaluator reads it, finds no direct relevance language, and scores it as "Some Confidence" because the relevance link is the contractor's job, not the evaluator's.

The second most common pattern. The contractor cites a contract worth one tenth of the magnitude of the current procurement and does not explain why it still demonstrates capability. Magnitude mismatches need to be addressed head-on. Sometimes the answer is that you scaled from a small base. Sometimes the answer is that the technical complexity transfers even if the dollar value does not. Either way, you have to make the argument.

The third most common pattern. The citation uses past performance language from a previous proposal, lightly edited. The previous proposal was for a different agency with a different definition of relevance. The recycled citation responds to the wrong target.

How to pick citations

You are usually allowed three to five citations. Pick them deliberately.

  • The most relevant contract you have, even if it is older than ideal. Lead with relevance.
  • The most recent contract that touches the same agency or a similar one. Recency plus customer overlap matters.
  • A contract that demonstrates magnitude. If the current solicitation is $20M and you have a $25M contract, cite it.
  • A contract that demonstrates a specific high-risk capability the RFP calls out. Cleared work. Surge staffing. Multi-site coordination.
  • If the RFP awards extra credit for small business participation or for specific socioeconomic categories, a citation that shows that participation.

Do not include a citation just because you are proud of the work. Every citation either advances the relevance argument or wastes a slot.

A note on subcontract citations

If you were a subcontractor, say so plainly, identify the prime, and describe your scope as a percentage of the total contract value. Evaluators discount unclear subcontract citations heavily. They credit clear ones at close to prime equivalent if the scope you owned was discrete and substantial.

Get a PPQ from the prime. Submit it. A subcontract citation without a PPQ is half a citation.

The discipline

The discipline is to write every citation as if the evaluator has never read your other citations, has not read your technical volume, and is reading your citation under time pressure. They need to be able to score relevance, recency, and quality without doing any synthesis on your behalf. The citation that requires synthesis loses to the citation that hands the evaluator the score sheet.

GovSight is built by federal acquisition practitioners who crossed over from contracting officer roles to industry contracts directors. We ship PursuitWorks for the proposal pipeline, TeamingWorks for the subcontract pipeline, and three supporting tools for the work around them.

Past performance citations that score, and the ones that quietly do not | Field Notes