Capability Statement for Government Contracts: What to Include + Template

What Is a Capability Statement?

A capability statement is not a brochure or a marketing flyer. It is a structured credential document that presents your business in the specific format contracting officers and program managers expect. Think of it as your company's resume for federal procurement — professional, factual, and scannable in under two minutes.

Capability statements are used in several contexts:

• Sources Sought and RFI responses — Agencies routinely request a capability statement alongside your narrative response.
• Industry days and agency outreach events — Contracting officers collect them from every vendor who attends. Yours needs to stand out and hold up on its own without you in the room.
• Cold outreach to contracting officers — A well-crafted capability statement is the professional way to introduce your firm to an agency you want to work with.
• Vendor registration portals — Some agency systems ask for a capability statement as part of your profile.

The most common mistake contractors make is creating one generic capability statement and sending it everywhere. Effective capability statements are tailored — you lead with the most relevant competency for the specific agency or opportunity, and you align your language to theirs.

The 8 Sections of a Capability Statement

Federal contracting has informal but well-established norms for capability statement content. These eight sections cover everything a contracting officer needs to evaluate your business quickly. Do not omit any of them.

1. Core Competencies

List 4–8 specific service areas or product categories using industry terminology, not marketing language. "IT infrastructure modernization" is better than "cutting-edge tech solutions." Align your competency labels to the language used in your target NAICS codes and in the agency solicitations you pursue. This is the section that determines in the first ten seconds whether the reader keeps going.

2. Past Performance

Include 3–5 examples with enough specificity to be credible: client name, contract number (if publicly available), dollar value, period of performance, and a 1–2 sentence scope summary. Both government and commercial work count, especially early in your federal contracting career. If you have CPARS ratings, note that they are available upon request. If you do not, a strong reference contact is a reasonable substitute.

3. Differentiators

This is the section most contractors get wrong. Differentiators must be specific and verifiable — certifications, active security clearances, proprietary methodologies, specialized equipment, geographic reach, or a specific combination of capabilities your competitors do not have. "Committed to quality" and "on-time delivery" are not differentiators. Every competitor claims those. State something that is actually distinctive about your firm.

4. Company Data

Include your UEI number, CAGE code, entity type (LLC, S-Corp, etc.), year founded, employee count, annual revenue range, and bonding capacity if you pursue construction or large project work. Missing your UEI or CAGE code is an automatic red flag — it signals to contracting officers that your SAM.gov registration may not be current.

5. Certifications and Set-Aside Status

List every applicable designation prominently: 8(a), HUBZone, SDVOSB, WOSB, EDWOSB, veteran-owned, and any agency-specific mentor-protégé relationships. Include expiration dates where applicable. A contracting officer looking for a specific set-aside will scan for this section first — make it easy to find. Expired certifications listed without dates are worse than not listing them at all.

6. NAICS Codes

List your primary NAICS code first, followed by secondary codes. Include the SBA size standard for each code — this helps contracting officers instantly confirm your eligibility for set-asides under those codes without having to look it up. If you have more than five or six NAICS codes, create a version of your capability statement for each major service area and lead with the most relevant codes for that audience.

7. Contract Vehicles

If you hold any existing contract vehicles — a GSA Schedule, a GWAC like CIO-SP4 or Alliant 2, a BPA, or an agency-specific IDIQ — list them here with the contract number. This matters because agencies often prefer to buy through existing vehicles to avoid a full competition. If you have no vehicles yet, omit this section entirely rather than noting the absence.

8. Contact Information

Name, title, email, phone number, website, and physical address (or the state you are based in, at minimum). Make this section impossible to miss — use a visually distinct block or sidebar. A capability statement that generates interest but makes it hard to reach you is a wasted opportunity.

Formatting Rules That Matter

A capability statement that reads well but looks unprofessional will undercut your credibility. Formatting conventions in federal contracting are not arbitrary — they reflect what works for a busy contracting officer scanning dozens of documents.

• Length: One page is ideal. Two pages is acceptable for complex businesses with multiple service lines. Beyond two pages, contracting officers stop reading.
• Format: Send as PDF. Only submit Word format if explicitly requested. PDF ensures your layout survives email forwarding and printing.
• Design: Your logo at the top, clean typography, clear section headers, and plenty of white space. This is not the place for dense paragraphs. Bullets and short phrases beat sentences.
• Agency-tailored versions: For important agencies, incorporate their color palette or mission language into a custom version. It signals you did your homework and are not mass-mailing a generic document.
• Frequency of updates: Review and update your capability statement at least quarterly. Stale past performance references (projects that ended years ago) and expired certifications listed without dates will hurt you.

Tailoring Your Statement Per Opportunity

A generic capability statement is better than nothing. A tailored one closes deals. The goal is to make the contracting officer feel like you wrote this document specifically for their agency and this specific opportunity.

• Read the notice before submitting. Lead with the core competency most directly relevant to the Sources Sought or RFI you are responding to. If the notice is about cybersecurity assessment services, your cybersecurity section should open the document — not your IT staff augmentation work.
• Mirror their language. If the agency uses "cybersecurity assessment," use that phrase — not "security consulting" or "vulnerability management." Language alignment signals domain fluency.
• Research the agency's strategic plan. Most agencies publish annual strategic plans and budget justifications publicly. Find where your capabilities align to their stated priorities and reference those priorities in your differentiators section.
• Surface agency-specific experience. If you have done work for that agency or its subcomponents before, lead with it in your past performance section. Familiarity with an agency's processes and culture is a genuine differentiator.

Common Mistakes That Kill Capability Statements

These errors appear repeatedly across the capability statements contracting officers reject. Build a checklist from this list and run every version through it before sending.

• Missing UEI or CAGE code. This signals your SAM.gov registration may be lapsed or incomplete. It is an automatic credibility hit for agencies that check registration status before responding.
• Generic differentiators. Phrases like "committed to excellence," "customer-focused," or "trusted partner" tell a contracting officer nothing. Every vendor says these things. Replace them with something specific you can prove.
• Past performance without dollar values or dates. Undated past performance is nearly worthless — it could be ten years old. Missing dollar values make it impossible for a contracting officer to gauge whether your experience is relevant in scope. Always include both.
• Certifications listed without expiration confirmation. An 8(a) certification that expired three months ago hurts you more than not having one. Either confirm current status or remove it.
• No tailoring. Sending the same document to the Army Corps of Engineers, the VA, and the GSA signals that you are conducting volume outreach, not strategic positioning. Most contracting officers can spot a generic document immediately.

Building Past Performance When You Have None

Every contractor faces this at the start. There are legitimate paths to building a past performance record without having won a prime federal contract yet.

• Subcontract under a prime. Work as a subcontractor on an existing federal contract to build documented, federal-specific experience. Your work can be cited as past performance — note the prime contractor and the agency contract number.
• Include state and local government work. State and local contracts are legitimate past performance for federal solicitations, especially when the scope and complexity are comparable.
• Cite analogous commercial work. IT services for a large hospital system are relevant experience for a VA contract. Healthcare logistics for a regional network is relevant for a DHA solicitation. Frame commercial work explicitly in terms of the federal analog.
• SBIR and STTR awards count. If your company has received Small Business Innovation Research or Small Business Technology Transfer funding, those are federal contracts and belong in your past performance section.
• Use reference letters strategically. If you lack CPARS ratings, a strong reference letter from a previous client — government or commercial — can partially compensate. Include a contact name and phone number so it can be verified.

For responding to Sources Sought notices, see our Sources Sought response guide.

Make sure your NAICS codes are accurate — NAICS codes guide.

If you have set-aside certifications, include them prominently — set-aside programs guide.