How to Write a Capability Statement That Wins Work
A capability statement is a one-page PDF. That's it. One page, maybe two if you're generous. Despite being the shortest sales document a federal contractor produces, it does more work than any other: it's the document a contracting officer looks at to decide whether to call you, include you on a source list, or invite you into a limited competition.
Most capability statements are bad. Not because the contractors are bad — because nobody explained what goes on the page and why. This guide walks through what belongs in a capability statement, what doesn't, and how to write one that produces actual call-backs.
What a capability statement is
A capability statement is a federal contractor's one-page résumé. It's distributed to contracting officers, small business specialists, prime contractors evaluating subs, and anyone else who needs a fast read on what your business does and whether you're worth engaging.
It sits at the top of every interaction. You send it before meetings. You attach it to teaming agreements. You upload it to SAM.gov and DSBS. You give it to mentors. You leave it at booth tables. It's your one-page positioning statement across the entire federal ecosystem.
The format is conventional. Government buyers have seen thousands of them. Deviation from the conventional format costs you credibility. Write it the way they expect to see it, then make the content better than everyone else's.
The non-negotiable sections
Five sections. Every capability statement has them. The proportions shift by contractor but the sections don't.
1. Company identity
Top of the page. Company name prominent. Tagline underneath — one sentence that describes what you do in plain English, not marketing language.
Then the identity bar: UEI (your Unique Entity Identifier from SAM.gov), CAGE code, website, email, phone. Contracting officers need these to find you in federal systems. Make them easy to scan.
DUNS is gone as of 2022 — UEI replaced it. If you're still showing DUNS on old statements, remove it.
2. Core competencies
The most important section. This is where the contracting officer decides whether you can do the work. Five to eight bullets, each one a specific capability, not a generic skill.
Bad: "IT services" Better: "Custom software development for federal financial systems" Best: "Custom .NET and Java development for Treasury OFAC screening and sanctions compliance systems"
Specificity signals capability. "IT services" is a category. "Treasury OFAC screening" is a past-performance-backed claim that filters out casual bidders and invites serious conversation.
Don't list every technology you've ever touched. Pick the capabilities that actually win you work and lead with those.
3. Differentiators
Three to five bullets. What makes you different from every other certified small business doing similar work.
Differentiators aren't just certifications (those go in the footer). They're:
- Specific domain expertise (veterans working in VA health informatics, for example)
- Geographic advantage (staff cleared and on-site at specific federal installations)
- Technical credentials (CMMC Level 2, FedRAMP Moderate, ISO certifications)
- Relationships (GSA schedule holder, specific IDIQ vehicle positions)
- Past performance volume (X contracts delivered in your target NAICS)
If you can't name three differentiators that aren't also true of every other SDVOSB in your NAICS, you haven't thought about positioning hard enough.
4. Past performance
Two to four contracts. Each one shows: customer, contract number, period of performance, approximate value, and a one-sentence description of what you delivered.
Choose past performance that matches the work you're trying to win now. If you want federal IT work, don't lead with a commercial landscaping contract. If you're competing for civilian agency contracts, lead with civilian past performance over DoD if both exist.
Contract values are strategic. Too low and you look like you can't handle larger awards. Too high and contracting officers wonder why you're bothering with smaller opportunities. Show the upper end of what you've handled to signal capacity.
Past performance is the single strongest filter in federal contracting. Bad past performance section — missing values, vague descriptions, unrelated contracts — kills your capability statement regardless of how strong the rest is.
5. Certifications and NAICS
Footer. Horizontal. Scan-ability matters more than detail.
Certifications: SDVOSB, 8(a), WOSB, HUBZone, whatever applies. Use the standard abbreviations, not spelled-out versions. Contracting officers recognize the abbreviations instantly.
NAICS: your primary NAICS first, then secondary codes. Mark the primary clearly. Include the title alongside the code ("541512 — Computer Systems Design Services") so readers can understand without looking it up.
What doesn't belong
Things that consistently appear on bad capability statements and shouldn't be there:
Mission statements. Nobody reads them. The tagline under your company name does the positioning work.
Long company history. Contracting officers don't care that you were founded in 2014. They care what you've delivered recently.
Stock photography. Pictures of people shaking hands, server racks, abstract technology imagery. Adds no information, takes up valuable page real estate.
Full bios. The "team" section on capability statements eats space. Point-of-contact with name and title is enough. Full bios belong in proposals, not in the capability statement.
Vague capability claims. "Full lifecycle IT services" — what does that mean? "Strategic solutions" — to what? Cut every phrase that could describe any company in any industry.
Page two. If your capability statement is two pages, you're padding. Edit. The one-page constraint forces prioritization.
Tuning the statement for specific searches
Your capability statement appears in two contexts: pushed (you send it to someone) and pulled (someone finds you and downloads it from DSBS or your website).
For pushed contexts, you can tailor. Build variants for different target agencies or NAICS codes. A VA-focused version leads with VA past performance and emphasizes SDVOSB. A DoD-focused version leads with cleared personnel and relevant DoD past performance.
For pulled contexts, your capability statement has to work for everyone. Keep one canonical version on SAM.gov / DSBS that represents your strongest positioning, and use the capability statement builder to generate variants for specific outreach.
Language matters for search. Contracting officers search DSBS with specific terminology. If your capability statement says "cyber risk advisory" but they search "cybersecurity consulting," you miss. Mirror the language of your target NAICS and your target agencies' contract solicitations.
Common mistakes
Treating the capability statement as a static document. A statement you wrote three years ago probably needs to be rewritten. New past performance, updated NAICS, current certifications, refreshed competencies. Plan to rewrite annually at minimum.
Not updating DSBS when the statement changes. Dynamic Small Business Search has its own profile and capability description field. Keep DSBS in sync with your statement. Some contracting officers search DSBS exclusively and never see your website.
Missing UEI or CAGE code. The first thing a contracting officer does is verify you're real and registered. No UEI = no seriousness = no call back.
Long paragraphs. Capability statements are scan documents. If a paragraph is more than two lines, someone is reading too much. Break everything into bullets.
Too many NAICS codes. Same mistake as in the NAICS selection. 15 NAICS on a capability statement looks unfocused. Pick 3-7 that reflect where you actually work.
Inconsistent branding. Your capability statement, website, and SAM.gov profile should look and sound like the same company. Contracting officers checking you across systems will notice inconsistencies.
Strong vs. weak: a quick comparison
Weak past performance entry:
Federal agency, software development, $1M-$5M
That tells the reader nothing. What agency? What kind of software? What contract number? When?
Strong past performance entry:
US Department of the Treasury, OFAC · 2022-2024 · $2.4M Contract HHS-OS-23-001: Delivered modernized sanctions screening platform processing 50M+ transactions daily with sub-second latency. Migrated legacy COBOL batch processing to cloud-native microservices architecture.
Specificity at every level. Customer, period, value, contract number, actual outcome, technical approach. A contracting officer reading this knows whether you can do similar work for them.
Same principle applies to every section. Specificity earns attention. Generality gets ignored.
Next steps
Use the capability statement builder to draft yours. The form walks through each section, the preview shows the 1-page PDF live, and the download gives you a file you can upload to SAM.gov and DSBS today.
Once your capability statement is solid, the next positioning work is NAICS alignment. Check the NAICS recommender to validate your codes match where federal demand actually lives. And if you haven't calculated your loaded labor rates, the wrap rate calculator is the companion tool for proposal pricing.
For help reviewing your capability statement — or building one from scratch for a specific agency or NAICS — schedule a 15-minute consultation.