A capability statement is one of the simplest and most useful documents an SME can keep ready. It is a short, evidence based summary that explains what your business does, which public sector requirement it can meet, and why a contracting authority should treat you as capable of delivering it. It supports your formal paperwork rather than replacing it. If you want the concise definition first, read the glossary entry for the capability statement and then use this guide to put it into practice.
The demand for well presented suppliers is real. KimonBids live data shows 1,088 tenders published in London and 653 tenders published in the South East in the last thirty days, which gives you a sense of how much work moves through the market at any one time. A clear capability statement helps you respond to that flow quickly, whether a buyer finds you during market engagement or you are introducing yourself to a larger supplier.
Why capability statements matter
A capability statement earns its place because it helps a busy buyer or prime contractor understand your business in seconds. It is most valuable at the moments before a formal procurement locks into a rigid format, including:
- Preliminary market engagement and supplier events
- Meet the buyer sessions
- Requests for information and early supplier engagement
- Framework or dynamic market discussions
- Conversations about subcontracting, consortium bids or individual lots
Under the Procurement Act 2023, contracting authorities are expected to have regard to the difficulties that smaller suppliers face and to consider how those difficulties can be reduced, for example by dividing contracts into lots and keeping documentation clear. That environment rewards suppliers who can state their offer plainly and quickly. A capability statement is how you make your relevance visible before the scoring starts.
It is important to be honest about the limits of the document. A capability statement cannot compensate for a weak tender, and it cannot overcome a mandatory requirement your business does not meet. If an opportunity demands a certification you do not hold or a turnover you cannot show, no amount of polish on an introductory sheet will fix that. The right response there is a clear go or no go decision, and our guide to go no go decisions that protect your bid budget can help you decide where to invest your effort. Treat the statement as a door opener, not a substitute for doing the formal work properly.
What to include
Aim for one or two pages and resist the urge to pad it with history. Every section should earn its space by connecting to what the buyer needs. The structure below works for most sectors.
Business summary and relevant capabilities
Open with the essentials: legal and trading name, company number, location, main contact, website, size of business and your core service. Then describe the specific work you can perform, using the buyer's own terminology where it is accurate.
Compare these two attempts. A weak version reads: "We provide excellent facilities management services." A stronger version reads: "We provide planned and reactive maintenance for public buildings, including electrical inspections, emergency call outs and statutory compliance reporting. Our team operates a 24 hour helpdesk and can attend emergency incidents within two hours across West Yorkshire." The second tells an evaluator exactly what you do, where, and how fast.
Evidence, people and controls
Include two or three short case studies. Each should name the customer or customer type, the requirement, what you delivered, the measurable result and the date. Then show capacity, not only skill, by covering:
- Qualified staff and professional registrations
- Service locations and geographic coverage
- Equipment, software or facilities
- Availability and mobilisation timescales
- Business continuity arrangements
- Relevant quality, safeguarding, information security and data protection controls
Only mention a certification if it is relevant to the opportunity, and never imply a certification is mandatory unless the tender says so. If you do not hold one, explain the equivalent process you operate and check whether the procurement permits equivalence. Keeping these proof points in a reusable bid content library means you can assemble a tailored statement in minutes rather than starting from scratch each time.
Turning a capability into evidence
The difference between an average statement and a convincing one is the move from claims to evidence. Imagine a council seeking grounds maintenance services. The requirement is to maintain parks and public open spaces, respond to urgent hazards and provide monthly performance information.
A weak response says: "We are experienced, reliable and committed to excellent customer service." That tells the evaluator nothing they can score.
A strong response reads: "GreenPath Services maintains public open spaces for local authorities, housing providers and schools. Our 22 person team manages grass cutting, hedge maintenance, litter removal and urgent public safety hazards across 65 sites. For a housing association contract covering 41 estates, we introduced route planning, photographic completion records and a 24 hour hazard response process. During the 2025 service year, 96% of routine visits were completed within the agreed schedule and urgent hazards were attended within four hours on 94% of occasions. Monthly dashboards gave the client site level information on completion, incidents and remedial action. We can mobilise within six weeks and provide trained supervisors for each operating area."
Why does this work? It does three things the weak version cannot:
- It names the actual activities so the reader recognises the scope immediately
- It gives figures, dates and systems that an evaluator can verify and trust
- It links every point back to the likely contract requirement, including reporting and mobilisation
Use client names only where you have permission. Otherwise describe the customer accurately, such as "a county council" or "a regional housing association". Accuracy matters more than prestige, and a false or unverifiable claim does far more harm than a modest but honest one.
Tailoring the statement to a tender
A generic document sent to every buyer is the most common failing. Before you submit anything, build a simple evidence map that lines up each buyer requirement against the proof you will provide. It forces you to answer the question the evaluator is actually asking.
For a maintenance style contract your map might pair these items:
- 24 hour emergency response matched to your helpdesk process, proved by response time data
- Work across multiple sites matched to a similar multi site contract, proved by the number of sites
- Monthly reporting matched to your existing dashboard, proved by a sample report or KPI results
- Safe delivery matched to training, risk assessments and supervision, proved by training records
- Contract mobilisation matched to a named lead and a timetable of responsibilities
Use the buyer's terminology where it is accurate. If the specification says "reactive maintenance", do not describe the same service only as "ad hoc repairs", because a tired evaluator may not connect the two. Where an opportunity sits on a framework or involves call offs, understanding how the work actually flows helps you pitch the right role, and our guide to how work flows through UK framework call offs explains the mechanics. Finish the statement by stating the role you want, whether prime contractor, lot supplier, specialist subcontractor, consortium partner or framework supplier. This single line helps buyers and larger suppliers place you quickly.
Capability statement versus the formal documents
It is worth being precise about where a capability statement sits among the paperwork, because confusing it with a scored submission causes avoidable losses. The documents serve different purposes:
- The capability statement introduces your relevant strengths and evidence in a concise format
- The selection questionnaire provides the declarations and information used to assess suitability and exclusion grounds
- The method statement explains how you will perform the contract
- The quality response answers the scored tender questions in the prescribed form
- The pricing schedule provides prices in the buyer's required layout
Never assume that uploading a capability statement satisfies a question in the selection questionnaire or invitation to tender. Answer each mandatory question in the exact form and location requested. If you rely on another organisation to meet a selection requirement, identify that reliance consistently across every document, because standard selection arrangements can require those organisations to submit their own information.
Common mistakes are easy to avoid once you know them. Watch for these in particular:
- Sending the same generic document to every buyer
- Listing services without showing outcomes
- Using unsupported claims such as "best in class"
- Omitting geographic coverage and capacity
- Claiming compliance without evidence
- Ignoring page, file format or portal instructions
- Including confidential client information without permission
Keep the language clear enough for a non specialist to follow, check every figure and date, and confirm the statement follows the buyer's instructions before you send it. A tidy, tailored and honest statement will always outperform a glossy, generic one.
Frequently asked questions
How long should a capability statement be?
Aim for one or two pages. A capability statement is meant to introduce your relevant strengths quickly, so keep it concise and tailored to the opportunity rather than including excessive company background.
Can a capability statement replace my tender response?
No. It supports your submission but never replaces it. You must still answer each mandatory question in the selection questionnaire and invitation to tender in the prescribed form and location, and provide the method statement, quality response and pricing schedule as required.
Do I need to name my previous clients?
Only where you have permission. Otherwise describe the customer accurately, for example a county council or a regional housing association. Accuracy and honesty matter more than name recognition, and unverifiable claims can damage your credibility.
What if I do not hold a certification the buyer mentions?
Do not imply the certification is mandatory unless the tender says so. If you do not hold it, explain the equivalent process you operate and check whether the procurement permits equivalence. Never claim compliance without evidence.
How do I tailor a statement to a specific contract?
Build an evidence map that pairs each buyer requirement with the proof you will provide, such as response time data or a sample report. Use the buyer's own terminology where it is accurate so an evaluator can connect your capability to their need.


