How to Write a Capability Statement to Win Tenders

Cabinet Office guidance now expects contracting authorities to assess social value in a consistent way, and the Procurement Act 2023 puts even more weight on clear, comparable supplier information. That matters at the very start of the buying process, long before a full method statement or pricing schedule is read.

A capability statement helps a buyer place your business quickly. In UK public procurement, that means showing where you fit against a framework lot, service requirement, or subcontract package, with enough evidence to justify keeping you in the running.

The documents that work are short, specific, and built for procurement readers. A commercial manager at a council, an NHS category lead, and a tier-one bid team all want the same first answer. What do you deliver, for whom, and with what proof?

Weak statements usually fail for predictable reasons. They read like generic marketing copy, cover every service the firm has ever offered, and bury the evidence under slogans. Strong statements do the opposite. They prioritise relevance, use plain language, and make first-stage assessment easier.

That matters even more in the UK public sector, where buyers are screening for policy fit as well as technical fit. If your statement ignores contract scope, sector experience, accreditations, and social value relevance, it creates work for the evaluator. In a busy sift, extra work usually means lost attention.

Why Your Business Needs a Killer Capability Statement

Around 99.9% of UK businesses are SMEs, according to the House of Commons Library. That means public buyers and prime contractors have a crowded supplier market to screen. A capability statement helps your business get sorted into the right pile quickly.

That early sift is where a lot of good suppliers lose momentum.

In UK public procurement, buyers often need a fast read before they ask for anything substantial. A framework manager may want to know whether you fit a lot. A council procurement officer may be checking whether your offer aligns with the contract scope. A tier one contractor may be deciding whether to include you in a supply chain for a bid that needs credible delivery partners, policy compliance, and social value support from day one.

A capability statement gives them that first answer.

I treat it as a short qualification document. It should help a buyer decide, with very little effort, whether your firm is relevant, credible, and worth the next conversation.

Practical rule: If the reader cannot place you against a service line, framework lot, or subcontract package within a few seconds, the statement still needs work.

A good capability statement earns its keep in three ways:

• It makes your offer easy to place against an actual requirement.
• It shows evidence of delivery through relevant contracts, accreditations, sectors served, and outcomes achieved.
• It saves evaluator time by putting the right facts in one document instead of making them hunt through your website or company brochure.

That matters more in the UK public sector than many generic guides admit. Buyers are not only checking whether you can do the work. They are also checking whether you understand public sector constraints. Under the Procurement Act 2023, that means clearer scrutiny of supplier information and stronger pressure on authorities to make decisions they can justify. If your statement is vague on compliance, sector experience, or social value relevance, it creates doubt at exactly the wrong point.

Buyers use capability statements in several practical ways. They show up in early market engagement, framework research, subcontractor onboarding, and introductory outreach to public bodies or primes. I have also seen them requested informally before a supplier is invited to respond to a mini-competition. The format is simple, but the decision behind it is not. The buyer is asking whether your business belongs in the next stage.

That is why trying to say everything usually backfires.

A one-page statement crammed with every service you have ever offered does not look stronger. It looks unfocused. If your firm covers retrofit consultancy, stock condition surveys, damp and mould diagnostics, PAS 2035 coordination, and planned maintenance support, split those offers properly or lead with the one that matches the opportunity. Relevance wins over range, especially where procurement teams are reading at speed.

Weak statements usually fail for familiar reasons. They rely on broad claims such as “end-to-end solutions” or “excellence in service delivery”. They list sectors with no proof. They mention social value as a slogan rather than showing something usable, such as local apprenticeships delivered on a repairs contract, SME supply chain spend, or tenant training linked to a housing framework.

A strong statement does the opposite. It helps the buyer say yes to the next step.

The Anatomy of a Winning Capability Statement

Most winning capability statements follow the same core structure. The exact design varies, but the bones don’t.

Use this visual as the basic model.

Start with a sharp company overview

The top section should answer three questions fast. Who are you. What do you do. What sort of work are you built for.

Keep it short. Two or three sentences is usually enough.

Bad version:

