Capability Statement: What It Is, What to Include, and How to Write One

A capability statement is a one-page document that summarizes a company’s core competencies, past performance, differentiators, and federal identifiers for government buyers.

Contracting officers, small business specialists, and prime contractors read it as a business resume: a fast answer to who you are, what you deliver, and whether you qualify.

The strongest statements pair four to six competencies with verifiable past performance and the UEI, CAGE code, and NAICS codes buyers use to verify the firm.

Key Takeaways

 

• A capability statement is a one-page business resume for the government marketplace, built around core competencies, past performance, differentiators, and company data.
• Federal identifiers belong on the page: UEI, CAGE code, NAICS codes, and any socioeconomic certifications such as 8(a), WOSB, SDVOSB, or HUBZone.
• Buyers give the document a first read of about six seconds, so the layout must surface qualifications without scrolling or page-turning.
• A targeted version, rebuilt for a specific agency or prime contractor, outperforms a general version in most pursuits.
• The CRED framework (Competencies, Results, Essential data, Differentiators) sequences the build so every line earns its space.

What Is a Capability Statement?

 

A capability statement is a concise marketing document that government contractors use to introduce their company to federal, state, and local buyers.

It condenses the firm’s qualifications onto a single page in the format contracting personnel expect. Buyers, program managers, and prime contractor representatives request it before any other document.

Some solicitations list it as a prerequisite: vendors must submit a capability statement before they can quote, bid, or propose.

The document introduces; a proposal persuades. A capability statement opens the door, and the pursuit that follows runs through the full solicitation cycle. Contractors should also know how to write a business proposal once the introduction lands.

The Four Core Sections of a Capability Statement

 

Core Competencies

 

Core competencies are the four to six concrete capabilities the company sells, phrased in the keywords buyers use. Contracting officers and small business specialists search the SBA’s Dynamic Small Business Search by capability keywords and NAICS codes.

The language on the page should match the language in those searches. “IT services” finds nothing; “cloud migration for FedRAMP Moderate environments” finds a buyer.

Past Performance

 

Past performance lists verifiable contracts: the agency or client, the contract value or scope, and the outcome.

Buyers weigh this section the way they weigh reference checks, and agencies making public sector procurement awards score prior delivery as a formal evaluation factor. New entrants without federal contracts can list commercial work, subcontracts, and state or municipal projects instead of leaving the section blank.

Differentiators

 

Differentiators answer one question: with fifty firms registered under the same NAICS code, the buyer needs a reason to call yours.

Strong differentiators name proprietary methods, niche certifications, security clearances, geographic reach, or response times a competitor cannot copy-paste. Weak differentiators claim commitment to excellence, which competitors also claim.

Company Data and Identifiers

 

The data block carries the identifiers buyers need to verify and register the firm: Unique Entity ID (UEI), CAGE code, primary and secondary NAICS codes, and socioeconomic certifications.

Add acceptance of government purchase cards where relevant, plus a direct contact with name, phone, and email. A missing CAGE code sends the reader to a competitor’s page rather than to a lookup tool.

Certifications and Set-Asides That Belong on the Page

 

Socioeconomic certifications change which contracts a firm can win, so they belong near the top of the data block.

The SBA’s contracting assistance programs cover the 8(a) Business Development program, Women-Owned Small Business (WOSB), Service-Disabled Veteran-Owned Small Business (SDVOSB), and HUBZone certification.

Federal agencies must direct a share of contract dollars to each category, and contracting officers search for certified firms to meet those goals. A certified firm that leaves the certification off its capability statement hides its strongest set-aside advantage.

General vs Targeted Capability Statements

 

A general capability statement serves the firm’s SAM.gov profile, DSBS listing, and networking events. One version, current identifiers, broad competencies.

Writers rebuild the targeted capability statement for a specific agency, opportunity, or prime contractor.

The writer reorders competencies against the buyer’s stated needs, swaps in the past performance closest to the scope, and mirrors the vocabulary of the solicitation or the agency’s mission page. The targeted version takes longer to produce and wins more meetings, because the reader sees their own requirements reflected on the page instead of a generic brochure.

The CRED Framework for a Capability Statement That Gets Read

 

The Write Direction developed the CRED framework to sequence the build so every line earns its space on the page.

