Past Performance in Government Contracting: How to Document and Leverage It

How Agencies Evaluate Past Performance

Federal Acquisition Regulation (FAR) Part 15 governs competitive negotiated procurements. Past performance is a required evaluation factor for most contracts above $35,000 and is frequently weighted at 30 to 40 percent of the total evaluation score in best-value competitions. That makes it one of the most heavily weighted factors in any competitive bid — often more influential than your technical approach.

Evaluators are looking for four things:

• Relevant scope — Does the work you've done match what they're buying? A $2M IT services contract is more relevant to a $3M IT RFP than a $20M construction contract, even though the dollar value is smaller.
• Comparable dollar value — Agencies want evidence you can manage a contract of similar size. A history of small task orders doesn't automatically qualify you for a large enterprise award.
• Recency — Most solicitations specify a lookback window of three to five years. Work completed six or seven years ago is typically excluded.
• Quality ratings — Performance ratings from CPARS, references, and prior agency feedback are the primary signal. A history of Satisfactory or better ratings is the baseline. Exceptional and Very Good ratings actively strengthen your score.

The agency evaluation sequence is predictable: they check CPARS first, then request written references, then may call references directly. That order matters — CPARS is the authoritative source, and anything you claim in a narrative will be compared against what's on record.

What Is CPARS?

The Contractor Performance Assessment Reporting System is the federal government's official past performance database. After a contract is completed — or at interim milestones on multi-year contracts — the Contracting Officer's Representative (COR) rates you across five dimensions:

• Technical — Quality of deliverables and whether you met the performance work statement
• Schedule — On-time performance against milestones and deadlines
• Cost Control — Staying within budget and managing cost growth on cost-type contracts
• Management — Communication, key personnel, subcontractor oversight, and responsiveness to issues
• Regulatory Compliance — Applicable on contracts with significant regulatory obligations (environmental, labor, export control)

The rating scale runs from Exceptional (E) and Very Good (VG) at the top, through Satisfactory (S) in the middle, down to Marginal (M) and Unsatisfactory (U). An Exceptional or Very Good rating is a genuine differentiator. Satisfactory is the floor — it's passing, not competitive.

You have 14 days to review and respond to a CPARS rating before it becomes final. Always exercise this right. If a rating is inaccurate or missing important context, your written response becomes part of the permanent record and source selection officials will see both the rating and your rebuttal. CPARS records are available across the entire federal government, meaning a strong rating with one agency helps you at every other agency.

How to Get Good CPARS Ratings

The foundation is straightforward: do the work well, on time, and within budget. But the agencies that consistently earn Exceptional ratings do a few things beyond that.

• Communicate proactively. Never let your COR be surprised by a problem. If a deliverable is at risk, surface it early and come with a mitigation plan. Agencies rate management separately from technical — a contractor who manages problems professionally can earn a Very Good even when execution has hiccups.
• Deliver early or on time, every time. "On-time" is the minimum expectation, not a differentiator. Delivering early, even on smaller milestones, signals execution discipline that evaluators notice.
• Build your paper trail throughout performance. Document every deliverable, every acceptance, every COR approval in writing. When your CPARS rating is issued, you want a complete record to support your review.
• Request interim ratings on long contracts. Multi-year contracts often produce only one CPARS rating at the end. If you're 18 months into a 3-year contract and performance has been strong, request an interim assessment. It gets into the record sooner and helps you on bids you submit while the contract is still active.
• Respond formally to any Marginal or Unsatisfactory rating. A single poor rating doesn't automatically disqualify you, but leaving it unrebutted makes it appear accepted. Source selection officials see your rebuttal — use it.

How to Write Strong Past Performance Narratives

When agencies request past performance narratives in a proposal, they expect a consistent structure. The formula that works across nearly every federal proposal is: Project + Period + Scope + Your Role + Outcome + Metric.

A well-written past performance citation looks like this:

• Client: [Agency name] — [Contract number if public]
• Period of Performance: [Start date] – [End date]
• Contract Value: $X (base + options if applicable)
• Scope: 2-3 sentences describing the deliverables, technical environment, and scale of the engagement
• Your Role: Prime contractor or subcontractor; which specific workstreams your firm owned
• Outcome: Measurable results — delivery dates, cost variance, CPARS rating, mission impact metrics

The outcome section is where most contractors leave points on the table. "We delivered the system on time" tells an evaluator nothing useful. "We delivered Phase 1 three weeks ahead of schedule and $120K under the contract ceiling, earning an Exceptional CPARS rating for Technical and Schedule" tells them everything. If you don't have exact numbers, get them before writing the proposal.

The most common mistakes in past performance narratives:

• Dollar values missing or intentionally vague ("multi-million dollar contract") — always specify exact amounts
• No performance metrics — describe outcomes in concrete, measurable terms
• Claiming subcontractor work as if your firm delivered it — clearly distinguish your role from work performed by teammates or subs
• Choosing impressive-sounding but irrelevant examples — evaluators will mark non-relevant past performance down, regardless of the dollar size

Building Past Performance When You're New

The classic chicken-and-egg problem: agencies want past performance you can only build by winning contracts. There are legitimate ways to break out of it.

Subcontracting under a prime

Find prime contractors in your NAICS space on USASpending.gov or through your local PTAC/APEX accelerator. Primes with set-aside compliance obligations need qualified subcontractors — your small business certifications (WOSB, SDVOSB, HUBZone) are genuine leverage. Subcontracting experience counts as past performance when you document it properly: client name, period, value, scope of your specific work, and outcome. Document it the same way you would a prime contract.

State and local government work

Municipal and state contracts count as past performance in federal proposals. Evaluators accept analogous experience — a $500K cybersecurity project for a city government is relevant to a federal IT solicitation. The key is framing: use the same documentation structure, specify the client, period, dollar value, scope, and measurable outcomes.

Commercial work as analogous experience

Not every agency weights commercial experience equally, but civilian agencies often accept it, especially for IT and professional services. Frame commercial work in government-adjacent language when you can — highlight compliance requirements, regulated-industry clients (healthcare, finance, utilities), or work that approximates federal performance standards.

SBIR/STTR awards

Small Business Innovation Research contracts are federal contracts. Even a Phase I SBIR ($150K–$300K) is documentable past performance with a federal agency. For science and technology-focused agencies — NIH, NSF, DOE, DARPA — an SBIR Phase II history is a strong signal of technical credibility.

Teaming arrangements

Team with an established prime as a key subcontractor on your first bid. Negotiate for a meaningful, defined scope — not just name-on-the-team-sheet status — so you can document real past performance from the engagement. SBA and DoD Mentor-Protégé programs provide formal teaming structures with established primes, specifically designed to help small businesses build their record.

References vs. CPARS

If you have no CPARS ratings, proposal submissions typically allow "other references" — project managers, CORs, and program managers who can speak to your work. These carry less weight than CPARS but are better than a blank past performance section.

Prepare your references before you need them. Brief each reference on the opportunity you're pursuing, send them a short summary of the work you want them to highlight, and confirm they can speak to the specific scope and outcomes you're citing. An unprepared reference who can't remember the details of a project from two years ago is worse than no reference.

For capability statements and capability briefings, reference letters — brief, signed letters on agency or client letterhead — are worth collecting proactively after each project closes. They're faster to produce than formal CPARS entries and can be used in pre-solicitation relationship-building before you ever write a proposal.

Once you have past performance documented, your capability statement is your next tool — see our capability statement guide. For structuring past performance citations within a full proposal, see our RFP response template. Set-aside certifications can help you break into subcontracting opportunities and build your record faster — see our set-aside programs guide.