Building Federal Past Performance From Zero

What federal past performance actually is

In federal procurement, past performance is the evaluator's best predictor of future contractor behavior. Past performance encompasses:

• Prior federal prime contracts and their CPARS ratings.
• Prior federal subcontracts with reference letters from the prime and customer.
• Prior grants and cooperative agreements.
• Commercial past performance, especially for commercial-item procurements.
• Technical signal (Kaggle, GitHub, peer-reviewed publications) supporting capability claims.

Evaluators look at three attributes:

1. Relevance. How similar is the prior work to the proposed effort?
2. Recency. How recent is the work (typically within 3-5 years)?
3. Quality. Was the work delivered on time, on budget, and to customer satisfaction?

All three matter. A highly relevant but 10-year-old engagement is less valuable than a 1-year-old engagement in a related domain. A similar-dollar and similar-scope engagement carries more weight than a much larger or smaller one.

CPARS: how it works

The Contractor Performance Assessment Reporting System (CPARS) is the federal government's central database of contractor performance ratings. Key mechanics:

• CPARS ratings are required on most federal contracts above $1M (simplified threshold is $250K for services).
• The contracting officer completes a CPARS report annually during performance and at contract close.
• Ratings use five levels across five to eight categories: Exceptional, Very Good, Satisfactory, Marginal, Unsatisfactory.
• Categories include Quality, Schedule, Cost Control, Management, Small Business Subcontracting, and Regulatory Compliance.
• Contractors may submit a written response (60 days) that becomes part of the record.
• Ratings remain in CPARS for three years and are visible to evaluators on future procurements.

A single Exceptional CPARS rating is worth enormous weight in future evaluations. A single Unsatisfactory or Marginal rating can be disqualifying on related pursuits. The strategic implication: earn Exceptional ratings on every contract by proactive customer communication, not post-hoc rating disputes.

The chicken-and-egg problem

New firms face three standard objections from evaluators:

1. "No corporate past performance."
2. "The team has relevant experience elsewhere, but not under this firm."
3. "The firm has never executed a contract of this size before."

All three are surmountable. The standard approach:

• Combine key personnel past performance (under W-2 or contract at prior employers) with corporate past performance (even limited).
• Use subcontractor past performance where the firm teams on the proposal.
• Present technical signal (Kaggle rankings, GitHub, peer-reviewed work) as supplemental evidence.
• Acknowledge the firm is newer and rely on specific task alignment to demonstrate capability.

Past performance sources for new firms

1. Key personnel experience

Most federal solicitations allow reference to key personnel's experience at prior employers. A founder who ran a machine learning program at a prior company can describe that program in a past performance narrative tied to themselves, not to the new firm. This is legitimate and effective. Keep it specific: customer, scope, outcome, dates, reference contact.

2. Subcontracting to primes

Teaming as a subcontractor on an established prime's contract is the fastest way to generate CPARS-eligible federal past performance under the new firm's name. Steps:

1. Identify primes in your capability area with active contracts.
2. Reach out with a capabilities statement and specific technical fit.
3. Sign a teaming agreement.
4. Deliver a discrete scope within a prime's task order.
5. Collect a reference letter and CPARS mention from the prime.

Prime relationships take 3-9 months to develop. Start early.

3. SBIR Phase I

A first SBIR Phase I award becomes the firm's first direct federal past performance reference. Even a $150K Phase I completed on schedule with a positive final report generates a viable narrative. The Phase I contract itself becomes a reference on future proposals.

4. Commercial past performance

Prior commercial delivery by the firm — even pre-federal-registration — counts on most solicitations. Document customer, scope, outcome, and reference. Commercial past performance is particularly valuable for commercial-item (FAR Part 12) procurements.

5. Grants and cooperative agreements

NSF, NIH, DOE, and other agencies issue grants and cooperative agreements that generate past performance records. These count on subsequent federal proposals.

6. Kaggle and technical signal

Kaggle competitions, GitHub repositories, published notebooks, peer-reviewed publications, and open-source contributions do not substitute for contract-based past performance, but they establish technical capability at a level evaluators respect. For a solo founder with a Kaggle Top 200 ranking, that signal communicates genuine machine learning expertise more credibly than a typical resume line. See our past performance page for examples.

7. Open-source contributions to federally relevant projects

Contributions to projects like Apache Airflow, MLflow, PyTorch, or other federal-adjacent open-source tools can be cited. Include commit counts, merged PRs, and specific features contributed.

8. Pilots and paid proofs-of-concept

A paid proof-of-concept with a federal program office — even a small one under $50K — counts as past performance. Document it formally.

