The federal capability statement that wins contracts (with a template)

Spend any time around federal buyers and you hear the same line. A contracting officer at an industry day, a small-business specialist on a call, a prime sizing you up for their team: "Send me your capability statement." It is the first document almost everyone in federal contracting asks for, and the one most new firms either don't have or get wrong.

A capability statement is a one-page summary of what your business does, who you've done it for, and the codes a buyer needs to find and contract with you. Think of it as a résumé for your company, written for someone who has thirty seconds and a specific problem to solve. It is not a brochure. It is not your About page. It is a working document a contracting officer can glance at and decide, in a few seconds, whether to keep reading.

When buyers actually ask for it

The capability statement shows up at every stage of the federal sales cycle, and it does different jobs at each.

Early on, you attach it to a response to a sources sought notice or a request for information, where an agency is doing market research before it writes a solicitation. A clean one-pager that maps to what they're buying can put you on the list of firms they're considering for a set-aside.

Later, you hand it to a prime contractor when you want a spot on their team, or you email it cold to a small-business specialist whose job is to steer work toward firms like yours. Some buyers will pull up your Dynamic Small Business Search profile and expect the capability statement to match it. The document is small. The number of doors it has to open is not.

The six sections buyers expect

There is no federal form for this. But over years of agencies asking and firms answering, the format has settled into six recognizable parts. The SBA's own 8(a) capability statement guide follows the same shape. Skip one and an experienced buyer notices the gap.

1. Company overview. Two or three sentences. Who you are, what you do, where you operate. No mission-statement filler.
2. Core competencies. The actual work you perform, in plain terms that match what the agency buys. This is the section buyers read first.
3. Past performance. A short, specific record of similar work: the customer, the scope, the outcome.
4. Differentiators. The concrete reasons to pick you over the firm below you on the list.
5. Company data. Legal name, business structure, year established, and where you fit by size.
6. The codes block. Your UEI, CAGE code, NAICS and PSC codes, set-aside status, and contact details. The machine-readable part a buyer copies into their system.

Most firms get the contact details right and treat the other five sections as an afterthought. The contracting officer reads them in roughly the opposite order of how much effort they got.

Core competencies that don't sound generic

This is where almost every weak capability statement falls apart. "We provide innovative, customer-focused solutions tailored to client needs" tells a buyer nothing. It describes every vendor who has ever existed. A contracting officer reading it learns only that you don't know how to describe yourself.

The fix is concrete language that maps to a budget line. Compare these:

• Weak: "IT solutions and services."
• Strong: "Network engineering and 24/7 SOC monitoring for DoD networks at IL4 and IL5."

• Weak: "Facilities and maintenance support."
• Strong: "HVAC preventive maintenance and emergency repair for federal buildings over 100,000 square feet."

The strong versions name the work, the environment, and the scale. A buyer can read them and immediately know whether you fit the solicitation in front of them. Write each competency as something an agency would put in a statement of work, not something a marketing intern would put on a banner. If a competency could belong to any company in your industry, it isn't a competency. It's filler.

A practical test: read each line and ask whether a competitor could copy it onto their own statement without changing a word. If yes, rewrite it until they can't.

Past performance and differentiators

Past performance is where you prove the core competencies are real. Keep it to a few entries, and for each one name the customer, the contract scope, the period, and the result. "Provided IT support to a federal agency" is weak. "Operated the help desk for 4,200 users at [agency], 2023 to 2025, 98% SLA compliance" is the version a buyer trusts. If you don't have federal past performance yet, use commercial or subcontract work that demonstrates the same scope. Buyers care that you've done the work, not only that you've done it for them.

Differentiators are the tiebreaker. Drop the empty claims ("quality," "integrity," "experienced team") and list the things a competitor can't simply assert. A facility security clearance. Cleared staff. A specialized certification like ISO 9001 or CMMI. A piece of equipment most small firms don't own. A repeatable process that lowers the buyer's risk. These are the lines that move you up the list when two firms look otherwise identical.

The codes block: UEI, CAGE, NAICS, PSC, set-asides

This is the part a contracting officer copies straight into their system, so accuracy matters more than prose. Include:

• UEI (Unique Entity ID). The 12-character alphanumeric identifier SAM.gov issues. It replaced the old DUNS number on April 4, 2022, and it's how every federal system refers to your business. If you don't have one yet, that's step one. Our SAM.gov registration guide walks through getting it, and it's free.
• CAGE code. The five-character Commercial and Government Entity code assigned by the Defense Logistics Agency during or after your SAM registration. Required for defense work, expected everywhere.
• NAICS codes. The industry codes that classify what you do. List the ones that genuinely fit, not a wall of every code you might brush against. If you're unsure which apply, our NAICS lookup gets you the right codes and the size standards attached to them.
• PSC codes. Product Service Codes, the buyer's-eye view of what's being purchased. Including the right ones helps your statement match how agencies categorize the spend.
• Set-aside status. Any socioeconomic designation you hold: 8(a), HUBZone, WOSB or EDWOSB, SDVOSB, or a small-business size status. This is often the reason a buyer picked up your statement in the first place, so make it easy to find.

Wrong codes here aren't a typo. They route your capability statement to the wrong desk or screen you out of a set-aside you actually qualify for.

Design and length: one page, and it has to read fast

One page. Front side only. A buyer scanning two dozen statements before lunch will not flip yours over, and a two-pager signals that you couldn't decide what mattered.

A few rules that hold up:

• Put your company name, logo, UEI, CAGE, and contact info where the eye lands first, usually a header or a left column.
• Use short blocks and bullets. Nobody reads paragraphs on a capability statement.
• Keep it legible printed in black and white. Some buyers still print these, and a design that depends on color falls apart.
• Save it as a PDF named something a human can recognize, like YourCompany_Capability_Statement.pdf, not final_v7_REAL.pdf.

The mistakes that get statements deleted

A handful of errors show up again and again:

• Generic core competencies that describe every vendor and commit to none.
• A missing or buried codes block. If a buyer can't find your UEI and NAICS in three seconds, you've made their job harder, and they have other statements.
• Past performance with no specifics. Vague claims read as no claims.
• Two pages. It signals you can't prioritize, which is exactly the skill a buyer is screening for.
• Stale information. An expired SAM registration or a set-aside you no longer hold turns a credibility document into a liability.
• Mismatched details. When the statement and your DSBS profile disagree, the buyer trusts neither.

None of these are about talent. They're about discipline, and they're all fixable before you ever hit send.

Build yours in minutes

You can absolutely build a capability statement in a blank document, line up the six sections, and fight with the formatting until it fits on one page. Most people who try that way end up with a file they're slightly embarrassed to send.

The faster path is our capability statement builder. You answer a guided set of questions, drop in your competencies, past performance, and codes, and it produces a clean, one-page, contracting-officer-ready PDF you can attach to a sources sought response or email to a prime today. It's free, and it keeps the structure buyers expect so you don't have to remember the conventions yourself.

Build your capability statement now. Then, if you're working toward set-asides like 8(a), WOSB, SDVOSB, or HUBZone to put a real designation in that codes block, CertifyAll handles the filing across agencies so the certifications behind your statement are working as hard as the document itself.