Past performance reference template for government proposals

Past performance is proof that you’ve done work similar to what the government is buying and did it well. Evaluators look at three things: relevance (was the work similar?), recency (was it recent?), and quality (did you deliver?). If you can show all three, your past performance volume strengthens your entire proposal. If you leave it thin or disorganized, evaluators will rate you lower — even if your technical approach is strong.

If you’ve already worked through our government bid proposal template, you know that Volume II covers past performance. This article gives you the template for that volume, walks through every field evaluators care about, and shows you how to build a past performance database before your first bid so you’re not scrambling at proposal time.

What evaluators actually look at

Government source selection teams evaluate past performance along four dimensions defined in FAR 15.305:

1. Currency. How recent is the work? Most solicitations define “recent” as the last 3-5 years, but each RFP sets its own window. A contract that ended in 2019 is probably too old.
2. Relevance. How similar is the cited work to the current requirement? Evaluators compare scope, dollar value, complexity, and contract type. An IT services reference won’t help much on a construction bid.
3. Source of information. Evaluators pull data from your proposal, from CPARS (the government’s contractor performance database), and from direct contact with your references. They’re not limited to what you submit — they can call anyone.
4. General trends. Is your performance improving, holding steady, or declining? A company that had problems two years ago but has clean evaluations since shows a positive trend. One that’s trending downward raises red flags.

Evaluators assign adjectival ratings — typically ranging from “Substantial Confidence” down to “No Confidence” — and document specific strengths, weaknesses, and deficiencies with page references to your proposal.

The template: what to include for each reference

Most solicitations ask for 3-5 past performance references. Section L of the RFP tells you exactly how many and may provide a specific format. Always follow the solicitation’s instructions first. If the RFP includes a Past Performance Questionnaire (PPQ) template, use it — don’t substitute your own format.

When the solicitation doesn’t provide a template, use this structure for each reference:

Reference information

Field	What to include
Contract/order number	The full contract number (e.g., W911NF-22-C-0045). Evaluators verify this in FPDS.
Contract type	FFP, T&M, CPFF, CPAF, or whatever applies. This affects relevance scoring.
Client agency or company	Full name of the contracting agency or commercial client.
Contract value	Total contract value AND the dollar value of work your company performed (important if you were a sub).
Period of performance	Start date through end date or “ongoing.” Recency matters.
Status	Completed or ongoing. If ongoing, state percent complete.
Place of performance	City/state, or “multiple locations” with specifics.
Your role	Prime contractor, first-tier subcontractor, or JV member. Be specific.
CAGE code	Your 5-character CAGE code.
UEI	Your 12-character Unique Entity Identifier.

Scope description

Write 150-300 words describing the work you performed. Don’t summarize what the contract was about in the abstract. Describe what your company did, what you delivered, and how it connects to the current requirement.

Bad: “Provided IT support services to a federal agency.”

Good: “Managed 24/7 Tier I/II help desk for the U.S. Army Communications-Electronics Command (CECOM), supporting 15,000 users across 12 installations. Handled an average of 2,400 tickets per month with a first-call resolution rate of 78%. Deployed and maintained Remedy ITSM ticketing system. All 14 help desk analysts held active Secret clearances.”

The good version gives the evaluator four data points: scale (15,000 users), throughput (2,400 tickets/month), quality (78% first-call resolution), and compliance (Secret clearances). Each one maps to something they can compare against the current solicitation’s requirements.

Measurable outcomes

Include at least two quantifiable results for each reference. Evaluators are trained to look for evidence, not claims. “Excellent performance” means nothing. “98.7% SLA compliance over 36 months” means everything.

Strong outcome examples:

• “Delivered all 12 milestone reports on time, zero late submissions across 3-year period”
• “$340K in cost savings identified through process automation, documented in quarterly reports”
• “Zero security incidents across 8,500 endpoints during 24-month monitoring period”
• “Completed $6.1M barracks renovation on budget, earned LEED Silver certification”

Points of contact

Provide at least two client contacts per reference:

Field	Details
Name	Full name of the person who can speak to your work
Title	Their title at the time of the contract AND current title if different
Phone	Direct number, not a switchboard
Email	Current, working email address
Relationship	Their role relative to your contract (COR, CO, Program Manager)

This is where proposals break down. Evaluators call references. If the phone number goes to voicemail and the email bounces, that reference effectively doesn’t exist. Before you submit any proposal, call every POC, confirm they’re still at that number and email, and ask if they’re willing to serve as a reference. Do this every time, even if you used the same reference six months ago. Government personnel move frequently.

Filled-in example: IT services firm

Here’s what a complete reference looks like for a small IT company bidding on a cybersecurity support contract:

