Template and evidence workflow
Past performance library template: make proof reusable and defensible
A practical structure for proposal and capture teams that need to find the right project evidence, assess its relevance, and tailor it without overstating what happened.
Published November 13, 2026
The short answer
A useful past performance library is not a folder of polished case studies. It is a governed set of project records that preserves the underlying evidence, explains what each project proves, and lets a pursuit team rank examples by relevance before reusing any narrative.
What you can use immediately
- A copy-ready 12-field past performance record
- A 100-point relevance score for choosing comparable projects
- An evidence-strength model that separates proof from memory
- A worked example, governance cadence, and final reuse checklist
Why the record matters
Evaluators assess relevance, not the elegance of your filing system
FAR 15.305 directs evaluators to consider the currency and relevance of past performance, the source and context of the information, and performance trends. That creates a practical standard for the bidder: preserve enough context and evidence to show why an example is comparable, then tailor it to the stated evaluation factor.
A previous proposal can help you find language. It should not become the authority for a project fact. Revalidate the claim against the underlying approved record before reuse.
Copy-ready template
Capture these 12 fields for every usable project
Keep the structured record beside the approved narrative and source files. A search result should tell a proposal manager both why a project may fit and what must be checked before it is cited.
| Field | What to record |
|---|---|
| Project identity | Customer, contract or project name, contract number, and vehicle where applicable. |
| Period and status | Start date, end date, current status, and the date the record was last verified. |
| Your role | Prime, subcontractor, partner, or named-personnel experience, with the work actually performed. |
| Scope and scale | Services, locations, users, transactions, assets, or other dimensions that make the work comparable. |
| Delivery conditions | Constraints, integrations, security, accessibility, schedule, and operating environment. |
| Outcomes | Results the evidence can support, including the measurement period and any important conditions. |
| Performance evidence | Approved source documents, references, acceptance records, or performance evaluations. |
| Problems and corrections | Material issues, corrective action, and the verified result when disclosure is appropriate. |
| Permission | Customer-name, confidentiality, teaming, and disclosure limits for the pursuit team. |
| Relevance tags | Buyer type, sector, capability, scope, complexity, geography, contract type, and outcome. |
| Record owner | Person accountable for questions, verification, and approval of updates. |
| Reuse note | What this record proves, what it does not prove, and the situations where it is most relevant. |
Evidence strength
Label how strongly every outcome is supported
- Verified: approved customer, contract, acceptance, performance, or delivery record supports the claim.
- Corroborated: multiple current internal records agree and an accountable owner has approved use.
- Narrative only: the wording exists in an approved asset, but the underlying proof still needs review.
- Unverified: the claim comes from memory, an old proposal, or an unsupported summary; do not reuse it.
Selection method
Score relevance before the kickoff meeting
Use the buyer's words to define what comparable means. Score each candidate project from zero to the maximum weight, document the reason, and shortlist the records with the best supported fit.
| Factor | Weight | Question |
|---|---|---|
| Scope match | 25 | How much of the required work was actually performed? |
| Complexity match | 20 | Were the operating constraints, integrations, risks, and stakeholders comparable? |
| Buyer and sector match | 15 | Is the customer environment similar enough to make the proof meaningful? |
| Delivery model match | 15 | Were your role, contract model, and responsibilities comparable? |
| Outcome strength | 15 | Are relevant results supported by current, permitted evidence? |
| Recency | 10 | Is the work recent enough for the solicitation and still representative? |
A score does not override the solicitation. If the RFP defines recency, similarity, page limits, references, or eligible experience, use those rules as hard gates before ranking.
Illustrative record
Show the proof and its boundary in the same view
This fictional example demonstrates the structure only. Replace every field with verified, approved information from your own delivery records.
| Buyer and project | Illustrative municipal permitting modernization |
| Role and period | Prime contractor; January 2024-June 2025 |
| Comparable scope | Workflow redesign, data migration, staff training, and managed transition |
| Verified outcome | Use only the acceptance and service results supported by approved project records |
| Evidence location | Signed acceptance record, approved project summary, and reference permission record |
| Reuse boundary | Relevant to municipal workflow modernization; not proof of unrelated infrastructure delivery |
Operating cadence
Turn delivery evidence into proposal-ready proof
1. Ingest
Create the record at award or project start, then link the controlling contract and approved scope.
2. Enrich
Add delivery milestones, outcomes, customer permissions, and evidence as the work progresses.
3. Verify
Have the accountable owner approve material facts, dates, numbers, and reuse boundaries.
4. Retrieve
Search and rank projects against the new RFP rather than defaulting to the last narrative used.
5. Tailor
Explain why the selected example reduces the buyer's stated risk and maps to the rated criterion.
6. Learn
After submission and debrief, update the record, narrative, and relevance tags with verified learning.
Final reuse check
Eight checks before a project becomes proposal proof
- The example meets every solicitation rule for eligible and recent experience.
- The role performed is explicit and cannot be mistaken for a partner's work.
- The scope and complexity are comparable to the buyer's requirement.
- Every material outcome traces to a current approved source.
- Customer names, contacts, and confidential details are permitted for use.
- Problems and corrective actions are represented accurately where required.
- The narrative explains relevance instead of pasting a generic case study.
- The final wording stays inside what the evidence can support.
Common questions
Questions teams ask before using the tool
What should a past performance library include?
Include project identity, dates, role, comparable scope and scale, delivery conditions, verified outcomes, evidence sources, corrective actions where relevant, disclosure permissions, relevance tags, an accountable owner, and a clear reuse boundary.
How is a past performance library different from a case study library?
A case study is usually a polished communication asset. A past performance record also preserves the source evidence, contract context, role, relevance fields, permissions, and limitations needed to support a scored proposal response.
How should teams choose which project examples to use?
Start with the solicitation language, then score candidate records for scope, complexity, buyer environment, delivery model, outcome strength, and recency. The highest total is only a shortlist; the proposal lead must still test the example against the exact evaluation factor.
Can subcontractor or key-personnel experience be included?
It can be recorded, but label whose experience it is and the role that party will perform. Whether it is relevant or permitted depends on the solicitation, so never present another entity or person's history as the bidder's own corporate performance.
How often should past performance records be reviewed?
Review a record when a project reaches a material milestone, when new evidence or customer permission becomes available, before reuse in a pursuit, and on a scheduled cadence so dates, contacts, outcomes, and disclosure limits remain current.
Research basis
Sources were reviewed on November 13, 2026. Examples in this guide are Novilo working examples, not procurement advice or customer results.
Find the proof that actually fits the pursuit.
Bring one opportunity and the project records your team uses today. We will map where evidence, relevance, permissions, and reuse governance are helping or slowing the response.
Book a bid-lifecycle diagnostic