Past Performance is Your Most Underused Growth Asset

Ask most GovCons where their past performance lives and you'll get one of two answers: a shared drive folder with a collection of write-ups in various formats, quality levels, and states of relevance. Or a proposal library that gets raided every time an RFP hits, producing sections that are part current, part outdated, and entirely reactive.

Past performance is typically treated as a documentation requirement. Something to compile when it's needed. A box to check in the proposal.

That framing is costing firms wins they should be collecting.

Past performance isn't a section of your proposal. It's the accumulated proof that your firm does what it says it does — delivered in a format that evaluators are trained to weigh heavily, because it's the closest thing to a prediction of future performance the government has.

In lowest-price, technically-acceptable (LPTA) evaluations, a solid past performance record is often the difference between being in the competitive range and being out of it. In best value evaluations, it's the evidence that separates "we believe you can do this" from "we know you've done this." It's not just a section. It's the credibility layer that makes everything else in your proposal believable.

Firms that treat it as a documentation requirement are always building from whatever they have. Firms that treat it as a strategic asset are building deliberately — toward the specific proof they'll need for the specific work they want to win next.

Most past performance write-ups have the same four problems.

They're written from the contractor's perspective, not the evaluator's. They describe what the firm did — scope, timeline, deliverables — without connecting that work to the outcomes the customer cared about. "Provided technical support to the program office" is a description of activity. "Reduced the backlog of unresolved technical issues by 40% within the first 90 days of performance, enabling the program office to meet its Congressional reporting deadline" is evidence.

They're too old. A past performance reference from eight years ago on a completed contract tells evaluators very little about your current capabilities, current team, and current quality. Recency matters. Firms that don't have recent, relevant references on priority pursuit areas have a positioning gap — and it's one that needs to be addressed well before the RFP.

They're generic. The same write-up gets used across 10 different proposals with the agency name swapped out. Evaluators aren't comparing you to a generic standard — they're comparing you to the specific requirements in front of them. A write-up that maps directly to the evaluation criteria for this procurement scores better than a technically stronger write-up that doesn't.

They don't surface the metrics. Every project has measurable outcomes. Schedule performance. Cost efficiency. Quality ratings. CPARS scores. Customer satisfaction data. If those numbers exist and aren't in the write-up, you're leaving the most persuasive part of your story on the table.

Here's the discipline shift that changes everything: past performance management is a capture function, not a proposal function.

By the time an RFP drops, it's too late to build the past performance story you need. You can document what you have. You can't manufacture relevance or recency that doesn't exist.

The firms that consistently have strong past performance sections started working on them during performance — when the work was happening, the outcomes were fresh, and the customer was available to validate what went well. That means someone with a BD or capture mindset is staying connected to active contracts, documenting outcomes in real time, and updating write-ups when performance milestones are reached — not six months after the contract ends.

It also means someone is asking the question that most firms never ask during a pursuit: what past performance will we need to win this, and do we have it? If the answer is no — if the work you're pursuing is meaningfully different from the work you've done — that's a strategic gap. The choices are to build that evidence through teaming, to invest in a performance period that creates the reference, or to make an honest go/no-go decision. What it shouldn't be is a surprise at proposal time.

Past performance isn't just documentation. It's relationships.

A written reference on a past contract is one data point. A reference who will take a call from a contracting officer and speak specifically about your performance, your team, and what it was like to work with your firm — that's a differentiator that doesn't show up anywhere in the write-up.

Most firms have no idea whether their past performance references are actually advocates. They list the COR's contact information and assume that an "Exceptional" CPARS rating means the conversation will go well. Sometimes it will. Sometimes the contracting officer has moved on, the relationship was transactional, or the customer had reservations they never formally documented.

The firms with the strongest past performance position maintain active relationships with their reference contacts — not just during the performance period, but after. They know who will pick up the phone and what they'll say. They know which references map best to which pursuit types. They make deliberate decisions about which references to list based on the specific evaluation they're facing, not just proximity and recency.

That's not manipulation. It's knowing your own evidence.

A past performance library that functions as a real growth asset has a few characteristics that distinguish it from a shared drive of old write-ups.

It's current. Write-ups are updated when contracts reach milestones, when CPARS scores are received, and when contracts close — not when a proposal is due in three weeks.

It's organized by relevance dimensions — agency type, contract vehicle, work category, dollar value, contract type — so a proposal team can identify the strongest references for a specific pursuit in minutes, not hours.

It contains the metrics. Every write-up has the numbers that matter: schedule performance, cost performance, quality indicators, customer satisfaction data. Where numbers don't exist yet, there's a plan for how they'll be obtained.

It's connected to reference relationships. The library notes not just who the reference contact is, but the current status of that relationship and who on the BD team is maintaining it.

None of this is complex. All of it requires discipline. And the firms that build it are competing with evidence while everyone else is competing with assertions.

Krystn Macomber, CP APMP Fellow, LEED AP

Founder + CEO | Summit Strategy