Reference 1 of 3

Field	Details
Contract number	W911NF-23-C-0189
Contract type	Firm-Fixed-Price
Client agency	U.S. Army CECOM, Aberdeen Proving Ground, MD
Total contract value	$4.2M
Value of work performed	$4.2M (prime)
Period of performance	09/2023 - 09/2025 (completed)
Your role	Prime contractor
CAGE code	3A7K2
UEI	J4K8M2N5P7R9

Scope: Provided enterprise cybersecurity operations for CECOM’s unclassified network environment, covering 22,000 endpoints across 8 installations. Responsibilities included 24/7 Security Operations Center (SOC) staffing, vulnerability scanning (weekly Tenable Nessus scans across all endpoints), incident response, and continuous monitoring per NIST 800-137. Managed a team of 14 cybersecurity analysts, all holding active Secret clearances. Delivered monthly threat briefings to the ISSM and quarterly risk assessments to the CIO.

Outcomes:

• Zero critical security incidents over 24-month contract period
• 99.2% SOC uptime against 99.0% SLA requirement
• Identified and remediated 1,847 vulnerabilities, with critical findings resolved within 24-hour SLA window 100% of the time
• Earned “Exceptional” CPARS rating for Technical Quality

Points of contact:

	Primary	Secondary
Name	Sarah Mitchell	James Rivera
Title	Contracting Officer Representative	Information Systems Security Manager
Phone	(410) 555-0142	(410) 555-0198
Email	sarah.m.mitchell.civ@army.mil	james.r.rivera.civ@army.mil

What to do if you don’t have federal past performance

This is the biggest barrier for first-time bidders, and it’s not as fatal as it feels. The FAR has a specific rule about this: under FAR 15.305(a)(2)(iv), a company with no relevant past performance record “may not be evaluated favorably or unfavorably.” That means you get a neutral rating — not a zero, not a disqualification. You’re still in the competition, and your technical approach and price carry the weight.

That said, neutral isn’t a strength. Here’s how to fill Volume II when you don’t have federal contract history.

Commercial contracts. Private-sector work counts. An IT firm that managed 5,000 endpoints for a Fortune 500 company has relevant experience even if none of those endpoints were government-owned. Frame the scope description the same way you would for a federal reference — measurable outcomes, specific deliverables, named POCs who can verify the work.

Subcontract experience. Work you performed as a first-tier subcontractor on a federal contract is legitimate past performance. Under SBA rule 13 CFR 125.11, you can request a formal past performance rating from the prime contractor within 30 days of contract completion. The prime must respond within 15 days using the same five-point scale the government uses in CPARS. This rating doesn’t go into CPARS itself, but agencies are required to consider it when evaluating your proposal.

State and local government contracts. State contracts show you can work within government procurement rules. The compliance framework is different from federal, but the project management discipline translates. If you’ve done work for a state or local government, include it.

Joint venture experience. If you performed work through an SBA-approved joint venture, you can claim that past performance. FAR 15.305(a)(2)(iii) requires evaluators to consider JV member past performance when the JV itself has no record.

Key personnel experience. FAR 15.305(a)(2)(ii) says evaluators “should” consider the past performance of key personnel who will work on the contract. If your lead engineer managed a $10M cybersecurity program for a previous employer, that experience is relevant. Frame it carefully — be explicit that you’re citing individual experience, not company experience, and make sure the person is committed to working on the contract you’re bidding.

CPARS: the system evaluators check first

Before they read your Volume II, evaluators pull your records from CPARS (Contractor Performance Assessment Reporting System) at cpars.gov. CPARS is the government-wide database where contracting officers document how you performed on every contract above the simplified acquisition threshold ($350,000 as of October 2025).

Here’s what you need to know about it:

You can’t control what goes in, but you can respond. When your contracting officer completes a CPARS evaluation, you get notified and have 14 days to submit comments, rebuttal statements, or additional information. Then you have a total 60-day review period. If you disagree with the rating, the agency provides review at a level above the contracting officer. The agency has final say, but your comments become part of the permanent record.

CPARS evaluates five areas. Technical quality, cost control (for non-fixed-price contracts), schedule and timeliness, management and business relations, and small business subcontracting (if applicable). Each area gets its own rating: Exceptional, Very Good, Satisfactory, Marginal, or Unsatisfactory.

Evaluations stick around. CPARS data is retained for 3 years after contract completion (6 years for construction and architecture-engineering contracts). Every evaluator on every future source selection can see them.

The old PPIRS system merged into CPARS in 2019. If you see references to PPIRS (Past Performance Information Retrieval System) in older guidance, that’s now part of CPARS. One system, one database.

