Past Performance Federal: Your Complete Guide to Success

Why Past Performance Can Win or Lose a Federal Contract Before Price Is Even Read

A small 8(a) IT services firm submitted a technically strong proposal for a $4.2M Army network support task order. Their price was competitive. Their technical approach was detailed. They lost anyway. The source selection authority (SSA) documented the reason in the debriefing: past performance rated "Marginal" because the firm's three CPARS references were for contracts under $200K on a requirement that specified "relevant experience at or above $1M." The firm had done the work. They just couldn't prove it at the right scale.

That scenario plays out across hundreds of federal competitions every year. Past performance is not a checkbox. Under FAR 15.305(a)(2), contracting officers must evaluate the quality and relevance of recent and relevant past performance as a separate source selection factor. In many agency-specific acquisition policies, past performance carries equal or greater weight than technical approach. Understanding exactly how that evaluation works, and how to build a record that survives scrutiny, is one of the highest-return investments a small business federal contractor can make.

What the FAR Actually Requires (and What Agencies Add On Top)

FAR 15.305(a)(2) establishes the baseline: past performance must be evaluated in negotiated competitive acquisitions above the simplified acquisition threshold (currently $250,000). The regulation requires evaluators to assess the currency and relevance of the information, the source of the information, and the context of the performance. FAR 42.1503 governs the Contract Performance Assessment Reporting System (CPARS), requiring agencies to complete evaluations within 120 days of the end of each contract year and within 120 days of contract completion.

Beyond the FAR baseline, agencies layer on their own requirements. DoD source selection procedures often follow the DoD Source Selection Procedures guide, which defines "relevant" as similar in scope, magnitude, and complexity. NASA and DHS frequently publish evaluation criteria that assign numerical scores to past performance factors. GSA Multiple Award Schedule (MAS) orders may rely on GSA Advantage ratings or agency-specific reference checks. Read the solicitation's Section M evaluation criteria carefully. "Relevant" is almost always defined, and that definition determines which contracts you should cite.

The Five Dimensions Evaluators Actually Score

CPARS uses a standardized rating scale: Exceptional, Very Good, Satisfactory, Marginal, Unsatisfactory. Evaluators assess performance across five areas. Understanding each one helps you manage contracts in real time, not just at proposal time.

Technical Quality

This covers defect rates, rework, deliverable acceptance, and whether you met or exceeded the statement of work (SOW) requirements. A CPARS narrative that says "contractor delivered all 47 data migration modules on schedule with zero critical defects" is worth far more than a generic "Exceptional" rating with no supporting detail. When you see a draft CPARS evaluation that is thin on specifics, that is your window to provide the contracting officer's representative (COR) with a performance summary they can incorporate.

Schedule

On-time delivery of contract line item numbers (CLINs), milestones, and reports. Evaluators look for patterns. One late deliverable explained by a government-caused delay is recoverable. A pattern of late submittals is not. Keep a running log of every deliverable, its required date, actual submission date, and any government-caused delays documented via email or contract modification. That log is your defense if a COR misremembers the timeline during CPARS evaluation.

Cost Control

For cost-reimbursement and time-and-materials contracts, evaluators examine whether you stayed within obligated amounts, managed burn rate appropriately, and flagged funding issues early. For firm-fixed-price (FFP) contracts, cost control is assessed indirectly through change order management and whether you sought excessive modifications. Demonstrating that you completed work within original funding, or achieved cost savings through process improvements, is a concrete differentiator.

Business Relations

This dimension covers responsiveness, communication quality, and professionalism. A COR who had to chase you for status reports will reflect that in the narrative. A COR who received proactive weekly updates and clear escalation paths will say so. This is the dimension most directly influenced by relationship management, and it is the one small businesses most often neglect.

Management

Key personnel stability, subcontractor oversight, and problem resolution. If you replaced a key person mid-contract, document the transition plan and continuity measures. If a subcontractor underperformed, document how you identified and corrected the issue. Evaluators want evidence that your management processes are repeatable, not that you got lucky on one contract.

Building a Past Performance Library Before the Next RFP Drops