“We are a multi-disciplinary provider of innovative, high-quality solutions across a wide range of sectors with a commitment to excellence and client satisfaction.”

That says almost nothing.

Better version:

“We help housing associations and local authorities deliver planned maintenance, compliance inspections, and retrofit support across occupied residential stock. Our team works on live environments where tenant communication, access management, and audit-ready reporting matter as much as technical delivery.”

That gives the reader a sector, service scope, and operating context.

List core capabilities like services, not slogans

Most statements often lack impact.

Your core capabilities should be a tight bullet list of what you deliver. Use language a buyer would recognise from tender documents, service specifications, and framework scopes. Avoid fluffy labels.

For example, an IT supplier targeting NHS trusts might use:

• Cloud migration support for legacy systems and hosted environments
• Service desk and end-user support across multi-site organisations
• Cyber security remediation aligned to public sector compliance needs
• Data integration and reporting for operational and management teams
• Project delivery and stakeholder training during transition periods

That reads like delivery capability.

This does not:

• Innovation
• Quality
• Flexibility
• Excellence
• Trusted partnerships

Those may be true, but they are not capabilities.

Show past performance with context

Past performance is where you move from “we say” to “we’ve done”.

You do not need a long case study. You need a concise example that shows similarity of scope, client type, and delivery conditions. Name the client if you can. If you can’t, describe them clearly enough to be useful.

A good entry usually includes:

• Client type
• What you delivered
• Why it was relevant
• Any measurable proof you can safely share

Here’s the difference.

Weak:

• Delivered cleaning services for multiple clients across the UK.

Stronger:

• Delivered daily cleaning and reactive hygiene support across a multi-site public-facing estate, including safeguarding-sensitive environments and out-of-hours response.

The second one gives the evaluator something to work with.

Add differentiators that are specific

Differentiators are not the place for clichés. “We care more” is not a differentiator. “Friendly team” is not a differentiator. “Years of combined experience” usually isn’t either unless it ties directly to the tender.

The best differentiators are choices or assets that change delivery risk in your favour.

Examples:

• Staff already cleared or trained for regulated environments
• Existing mobilisation process for occupied sites
• In-house reporting system aligned to client audit needs
• Experience working as a subcontractor under framework call-offs
• Sector-specific certifications or technical accreditations

The key question is simple. Why would this matter to the buyer on this contract?

If your differentiator wouldn’t affect award risk, mobilisation, compliance, or service quality, leave it out.

Include company data without clutter

This part is functional, but buyers still need it.

Include the basics:

• Registered business name
• Website
• Location
• Key contact
• Relevant certifications
• Frameworks or routes to market if relevant
• Classification or category codes used in your market

For UK public tenders, use the coding and procurement language that fits the route you’re pursuing. Don’t copy US-focused templates with NAICS, CAGE, or SAM.gov references if they don’t apply to your target buyer.

Keep it to one page if you can

One page forces discipline. It also matches how procurement teams read these documents. They scan first, then decide whether to ask for more.

That doesn’t mean the page has to be cramped. White space matters. Headings matter. Bullet lists matter. A buyer should be able to find your competencies, examples, and contact details without effort.

A simple layout works best.

A practical layout that works

I’d structure it in this order for most UK SMEs:

1. Header with logo and short positioning line
2. Company overview
3. Core capabilities
4. Relevant experience
5. Differentiators
6. Company data and contact details

That order mirrors how buyers think. First fit. Then evidence. Then confidence checks.

What strong wording sounds like

A capability statement should sound plain, assured, and precise. Not over-polished.

Try these swaps:

• “High-quality solutions” becomes planned and reactive maintenance support for public buildings
• “Client-focused delivery” becomes single point of contact with weekly reporting and issue escalation
• “Experienced leadership team” becomes contracts led by sector-qualified managers with public sector delivery experience
• “Trusted by clients” becomes repeat delivery for local authority and housing clients

The second version in each pair gives the buyer something concrete.

What to cut before you send it

Before you finalise the page, remove:

• mission statements that could belong to any firm
• full service catalogues
• tiny text blocks
• stock phrases like “end-to-end solutions”
• irrelevant private sector examples
• decorative graphics that take space from proof

