Turn scattered project history into a past-performance volume an evaluator can score in two minutes, so the section that decides most awards stops being the one you scramble.
Why 8(a) firms need a past-performance package
You won 8(a) status to get a seat at the table. Now you are at the table, and the question that decides most of these awards is not whether you are certified. It is whether you can show, in writing, that you have done this work before and done it well. Past performance is the part of a proposal that small firms most often hand in thin, late, or scattered, because it is not one form you fill out. It is a package you assemble: a set of references, contract facts, performance ratings, and short narratives that a contracting officer can read in two minutes and believe. The firms that win consistently are not always the ones with the longest history. They are the ones who present the history they have in a way the evaluator can actually use.
Here is where it goes wrong for most 8(a) firms. The proposal is due, somebody opens last year’s proposal, copies the past-performance section, and swaps a few project names. The reference phone numbers are stale. The contract values do not match what is in the system. The narrative talks about effort instead of results. The relevance to the current requirement is left for the evaluator to figure out, and evaluators do not figure it out, they score what is in front of them. Under FAR 15.305, past performance is one indicator of your ability to perform, and the rule directs the government to weigh the currency and relevance of what you submit. A package that is current and clearly relevant scores. A package that is neither gets the benefit of no doubt.
A past-performance package template fixes the scramble. Not a fancy one, just a real one: one place where every reference you might cite has a complete, current, reusable record, and a repeatable structure for turning that record into the section a solicitation asks for. When the reference facts live in a maintained package instead of a memory, building the past-performance volume becomes assembly instead of archaeology. You can see at a glance which references are current, which contract values are confirmed, which CPARS ratings you have in hand, and which reference contacts you have called in the last six months. And when a solicitation drops with a five-day past-performance turnaround, you are pulling from a maintained library instead of starting from a blank page.
The structure in this template comes straight from how the government actually evaluates past performance. CPARS, the Contractor Performance Assessment Reporting System at cpars.gov, is the official source the government uses for past-performance information under FAR 42.1501. FAR 15.305(a)(2) makes past performance an evaluation factor and tells evaluators to consider currency, relevance, source, and trend. FAR 15.305(a)(2)(iii) lets the government count the experience of predecessor entities, key personnel, and major subcontractors when it is relevant, which matters enormously for a young 8(a) firm. And for set-aside work, 13 CFR 125.11 lets a small business use the past performance it earned as a member of a joint venture and as a first-tier subcontractor. The specific thresholds, portals, and rating mechanics in this space get revisited over time, so treat this template as the structure and confirm each current requirement against the live rule at acquisition.gov and ecfr.gov for your pursuit.
Who this package is for
- 8(a) firm owners and presidents who own the win and need the past-performance volume to land complete every time, not just when there is time to build it
- Capture and proposal managers who assemble the past-performance volume against a solicitation’s relevance criteria on a deadline
- Business development leads building a maintained reference library so the next pursuit starts from a library, not a blank page
- Contracts and compliance managers tracking CPARS ratings, contract numbers, and values so the facts in the package match the facts in the system
- Subcontract and teaming leads who need to document first-tier subcontract and joint-venture performance the firm is entitled to claim
- Primes, GCs, and prequalification teams vetting an 8(a) sub’s track record before they put it on a federal pursuit
The 16-field 8(a) past-performance package
The package organizes 16 fields every 8(a) firm should capture for each past-performance reference and for the volume as a whole:
- Project and contract identification. For each reference, capture the project title, the awarding agency or prime, the contract or order number, and the contract type (firm-fixed-price, cost-reimbursement, IDIQ task order). These are the anchor facts an evaluator cross-checks, and the contract number is what ties your narrative to the record in CPARS at cpars.gov. Get them exactly right, because a contract number that does not match the system reads as carelessness on the one volume where carelessness is fatal.
- Period of performance and recency flag. Record the start and completion dates for each reference, and flag how recent it is. Recency matters because the government weighs the currency of past-performance information under FAR 15.305(a)(2)(i), and CPARS evaluations are generally used within three years of completion, with six years for construction and architect-engineer contracts under FAR 42.1503(g). Confirm the current recency window for your solicitation, and lead with your most recent and most relevant references rather than your oldest war story.
- Contract value and scope summary. Capture the total contract value and a one-paragraph scope summary for each reference. The value signals whether the reference is comparable in size to the current requirement, and the scope summary is what an evaluator reads to judge whether the work is similar. Keep the value confirmed against your accounting and the scope summary factual, because inflated values and vague scopes are exactly what reviewers discount.
- Relevance mapping to the current requirement. For each reference, write one or two sentences that explicitly map the work to the requirement you are pursuing: same type of work, same agency, same complexity, same place. Relevance is the single most important factor in how the government scores past performance under FAR 15.305(a)(2)(i), and it is the one most firms leave for the evaluator to infer. Do not make them infer it. State the connection in plain terms so the relevance is on the page, not in your head.
- Reference point-of-contact and currency check. Capture the name, title, organization, phone, and email of a contracting officer, COR, or project owner who will speak to your performance, and record the date you last confirmed the contact is current. A reference who has moved on, or a phone number that rings to nobody, turns a strong reference into a dead end. Re-verify each contact at least twice a year, because the fastest way to lose past-performance credit is a reference the evaluator cannot reach.
- CPARS rating and evidence. Where the reference is a federal contract above the reporting threshold, capture the CPARS rating and the dimension scores you have. CPARS is the government’s official source for past-performance information under FAR 42.1501, and the evaluation rates dimensions including quality, schedule, cost control, management, and small-business subcontracting on a scale running from exceptional through unsatisfactory. Keep your ratings on file and reconcile them with what you submit, because the evaluator can pull the source and a mismatch undermines the whole volume.
- Past-performance questionnaire (PPQ) status. Many solicitations ask references to complete a past-performance questionnaire directly, on the solicitation’s own form. For each reference, track whether a PPQ was requested, sent, and returned, and by when. The PPQ is often the long pole in the tent because it depends on a busy government official, so request it early and follow up. A returned PPQ in hand is worth more than a promise that one is coming.
- Self-performed work and the role you played. Document what your firm actually performed on each reference, prime or subcontractor, and the percentage or scope you self-performed. Evaluators care about the work you did, not the work your team did around you, and for set-aside work the rules limit what experience you can claim. Under 13 CFR 125.11, a small business cannot claim as its own the experience for work performed exclusively by other partners in a joint venture. Be precise about your role so every claim is one you can defend.
- Joint-venture and subcontractor past performance you may claim. For young firms, this field is where awards are won. FAR 15.305(a)(2)(iii) allows the government to consider the past performance of predecessor companies, key personnel with relevant experience, and subcontractors performing major or critical aspects of the requirement. For set-aside contracts, 13 CFR 125.11 lets a small business use the experience it earned as a member of a joint venture and its rating of past performance as a first-tier subcontractor. Capture those references with the same rigor, and note the basis on which you are entitled to claim each one.
- Key-personnel relevant experience. Capture the relevant past-performance and project experience of the key personnel you are proposing, tied to named individuals and the projects they led. FAR 15.305(a)(2)(iii) expressly allows the government to consider key personnel who have relevant experience, which lets a firm with a short corporate history field a team with a long one. Keep résumés and project histories current for proposed key staff so this evidence is ready when a solicitation values it.
- Problems encountered and corrective action. For references where something went wrong, capture a short, honest account of the problem and the corrective action you took. FAR 15.305(a)(2)(ii) gives offerors the opportunity to provide information on problems encountered and the corrective actions taken, and a candid, well-handled problem narrative often reads better than a suspiciously perfect record. Document the recovery, not just the issue, because how you fix problems is itself past performance.
- Relevance and currency self-score. For each reference, score its relevance and currency to the current pursuit on a simple scale so you can rank which references to lead with. The government weighs both relevance and currency under FAR 15.305(a)(2)(i), so your own ranking should mirror theirs. Lead the volume with your highest-scoring references and use the marginal ones only if the solicitation asks for more than your strong references can fill.
- Narrative summary in results language. Write a tight performance narrative for each lead reference that describes outcomes, on time, on budget, what you delivered, not activity. Evaluators score results, and a narrative full of effort verbs without a single outcome reads as filler. Anchor each narrative in something measurable: the schedule you held, the deliverable you completed, the rating you earned, the problem you prevented.
- Volume formatting and solicitation compliance. Capture the solicitation’s specific past-performance instructions: page limits, the number of references requested, the recency and relevance definitions the solicitation uses, and the exact format. Past-performance volumes get thrown out for blowing a page limit or ignoring the prescribed format as readily as for thin content. Build a compliance checklist from Sections L and M of each solicitation and check the volume against it before submission.
- SAM.gov registration and entity facts. Confirm the firm’s active registration in SAM.gov, its Unique Entity ID, and that the entity facts in the proposal match the entity facts in the system. Federal contracting requires an active SAM.gov registration, and an evaluator who finds a mismatch between your proposal and your registration has a reason to doubt the rest. Track the SAM.gov expiration date as a hard deadline so a lapsed registration never sinks an otherwise strong bid.
- Reference library maintenance log. The front of the package is a maintenance log that lists every reference, its relevance and currency score, the last date you verified the contact, the CPARS or PPQ status, and the owner. This is the field people actually use, because it turns a scattered set of project memories into a living library you can pull from on a deadline. Review it on a set cadence, retire stale references, and add each new completed contract the month it closes so the library is always ahead of the next solicitation.
How to run the package
Build the library once, then maintain it on a cadence. Start with Field 16, the maintenance log, and list every contract and order your firm has completed or is performing, plus the joint-venture and first-tier-subcontract work you are entitled to claim under 13 CFR 125.11 and the key-personnel experience FAR 15.305(a)(2)(iii) lets you count. For each one, fill in the identification, dates, value, and scope while the facts are fresh, because reconstructing a contract number or a final value two years later is its own small project.
When a solicitation drops, work the package in two passes. First pass: read Sections L and M, capture the past-performance instructions in Field 14, and use the relevance and currency self-score in Field 12 to rank which references to lead with. Second pass: for each lead reference, confirm the point-of-contact is current in Field 5, pull the CPARS rating or request the PPQ in Fields 6 and 7, and write the results-language narrative in Field 13. Mark every field Done, Open, or Verify. Verify means the item depends on a current rule, threshold, or portal, like the CPARS recency window or the SAM.gov registration status, that you need to confirm against acquisition.gov, cpars.gov, or SAM.gov for this pursuit.
The Excel version turns the package into a live reference library: a row per reference with relevance and currency scores, contact-verification dates, CPARS and PPQ status, and a readiness formula that shows how many of your references are submission-ready, so you know before a solicitation drops whether your library is ahead of the next deadline or behind it.
Stop rebuilding your past-performance volume from a blank page
Stale reference contacts, contract values that do not match the system, narratives full of effort instead of results, and a relevance argument left for the evaluator to infer. The past-performance volume is where small firms lose winnable awards, not because the history is not there, but because it is scattered across old proposals and somebody’s memory when the deadline hits. Contracts Connected gives every reference a maintained home with current contacts, confirmed facts, ratings, and relevance mapping, so the volume becomes assembly instead of archaeology, for your own firm and for the 8(a) subs you team with. The template tells you what to capture. CC keeps it current.
Part of Contracts Connected’s construction compliance software. For educational purposes.
These templates, checklists, and trackers are operator-built starting points designed to help you move faster on the kind of work that usually drowns construction admins in email chains. They are not legal, insurance, accounting, or tax advice. Each project, jurisdiction, and contract has its own quirks. Review the document, refine the language, and consult your attorney, broker, CPA, or compliance officer before relying on it for a live project decision.
Frequently asked questions about the 8 past-performance package template
What is an 8(a) past-performance package?
An 8(a) past-performance package is the organized set of references, contract facts, performance ratings, and narratives a firm submits to show it can perform the work it is bidding. It is built around how the government actually evaluates past performance: FAR 15.305(a)(2) makes past performance an evaluation factor and directs evaluators to weigh currency, relevance, and source, and CPARS at cpars.gov is the official source the government uses for past-performance information under FAR 42.1501. The package collects, for each reference, the contract identification, period of performance, value and scope, relevance to the current requirement, a current point of contact, and a results-focused narrative. The template is the structure; confirm the exact submission requirements against your solicitation’s Sections L and M for each pursuit.
How important is past performance in a federal evaluation?
It is usually one of the decisive factors. FAR 15.305(a)(2) describes past performance as one indicator of an offeror’s ability to perform the contract successfully, and in many best-value source selections it is weighted heavily alongside technical and price. The rule tells evaluators to consider the currency and relevance of the information, its source, the context of the data, and general trends in the contractor’s performance under FAR 15.305(a)(2)(i). A current, clearly relevant reference with a strong CPARS rating moves the needle; a stale or vaguely relevant one does little. Read each solicitation’s Section M to see exactly how that solicitation weights past performance, because the weight varies by acquisition.
What if my 8(a) firm has limited past performance?
You have more to work with than you think, and the rules are written to help you. FAR 15.305(a)(2)(iii) lets the government consider the past performance of predecessor companies, key personnel who have relevant experience, and subcontractors that will perform major or critical aspects of the requirement, when that information is relevant. For set-aside contracts, 13 CFR 125.11 lets a small business use the experience and past performance it earned as a member of a joint venture, and a contracting officer is directed to consider the firm’s rating of past performance as a first-tier subcontractor. There is also a protection in FAR 15.305(a)(2)(iv): an offeror without a record of relevant past performance may not be evaluated favorably or unfavorably on past performance. So document your key personnel, your subcontract work, and any joint-venture experience, and lean on those references where your corporate history is thin.
What is CPARS and how does it relate to my proposal?
CPARS, the Contractor Performance Assessment Reporting System at cpars.gov, is the government’s system of record for past-performance evaluations and the official source for past-performance information under FAR 42.1501. After a federal contract above the reporting threshold is performed, the agency prepares a CPARS evaluation rating dimensions such as quality, schedule, cost control, and management, and you are given an opportunity to comment on it, generally up to fourteen calendar days from notification under FAR 42.1503(d). When you assemble a proposal, the references you cite can be cross-checked against CPARS, so the contract numbers and ratings in your package should match what is in the system. Keep your own copies of your CPARS ratings, and review every evaluation when it posts so you can comment or rebut while the window is open.
How recent does past performance have to be?
It depends on the solicitation, but the government’s general practice gives you a useful default. Under FAR 42.1503(g), agencies use the past-performance information in CPARS that is within three years of the completion of performance, and within six years for construction and architect-engineer contracts. FAR 15.305(a)(2)(i) separately directs evaluators to weigh the currency of the information, which is why a recent reference generally outscores an older one of similar relevance. Each solicitation can define its own recency window, so read Section L for the specific requirement and lead your volume with your most recent, most relevant references. Confirm the current windows against acquisition.gov for your pursuit, because the figures are written into the rule and get revisited over time.
How does this package help a prime or GC vetting an 8(a) sub?
A prime or GC putting an 8(a) firm on a federal pursuit is staking part of its own past performance on that sub. A sub that keeps a maintained past-performance package, with current references, confirmed contract facts, CPARS ratings in hand, and clear relevance mapping, is showing exactly the discipline a prime wants to see before it teams. Asking a prospective sub for its past-performance package is a fair prequalification step, and a sub that can produce an organized library answers it instantly instead of going quiet for a week. That is why this template sits alongside subcontractor prequalification and capability-statement work, not just internal 8(a) proposal prep.