How to Write a Federal Capability Statement (with Template)
A capability statement is a 1-2 page document that introduces your company to federal buyers. It must include: core competencies, differentiators, past performance, company data (CAGE code, NAICS codes, UEI number, certifications), and contact information.
What Is a Capability Statement?
A capability statement is your company's federal marketing one-pager. It communicates who you are, what you do, what makes you different, and whether you are qualified to do government work — all in a format that a contracting officer can scan in 30 seconds. It is not a proposal, not a resume, and not a brochure. It is a precise document with a specific structure that federal buyers expect.
Every serious federal contractor needs one. Contracting officers collect them. Small business specialists ask for them at industry days. Teaming partners want to see them before agreeing to a bid. And when you respond to a Sources Sought notice, your capability statement is often the entire submission.
When to Use Your Capability Statement
- Responding to Sources Sought notices on SAM.gov — this is the most common formal use
- Industry days and pre-solicitation conferences — hand it to every contracting officer in the room
- Cold outreach to agency small business representatives (OSDBUs)
- Submitting to a large prime's vendor database for teaming opportunities
- Small Business Administration (SBA) matchmaking events and procurement conferences
- Any time a contracting officer asks "tell me about your company"
The Six Required Sections
Company Overview
2–3 sentences maximum. Legal company name, what you do, how long you have been in business, and where you operate. No fluff. "Acme IT Solutions LLC is a veteran-owned IT services firm specializing in cybersecurity and cloud migration for federal civilian agencies. Founded in 2018, headquartered in Reston, VA." That is all you need.
Core Competencies
A bulleted list of 4–8 specific capabilities. Not vague ("IT support") — specific ("NIST SP 800-53 security assessment and authorization", "AWS GovCloud migration", "Agile software development in Python/Java"). Each item should map to real work you have done and real contracts you could win. These become your searchable keywords when contracting officers look for vendors.
Differentiators
3–5 bullets explaining why the government should choose you over a competitor. Must be specific and verifiable. "98% on-time delivery rate across 12 federal task orders." "Security clearance facility with 14 cleared personnel." "ISO 9001:2015 certified quality management system." Avoid generic claims like "committed to excellence" — every company says that and it means nothing to a contracting officer.
Past Performance
List 3–5 relevant contracts. For each: the agency name, contract number (if public), brief description of work, contract value, and period of performance. Format: "USDA OCIO | Contract # AG-3151-C-22-0041 | Network infrastructure design and implementation | $2.4M | 2022–2024." If you lack federal past performance, include relevant commercial contracts — just be transparent that they are commercial. No past performance at all is better than irrelevant past performance.
Company Data
The hard facts contracting officers need to verify your registrations and eligibility. This section is non-negotiable — leave any of these out and your capability statement is incomplete. Required fields: UEI (Unique Entity Identifier), CAGE Code, DUNS (legacy, but some agencies still ask), EIN (Employer Identification Number), business entity type (LLC, Corporation, etc.), founding year, number of employees, annual revenue (if comfortable disclosing), primary NAICS codes, and any active set-aside certifications with certification number if applicable.
Contact Information
Name, title, phone, and email of the person contracting officers should contact. If you have a dedicated government sales or BD (business development) contact, use them. Otherwise, the owner or CEO. Include your company website if it has a government-focused page. Physical address is optional but looks professional.
Template Layout
Capability Statement — Template Outline
One page preferred, two pages maximum. PDF format only. Use your company colors. Update quarterly.
300 DPI recommended
• [Specific technical capability 1]
• [Specific technical capability 2]
• [Specific technical capability 3]
• [Specific technical capability 4]
• [Specific technical capability 5]
• [Specific, measurable differentiator 1]
• [Specific, measurable differentiator 2]
• [Specific, measurable differentiator 3]
• [Set-aside certification (SDVOSB, WOSB, etc.)]
• [Industry certification (ISO, CMMC, etc.)]
• [Clearance level if applicable]
Agency Name | Contract # | Brief description | $Value | 20XX–20XX
Agency Name | Contract # | Brief description | $Value | 20XX–20XX
Agency Name | Contract # | Brief description | $Value | 20XX–20XX
Common Mistakes to Avoid
- Two pages when one would do If you can fit it on one page without cramming, do it. Contracting officers get dozens of these. A tight, well-designed one-pager gets read. A cramped two-pager gets skimmed and filed.
- Outdated NAICS codes If your primary NAICS doesn't match the opportunity you're pursuing, the contracting officer can't use your capability statement. Review and update your listed NAICS codes every quarter. Add new codes to your SAM.gov registration before submitting.
- Generic differentiators "Customer-focused," "high quality," "responsive" — every vendor says this. Contracting officers hear it constantly. Replace every generic phrase with a specific fact: a number, a name, a certif ication, a clearance level, a rate, or a metric.
- No CAGE code or UEI Some small businesses forget these. Without them, a contracting officer cannot verify your SAM registration. The capability statement is useless.
- Past performance that doesn't match the opportunity Submitting a capability statement for a cybersecurity set-aside with past performance in landscaping signals you don't know what you're doing. Keep multiple targeted versions — one per NAICS code cluster — rather than one generic document for everything.
- Sending it as a Word document Always send PDF. Word docs render differently on different systems. A PDF looks exactly as designed, every time. It also signals professionalism.
For related reading: How to read a SAM.gov Sources Sought notice, set-aside certifications, and procurement types explained.