Capability Statement: What It Is and How to Write One

A capability statement is a one page business summary that tells a government or corporate buyer what your company does, what it has done before, and why it should be selected. It typically covers four blocks: core competencies, past performance, differentiators, and corporate data such as NAICS codes, a CAGE code, and a Unique Entity ID.

Buyers treat it as a screening document. It is the page that sits in a file when an agency decides who to call about an upcoming requirement, and it is the standard attachment when you answer market research. Getting it right has far less to do with graphic design than with specificity.

What goes in a capability statement

Most capability statements follow the same four block structure, and buyers have learned to look for it. The table below sets out what each block answers and what belongs inside it.

Core competencies

This is where most capability statements fail. A list that reads consulting services, IT solutions, and program support describes thousands of companies and disqualifies you from none. Write four to six competencies specific enough that a contracting officer could match them to a line item in a statement of work, and use the vocabulary the agency uses rather than your internal service names.

Past performance

Relevance beats volume. Two contracts of similar scope, dollar value, and complexity carry more weight than a list of twelve unrelated engagements. For each one, name the customer, describe the scope in a sentence, and give the contract value, period of performance, and contract number. If you have worked for the same agency, say so plainly rather than leaving the reader to infer it. A past performance questionnaire is often how a buyer verifies what you claim here, so keep the two consistent.

Differentiators

A differentiator has to be something a comparable vendor cannot say. Quality work, customer focus, and experienced staff are table stakes, not differentiators. Certifications, security clearances, a proprietary methodology, a specific geographic footprint, or a documented performance record all qualify. Test each one by asking whether your closest competitor could copy the sentence onto their own page without changing a word. If they could, cut it.

Corporate data

This block exists so a buyer can verify you and buy from you without making a phone call. Include your Unique Entity ID, CAGE code, the NAICS codes you compete under, your size status against the small business size standard for each of those codes, and any socioeconomic designations you hold, such as 8(a), HUBZone, woman owned small business, or service disabled veteran owned. Note that the Unique Entity ID replaced the DUNS number as the official federal identifier when GSA systems switched over on April 4, 2022, so a statement still listing a DUNS number tells the reader nobody has refreshed it in years.

How to write a capability statement

The sequence below keeps the document grounded in verifiable facts rather than adjectives.

1. Confirm your registration and identifiers are current, including your Unique Entity ID, CAGE code, and the NAICS codes on your record.
2. Choose the NAICS codes you genuinely compete under and check your size status against the small business size standard for each one.
3. Draft core competencies in the buyer's language, working from solicitations and market research notices you have actually read.
4. Select two or three past performance references that match the scope and size of the work you are targeting.
5. Write differentiators a competitor could not copy, and delete anything that fails that test.
6. Lay it out on one page, export to PDF so the formatting survives, and name the file with your company name and the date.
7. Build a tailored version for each agency or capability area instead of sending the same page everywhere.

Formatting rules that actually matter

One page is the working convention and two is the practical ceiling. Past that, the document stops being a screening tool and becomes something nobody reads. Use a single readable typeface, keep the contact block and identifiers in a consistent position so a buyer knows where to look, and always send PDF. The Small Business Administration publishes a sample capabilities statement layout that shows the conventional arrangement of the four blocks on a single page.

Where a notice states its own page limit or format requirement, that instruction overrides the convention every time. Agencies do set their own limits, and ignoring one signals how you will treat page limits on the proposal itself.

Why one generic capability statement is not enough

A capability statement written once and sent everywhere is the most common failure mode. The document is supposed to argue that you fit a specific requirement, and a generic page cannot do that. Our guide to responding to a sources sought notice makes the same point from the agency side: an unmodified corporate capability statement that never mentions the requirement gives the contracting officer nothing to act on.

Teams are not unaware of this. The obstacle is that tailoring takes time nobody has when a notice closes in five days. Most teams keep at least four working versions, and the useful discipline is knowing which parts move and which stay fixed.

That makes this a knowledge management problem more than a writing problem. The Consortium for Service Innovation built the Knowledge-Centered Success methodology around exactly this idea: capture knowledge as a byproduct of doing the work, reuse it, and improve it in place instead of rewriting it from memory each time. Its KCS resource library documents the practices, and they apply cleanly here. Past performance summaries, certifications, and competency descriptions are reusable knowledge articles that happen to live inside a marketing document.

When those pieces live in a governed content library with named owners and review dates, producing a tailored capability statement stops being a writing project and becomes an assembly job measured in under an hour. The same discipline that keeps RFP content current is what keeps your capability statement from quietly going stale between opportunities.

If your team sends the same capability statement to every agency because building a tailored one takes too long, the constraint sits upstream of the document. See how the RocketDocs RFP response solution keeps approved past performance, certifications, and capability content current and reusable, then book a demo to see it run against a real opportunity.