• Competencies first. Draft the four to six capabilities in the buyer’s search keywords before touching design. The competencies drive the DSBS match, the six-second scan, and the reader’s decision to keep going.
• Results, quantified. Convert past performance into numbers: contract values, delivery timelines, performance ratings, renewal counts. A line that reads “delivered 14 task orders across three DHS components with zero missed deadlines” outworks a paragraph of description.
• Essential data, findable in seconds. Place the UEI, CAGE code, NAICS codes, and certifications in a fixed block the reader can locate without hunting. Buyers copy these identifiers into their systems, and friction here costs the follow-up call.
• Differentiators a competitor could not sign. Test each differentiator by asking whether a rival firm could paste it onto their own page without lying. Cut every line that passes the test.

Formatting Rules That Keep It to One Page

 

Keep the document to one page and deliver it as a PDF that prints clean in black and white. The layout should carry the company logo, consistent brand colours, and a column or block structure a reader can scan in seconds.

Contracting reviewers give an unsolicited document a first read of about six seconds before they file it or forward it. Dense paragraphs, mission statements, and company history filler consume the space that competencies and identifiers need.

The same plain-language discipline that governs business writing in government RFPs applies here at higher compression: short lines, concrete nouns, zero jargon.

Where to Use a Capability Statement

 

The document works across the full pursuit cycle:

1. SAM.gov profile. Firms registered through SAM.gov entity registration can reference the capability statement in their profile, where buyers conducting market research find it.
2. DSBS listing. Small businesses appear in DSBS searches, and the capability narrative there should mirror the statement’s competencies.
3. Sources sought and RFI responses. Agencies run market research before issuing a solicitation, and a capability statement attached to a sources sought response shapes the requirement in the firm’s favour.
4. Industry days and matchmaking events. The printed one-pager replaces a pitch when the conversation lasts three minutes.
5. Prime contractor outreach. Primes hunting subcontractors to meet small business subcontracting plans review the document before any teaming call.
6. Contracting officer emails. A short introduction with the PDF attached is the standard cold approach in federal sales.

The capability statement starts conversations that solicitations finish. Firms should understand what an RFP is in government contracting and the full government RFP process before the introduction turns into a live pursuit.

Common Capability Statement Mistakes

 

• Generic competencies. “Professional services” matches no buyer search and answers no need.
• Unverifiable past performance. Claims without an agency name, scope, or value read as decoration. Buyers check.
• Missing identifiers. A page without a UEI or CAGE code fails the reader’s first verification step.
• Multiple pages. Page two goes unread and signals the firm cannot follow government norms.
• One version for every audience. A general statement sent against a specific opportunity loses to a targeted one.
• Mission-statement filler. Vision paragraphs displace the competencies and data the reader came for.

The Write Direction audits client statements against each of these failure points. Our team then rebuilds the page with the compliance discipline in our RFP compliance checklist, because the habits that win proposals start with the first document a buyer sees.

Frequently Asked Questions

 

What is the purpose of a capability statement?

 

A capability statement introduces a company to government buyers and prime contractors.

It gives contracting officers a one-page summary of core competencies, past performance, differentiators, and federal identifiers. The reader can decide within seconds whether the firm fits a requirement, a set-aside goal, or a teaming need.

How long should a capability statement be?

 

One page. Government buyers expect a single page, and reviewers give an unsolicited document a first scan of about six seconds. Firms with broad service lines should build separate targeted versions per capability area rather than extend the page, since a second page goes unread in most cases.

Is a capability statement required for government contracts?

 

No law requires one, but many solicitations and market research notices request a capability statement as a prerequisite to quoting or proposing. In practice, contracting officers, small business specialists, and prime contractors ask for it as the first document, which makes it a working requirement for federal sales.

What is the difference between a capability statement and a proposal?

 

A capability statement is a one-page marketing introduction sent before any solicitation, with no pricing and no contractual commitment. A proposal responds to a specific RFP with a technical approach, past performance volume, and cost, and it can lead to a contract award. The first opens doors; the second wins work.

How often should you update a capability statement?

 

Review it quarterly and update it whenever a contract closes, a certification changes, or the firm adds a NAICS code. Stale past performance and expired certifications damage credibility during buyer verification. Firms in active pursuit cycles should also rebuild the targeted version for each new opportunity rather than reuse the last one.

Put Your Qualifications on One Page That Works

 

A capability statement earns its keep when a contracting officer can read it in six seconds, verify the firm in one search, and forward it with confidence. The four sections, the identifiers, and the targeted rebuild per opportunity turn a brochure into a sales tool.

At The Write Direction, we write capability statements, RFP responses, and the supporting procurement documents that carry government contractors from first contact to contract award.

Our writers build the page around the keywords your buyers search and the evidence they verify. Book a consultation to discuss your capability statement, or email us at [email protected] to get started.