Past Performance: How to Document and Present It

Strong past performance examples share one quality: every claim can be verified. Past performance is the documented record of how well your firm delivered previous, relevant contracts, and evaluators use it to predict how you will perform on the work they are about to award. This guide shows the entry format evaluators prefer, a worked example, and a six-step method for documenting and presenting it - whether you are responding to a US federal solicitation, an EU tender, or a commercial prequalification.

Past performance is the evidence layer beneath your capability statement: the statement summarizes it, the proposal expands it, and a project reference sheet records each project so it can be checked.

What “past performance” means to an evaluator

To a buyer, past performance answers a single question: has this firm already done work like ours, and did it go well? It is not a list of everything you have ever built - it is curated, verifiable evidence chosen to resemble the contract on the table. Three properties make an entry credible:

• Relevance - the project matches the advertised scope in sector, scale, and complexity.
• Recency - it falls inside the time window the buyer specifies (commonly three to five years).
• Verifiability - a named client, a contract value, real dates, and a reference who will confirm it.

In US federal procurement, past performance is a formal evaluation factor, and completed-contract ratings are recorded in CPARS, which contracting officers can consult directly. In the EU, authorities may require “a list of the works carried out over at most the past five years” accompanied by certificates of satisfactory execution (Directive 2014/24/EU, Annex XII). The mechanics differ; the underlying demand for verifiable evidence does not.

The entry format evaluators prefer

Present every past-performance entry in the same field order so reviewers can compare projects side by side:

Field	What to write
Client / contracting authority	The organization name, or client type if under NDA
Scope	One sentence on what your firm actually delivered
Contract value	State the currency; a range is acceptable where confidentiality applies
Period of performance	Start and completion dates; note if delivered on schedule
Your role	Prime, subconsultant, JV partner - never left ambiguous
Outcome	One measurable result the client would confirm
Reference	Named contact, current phone and email

Keep each entry to one to three lines in a capability statement, expanding to a short paragraph in a proposal where the solicitation allows narrative.

Past performance example

A worked entry from a fictional civil engineering firm, written to the field order above:

Client: City of Northgate Utilities (municipal, public sector) Scope: Design and construction-phase engineering for a wastewater treatment plant capacity upgrade. Value: $18M construction · Period: 03/2023 - 05/2025, completed on schedule Role: Prime consultant Outcome: Expanded treatment capacity from 12 to 17 MGD, delivered 3.2% under construction estimate, zero permit violations. CPARS rating: Exceptional (Quality, Schedule). Reference: J. Alvarez, Director of Utilities · +1 253 555 0142 · j.alvarez@northgate.example.gov

Notice the discipline: the role is explicit, every outcome is a number, and the reference is reachable. Compare this to a weak entry - “Provided engineering services for various municipal clients with excellent results” - which gives an evaluator nothing to score or verify.

How to document and present past performance in 6 steps

1. Build a master list of every relevant project. Compile every project that could serve as evidence, with client, value, dates, role, and outcome, before you tailor anything. You cannot select good references from a list you have not written down.
2. Select projects for relevance, recency, and role. For each submission, pick three to five projects that match the advertised scope in sector and scale, fall inside the required time window, and where your firm’s role was material rather than minor. A modest but directly comparable project beats a glamorous unrelated one.
3. Write each entry in the evaluator’s field order. State client, one-sentence scope, contract value, period of performance, your role, and one measurable outcome - in the same order every time so entries can be compared at a glance.
4. Attach verifiable proof and a reference contact. Add a named client contact with current phone and email, and cite any formal record such as a CPARS rating or a certificate of satisfactory execution. Confirm the referee is reachable and willing before you submit - evaluators do call.
5. Quantify the outcome. Replace “delivered successfully” with numbers an evaluator can check: cost variance against estimate, schedule performance, capacity or volume delivered, or a documented quality metric.
6. Keep the record current and reuse it. Store each project’s facts, metrics, and reference permissions once so entries stay accurate across every bid, and update the record at project close-out rather than reconstructing it under deadline pressure.

Presenting past performance in different documents

The same underlying evidence appears at three zoom levels, and using the right one matters:

• Capability statement: three to five one-line entries in the past-performance section. Density over narrative. See the capability statement template.
• Proposal / bid: the full narrative the solicitation requests, mapped to the award criteria. How to match references to criteria is covered in project references for tenders.
• Reference sheet: one standalone, verifiable page per project, used in prequalification and PQQs - the project reference sheet format.

Common past-performance mistakes

Even experienced firms lose points on past performance for a handful of recurring reasons. Avoid these:

• Leading with your biggest project instead of your most relevant one. Evaluators score relevance, not prestige. A directly comparable mid-size project beats a marquee project in the wrong sector.
• Vague roles. “Involved in” and “supported” invite the evaluator to assume the smallest possible contribution. State whether you were prime, subconsultant, or JV partner, and what you were accountable for.
• Unquantified outcomes. “Completed successfully” is filler. If you cannot attach a number - cost variance, schedule performance, capacity delivered - the entry adds nothing.
• Referees who have not been briefed. A referee surprised by an evaluator’s call, or unaware which project is being asked about, can sink an otherwise strong entry. Tell each referee which projects you have cited and when a call might come.
• Letting the newest project age out. A statement whose most recent project is three years old signals a firm in decline. Refresh the set as new projects close.

Most of these trace back to the same root cause: past performance is treated as prose to rewrite each time, rather than data to maintain once.

Keep past performance current without rewriting it

Past performance ages faster than any other part of your credentials: projects complete, metrics finalize, referees change jobs, and CPARS ratings post months after closeout. Firms that store the documents end up with contradictory copies; firms that store the data do not. The free project reference manager keeps each project’s facts, outcomes, and reference permissions in one record and regenerates past-performance entries, reference sheets, and capability statements from it - update a project once, and every bid that cites it stays accurate. Build these from your projects automatically - create a free SUNAGO account.