Past performance is where most small-business proposals quietly lose points. Not because the work wasn't good — because the writeup didn't give the evaluator anything to score.
I've sat on the contractor side of enough debriefs to tell you: the government employee reading your past performance volume has a worksheet. They are assigning numbers. Your job is to make the numbers easy to assign, and to assign high.
Here is how that actually works, and how to build the section when you are a two-to-fifty-person shop without a full proposal team.
What evaluators are actually looking at
Forget what the RFP cover letter says. Open the Section M evaluation criteria and look at the past performance paragraph. You will almost always see four words, even if they are buried: relevance, recency, magnitude, complexity.
- Relevance — Is the scope of work on the reference contract similar to the scope they are buying now? Not the industry. The scope. IT help desk for the Navy is relevant to IT help desk for the Army. It is not especially relevant to software development for the Navy.
- Recency — Most solicitations want work performed within the last three years, some within five. Completed ten years ago does not count, even if it was brilliant.
- Magnitude — Dollar value and period of performance. A $200K ref does not easily support a $10M bid. Evaluators are looking for references within roughly the same order of magnitude as the work being competed.
- Complexity — Multi-site, multi-stakeholder, security clearances, integration with legacy systems, surge requirements. If the new contract has those, your reference needs to show those.
Your whole job in writing past performance is to make those four things obvious on the first page of each reference.
Picking three references from your backlog
Most solicitations ask for three. Some ask for five. Pick badly and you waste slots.
Here is a scoring framework that works. For each contract you've held in the last five years, score it 1-5 on each dimension, then total it:
- Scope overlap with the new RFP (1 = unrelated, 5 = nearly identical scope)
- Recency (1 = finished 4+ years ago, 5 = active or completed within 12 months)
- Dollar magnitude vs. the new RFP (1 = less than 10% of the new value, 5 = within 50-200% of the new value)
- Complexity match (1 = simpler than the new work, 5 = as complex or more)
- Customer willingness to give a strong CPARS or verbal reference (1 = lukewarm, 5 = they will call the CO on your behalf)
Rank every contract. Pick the top three. If your top three all come from the same agency, swap one for a different agency if you have a solid option — evaluators get nervous when all your past work is with one customer because it reads like you can't function outside that relationship.
If you don't have three strong references, submit two strong ones and a third that is honest about what it doesn't cover. A weak third is better than lying about relevance. Evaluators read a lot of these and they notice.
The four sections of a past-performance writeup that win points
Every reference should have the same four blocks, in this order:
1. Contract identification
Contract number, customer agency, contracting officer name and phone, COR name and phone, period of performance (start and end dates), total contract value, your role (prime or sub, and if sub, what percentage of the work you performed). Put this in a clean table at the top. Evaluators will check the POC info — if the phone number is wrong or the person has retired, you look sloppy.
2. Scope of work
Three to five sentences. What did you actually do? Use the same verbs and nouns the new RFP uses, wherever they honestly apply. If the new RFP talks about "cybersecurity program management," and your reference involved cybersecurity program management, write "cybersecurity program management." Don't write "IT security stuff." The evaluator is keyword-matching whether they admit it or not.
3. Outcomes
This is where most small businesses lose. They write "successfully executed all requirements" and move on. That gives the evaluator nothing to score.
Outcomes need numbers and they need to be defensible. "Reduced customer help-desk ticket backlog from 4,200 to under 400 within six months" is a scorable outcome. "Delivered all monthly deliverables on time across the 36-month base period with zero CPARS deficiencies" is a scorable outcome. "Provided excellent customer service" is not.
If you have a CPARS rating, cite it. If the rating was "Exceptional" or "Very Good" on a specific element, cite the element. If you don't have CPARS, use the customer's own words from emails or award letters — and make sure the reference knows you're quoting them.
4. Relevance statement
One paragraph. This is where you close the loop for the evaluator. "This contract is relevant to RFP XYZ because it required [scope element from new RFP], at [dollar magnitude close to new RFP], within [recency window], and involved [complexity element the new RFP calls out]." Spell it out. Don't make them work for it.
The dealbreakers
Things that cost points even when the underlying work was strong:
- Vague outcomes. "Met all requirements" reads as "we have nothing specific to brag about."
- Cherry-picked metrics. If you cite a great Q3 but the contract ran 36 months, the evaluator wonders about the other 33. Use lifecycle metrics or explain the window.
- Missing or stale POC info. Call every POC before you submit. If they've moved agencies, get a current phone number or swap the reference.
- Reference mismatch. Submitting a $300K janitorial contract as past performance on a $5M IT services bid. Evaluators read this as either confusion or desperation.
- Over-claiming as a sub. If you were a 12% sub, don't describe the contract as if you ran it. The prime will get called, and your credibility dies.
- No customer tie-back. Not giving the evaluator a quote, a CPARS element, or an award-fee reference. You are asking them to take your word for it, and they won't.
Worked example
Here is a past-performance writeup for a fictional small business, Meridian Technical Services LLC, responding to a solicitation for IT help desk support:
Contract: GSA Federal Acquisition Service — Tier 1/2 Help Desk Support
Contract Number: 47QTCA22D0XXX
Customer: GSA FAS, Washington, DC
CO: Jane Morales, (202) 555-0144, [email protected]
COR: Robert Liu, (202) 555-0178, [email protected]
Period of Performance: March 2023 – present (base + two options exercised)
Total Value: $4.2M
Role: Prime, 100% self-performed
Scope: Meridian provides Tier 1 and Tier 2 help desk support for 3,800 GSA FAS users across twelve regional offices. Services include ticket intake via phone, email, and ServiceNow portal; account provisioning and deprovisioning; standard software troubleshooting; VPN and MFA support; escalation to GSA infrastructure teams; and monthly trend reporting to the COR.
Outcomes: Reduced average ticket resolution time from 4.8 hours at contract start to 1.9 hours by end of base year one. Maintained first-call resolution rate above 78% across all eight quarters. Received "Exceptional" CPARS ratings on Quality and Schedule for both completed option periods. COR stated in the option-two exercise letter: "Meridian's performance has exceeded our expectations and set the standard for help desk support across FAS."
Relevance: This contract is directly relevant to RFP W15P7T-26-R-0XXX because it required multi-site Tier 1/2 help desk support at similar user-count magnitude (3,800 vs. 4,500 in the new requirement), was performed within the three-year recency window, and involved the same complexity drivers — ServiceNow-based ticketing, VPN/MFA troubleshooting, and multi-region coverage — called out in PWS sections 3.1 through 3.4 of the new solicitation.
That is what a scorable reference looks like. Four blocks. Numbers. A customer quote. A line-by-line tie to the new RFP.
One more thing
Start your past-performance volume earlier than your technical volume. Customers take time to approve quotes. CPARS pulls take time. POC calls take time. If you are writing past performance the week before submission, you are writing weak past performance.
The Contract Wire sends one short, tactical note a day to small-business federal contractors — RFP breakdowns, pricing plays, and proposal patterns that win. Subscribe free.