Most statements improve when you delete about a quarter of the first draft.

Tailoring Your Statement for UK Public Tenders

A generic capability statement is better than nothing. It is not enough for serious UK public sector bidding.

The problem with most online guides is that they’re written for US government contracting. They tell you to add US codes, US registrations, and US positioning cues. None of that helps a buyer running a UK framework competition, a DPS application, or a call-off under current procurement rules.

Match the Procurement Act 2023 environment

Under the Procurement Act 2023, compliance with the UK’s Social Value Model is a major evaluation factor, and data cited by Crown Commercial Service shows that statements specifically designed for UK requirements, including social value metrics, can boost shortlist rates by as much as 35%, according to this UK-focused capability statement guidance.

That tells you the statement is no longer just about technical capability. It also needs to show that you understand how public buyers evaluate value.

If you’re bidding into UK public sector work, your capability statement should reflect:

• the type of authority or public body you’re targeting
• the contract route, such as framework, DPS, or open competition
• your social value position
• your delivery controls in regulated or public-facing settings

If you need a clearer grounding in the legal backdrop, Bidwell’s guide to public sector procurement regulations is a useful companion read.

Put social value in the document, not just the bid

A common mistake is treating social value as something you deal with later in the tender response. Buyers often look for signals much earlier than that.

If your capability statement says nothing about apprenticeships, local supply chain use, community benefit, carbon-conscious delivery, or inclusive employment practices, it can feel disconnected from how UK tenders are scored. Even where the statement isn’t formally evaluated, it shapes first impressions.

That doesn’t mean stuffing the page with promises. It means adding credible, relevant lines such as:

• your approach to local recruitment on service contracts
• how you reduce travel or site waste
• any community-facing delivery model already used in similar contracts
• how contract management captures and reports social value outputs

Reflect the route to market

A statement for G-Cloud should not read like one for an estates maintenance framework. A statement for a Dynamic Purchasing System should not read like one for a one-off below-threshold procurement.

Adjust the wording so it matches the buying route.

For example:

• A digital supplier targeting G-Cloud should stress service definition, implementation support, security, and ongoing service management.
• A care or community supplier should foreground safeguarding, mobilisation, staffing continuity, and service-user outcomes.
• A construction-related SME should focus on live-site working, compliance, programme control, and subcontractor management.

Buyers notice when a statement has been lifted from a generic template. They also notice when it sounds like it belongs in their market.

Use UK coding and terminology

Adapted statements often beat imported templates.

Use the codes, framework references, and service descriptions that fit UK procurement language. Use British English. Refer to local authorities, NHS trusts, housing associations, schools, universities, and central government bodies by the names buyers themselves use.

It sounds basic, but it matters. If your statement feels foreign to the route you’re bidding through, it creates distance. If it uses familiar terms, it creates confidence.

Writing with Impact Using Measurable Proof

Most capability statements collapse into adjectives. Reliable. Experienced. Flexible. Professional.

None of those words help much unless you prove them.

What works is measurable proof. Not because buyers love numbers for their own sake, but because evidence lowers perceived risk. It shows that your claims come from delivery, not copywriting.

Start with evidence you already have

You probably have more usable proof than you think.

Look in:

• completed project summaries
• contract management reports
• client feedback
• internal KPIs
• mobilisation plans
• audit outcomes
• helpdesk or service logs
• framework performance reviews

The point is not to invent a glossy case study. The point is to pull out facts you can stand behind.

If a project improved reporting quality, what changed in practice. If your team mobilised quickly, what did that involve. If a client retained you, what scope did they trust you with next.

For a sharper understanding of what evaluators look for in scored answers, Bidwell’s article on tender evaluation criteria examples helps frame the difference between a claim and a defendable point.

Turn vague statements into proof-led lines

Here are a few before-and-after examples.

Notice what changed. The improved versions describe observable practice.

Use numbers only when you can prove them

If you have real contract values, delivery timescales, service volumes, audit scores, or repeat-award evidence, use them. If you don’t, don’t force it.

