Skip to content

What is a capability statement?

A capability statement is a supplier's short, evidenced account of what it can deliver for a kind of contract. It covers services, dated experience, accreditations and capacity, and buyers ask for it in an RFI, in market engagement or at selection.

A capability statement works as standing evidence about a supplier. The bid team keeps one approved version and adapts it each time a buyer asks which suppliers could deliver a kind of contract. In UK and EU bidding, it can be a document in its own right or a section the buyer asks for inside a larger response. Either way, it describes the organisation, not a solution to one specification.

Its meaning ends where the buyer's own questions take over. A questionnaire with fixed questions and thresholds, or a scored answer to a requirement, is a different thing, even when it reuses the same evidence. In US federal contracting the term usually names a one-page summary built around registration codes such as UEI, CAGE and NAICS, a separate format with its own conventions.

What a capability statement holds

A capability statement holds evidence about the organisation and what it has already delivered: its services, dated references, accreditations, capacity and differentiators. It does not propose a solution to one requirement, and it leaves out anything the organisation cannot prove or has not approved.

Services, experience and references

The services section names what the organisation delivers now, grouped by the service lines that match the kind of contract in question. Experience follows as a set of comparable contracts, each with the buyer, the scope, the value and the dates, and a referee who has agreed to be contacted. The UK government's Sourcing Playbook, guidance for central government buyers in England, says questions on technical and professional ability should focus on the bidder itself and its past experience.

Dates matter as much as the contracts. In the EU, Annex XII of Directive 2014/24/EU lets a buyer ask, as proof of technical ability, for a list of the main services provided over at most the past three years, with sums, dates and recipients. References in a capability statement therefore carry their start and end dates and their values, so a buyer can read them against that window.

Accreditations, capacity and differentiators

Accreditations and certifications appear with the issuing body, the scope they cover and their expiry date. A certificate that covers one site or one service line says less than its name suggests. Capacity sets out what the organisation can take on: the people in the relevant service line, its locations, the contracts it runs in parallel and how it would mobilise. Insurance levels and financial standing sit here too when the buyer asks for them.

Differentiators close the evidence. In a capability statement they are things a buyer can check, such as a method the organisation has used on named contracts, a sector it has served for years or a specialist accreditation. Each one ties back to a reference or a certificate earlier in the document. A differentiator with no evidence behind it reads as marketing copy.

What stays out

Claims that cannot be verified stay out: superlatives, unsourced figures and market positions nobody has measured. They give the buyer nothing to rely on and weaken the evidence around them. Confidential detail from past contracts, such as pricing or terms a referee has not cleared for disclosure, stays out even where it would strengthen a reference.

Commitments the organisation has not approved stay out too. A capability statement describes what has been delivered and what can be delivered. It does not set prices, timelines or terms for a contract that doesn't yet exist, and the bid manager answers for every response that leaves the organisation, this one included. The proposed solution to a specific requirement belongs in the later response, where the buyer scores it.

When buyers ask for a capability statement

Buyers ask for a capability statement at two points: before any tender notice, to find out which suppliers could deliver, and at selection stages, supplier lists and frameworks, where the supplier itself is assessed.

Before a tender: RFIs and market engagement

An early request comes as an RFI or as a questionnaire issued during preliminary market engagement. In England, Wales and Northern Ireland, the Procurement Act 2023 guidance on preliminary market engagement, republished for buyers by the Welsh Government, places that engagement before a tender or transparency notice is published.

A capability statement sent at this point is read before any bid exists, and it can be the first document a buyer sees from a supplier. The tender process then moves on through selection and award, each asking for different evidence.

Selection stages, supplier lists and frameworks

Later in a procurement, the request moves to the stage where the supplier itself is judged. The Sourcing Playbook, guidance for central government buyers in England that in places still reflects the regime before the Procurement Act 2023, describes the selection stage as an assessment of the suppliers themselves, as opposed to the evaluation and award stage, which assesses their bids. A capability statement sits on the selection side of that line. It answers whether the organisation can deliver, not how it would deliver this contract.

Buyers building a supplier list or appointing to a framework ask the same question across a range of future call-offs. A statement for that purpose covers the breadth of the organisation's service lines rather than one requirement. A tender can also request a capability statement as one section of a response, and then the buyer's heading, word limit and template set its shape.

