Building a Capability Statement for Government Contracting

Last reviewed on May 12, 2026.

What a capability statement is for

A capability statement is a one-page (occasionally two-page) summary of your firm that contracting officers, small business specialists, and prime contractors use to decide whether to talk to you further. It is not a brochure, not a marketing flyer, and not a substitute for a proposal. It does one job: convince a busy reader, in under sixty seconds, that your firm can solve a problem they have.

Contracting officers commonly request capability statements at industry days, in response to sources sought notices, and during market research before a solicitation is issued. The document is also the most-requested attachment when a small business specialist asks to know more about your firm.

The six standard sections

Most effective capability statements include these elements, usually arranged on a single page:

1. Header

Your company name, logo, and a single-sentence tagline that names your industry and primary differentiator. The tagline should be specific — "cleared cybersecurity engineering for civilian agencies" beats "innovative IT solutions."

2. Core competencies

Three to five service lines, stated in the language the customer uses. If your target agency calls it "cloud migration services," don't call it "digital transformation enablement." Each competency should be one short phrase, not a paragraph.

3. Differentiators

Why a contracting officer should pick your firm over a comparable one. Real differentiators are concrete — geographic presence near the customer, specific clearances held, a methodology with proven outcomes. "Customer-focused" and "agile" are not differentiators.

4. Past performance

Three to six representative contracts. Each entry should name the agency, contract number, period of performance, and contract value. Include outcomes only if you can cite them accurately — a phrase like "reduced backlog from 1,200 to 200 tickets in eight months" beats "improved efficiency."

5. Company data

UEI, CAGE code, NAICS codes (with size standard for each), set-aside certifications (8(a), SDVOSB, WOSB, HUBZone, as applicable), and date the firm was founded. This is what contracting officers copy into their systems.

6. Contact block

A single point of contact: name, title, email, phone number, and website. Use a person, not a generic "info@" mailbox. Multiple POCs make the reader guess; the goal is to make it easy to start a conversation.

A worked example: structure of an effective page

Imagine a small environmental services firm submitting a capability statement to an Army Corps of Engineers small business specialist. The structure might be:

Top band: Company name, logo, tagline ("Environmental remediation and compliance for federal facilities, Southeast region").
Left column: Core competencies — Phase I/II/III environmental site assessments; CERCLA and RCRA remediation; air and water permitting support; environmental compliance audits.
Right column: Differentiators — Five years of USACE district experience; in-house EPA-licensed asbestos and lead inspectors; 24-hour emergency response within a defined geographic footprint; ISO 14001 certified management system.
Middle band: Past performance — three USACE projects with contract numbers, dollar values, and a one-line outcome each.
Bottom band: UEI, CAGE, primary NAICS (562910 environmental remediation, $25M size standard), secondary NAICS, SDVOSB and small business indicators, and contact block.

The whole document is one page. A reader can extract every piece of information they need without scrolling or flipping pages.

What separates a good capability statement from a generic one

Specificity. Generic statements use abstractions ("solutions," "transformation," "synergies"). Effective statements use concrete words a contracting officer can search for in their solicitation drafting tool.
Customer language. If your target buyer is the VA, mirror VA's program names. If it is the Air Force, use Air Force terminology. The same firm may legitimately have two or three capability statements aimed at different agency families.
Recent and relevant past performance. Five-year-old contracts in a different sector are less useful than smaller, more recent contracts in the target buyer's domain. Include relevance, not just impressiveness.
Visual scannability. Two columns, clear section headers, and a single typeface family help a reader extract data in seconds. A solid wall of text wastes the format.

Common mistakes

Two or three pages. If it does not fit on one page, the structure is wrong. Compress.
Marketing prose where data belongs. "Our team brings decades of combined experience" tells the reader nothing. List the contracts, the agencies, the dollar values.
Fabricated or exaggerated past performance. Contracting officers verify contract numbers in FPDS and may call references. A discovered embellishment ends the conversation permanently.
Generic stock graphics. A photo of an office building or a handshake adds nothing. If you use imagery, use it to show actual project work.
Outdated certifications. An expired 8(a) date or stale CAGE code signals a firm that doesn't maintain its registrations. Update at every renewal cycle.
One capability statement for every audience. A statement optimized for civilian agencies will not work well for DoD. Maintain a small number of audience-specific versions if you target distinct customer groups.

How often to refresh

At a minimum, review the capability statement every six months and revise whenever:

A new significant contract has been awarded and can be added to past performance
A certification status changes (a new set-aside has been earned or an existing one has lapsed)
NAICS codes in SAM are updated
The firm changes addresses, points of contact, or banking information

Where to share it

Sources sought notices. When an agency posts a request for capability information before a solicitation, this is the document to send.
Industry days. Hand the printed version directly to the contracting officer and small business specialist.
Prime contractor outreach. When introducing your firm to a prime as a potential subcontractor, lead with the statement.
Agency Office of Small and Disadvantaged Business Utilization (OSDBU) meetings. Bring the statement to every OSDBU meeting.
Your own website. Host a PDF version at a stable URL so you can link to it in introduction emails.

Building a Capability Statement