Capability Statement: Definition, Format & How to Write One

A capability statement is a one-page document that tells a buyer what your company does, what makes it different, what it has already delivered, and how to reach you. Government agencies and prime contractors use it the way recruiters use resumes: as a fast screening tool, read in 30-60 seconds, to decide which vendors are worth a conversation.

This guide covers the standard capability statement format, how to write each section, and the mistakes that get statements discarded. If you already know what you need, grab the free capability statement template (free: the PDF and the editable Word and Google Docs versions all come with a free account) or use the free capability statement generator to build one from a form.

On this page:

• What is a capability statement?
• Who asks for capability statements
• The standard format: 5 sections
• How to write one in 7 steps
• How long should it be?
• Capability statement vs. profile, brochure, portfolio
• Industry variants
• Mistakes that get statements discarded
• Where to use it
• Keeping it current
• FAQ

What is a capability statement?

A capability statement is a concise credentials document - almost always a single page - that answers four buyer questions in a fixed order: What do you do? (core competencies), Can you prove it? (past performance), Why you and not the next firm? (differentiators), and Who are you, formally? (company data and contact details).

The document grew out of US federal contracting, where agencies’ small business offices ask vendors to submit one before any solicitation exists. The US Small Business Administration treats it as a core marketing document for firms pursuing federal work, and agency small business offices commonly request it as the first touchpoint. But the format has spread well beyond government: prime contractors collect capability statements to build subcontractor benches, and commercial buyers in construction, engineering, and professional services increasingly expect the same one-page summary under names like company capability statement or capability document (in Australia, capability statements are standard in commercial tendering, not just government work).

Two properties define the genre and explain everything else in this guide:

1. It is a screening document, not a sales document. The reader is deciding whether to shortlist you, not whether to buy. Density and scannability beat persuasion.
2. It is unsolicited-ready. Unlike a proposal, it exists before any specific opportunity, so it must carry the identifiers (UEI, CAGE, NAICS codes, certifications) a contracting officer needs to act on it without asking you anything.

Who uses capability statements - and who asks for them

• Federal contracting officers and OSDBU/small-business specialists request them at matchmaking events and in response to capability inquiries, and use them to fill market research files for sources-sought notices.
• Prime contractors collect them to identify subcontractors - especially small, certified firms that help primes meet subcontracting plan goals.
• State, local, and education (SLED) buyers ask for them during vendor registration and at outreach events.
• Commercial clients in project-based industries (construction, engineering, architecture, IT services, consulting) request them during prequalification, alongside or instead of a project reference sheet.
• Teaming partners exchange them when assembling joint ventures or bid teams.

If your firm sells expertise or delivers projects, someone in your pipeline will eventually ask for this document - usually with less than a day’s notice.

The standard capability statement format

The format is remarkably consistent across agencies and industries: five sections, one page. Federal small-business offices (including the HHS Office of Small and Disadvantaged Business Utilization) describe essentially the same structure in their vendor guidance.

Section	What it contains	Typical share of page
Core competencies	4-6 bullet points naming the services/products you deliver, phrased around buyer outcomes	20%
Past performance	3-5 recent, relevant projects: client, scope, contract value, period, outcome	30%
Differentiators	2-4 specific, evidence-backed reasons to pick you over lookalike firms	15%
Company data	Legal name, UEI, CAGE, NAICS codes, socioeconomic certifications, size, year founded, bonding/insurance where relevant	20%
Contact information	One named person, direct phone, email, website, address	10%

The remaining space goes to your logo and header. Certifications (8(a), WOSB, SDVOSB, HUBZone, ISO 9001, industry licenses) sit inside company data or as their own labeled block - evaluators look for them, so make them findable at a glance.

The free capability statement template implements exactly this layout, with the federal code block included and easy to delete for commercial versions.

How to write a capability statement in 7 steps

1. Start from the buyer, not from your brochure. Identify the specific agency, prime, or client segment the statement targets. Pull the NAICS codes they buy under and the language they use in solicitations - your competencies should echo it.

2. Write core competencies as outcome statements. “Civil engineering” is a category; “design and permitting of municipal stormwater systems up to $40M construction value” is a competency a buyer can match to a need. Four to six bullets, each one line.

3. Select past performance for relevance, not size. Three to five projects that resemble the work you want next. For each: client name (or type, if under NDA), scope in one sentence, contract value, period of performance, and one measurable outcome. Our guide to past performance examples shows the exact entry format evaluators prefer, and where formal systems like CPARS fit in.

4. Prove your differentiators. A differentiator is only real if a competitor could not paste it into their own statement. Attach evidence: “in-house drilling crews - no subcontracted site investigation,” “98% of deliverables accepted without revision across 40 federal task orders.” Delete anything that starts with “commitment to excellence.”

5. Fill in company data completely. For US federal work: UEI and CAGE code (from your SAM.gov registration), primary and secondary NAICS codes, socioeconomic certifications, employee count, and year founded. For commercial or non-US versions, replace codes with registrations that matter in your market (bonding capacity, professional licenses, ISO certifications).

6. Put a human in the contact block. A named business development contact with a direct phone number and email. Statements routing to info@ addresses signal that nobody owns the relationship.

7. Design for a 30-second read. One page. Clear section headers, bullets over paragraphs, your logo and certifications visible without scrolling or squinting. Export to PDF so the layout survives email. Then have someone outside the company find your three most important facts in 30 seconds - if they can’t, cut until they can.

