A capability statement is a one-page document that markets your business to federal buyers. Most are ignored. Here's what contracting officers actually look for and how to structure yours.
What a Capability Statement Actually Is
A capability statement is not a brochure. It is not a resume. It is not a marketing flyer with your logo and tagline on it.
A capability statement is a structured one-page document — occasionally two pages at most — that gives a federal contracting officer, small business specialist, or prime contractor the specific information they need to evaluate whether your business is a credible source for the work they have to award.
The people reading your capability statement are busy. They have a stack of them. They are scanning for three things, in roughly this order: Do you have the relevant experience? Are you registered and compliant? Is your contact information complete? If the answer to all three is yes, your capability statement has done its job. If the answer to any is no, it goes in the rejection pile — or more accurately, it never comes out of the unsolicited materials folder.
Everything about how you write and format a capability statement should be organized around those three questions.
The Five Required Sections
### Section 1: Core Competencies
This is the first thing they read and the first filtering decision they make. Core competencies should be a clear, concise list of the specific services or products your business provides — written in the language of federal procurement, not marketing language.
Bad: "We deliver transformative digital solutions that accelerate organizational agility."
Good: "Custom software development (NAICS 541511), IT systems integration (NAICS 541512), cloud migration and managed services (NAICS 541519)"
Federal buyers search by NAICS code. Including your relevant NAICS codes in the core competencies section connects your description directly to the codes they use to find vendors.
Keep core competencies focused. Three to seven bullet points is the right range. A list of fifteen competencies signals that the business does not know what it is.
### Section 2: Past Performance
Past performance is the credibility section. For federal contracting, past performance must reference actual contracts — not client references in the general sense, but specific engagements with enough detail to be verifiable.
For each reference, include:
- ▸Agency or prime contractor name
- ▸Contract number (if federal)
- ▸Contract value
- ▸Period of performance
- ▸Brief scope description (one to two sentences)
- ▸Outcome or performance highlight if available
New businesses without federal past performance can use relevant commercial work or sub-contractor experience. Be honest about what you have. Fabricating or inflating past performance is a federal contracting violation with criminal exposure.
Two to four strong references are more effective than seven weak ones.
### Section 3: Differentiators
This section answers the question: why you over the other small businesses who do the same thing? This is where you earn attention rather than just passing the compliance filter.
Effective differentiators are specific and defensible:
- ▸Proprietary methodologies or tools with a defined outcome
- ▸Certifications specific to the work (ISO, CMMC, specific security clearances)
- ▸Geographic or demographic reach relevant to the agency's mission
- ▸Speed to mobilize based on past performance data
- ▸Specific technology expertise in a platform the agency uses
- ▸Awards, recognition, or performance ratings from prior federal work
Avoid generic differentiators: "committed team," "customer focus," "quality work." Every business says this. None of it differentiates.
### Section 4: Company Data
This is the compliance data section. Include:
- ▸Legal business name (exactly as in SAM.gov)
- ▸Physical address
- ▸CAGE code
- ▸UEI
- ▸DUNS number if you have historical records referencing it (legacy, but occasionally still requested)
- ▸SAM.gov registration status and expiration date
- ▸Business type (LLC, corporation, etc.)
- ▸Small business certifications (8(a), HUBZone, SDVOSB, WOSB, MBE — whatever applies)
- ▸Primary and secondary NAICS codes with their size standard thresholds
- ▸PSC codes if relevant to your business
- ▸Fiscal year revenue (optional, but useful context for size)
Contracting officers sometimes verify SAM.gov status directly — making sure your capability statement matches your SAM.gov record is basic due diligence.
### Section 5: Contact Information
Make this findable and redundant. Include:
- ▸Primary contact name and title
- ▸Phone number (direct line, not a main number that routes to a queue)
- ▸Email address (use a role-based address — contracts@yourdomain.com — that persists through staff changes)
- ▸Physical address
- ▸Website
- ▸LinkedIn (optional, but increasingly expected)
The contact information section is where a significant percentage of otherwise good capability statements fail. If a contracting officer cannot reach you in under 30 seconds, they move on.
The One-Page Rule
One page. There are exceptions — highly technical work, agencies with specific requirements — but start with one page as your default and build a case for why you need two before breaking the rule.
The one-page constraint is not arbitrary. It reflects the reality that capability statements compete for attention with dozens of others. A document that requires two pages to get to the point is telling the reader that the business cannot prioritize.
Design it as a document, not a text file. Use columns, borders, and typography to create visual hierarchy that guides the reader's eye to the high-value information: core competencies, key past performance, certifications, contact. White space is not wasted space.
Formatting Dos and Don'ts
**Do:** Use your brand colors and logo — capability statements are marketing documents, not government forms. Consistent branding makes you memorable.
**Do:** Use clear section headers that match the five required sections — make it easy to navigate.
**Do:** Include your CAGE code and certifications prominently — these are the first things small business specialists look for.
**Don't:** Use small font to cram more content. If you cannot say it at 10–11pt font with normal margins, you have too much content.
**Don't:** Use stock photos or decorative imagery. The document should be text and data, organized visually. Images that are not substantive (logos, perhaps certification badges) belong in a brochure, not a capability statement.
**Don't:** Use jargon that is not recognizable in federal procurement. Contracting officers are not reading to understand your internal terminology — they are scanning for familiar signals.
Digital vs. Print Versions
You need both, configured differently.
The print version is for industry days, small business events, and physical mail to procurement offices. It should be formatted for single-sided 8.5x11 printing in color.
The digital version should be a PDF optimized for screen viewing, with hyperlinks active: website, email address, LinkedIn profile, and SAM.gov entity search link with your CAGE code. Add metadata to the PDF file (title, author, keywords) that makes it findable in a document management system.
File naming matters. A file named "Capability_Statement.pdf" is unfindable in a folder with 50 other files named "Capability_Statement.pdf." Name yours: "ACME_Consulting_CapabilityStatement_541511_2026.pdf" — your company name, document type, primary NAICS, and year.
Agency-Specific Customization
A single generic capability statement is better than none. An agency-specific capability statement is significantly better than generic.
Before submitting to a specific agency or responding to a specific small business opportunity:
1. Research the agency's mission and current priorities
2. Identify which of your capabilities are most relevant to their work
3. Revise the core competencies and differentiators section to lead with those specific capabilities
4. Add past performance references most relevant to the agency's work
5. Reference the specific program office or contracting officer if known
The customization signals that you have done your homework. Contracting officers notice. Small business specialists who refer vendors to program offices remember which companies they have to explain versus which companies showed up prepared.
Key Takeaways
- ▸A capability statement is a structured data document, not a marketing brochure — the audience wants specific information, not persuasion
- ▸The five required sections are: core competencies, past performance, differentiators, company data, and contact information
- ▸NAICS codes belong in the core competencies section — federal buyers search by NAICS
- ▸Past performance must reference verifiable specific engagements with contract numbers and outcomes
- ▸One page is the default — break it only when there is a documented reason to do so
- ▸Maintain both a print and a digital (PDF with hyperlinks) version with descriptive file names
- ▸Customize for each target agency — generic capability statements signal generic contractors
Share this article
