Your Past Performance Library Is Broken — Here's How to Fix It

A broken past performance library costs you wins before you even start writing. This episode breaks down exactly how to build a structured, searchable reference set that holds up under evaluator scrutiny — no scrambling required.

Show Notes

When an RFP lands and the clock starts, most proposal teams don't have a past performance problem — they have a library problem. This episode of RFP.co tackles one of the most overlooked competitive advantages available to small and mid-sized firms: a structured, maintained, and searchable past performance library that's ready before the solicitation hits, not assembled in a panic after it does.

The episode walks through what separates a real past performance library from a folder of old proposals, why the structure of each record directly affects how evaluators perceive risk, and how to build records that hold up when they matter most. Key topics include:

• What a past performance record actually needs: four elements every entry must contain — a plain-language scope description, a concrete measurable outcome, any recognition or option-year signals, and a verified point of contact.
• Why the POC is the most skipped — and most consequential — piece: a reference that goes to voicemail or reaches someone who has moved on is not a neutral outcome, and evaluators notice.
• Maintaining POC relationships like a warm pipeline: a simple check-in every six months keeps you on a contact's radar before the call comes in from an agency.
• Tagging and sorting for speed: organizing records by domain, contract type, agency level, and work category means filtering to your best three references takes minutes, not days — especially useful when response automation tools are pulling from your content library.
• Building for the market, not the trophy shelf: the strongest library reflects the scope and type of work you're actually competing for, not just the engagements you're most proud of.
• The one action to take this week: pick one closed contract, write all four elements, and store it somewhere structured — then repeat the habit every time a contract closes.

For firms pursuing federal RFPs or state and local RFPs, a well-organized past performance library also makes it far easier to evaluate whether a new opportunity is worth pursuing in the first place — because you can quickly see whether your references actually match what an evaluator will be looking for. If you want to go deeper on how evaluation criteria shape which references you should lead with, check out the RFP.co episode How to Read an Evaluation Criteria Section Before You Read Anything Else.

RFP.co

What is RFP.co?

Procurement discovery and proposal automation, from both sides of the table. Finding the right opportunities, qualifying out early and without regret, building a reusable answer library, pricing decisions, and the operational discipline that turns responses from heroics into a repeatable process.

Each episode takes one part of the cycle — a bid/no-bid call, a compliance matrix, a debrief worth requesting — and works it through practically. Written for capture managers, proposal teams and the small companies competing against much larger ones. Five or six minutes an episode.

Topics include bid/no-bid decisions, opportunity discovery and filtering, compliance matrices, reusable answer libraries, pricing and win themes, past performance narratives, debriefs worth requesting, and competing against much larger incumbents.

Produced by RFP.co, procurement discovery and proposal automation. Full details, services and further reading at https://rfp.co