Every deal runs on its own vocabulary. This glossary defines the terms behind RFPs, proposals, and modern sales workflows, in plain language, for the teams who live them.
Past performance is the record of how a supplier delivered on comparable contracts, used by buyers as evidence that a bid's promises are achievable. It is assessed through references, case detail, and in public procurement often through formal performance ratings that follow a supplier from contract to contract.
Every bidder claims capability, and claims cost nothing to make. Past performance is the only section where the buyer gets something they can verify independently, which is why it carries disproportionate weight in the decision even when it carries modest weight in the scoring.
It also works asymmetrically. A strong record rarely wins a bid on its own, but a weak or unverifiable one loses plenty. Buyers are protecting themselves against a delivery failure that would be their responsibility to explain, so an unevidenced claim reads as a risk rather than a neutral absence.
Buyers assess similarity on four axes: scale, complexity, sector, and recency. A contract of comparable value and scope in an adjacent sector usually beats a larger one in an unrelated field, because the transferability is easier for an evaluator to accept. Recency matters more than people expect, and most buyers discount anything older than three to five years.
Relevance is arguable, and arguing it is part of the job. A commercial contract can evidence a public-sector bid if you draw the parallel explicitly rather than leaving the evaluator to make it. What does not work is listing an impressive client name with no detail: the buyer is assessing the delivery, not the logo. This is where a capability statement earns its keep, because the material is prepared before the deadline rather than during it.
Structure each example the same way: the client context and problem, what you delivered, the measurable outcome, and the named referee. The outcome is the part usually missing. Delivered on time and to budget is a claim; reduced processing time by 40 percent across 12 sites, verified by the client, is evidence.
Keep referees warm and warn them before a bid goes in. A referee who is surprised by a call, or who has left the organization, converts your strongest section into a gap. And name the constraint you worked under, because a project delivered despite a mid-contract scope change tells the evaluator more about you than one that went smoothly. This is the discipline that separates good bid writing from a list of logos.
A software firm bids for a local authority case management contract with no public-sector delivery history. Rather than claiming sector experience they do not have, they present three commercial deployments matched on scale and data sensitivity, each with a named referee, migration timeline, and downtime figure. The narrative explicitly addresses the transfer: what is the same, what is different, and how they would handle the difference. They score second on past performance behind an incumbent, which is enough.
The evidence exists. It is in a delivery lead's memory, an old case study, a support ticket history, and a closing email nobody kept. Reassembling it under deadline is why past-performance sections so often end up generic, and generic is the one thing this section cannot afford to be. Cobl keeps deal material in one workspace, so what a delivery produced is still attached to the account when the next bid needs to cite it.
Teams that capture outcomes at the end of a project rather than at the start of a bid have a permanent advantage here, and it compounds with every contract they finish.
Whatever the buyer asks for, usually two or three, and no more. Adding a fourth weaker example dilutes the set, and evaluators often score the average rather than the best. Choose for relevance to this requirement, not for prestige.
Present the closest work and address the gap directly, naming what transfers and what does not, with the mitigation. Evaluators are more forgiving of an acknowledged gap than of an evidently stretched comparison, which they will notice and discount anyway.
In US federal contracting, a formal performance assessment recorded against a contractor and visible to other agencies on future bids. Similar mechanisms exist in other regimes. The effect is that delivery quality on one government tender becomes a scored input on the next one.
Check first. Many contracts restrict naming the client in marketing or bid material, and public-sector references are usually more permissive than commercial ones. Where naming is restricted, an anonymized description with a referee who will confirm privately still works.
Cobl reads the RFP and generates the full response set: go/no-go, answers, technical proposal, pricing, and slides, built on your own rules.