Capability Statement for Government Contractors: What to Write and Why
A capability statement is a one-page summary of your firm's qualifications, past performance, and relevant experience for a specific type of government work. Federal agencies use them to screen contractors during the early stages of a solicitation. For small firms without dedicated capture managers, a strong capability statement is often your only chance to prove you belong in a competitive bid.
What Is a Capability Statement?
A capability statement is not your full proposal. It is a pre-proposal document—sometimes called a "one-pager"—that demonstrates your firm can perform the work the agency is requesting. Agencies post solicitations on SAM.gov and expect contractors to submit a capability statement within the first few days if they want to be considered. Some agencies make it part of the formal proposal; others use it only to filter the qualified pool before releasing the full request for proposal (RFP).
For a construction firm, a capability statement might highlight your experience with General Services Administration (GSA) projects, your bonding capacity, and the size of your in-house crews. For an IT services firm, it might list your certifications, past client experience, and team depth in a specific technology domain.
Why Capability Statements Matter for Government Contracting
Government agencies receive dozens or hundreds of capability statements for a single solicitation. They use these documents to narrow the field before investing time in reviewing full proposals. A weak or missing capability statement can disqualify you before your technical team ever sees the opportunity.
Agencies also use capability statements to evaluate past performance and relevant experience. Under Federal Acquisition Regulation (FAR) Part 15, agencies must consider contractor past performance as one of the evaluation factors. A well-written capability statement connects your past wins directly to the current opportunity.
For firms without a capture team, the capability statement is your tool for getting on the radar. It forces you to articulate why you are the right choice and creates a record that the agency can reference when they ask for references or past performance documentation later.
Key Sections Your Capability Statement Must Include
| Section | Purpose | Length |
|---|---|---|
| Company Overview | Your firm name, location, years in business, DUNS number, CAGE code, business size classification | 3-4 lines |
| Relevant Experience | Specific past contracts matching the solicitation scope; client names, contract values, duration | 4-6 lines |
| Core Competencies | Technical skills, certifications, equipment, or processes unique to your firm | 3-4 lines |
| Management Approach | Your process for quality, scheduling, safety, compliance, or other critical factors | 3-4 lines |
| Past Performance References | 3-5 customer names, contract types, and contact details (usually at bottom of page) | 2-3 lines |
| Subcontractors (if applicable) | Key subcontractor names and their role; confirm their CAGE codes and certifications | 2 lines |
How to Write Each Section
Company Overview
State your firm's legal name, headquarters location, DUNS number, CAGE code, and years in continuous operation. Include your business size status (small business, woman-owned, minority-owned, veteran-owned, or HUBZone, if you qualify). Agencies filter solicitations by these categories, so getting your status correct is critical. If you are registered in SAM.gov, your status should already match; verify it is current.
Relevant Experience
List 3-5 contracts from the past 5-10 years that match the scope of the current solicitation. For each contract, provide the customer name (or agency), contract type, value, duration, and your specific role. Be concrete. Instead of "managed projects," write "managed installation of enterprise network infrastructure for 12 federal facilities over 18 months, $2.3M contract."
If you do not have exact past-performance matches, select contracts that show the skills the solicitation requires. A facilities maintenance firm bidding on a new GSA building can reference similar-sized projects even if they were for a different client, because scope and scale matter more than the customer name.
Core Competencies
List the technical capabilities that set you apart. For a construction firm: specific trades, equipment, certifications, bonding capacity. For an IT services firm: security clearances, software certifications, languages your team speaks. For a professional services firm: industry expertise, staff credentials, or proprietary methodologies.
Be specific. "Expert in federal procurement" is generic; "GSA Schedule 84 certified and experienced with FAR Part 15 competitive proposals" is concrete. List credentials: ISO certifications, security clearances (Secret, Top Secret), SBA certifications, or specialized licenses relevant to the work.
Management Approach
Describe how you will execute the work on time and on budget. Agencies care about risk management, scheduling discipline, quality assurance, and compliance. Mention your system for tracking progress (e.g., weekly status reports, earned-value reporting), your quality-assurance process (inspections, testing, audits), and how you handle changes and schedule risk. If you use software tools (project management, timekeeping, accounting), mention them by name—it signals maturity and transparency.
Past Performance References
List 3-5 past clients with a brief description of the work, contract value, and duration. Include the customer's name, the contracting officer's name, phone number, and email. Call these references before submitting to confirm they remember your firm and will respond to inquiries. Agencies often contact references during the evaluation process.
Common Mistakes to Avoid
Overselling. Agencies distrust vague claims. "Best-in-class customer service" does not prove anything. Show what you did: "Completed three site audits ahead of schedule and identified $240,000 in cost savings for the customer."
Mismatched experience. If the solicitation asks for IT security services and your past work is in IT operations, say why you can do security. Do not list projects that have no connection to the scope.
Outdated references. If your past performance references are from more than 10 years ago, add newer ones. Agencies want evidence that you are still performing at a high level.
Missing details. "Worked on several government contracts" is not enough. Agencies need contract numbers, customer names, dates, and contract values to verify your past performance during the evaluation.
Ignoring formatting. A crowded, hard-to-read page signals disorganization. Use clear headers, bullet points, white space, and a readable font. Keep it to one page—two pages only if the solicitation explicitly allows it.
Tools and Process for Capability Statements
Managing capability statements across multiple solicitations takes coordination. You need to know which opportunities are live, what deadlines apply, and whether your past performance matches the scope. SAM.gov publishes solicitations and amendments continuously, and deadlines vary by solicitation—some agencies accept submissions for two weeks, others for only five business days.
Tools like BidWatch (bidwatch.9gg.app) monitor SAM.gov for solicitations matching your NAICS codes and keywords, track amendments and response deadlines, and send alerts 14, 7, 3, and 1 days before close. For a small firm, even missing one deadline by a day can cost months of potential revenue.
Your process should be: monitor for opportunities, pull the solicitation and any amendments, identify past performance that matches, write or adapt your capability statement, and submit by the deadline. If your team wins the opportunity, keep the capability statement and past-performance summary for your archive so you can reference them in future proposals.
A free plan lets you track one solicitation; paid plans start at $12.99/month with a 14-day trial, so you can test whether it fits your workflow before committing.
FAQ
How long should a capability statement be?
One page is the standard. Some solicitations allow two pages; read the instructions carefully. A tight one-pager forces you to be clear about what matters most. Agencies that want more detail will ask for it in the full RFP.
Should I use the same capability statement for every opportunity?
No. Tailor the relevant experience and core competencies sections to each solicitation. Use your boilerplate company overview, management approach, and references, but change the specific projects and skills to match what the agency is requesting. A generic capability statement signals that you are not serious about the work.
What if I do not have past performance for this specific type of work?
Be honest about your background and explain how your existing skills apply. For example, if you are a construction firm with experience in commercial building but you are bidding on a GSA federal courthouse project for the first time, highlight your relevant experience in similar-scale projects, your bonding capacity, and your past performance on buildings with strict quality and compliance requirements. Agencies understand that firms grow into new markets. What matters is whether you have the underlying capability to perform.
Do I need to update my capability statement if I win a new contract?
Yes. After winning a government contract, add it to your capability statement as past performance. Within 3-6 months, it becomes your most recent proof point. Keep your references current and update any certifications or team changes that affect your competitive position.
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. Your first solicitation is free; paid from $12.99/mo.
Start free — 14-day trial on paid plansUse BidWatch free
Your first solicitation is free. BidWatch matches SAM.gov opportunities to your NAICS codes and alerts you to every response deadline.
Use BidWatch free →