How a standing capability statement is kept and tailored

A standing capability statement is kept as one approved master version, and every copy that goes to a buyer is tailored from it to that buyer's question and template. Each claim in it has an owner and a review date, and the bid manager signs off each version before it's sent.

Master version and tailored versions

The master version holds the approved wording for each service line, the full dated reference list, current accreditations and confirmed capacity figures. A tailored version selects from it and reorders it to follow the buyer's questions, headings, word limits and format. It uses the buyer's own terms for the need it describes.

What changes between versions is selection, order, emphasis and length. The references closest to the buyer's sector come first, and service lines the buyer did not ask about drop out. What does not change is the facts: contract values, dates, accreditation scopes and capacity figures read the same in every version as in the master.

Owners, sign-off and review dates

Each claim in the statement has an owner who confirms it and a review date by which it is checked again. BSI's PAS 360:2023, the code of practice for bid and proposal management, covers good working practice, roles and responsibilities.

Each item carries a review date set by how fast it goes stale: an accreditation by its expiry, a reference by its age, a capacity figure by the next reorganisation or contract win. The bid manager signs off each tailored version, as for any response. An auditable library of approved answers and evidence keeps those owners, dates and approvals traceable.

One fact base behind every version

Every tailored version draws on the same approved facts, so no two buyers, and no two teams at one buyer, see different figures for the same contract. McKinsey's 2026 Global B2B Pulse Survey, of nearly 4,000 decision-makers in 13 countries, found inconsistent information across teams to be the top reason buyers switch suppliers. The survey covers commercial B2B purchasing rather than public tenders, and the same report finds buyers judging suppliers on their ability to operate as one integrated commercial system.

The survey also places generative AI among the top five channels buyers use to discover and evaluate suppliers. The statement, and the material it draws on, may be read by AI tools as well as by people, alongside every other place the supplier states the same facts.

How a capability statement differs from a brochure, a proposal and a PQQ

A capability statement is the supplier's own evidenced account of the organisation. A brochure markets the organisation without having to prove anything, a proposal answers one requirement and is scored at award, and a PQQ answers questions the buyer has fixed.

Company brochure

A company brochure is written to persuade a broad audience, and it need not evidence what it says. A capability statement may share some wording, but each claim traces to a reference, an accreditation or a confirmed figure.

The difference shows on the page. A capability statement names contracts with dates and values, accreditations with their scope and capacity in numbers, and it carries the bid manager's sign-off like any other response. A brochure carries adjectives and images, and it is approved as marketing.

Full proposal

A full proposal answers one requirement. It sets out the solution, method, team and price for a specific contract.

A capability statement comes earlier or sits beside that work. It evidences the organisation rather than proposing anything. A proposal's experience section can draw on it, but a scored question still needs an answer to the specification in front of the bid team.

PQQ

A capability statement follows the supplier's own structure unless the buyer supplies a template. It states what the organisation can deliver rather than whether it meets a threshold.

Much of the same organisation-level evidence serves both. The references, accreditations, insurance and accounts in a PQQ response are the same ones that back a capability statement's claims, drawn from the same approved fact base.

How SEQUESTO supports capability statements

In SEQUESTO's agentic operating system (aOS), a capability statement starts when an RFI arrives in a project. James recognises it as an RFI from its structure, language, and metadata, or the team sets the type, and the output follows the type: a short capability statement rather than a full technical and commercial submission. Under his orchestration, Agent Force drafts each part at question level from approved content in the Knowledge Hub, and the team sees the reasoning behind each draft.

Each Knowledge Hub item keeps its owner, review cycle and expiry date, so an expired accreditation or out-of-date reference is flagged before it reaches the draft. For each question, Agent Force searches the evidence library by meaning and returns matching references ranked with a confidence score from 0 to 100. A low score shows the evidence may not exist yet and names the kind of document that would close the gap. Only documents tagged as shareable are suggested for an external submission.

The bid manager reviews the draft, accepts, adjusts or rejects each part and signs off on the final wording. The statement is rendered in the team's Word template, or the buyer's format, and a person on the team submits it. SEQUESTO does not submit on the team's behalf.

Frequently Asked Questions

Further Reading

Put the terminology to work

Now you know the language, see how SEQUESTO automates the process. Book a demo and experience AI-powered bid management first-hand.