Federal contracting officers review dozens of capability statements a week. Most end up ignored because they read like product brochures written by a committee. This guide covers what those officers actually want to see, what disqualifies you before they finish the first paragraph, and how to get your document in front of the right people.
What a capability statement is (and is not)
A capability statement is a 1-2 page marketing document that summarizes your business for federal buyers. Contracting officers at agency Office of Small and Disadvantaged Business Utilization (OSDBU) offices, small business specialists, and prime contractors use it to quickly assess whether your business is a fit for an upcoming procurement.
It is not a resume. It is not a brochure. It is not a white paper.
One page is better than two. Two pages is the hard ceiling. If you cannot explain what you do and why you are credible in that space, the problem is not page count.
The 5 required elements
1. Core competencies
This is the section most businesses get wrong. Core competencies are not a list of industries you have worked in. They are specific technical or professional capabilities tied to NAICS codes and deliverables.
Bad: "We provide IT services and consulting."
Better: "Enterprise network architecture and implementation (NAICS 541512). Cisco-certified team of 14 engineers. Cleared to Secret. Delivery experience on LAN/WAN, zero-trust segmentation, and SD-WAN rollouts across DoD and civilian environments."
Write three to five competency statements. Each one should answer: what exactly do you do, and who on your team does it.
2. Past performance
This section either builds trust or destroys it. List two to five contracts with actual detail. Federal buyers want contract numbers, agency names, dollar values, and dates.
Weak: "Delivered IT support to federal agencies."
Credible: "USDA Forest Service, Contract GS-35F-0123X, 2022-2024. $1.4M. Deployed and managed network monitoring infrastructure across 14 field offices in three regions."
Include a point of contact if you have permission. A real name and phone number on a past performance reference is worth more than three vague bullet points.
If you are a new business with no federal contracts, list relevant state, local, or commercial contracts. Be honest about where you are in the process. Contracting officers know what a startup looks like; they do not appreciate discovering you misrepresented your experience.
3. Differentiators
What do you do that your competitors do not? This section typically runs three to five bullet points. Be specific.
Weak: "We deliver high-quality work on time."
Specific: "FedRAMP-authorized cloud environment ready for ATO. Two cleared project managers on staff. 97% on-time delivery across 23 federal task orders in FY2023."
If you hold certifications (8(a), WOSB, HUBZone, SDVOSB, veteran-owned), list them here with certification numbers and expiration dates. Contracting officers use set-aside categories to meet their socioeconomic goals. Make it easy to verify your eligibility.
4. Company data
Every capability statement needs this block, formatted cleanly:
- UEI: Your Unique Entity Identifier from SAM.gov (replaced DUNS as of April 2022)
- CAGE Code: Your Commercial and Government Entity code
- NAICS Codes: Your primary NAICS code first, then two to four secondary codes
- Business size: Small, woman-owned, veteran-owned, 8(a), HUBZone, etc.
- Founded: Year established
- Employees: Current headcount
- Bonding capacity (if relevant to construction or service contracts)
- Facility clearance level (if applicable)
Missing NAICS codes is one of the most common reasons a capability statement gets set aside. A contracting officer searching for 541330 (Engineering Services) will not look up whether your description matches that code. Include the code.
5. Contact information
Name, title, phone, email, and website. Some businesses add a QR code linking to their SAM.gov profile or a digital version of the statement.
Use a named contact, not a generic inbox. "info@company.com" signals that nobody specific owns business development.
How to tailor your capability statement to a specific agency
A generic capability statement is worse than no capability statement. When you send the same document to every agency, it reads like spam.
Before you send anything, spend 30 minutes reading the agency's strategic plan, their OSDBU forecast, and any Broad Agency Announcements (BAAs) relevant to your work. The SBA's DSBS database and agency procurement forecasts (published annually by most civilian agencies) tell you what they are buying and in what categories.
Then do three things:
Mirror their language. If the agency's strategic plan uses the phrase "zero-trust architecture," use that phrase in your competencies section. If they reference "mission-critical IT modernization," use that language, not yours. Federal procurement is full of agency-specific terminology. Match it.
Reference their mission. One sentence connecting your work to what that agency does is more persuasive than a general company description. "We have supported similar forest inventory digitization efforts for the USDA, which aligns with your agency's land management data modernization objectives" is more credible than a generic paragraph about your commitment to excellence.
Adjust the highlighted past performance. If you are targeting DHS, lead with your civilian agency contracts. Targeting DoD? Lead with any defense experience, even if it was subcontract work.
Keep a master capability statement and a folder of tailored versions. The core competencies and company data stay the same. The past performance section and the opening summary get adjusted.
What makes a capability statement stand out
Specificity. That is the entire answer.
Contract numbers beat company descriptions. Dollar values beat vague references. Named agencies beat "various federal clients."
A few things that consistently differentiate strong capability statements:
- Clearances: If your team holds clearances, list them. TS/SCI, Secret, Public Trust. Include the number of cleared personnel. This is a real filter for many procurements.
- Certifications with dates: List 8(a) graduation date or expiration, WOSB certification number, HUBZone designation. Expired certifications on a capability statement signal disorganization.
- Subcontract history: If you have performed as a subcontractor to Booz Allen, Leidos, SAIC, or similar primes, list it. Primes looking for subs recognize their peers' contract vehicles and quality standards.
- GSA Schedule number: If you hold a GSA Multiple Award Schedule (MAS), include it. Schedule holders get requests they never solicited because they are searchable in GSA Advantage.
Design matters less than people think, but legibility matters a great deal. Use a clean layout with enough white space to scan quickly. One color accent is fine. Stock photos are not.
Common mistakes
Too long. Two pages maximum. Three pages means two things did not get cut that should have.
No NAICS codes. Already covered. Include them.
Vague competencies. "We support government clients with technology solutions" tells a contracting officer nothing they can act on.
Outdated SAM.gov registration. Your SAM registration must be active to receive a federal award. Contracting officers check. An expired registration on your company data block will end the conversation.
Forgetting subcontracting opportunities. Large prime contractors at companies like Lockheed Martin, CACI, and ManTech have their own small business outreach programs. A capability statement tailored for prime outreach should emphasize your availability as a sub, your clearance posture, and your subcontract past performance.
Generic contact info. A shared inbox or a missing phone number signals that nobody specific is accountable for business development.
Template structure
Use this as a starting framework:
``` [Company Logo] [Tagline — one short sentence]
CORE COMPETENCIES • [Competency 1 — NAICS code, specific capability, credential] • [Competency 2] • [Competency 3]
PAST PERFORMANCE • [Agency, Contract #, Year, Dollar Value, 1-sentence description] • [Agency, Contract #, Year, Dollar Value, 1-sentence description] • [Agency, Contract #, Year, Dollar Value, 1-sentence description]
DIFFERENTIATORS • [Certification with number and expiration] • [Clearance level and # of cleared personnel] • [Specific metric or technical credential]
COMPANY DATA UEI: [number] CAGE: [code] NAICS: [primary], [secondary codes] Founded: [year] Employees: [count] Certifications: 8(a) | WOSB | HUBZone | SDVOSB | [other]
CONTACT [Name, Title] [Phone] | [Email] [Website] | [SAM.gov profile link] ```
How to distribute your capability statement
OSDBU offices. Every major federal agency has an Office of Small and Disadvantaged Business Utilization. Their websites list small business specialists by category. Email is the standard approach. Keep it short: two sentences about your company, attach the capability statement, ask for 15 minutes.
Small business specialists. Agency websites publish directories. Some agencies, including the Army Corps of Engineers and NASA, post procurement forecasts that list the small business specialist assigned to each anticipated procurement. Target those names directly.
Industry days and matchmaking events. The SBA, APEX Accelerators, and agencies themselves host these regularly. Bring printed copies. Exchange business cards. Follow up within 48 hours with your capability statement attached.
GovWin IQ. Deltek's GovWin platform maintains a capability statement repository that prime contractors and agencies use when searching for subs and small businesses. A free basic profile exists; the paid tier gives you more visibility.
Beta.SAM.gov. Your SAM.gov registration includes a place for a capabilities narrative. Fill it out. It feeds into the DSBS database that agencies use to find small businesses.
Prime contractor portals. Lockheed Martin, Northrop Grumman, Raytheon, and most large primes have supplier diversity portals where you can register and upload your capability statement. Registration takes 20 minutes and puts you in a database that subcontract managers search.
Update your capability statement at least once a year. Refresh past performance as contracts close, update certifications before they expire, and adjust your NAICS codes if your business scope has changed. A capability statement with a 2021 contract as your most recent reference tells the reader that nothing has happened since then.
