What should a capability statement page include?
A capability statement page should show who you are, what you do best, why a buyer should pick you, and the identifiers a contracting officer needs to look you up: your UEI, CAGE code, NAICS codes and set-aside status. Add a short company overview, your core competencies, differentiators, past performance you are cleared to share, contact details and a downloadable PDF.
Think of it as the page a contracting officer opens when they have two minutes and a short list of companies. If they can find your identifiers and understand what you do in that time, you stay on the list.
What is a capability statement, and why put it on a web page?
A capability statement is a short summary of your business, usually one page, that you send to government buyers and prime contractors. A web page version does three extra jobs that a PDF alone cannot do:
- It can be found. Search engines read text on a page far more reliably than text locked inside a PDF.
- It stays current. You update one page instead of chasing old PDFs in old emails.
- It is easier to read on a phone and with assistive technology, which matters for government buyers.
Keep the PDF too. Buyers often want something they can attach to a file. The page and the PDF should say the same thing.
Which identifiers belong on the page?
These are the details buyers use to confirm you are real and registered. Each one should match your registration exactly.
| Item | What it is | Where it comes from |
|---|---|---|
| UEI | Unique Entity ID, the identifier for your business in federal systems | Assigned when you register in SAM.gov |
| CAGE code | Commercial and Government Entity code that identifies your business | Issued through your SAM.gov registration |
| NAICS codes | Industry codes that describe the work you do | You choose them and list them in SAM.gov |
| Set-aside status | For example SDVOSB, VOSB, 8(a), WOSB or HUBZone | Only what you actually hold |
| Contract vehicles | For example a GSA schedule | Only vehicles you are on |
Two rules keep this section trustworthy. First, copy the details from your active SAM.gov registration so nothing differs between the website and the registry. Second, list the NAICS codes that describe your real work, with your primary code first, rather than a long list of everything you could do.
What else goes on a capability statement page?
flowchart TD
A[Company overview] ==> B[Core competencies]
B ==> C[Differentiators]
C ==> D[Past performance]
D ==> E[Company data: UEI, CAGE, NAICS, status]
E ==> F[Contact and PDF download]
Work through the page in this order:
- Company overview. Two or three plain sentences: what you do, for whom, and where you are based.
- Core competencies. A short list of what you do best, each in a line a buyer can scan. Write what you deliver, not adjectives.
- Differentiators. Why a buyer picks you: your set-aside status, relevant certifications, a niche, or specific tools and methods. Only claim what you can support.
- Past performance. Contracts you have delivered, only where you are allowed to share them. If you are new, leave this out rather than stretch the truth. A clear, honest page beats a padded one.
- Company data. The identifiers from the table above, in one tidy block.
- Contact. A named person, an email address and a phone number a buyer can actually use.
- Downloadable PDF. A link with a descriptive name, such as "Download our capability statement (PDF)".
Should the capability statement be a page, a PDF, or both?
Both. Use the page for search, mobile reading and easy updates, and the PDF for attachments and bid packages. Do not make the PDF the only place your information lives. If you publish a PDF, keep it accessible, with real text rather than a scanned image and a sensible reading order, because government buyers may need to meet accessibility requirements. Our Section 508 checklist for contractor websites covers the basics.
What mistakes weaken a capability statement page?
- Mismatched details. A UEI or NAICS code that differs from SAM.gov makes a buyer doubt everything else.
- Too many NAICS codes. A long list signals that you do everything, which reads as expertise in nothing.
- Claiming status you do not hold. Listing a certification you do not have can cost you far more than it gains.
- Vague competencies. "Innovative, customer-focused solutions" tells a buyer nothing. Say what you build, run or deliver.
- A stale PDF. An old year or a former contact name makes the whole company look inactive.
- No contact person. Buyers want to know who to call.
How does the page fit into the rest of the website?
The capability statement page is one part of a complete federal contractor website. Buyers also expect a clear homepage, a page for each core capability, your set-aside status shown plainly, and a simple way to contact you. If you are weighing the options, read our guide to what a government contractor website costs, or see how we approach government contractor website development. Based in New Mexico? We have a page for New Mexico government contractor websites.
Frequently asked questions
Where do I find my UEI and CAGE code?
Both come from your SAM.gov registration. Sign in to your SAM.gov entity record to see them. If you are not registered yet, registration is the first step, and a website cannot replace it.
How long should a capability statement be?
The PDF is typically one page, so a buyer can read it quickly. The web page can go a little further, but keep each section short and scannable.
Do I need past performance to publish a capability statement?
No. If you are a new contractor, focus on your core competencies, your team's relevant experience and your differentiators. Do not invent contracts or results.
