How to Write a Capability Statement for Government Contracting
A capability statement is a one-page document federal contractors use to introduce their firm to procurement officers and show why they're qualified for government work. It lists your company's experience, capabilities, NAICS codes, and certifications—and serves as your first impression when agencies evaluate new contractors for solicitations.
What Is a Capability Statement and Why Does It Matter?
If you're a small government contractor, your capability statement is often the deciding factor in whether a contracting officer calls you or passes you over. Here's why:
When a federal agency issues a solicitation for bids or proposals, they search SAM.gov for contractors in relevant NAICS codes and review capability statements to build their bid list. For construction, facilities, IT, and professional-services firms, this is your moment to stand out. A strong capability statement shows that you understand the agency's requirements and can deliver the work. A weak one gets you filtered out before you ever see the solicitation itself.
Many government procurement officers receive hundreds of capability statements. They typically spend 30 seconds to 2 minutes evaluating each one. Your job is to make those seconds count by showing relevant experience, certifications, and the specific work you can do.
What Should Your Capability Statement Include?
The following table outlines what procurement officers expect to see:
| Section | What to Include |
|---|---|
| Company Name & Details | Legal business name, CAGE code, DUNS number, SAM.gov registration status |
| NAICS Codes | Primary and secondary NAICS codes that match the work you do; include the full description (not just the number) |
| Certifications | Small business status (SB, HUB Zone, WOSB, VOSB, SDVO), ISO, security clearances, bonding capacity |
| Years in Business | Company founding year; years in federal work; staffing size (rough headcount) |
| Core Capabilities | Specific services and experience. Use concrete language (e.g., "manage A/E/C projects up to $15M" instead of "provide construction services") |
| Key Personnel | PM/project manager names, licenses (PE, PMP, security clearances), years of relevant experience |
| Past Performance | References or recent relevant projects (if not prohibited by contract terms); contract value, completion date, agency name |
| Contact Information | Bid/proposals email, phone number, mailing address, and a name (not a generic "Submissions") |
Example for a construction firm: Instead of writing "We provide construction services," write "We manage heavy civil and commercial construction projects for federal agencies, with primary experience in HVAC replacement (NAICS 238220), facility maintenance (NAICS 561210), and general contracting (NAICS 236210). We are bonded up to $5 million and have successfully completed 12 projects for the General Services Administration and the Department of Veterans Affairs totaling $23 million in the past three years."
How to Write an Effective Capability Statement
Keep it to one page. Procurement officers will not read more. Print it at actual size to ensure your single page does not overflow. If you're tempted to use 8-point font to cram in extra text, don't. One page, 10-12 point font, real margins.
Use simple, direct language. Avoid jargon unless it's specific to the work you do. "We perform HVAC preventive maintenance and emergency repairs at federal facilities" is clearer than "We deliver integrated mechanical systems optimization." Procurement officers want to understand your capabilities immediately.
Mirror the solicitation language. When you're responding to a specific opportunity, tailor your capability statement to match the keywords and requirements in the statement of work. If the solicitation asks for "IT system administration and cybersecurity support," make sure those exact phrases appear in your document.
Include numbers that matter. Contract value, project count, staffing size, bonding capacity, and years in business all tell a story. "18 years in federal contracting," "managed 40+ annual maintenance contracts," and "bonded to $10 million" are more credible than generic claims.
Make your contact information prominent. Procurement officers need to find it in seconds. Include a specific person's name—not "Proposals Team." A procurement officer wants to call John Smith or Maria Rodriguez, not a blank inbox.
Common Mistakes to Avoid
Making it too long or too fancy. A two-page capability statement signals that you don't understand federal procurement requirements. An overstyled document with graphics and multiple columns can be hard to scan and may not convert to text correctly in agency systems.
Being too vague about your experience. "30+ years of expertise" tells an agency nothing. "30 years delivering IT infrastructure support to federal agencies, including network administration (CompTIA Network+), cybersecurity patching (NIST 800-53 compliance), and helpdesk services for departments of 20-50 users" is credible and specific.
Listing certifications you don't have or exaggerating small business status. Agencies verify. If you claim HUB Zone status but your SAM.gov registration shows something different, you lose the opportunity and your credibility.
Forgetting to update it. Your capability statement should reflect your current qualifications. If your key project manager left three years ago, update it. If you earned a new certification, add it. Outdated information undermines your bid.
How to Use Your Capability Statement in Your Pursuit Strategy
Your capability statement is not a one-time document. It's part of an ongoing capture process.
When you see a new solicitation on SAM.gov that matches your NAICS codes and expertise, tailor your capability statement for that specific opportunity. If the solicitation emphasizes security clearances and you have employees with clearances, make sure that detail appears in your document. If the work requires specific certifications, lead with those.
The challenge is staying on top of new opportunities. Federal agencies post solicitations continuously, and response deadlines—often 7 to 21 days—move fast. Tools like BidWatch monitor SAM.gov for your NAICS codes and keywords, then alert you when new solicitations post. That gives you time to review the requirement, tailor your capability statement, and prepare a competitive bid. You can try it free for 14 days or use the free plan to watch 3 opportunities at a time.
Between bids, keep your capability statement current. Review it quarterly. If you've completed major projects, gained certifications, or expanded your team, update the document. A fresh, relevant capability statement increases your chances across all future opportunities.
FAQ
What is the difference between a capability statement and a proposal?
A capability statement is a standing introduction to your company—it should be ready to go before any solicitation lands. A proposal is your response to a specific solicitation and includes pricing, detailed work plans, and answers to the agency's specific questions. Your capability statement is a starting point; a proposal is your full bid.
Do all federal agencies require a capability statement?
No. Some agencies specifically request one; others don't ask for it but welcome it. The safest practice is to include a capability statement with every initial bid unless the solicitation explicitly says not to. Many procurement officers use capability statements to screen new contractors even if they don't formally require one.
Should I include pricing or past contract values in my capability statement?
You can include contract values to show scale and experience—for example, "completed projects ranging from $500,000 to $4.2 million." Do not include pricing or rates unless the solicitation specifically asks for it. Capability statements are about qualifications, not cost.
How often should I update my capability statement?
Update it at least once a year or whenever something significant changes: a key hire, a major project completion, a new certification, or a change in your small business status. If you're actively pursuing government contracts, review it quarterly to ensure it reflects your current qualifications and speaks to current opportunities.
Stop losing bids to missed amendments
BidWatch monitors SAM.gov for your NAICS codes, tracks every response deadline and amendment, and drafts the response outline. Free for 3 solicitations; paid from $12.99/mo.
Start free — 14-day trial on paid plans