You’re better off writing:

• delivered across multiple occupied sites
• supported a live operational environment with strict access controls
• provided recurring reporting to client stakeholders
• managed planned and reactive work under one contract structure

than adding invented precision.

That’s one of the biggest discipline points in learning how to write a capability statement. Precision is powerful only when it’s real.

Useful test: Could you defend this line if the buyer asked for evidence tomorrow? If not, rewrite it.

Build compact proof blocks

One format I like is a short proof block under each selected experience example.

For instance:

• Public sector FM support
  Delivered planned and reactive support in occupied buildings. Included access coordination, compliance records, and regular client reporting.

• Housing retrofit consultancy
  Supported survey, planning, and resident-facing communication on improvement works. Worked in live homes where scheduling and communication affected delivery success.

• IT support for regulated environments
  Managed user support, issue logging, and transition activity for teams that needed continuity during service change.

Each block is small, but it says something specific.

Quote outcomes carefully

Client testimonials can help, but only if they add substance and you have permission to use them. In most cases, plain evidence works better than a glowing quote with no context.

Instead of:

• “Our client was delighted with the service”

say:

• appointed to deliver follow-on work after initial contract completion

That lands better because it implies trust through action.

Match proof to the tender you want

This is the part people skip. They gather evidence, then use the same examples everywhere.

Don’t do that.

A school catering contract, an NHS digital support contract, and a local authority estates framework all need different proof. Even if your company is the same, the examples you foreground should shift.

Choose examples that mirror:

• service environment
• user group
• compliance demands
• delivery model
• contract management needs

Relevance beats volume every time.

Common Capability Statement Pitfalls to Avoid

The easiest way to improve a capability statement is often to stop doing what weak statements always do.

Most of the problems are self-inflicted. They come from trying to sound bigger, broader, or more polished than the document can support. Buyers spot that quickly.

Trying to say everything

This is the most common mistake.

Firms cram every service, sector, client type, and credential onto one page because they don’t want to leave anything out. The result is a page that says a lot but positions nothing clearly.

The fix is simple. Choose the contract type first, then build the statement around that. A housing maintenance capability statement should not read like a generic corporate profile for every possible buyer.

Using internal jargon

Internal language kills clarity.

Phrases your team uses every day might mean nothing to a procurement officer outside your business. Product nicknames, team acronyms, and process shorthand make the reader work too hard.

Use buyer language instead. Lift service terms from real specifications, framework scopes, and award notices. If the buyer says “voids works”, “compliance servicing”, or “end-user support”, use those terms where they fit.

Leading with values instead of capability

There’s nothing wrong with values. They’re just not the lead story in a one-page statement.

If the top half of the page is full of mission, purpose, and culture language, the buyer still won’t know what you deliver. Values support trust. They do not replace service fit.

Move from identity to capability quickly.

Making unsupported claims

Buyers are used to seeing phrases like “market-leading”, “trusted experts”, and “unrivalled service”. Unless you can prove them, they weaken the page.

A safer move is to describe what you do in operational terms. Mention the environments you work in, the controls you use, and the type of clients you support. Concrete language carries more authority than self-awarded status.

The fastest way to sound credible is to stop trying to sound impressive.

Burying the useful details

Sometimes the right content is there, but the layout hides it.

Tiny fonts, oversized logos, long paragraphs, and dense company history blocks force the evaluator to hunt for the relevant parts. That’s enough to lose attention.

Fix the hierarchy:

• clear section labels
• short bullets
• visible contact details
• experience examples grouped together
• enough white space to scan quickly

Reusing the same file forever

A capability statement is not a one-and-done document.

Services change. Framework positions change. Certifications expire or renew. Team structure changes. Public buyer priorities move. If your statement still reflects the company you were two years ago, it can create doubt before the buyer even gets to the tender.

Review it regularly. Be sure to keep a base version and then tailor from that.

Looking polished but saying very little

This one catches a lot of firms with nicely designed PDFs.

The branding looks great. The icons are tidy. The colours are consistent. But the actual content is generic and light on proof. Good design helps readability, but it cannot rescue weak substance.

