Government Contracting Capability Statement: What Agencies Actually Want

A government contracting capability statement is a concise, agency-focused summary of your firm's qualifications, past performance, and capacity to deliver on a specific type of work. Federal agencies use it to quickly screen which contractors can actually execute the solicitation—not to build your brand, but to verify you meet their technical and past-performance bar. One to two pages, usually PDF, submitted in response to a Request for Proposal (RFP), Request for Quotation (RFQ), or Request for Information (RFI).

Why Contractors Need a Capability Statement

A capability statement sits at the threshold of every federal opportunity. When the General Services Administration (GSA), Department of Defense (DoD), or the Department of Veterans Affairs publishes a solicitation, your firm's first submission is almost always this one document. Contracting officers scan it in 90 seconds to answer two questions: Do you appear qualified? Do you have past performance proof? If the answer to either is no or unclear, your proposal moves to the reject pile before your technical team ever reads it.

Small contractors often skip this step or treat it as optional. It's not. Many RFPs on SAM.gov explicitly require a capability statement, and even when optional, agencies weight it heavily. They're short on time, flooded with submissions, and this document is their fastest filter.

What Goes Inside a Capability Statement

A standard capability statement follows this structure:

Agencies don't care about your mission statement or your vision for innovation. They care whether you've done exactly this work before, for which agencies, and how much you charged.

The Opening: Agency Relevance, Not Company Pride

Your opening line should mirror the language of the opportunity. If the RFP says "facilities management services," your statement says "facilities management services"—not "integrated facilities solutions." If it calls for "IT infrastructure support," don't reframe it as "digital transformation partnerships."

Contracting officers search their inbox for keywords before they read. A quick copy-and-match approach to the first paragraph increases your odds of landing in the shortlist.

Past Performance: Specific, Traceable, Recent

Federal buyers assume recent work is more relevant than old work. A contract you executed last year carries more weight than one from five years ago. Include the agency name, contract number (if unclassified), completion date, and the specific deliverable or service. General statements like "provided IT support to federal clients" cost you the sale. Detailed statements like "supported the Army Corps of Engineers contract DACW42-22-C-0001 (2022–2024), managing network administration and helpdesk operations for 200+ users across three field offices" keep you in the running.

Dollar value also matters. A firm that delivered $500K in work has more demonstrated capacity than one citing a $25K task order, even if both are legitimate. Include the size of past contracts when possible.

Technical Qualifications and Certifications

List every certification or qualification directly tied to the opportunity. If the RFP requires a Facility Security Officer (FSO), name your FSO and their credentials. If you're bidding IT work, list your CMMC certification level, if applicable. If you're a construction firm, include your bonding capacity and the bonding company name.

Contracting officers verify certifications during the pre-award survey. Don't list anything you can't prove within one business day.

Agency-Specific Tailoring

A single generic capability statement submitted to every agency is a waste. Rewrite the past-performance section for each agency type. A contract with the Department of Transportation carries different weight when bidding on a DoD solicitation than when bidding on another DOT opportunity.

If you're preparing responses across multiple solicitations, track which agencies are your repeat buyers and where your strongest past performance sits. Many contractors find they're strongest with one or two agencies and weaker with others—that's normal and useful information for bid strategy. Tools like BidWatch monitor multiple solicitations across your NAICS codes and keywords, flagging deadlines and amendments; using that tracking data to spot patterns in which agencies value your work most can sharpen your tailoring.

Common Mistakes That Trigger Rejections

Vague past performance. Avoid "provided services to federal clients" or "supported government agencies." Name the agency and describe the work.

Exaggerating staff capacity. A contracting officer will ask for resumes and call your references. If you claim 50 employees and have 12, you'll be disqualified before the technical evaluation.

Dated information. A capability statement showing work from 2018 but nothing recent signals you may have lost customers or capacity. Update it at least quarterly.

Ignoring the RFP requirements. Some RFPs specify format, length, or sections. Missing those details is an automatic rejection at many agencies.

Listing unrelated past performance. A contract you completed for a private client doesn't prove you can work under federal compliance rules. Include only work that's directly relevant to the solicitation.

How Agencies Use Your Capability Statement

Contracting officers use capability statements in three phases: the initial screening, the past-performance evaluation, and the pre-award survey.

Screening phase: The contracting officer reads your statement to confirm you meet the minimum qualifications (NAICS codes, required certifications, past performance with similar work). Failing this step means no proposal evaluation. Most screens take 60–120 seconds per submission.

Evaluation phase: If you pass screening, your past-performance section is scored against competitors. An evaluator cross-references your stated contracts with available public records and may contact references. Completeness and specificity directly affect your score here.

Pre-award phase: If you're ranked for award, the agency's procurement office will verify every claim in your capability statement. They'll call your past customers, confirm certifications, and request proof of bonding or insurance. Discrepancies found here can disqualify you at the last moment.

Deadlines and Amendments

Capability statements are often due at the same time as full proposals. On SAM.gov, most RFPs allow 14–21 days from posting to deadline. Some allow only 7–10 days, particularly for small modifications or resolicitations.

Many firms treating the capability statement as an afterthought run out of time. Writing and tailoring a solid statement takes 4–6 hours per solicitation. If you discover a major amendment—a change to the scope or past-performance requirements—three days before deadline, you'll need to rewrite and get approvals quickly. Planning ahead and monitoring amendments as they release is how firms avoid missing deadlines.

A contracting officer can publish amendments at any point before the deadline, sometimes extending time, sometimes shortening it, and often changing the evaluation criteria or past-performance requirements. A firm that doesn't track amendments might submit a capability statement that's already obsolete by the time it reaches the evaluator's desk.

FAQ: Government Contracting Capability Statements

Q: How long should a capability statement be?

Most agencies want one to two pages. Some RFPs specify length; follow that exactly. If no length is given, one page is safer—it signals focus and clarity. If you have substantial past performance, two pages is standard and acceptable.

Q: Can I use the same capability statement for every opportunity?

You can reuse the company overview, qualifications, and contact sections. You should rewrite or customize the past-performance section for each agency and opportunity type. Generic past performance is a visible red flag to evaluators.

Q: What if I don't have federal past performance yet?

List relevant private-sector past performance with similar scope and complexity. Many first-time federal bidders use this approach. Be specific: describe the client (without breaching confidentiality), the work performed, and the contract size. If you have zero relevant past performance, acknowledge it honestly and emphasize why your team is qualified—technical certifications, staff expertise, equipment, or industry licenses. Some agencies value transparency here.

Q: Should I include pricing in my capability statement?

No. Capability statements are for qualifications and past performance only. Pricing goes in your cost proposal, submitted separately. Including pricing in the capability statement can result in rejection for non-compliance with RFP instructions.

Q: Do I need a new capability statement for every solicitation?

Not for every element. Update your core sections—company info, qualifications, certifications—annually or when major changes happen. For each solicitation, tailor the past-performance section to the agency and scope. A minor update (1–2 hours) is better than submitting a generic version or scrambling to write from scratch at the last minute. Tracking solicitations and their deadlines gives you time to do this right.

Start monitoring SAM.gov opportunities free so you catch every amendment and deadline in your pipeline.