For worked examples of the finished product across twelve sectors, see our capability statement examples.

How long should a capability statement be?

One page. This is the closest thing the genre has to a hard rule.

The people who read capability statements read them in stacks - after an industry day, a contracting specialist may have fifty. Multi-page statements either get skimmed as if they were one page (so the second page did nothing) or get discarded (so it did worse than nothing). Two situations justify more:

• A two-sided page works when a specific buyer asks for depth on equipment, facility, or personnel data - common in construction and manufacturing.
• Attachments beat expansion. If you genuinely have more to show, keep the statement at one page and pair it with a project portfolio - a separate document the interested reader requests or clicks into, with full project spreads.

If you’re fighting for space, cut past performance entries before you shrink the font. Three readable projects outperform five cramped ones.

Capability statement vs. company profile, brochure, and portfolio

These documents get conflated constantly, and using the wrong one reads as inexperience:

• Company profile / brochure: written for a general audience, organized around who you are, often multi-page and design-led. It carries no UEI or CAGE codes and rarely any past performance with contract values. Useful for marketing; not what a contracting officer asked for. For a designed firm-wide showcase that pairs services with project evidence, use a company portfolio template.
• Capability statement: written for a buyer performing screening. One page, fixed section order, codes and certifications included, past performance with values and dates.
• Project portfolio: the depth document - one spread per project with images, metrics, and narrative. Follows the capability statement in the sequence; never replaces it.
• Project reference sheet / data sheet: a per-project factual record (client contact, values, dates) used inside bids and prequalification questionnaires - the raw material your past performance section summarizes.

The practical takeaway: these documents share one data source - your projects, people, and credentials - presented at different zoom levels. Firms that treat them as four unrelated files end up with four contradictory versions of the truth.

Industry-specific capability statements

The five-section skeleton holds everywhere, but evaluators in each industry check different proof points first. We maintain dedicated templates with filled-in examples per industry:

• Construction capability statement: bonding capacity, licenses, safety record (EMR, OSHA history), self-performed trades, and completed project values are checked before anything else.
• Engineering capability statement: disciplines and PE licensure, design codes and standards worked to, notable projects by sector, and QA certifications.
• IT services capability statement: contract vehicles (GSA MAS, GWACs), relevant NAICS (541511/541512), security clearances and compliance frameworks (FedRAMP, CMMC), and technology partnerships.
• Consulting capability statement: practice areas, methodologies, engagement outcomes with measurable results, and key personnel credentials.

If your industry isn’t listed, start from the general template and swap the company-data block for the credentials your buyers verify first.

7 mistakes that get capability statements discarded

1. More than one page. The most common and most fatal error.
2. Missing codes. No UEI/CAGE/NAICS on a statement aimed at federal buyers means the reader must email you before they can do anything - most won’t.
3. Generic competencies. “Full-service solutions provider” matches no procurement need. Name the services and the scale.
4. Stale past performance. Newest project four years old? The reader assumes you’ve been idle since.
5. Unverifiable differentiators. Claims without numbers, clients, or credentials attached get mentally deleted; enough of them and the whole document loses credibility.
6. Design that buries the data. Dense paragraphs, tiny fonts, decorative layouts that hide certifications. Evaluators scan; structure for scanning.
7. One statement for every audience. The Navy prime, the state DOT, and the commercial developer care about different competencies and codes. Maintain one master dataset, generate targeted versions - not one compromise document.

Where to use your capability statement

• SAM.gov and agency vendor portals - several agency registration flows accept or request an upload.
• Matchmaking and industry-day events - bring print copies; follow up by email with the PDF the same day.
• Sources-sought and RFI responses - attach it to every response as standard practice.
• Prime contractor supplier registrations - most large primes’ subcontractor portals have an upload field for it.
• Email signatures and your website - link the PDF where buyers researching you will find it.
• Prequalification packages and tenders - alongside financial data and project references in bids and tenders, where the statement frames the past-performance evidence evaluators score.

Treat every submission as a data point: note which version went where, so when the callback comes you know what they’ve seen.

Keep it current: the maintenance problem nobody plans for

Writing a capability statement takes an afternoon. Keeping it true is the part that fails. Six months later, the flagship project is missing, an old certification has lapsed, and three inconsistent copies live on three laptops - and the best version surfaces only after the deadline passes.

The root cause is that most firms store the document instead of the data. The information on a capability statement - projects, values, certifications, codes, people - changes on its own schedule, and a static Word file cannot follow it.

That’s the problem SUNAGO’s free project reference software suite exists to solve: your projects, references, and firm credentials live in one structured database, and the capability statement builder regenerates a current, formatted PDF from it on demand. Because the same database holds each expert’s profile, the free CV and skills management tool keeps the key-personnel CVs a statement relies on current too. Update a project once, and every document that cites it - capability statement, portfolio, reference sheet - is up to date the next time you export. All existing template downloads work standalone, so you can start with the file and adopt the database when maintenance starts to hurt.

Free template and generator

Two free ways to get from this guide to a finished document:

• Download the capability statement template - free in A4 and US Letter, with a complete filled-in example; create a free account to get the PDF and the editable Word and Google Docs versions.
• Use the free capability statement generator - enter your firm’s details in a form and export a formatted PDF; save your data to regenerate updated versions whenever something changes.

Better still, stop maintaining the document by hand. Build your capability statement - and every reference document your firm needs - automatically from your projects: create a free SUNAGO account.