How to write a past performance narrative

A strong past performance narrative follows a consistent structure. Typical length: 1-2 pages. Structure:

1. Customer name and contracting office. Full legal name, not an acronym.
2. Contract or reference number. Federal contract number if available; otherwise an internal reference.
3. Period of performance. Start and end dates.
4. Total dollar value. Both the contract value and any optional quantities exercised.
5. Role. Prime or subcontractor, with percentage of work.
6. Technical scope. Two to four paragraphs describing what the firm did. Use the same technical language the new solicitation uses.
7. Outcomes. Measurable results: delivered on time, on budget, capability enabled, CPARS rating if available.
8. Reference contact. Name, title, phone, email of someone who can verify the engagement.

Two narrative pitfalls to avoid: generic scope descriptions that could apply to any engagement, and missing reference contact information. Both signal to evaluators that the past performance is weak.

Relevance mapping

On every proposal, map each past performance narrative to the PWS (Performance Work Statement) of the new solicitation. Evaluators look for explicit alignment. A relevance map typically takes the form of a table:

The relevance map often appears in the proposal explicitly. Evaluators appreciate it; it does their work for them.

Reference management

Every past performance narrative needs a reference who will answer the phone. Practices:

• Confirm the reference is willing to be contacted before listing them.
• Tell the reference which proposal you are using them on and send the narrative.
• Keep a master reference list with preferred contact method and current employer.
• Update references annually; people change jobs, phones, and emails.
• Thank references after each proposal.

Reference calls are taken seriously by evaluators. A reference who cannot confirm basic facts about the engagement damages credibility badly.

Past performance traps

• Claiming credit for work the firm did not do. Claiming a team member's prior employer's contract as the firm's past performance is a misrepresentation that can result in debarment.
• Vague technical scope. "Provided data analytics services" does not communicate anything. Use specific technical language.
• Missing CPARS ratings. If CPARS ratings exist, include them. Evaluators will look them up anyway.
• Old work weighted heavily. A 7-year-old engagement as the primary past performance signals the firm has not worked recently.
• Reference contact not answering. A reference who cannot be reached is worse than no reference.
• Size mismatch. Claiming a $5M delivery capability based on a single $200K engagement does not land.

The 12-month past performance roadmap

A realistic first-year plan for a new federal AI small business:

1. Month 1-2: Inventory existing technical work (W-2, open-source, publications). Build capabilities statement.
2. Month 2-3: Publish public technical signal (Kaggle, GitHub, technical blog).
3. Month 3-6: Outreach to primes for subcontract opportunities. Submit first SBIR Phase I proposals.
4. Month 6-9: First SBIR Phase I award or subcontract kickoff. Begin executing.
5. Month 9-12: Complete first engagement. Collect reference. First direct federal past performance reference in hand.
6. Year 2: Stack additional engagements. By year 2 end, typical new firm has 3-5 past performance narratives including 1-2 direct federal.

FAQ

What counts as federal past performance?

A federal contract, grant, or cooperative agreement completed by the offering firm, with CPARS ratings where applicable. Commercial past performance counts on most solicitations. Subcontract performance counts when documented with prime reference letters.

What is CPARS?

Contractor Performance Assessment Reporting System. The federal database of contractor performance ratings. Required on most contracts above $1M (services $250K). Ratings from Exceptional to Unsatisfactory across multiple categories.

Can I use Kaggle or GitHub as past performance?

Not as direct contract past performance, but as supporting technical signal. A Kaggle Top 200 ranking or well-trafficked GitHub repository demonstrates real capability. Include in capability statements and team narratives.

How do I build past performance without prior federal contracts?

Subcontract to primes, win an SBIR Phase I, document commercial work, contribute to open-source, and publish technical work. A first SBIR Phase I is the most efficient path to first direct federal past performance.

How long should a past performance narrative be?

1-2 pages typically. Some solicitations limit to half a page. Always read the solicitation format requirements.

How recent must past performance be?

Most solicitations require work from the last 3-5 years. Older work may be included but is typically weighted less.

Does a subcontract count as past performance?

Yes. Subcontract performance counts when documented with a prime reference letter describing scope, dollar value, and outcomes.

What if my past performance is mostly commercial?

Commercial past performance is acceptable on most solicitations, especially commercial-item (FAR Part 12) procurements. Describe the work with the same rigor as a federal engagement: customer, scope, outcome, reference.

Related resources

• SBIR-Ready Checklist
• SBIR Phase I Guide
• SAM.gov Registration Guide
• 8(a) Certification Guide
• Precision Federal Past Performance