A plain one-page statement with relevant capability, useful examples, and buyer-friendly wording will beat a beautiful empty document most of the time.

Build Your Statement Faster with Bidwell's AI Platform

Writing a strong capability statement is not difficult once. The hard part is keeping it current, evidence-based, and ready to adapt for different tenders.

That’s where process matters more than writing talent.

The firms that produce these documents quickly usually aren’t starting from scratch each time. They keep approved content in one place, update it as projects finish, and then tailor from a controlled base. That’s the logic behind using a platform rather than a scattered mix of old folders, inbox searches, and copied Word files.

Use tender monitoring to decide what version you need

A capability statement only works if it reflects the opportunity you’re chasing.

Bidwell’s tender monitoring helps at the very start. If you’re receiving alerts from portals such as Find a Tender, Contracts Finder, Public Contracts Scotland, and Sell2Wales, with AI-generated summaries of relevant opportunities, you can spot the contract themes that matter most to your business. That changes how you shape the statement.

Instead of writing one generic page, you can maintain targeted variants for:

• facilities and estates work
• digital and IT support
• consultancy and professional services
• framework entry packs
• subcontracting introductions

That’s a better use of time because the market tells you what to prepare.

Build a usable knowledge base

The bottleneck in capability statements is not formatting. It’s retrieval.

Teams waste hours hunting for the latest staff bio, the correct certification wording, the right project example, or an approved social value paragraph. Bidwell’s knowledge base solves that by storing reusable content in a structured way.

That means you can keep:

• approved competency bullets
• past performance summaries
• staff profiles
• certification details
• framework references
• social value examples
• measurable proof points

in one place, ready for reuse.

This is also where AI tools are most helpful in practice. Not as magic writers, but as systems that work from approved material. If you want a broader view of where AI is being used across commercial content workflows, Miles Marketing’s guide to essential AI marketing tools is a sensible outside reference.

Draft faster with AI response generation

Once your source material is organised, Bidwell’s AI response generation can draft specific content using the knowledge base and the tender context you’ve selected. That includes capability-statement style summaries for a specific buyer, framework, or service line.

The workflow is straightforward:

1. Identify the opportunity through tender monitoring.
2. Pull the relevant past performance, competencies, and credentials from the knowledge base.
3. Generate a draft aligned to the contract context.
4. Review, tighten, and remove anything that doesn’t earn its place.

Bidwell explains that process in more detail in its guide to AI tender writing.

What this changes in practice

The value isn’t just speed. It’s consistency.

When your team uses the same approved source content, you avoid common problems like old certifications appearing in live documents, inconsistent service descriptions across bids, or different team members describing the same project in conflicting ways.

It also makes tailoring less painful. You’re no longer rewriting the company from the ground up. You’re selecting the right evidence and shaping it for the right buyer.

Good bid teams don’t write every document from a blank page. They build systems that make the right content easy to find and hard to misuse.

That’s exactly how capability statements should be managed. As living assets tied to your live pipeline, not static PDFs buried in a shared drive.

Your Next Steps and a Fillable Template

A capability statement is a working sales document for procurement. Treat it that way and it starts to pull its weight.

Keep it short. Make it relevant. Use proof instead of adjectives. Adapt it for UK public tenders rather than copying US templates that don’t match your buyers. If the document helps an evaluator place you quickly, it’s doing the job.

The easiest next move is to build one strong base version, then create customized variants for the sectors and tender routes you pursue most often. If you want more practical writing ideas for sharpening business content and prompts, the Rudyard blog is worth a look.

Use a fillable template so your team can standardise the structure:

• company overview
• core capabilities
• relevant experience
• differentiators
• company data and contact details

Then review it like a buyer would. What’s clear. What’s vague. What looks like evidence. What sounds like filler. That final pass usually decides whether the statement earns attention or gets ignored.

If you want to stop rebuilding capability statements from old files every time a tender appears, Bidwell can help. It brings together tender monitoring, a searchable knowledge base, and AI response generation so your team can spot the right opportunities, keep approved evidence in one place, and produce customized bid content faster.