The contractors who write the strongest past performance volumes are not the ones who scramble at proposal time. They are the ones who treat every active contract as a documentation project running in parallel with the actual work.

What to Capture During Performance

• Monthly performance summaries with quantitative metrics tied to contract requirements (deliverables completed, SLA compliance percentages, help desk ticket resolution times, etc.)
• Customer correspondence including emails from CORs and program managers acknowledging good work, approving deliverables, or thanking your team for problem resolution
• Formal award letters, contractor of the quarter designations, or any written recognition from the contracting officer (CO) or program office
• Modification history showing scope growth the government requested, which signals the agency trusted you with more work
• Corrective action records documenting any issue that arose, the root cause, and the fix, because showing you resolved problems professionally is often more persuasive than claiming you had none
• CPARS draft review notes and your formal contractor comments, which become part of the permanent record

The CPARS Review Process Is Not Optional

When a draft CPARS evaluation is released, you have 14 calendar days to review and comment. Most small businesses either miss this window or submit a one-line acknowledgment. That is a significant missed opportunity. If a rating is lower than your performance warrants, submit a detailed, factual rebuttal with supporting documentation. Reference specific deliverables, dates, and contract requirements. Avoid emotional language. The goal is to give the assessing official (AO) enough documented evidence to upgrade the rating or at minimum add context that future evaluators will see. A contractor comment that says "Contractor notes that all 12 quarterly reports were submitted on or before required dates per CDRL A001; see attached delivery confirmation log" is far more useful than "We respectfully disagree with this rating."

Selecting and Presenting Past Performance in a Proposal

Most RFPs ask for three to five past performance references. Choosing the right ones requires matching three variables: recency (typically within three to five years), relevance (scope, complexity, and dollar value similar to the requirement), and rating quality (Exceptional or Very Good in CPARS, or equivalent documented evidence for non-CPARS work).

Use a relevance matrix. Create a simple table that maps each cited contract to the specific evaluation criteria in Section M. If the RFP says evaluators will assess "experience supporting enterprise IT infrastructure for federal civilian agencies," your matrix should show which of your cited contracts involved federal civilian agency customers, what the infrastructure scope was, and the contract value. Do not make evaluators infer relevance. State it explicitly.

For each reference, structure the narrative to include: contract number, agency, period of performance, dollar value, scope summary, specific performance highlights with metrics, and any CPARS ratings. If a CPARS rating was Satisfactory on an otherwise strong contract, address it directly. A brief explanation of context, such as a contract that was descoped mid-performance due to a continuing resolution, is better than hoping evaluators overlook the rating.

When You Do Not Have Directly Relevant Past Performance

New entrants and companies pursuing contracts significantly larger than their current portfolio face a structural challenge. Several legitimate strategies exist. First, consider teaming arrangements where a prime or subcontractor with relevant past performance is included specifically to address this gap. FAR 15.305(a)(2)(iii) allows evaluators to consider the past performance of subcontractors and teaming partners when that work is relevant to the requirement. Second, if you genuinely have no relevant past performance, FAR requires evaluators to treat that as a neutral rating, not a negative one. A well-written proposal that acknowledges this and explains your management approach for mitigating risk can still be competitive. Third, pursue smaller agency-specific contracts in your target domain now, specifically to build the CPARS record you will need for larger competitions in 18 to 24 months.

A Practical Starting Point

Pull your active contracts today. For each one, identify the COR, confirm you know when the next CPARS evaluation is due, and create a shared folder for performance documentation. If you have contracts that completed in the last three years with no CPARS on file, contact the contracting office. Late evaluations can still be entered. A documented "Exceptional" from two years ago is worth the 30-minute phone call it takes to get it recorded.

Tools like Winrove (from IT Custom Solution LLC, plans starting at $49/mo) can help you identify which active opportunities weight past performance most heavily and match your existing CPARS record to relevant solicitations before you invest proposal resources. The underlying principle, though, is the same regardless of what tools you use: past performance is built on active contracts, not assembled during proposal sprints. Start the documentation process now, and the proposal volume writes itself later.