The lesson: treat every active contract as a future past performance reference. If a COR sends you an email praising your team’s work, save it. If you hit every milestone on time, track it. When that CPARS evaluation comes, you want the record to support the rating you deserve — and if it doesn’t, you want the data to write a compelling rebuttal during the comment period.

Build your past performance database now

Don’t wait until you’re writing a proposal to start collecting reference data. By then, POCs have moved, contract numbers are buried in old emails, and measurable outcomes are half-remembered.

Start a spreadsheet or database with these columns, and update it after every contract milestone:

Column	Example
Contract number	W911NF-23-C-0189
Client	U.S. Army CECOM
Contract type	FFP
Total value	$4.2M
Your value	$4.2M
Start date	09/2023
End date	09/2025
Status	Completed
Your role	Prime
Scope (100 words)	Enterprise cybersecurity operations, 22K endpoints…
Key deliverables	Monthly threat briefs, quarterly risk assessments
Measurable outcomes	Zero critical incidents, 99.2% SOC uptime
POC 1 name	Sarah Mitchell
POC 1 title	COR
POC 1 phone	(410) 555-0142
POC 1 email	sarah.m.mitchell.civ@army.mil
POC 1 last verified	01/2026
CPARS rating	Exceptional (Technical), Very Good (Schedule)
Letters of commendation	Yes - saved to /references/cecom/

Two things to do every quarter: verify POC contact info (a quick email or call) and add any new measurable outcomes from active contracts. Government personnel rotate assignments, change agencies, and retire. A reference you verified six months ago might have a disconnected number today.

What’s changing: Section 824 and the FY2026 NDAA

The biggest near-term development for small businesses with limited federal history is Section 824 of the FY2026 National Defense Authorization Act, signed in December 2025.

Section 824 directs the Department of Defense to:

• Issue guidance on accepting commercial and non-government past performance as relevant in DoD contract evaluations
• Establish methods for validating non-government references (attestations, verifiable contacts)
• Expand use of alternative evaluation techniques like demonstrations, testing, and proof-of-capability exercises
• Identify and eliminate procedural barriers that disproportionately affect small businesses and nontraditional defense contractors (within 90 days)

The one-year deadline for DoD guidance is approximately December 2026. The implementing regulations haven’t been issued yet, but the direction is clear: DoD is acknowledging that the “you need past performance to get past performance” catch-22 locks out capable companies, and it’s building off-ramps.

If you’re a commercial technology company or a small business with strong private-sector results but no CPARS history, this is worth watching. It could make your commercial track record directly citable in DoD proposals.

Common mistakes that hurt your Volume II

Recycling boilerplate. Evaluators read dozens of proposals per solicitation. They spot generic language instantly. Each reference writeup should be tailored to show relevance to the specific contract you’re bidding on. The scope description for the same reference will read differently in a cybersecurity proposal than in a general IT support proposal — emphasize whatever matches.

Listing irrelevant references. A $500K janitorial contract doesn’t strengthen your bid for a $5M cybersecurity requirement, even if the CPARS rating is Exceptional. Evaluators care about relevance more than prestige or dollar volume. Pick references that match the solicitation’s scope and complexity.

Unreachable points of contact. Call every POC before you submit. If their number is disconnected or their email bounces, replace them. An unverifiable reference can be rated worse than no reference at all.

Ignoring adverse past performance. If you have a Marginal or Unsatisfactory CPARS rating, evaluators will see it whether you mention it or not. The FAR gives you the right to explain problems encountered and corrective actions taken. Address it head-on. Explain what happened, what you fixed, and what your subsequent performance looks like. Hiding it tells evaluators you’re either unaware or hoping they won’t notice. They will.

Submitting fewer references than requested. If Section L asks for five references and you submit three, you’ve given the evaluator a reason to score you lower than someone who submitted five detailed references. If you don’t have five federal contracts, use commercial, state/local, or subcontract experience to fill the gaps.

Free help with your Volume II

APEX Accelerators. Your local APEX Accelerator (formerly PTAC) will review your past performance volume, help you select the strongest references for a specific solicitation, and coach you on framing scope descriptions. The service is free.

SBA resources. The SBA’s Contracting Classroom covers proposal writing, including past performance sections. Your local Small Business Development Center can also help.

Your past performance volume is the one part of the proposal where the evidence speaks for itself. A strong technical approach tells evaluators what you plan to do. Past performance tells them you’ve already done it. Start building your reference database today — even if your first proposal is months away. When the deadline hits, you’ll be pulling from a spreadsheet instead of digging through old emails at midnight.

If you haven’t built your capability statement yet, do that first — it’s the document you’ll send when approaching primes for subcontracting opportunities, which is the fastest way to start building the performance record this template is designed to capture.