Writing a Capability Statement That Gets Read (Not Filed and Forgotten)
Contracting officers and primes receive dozens of capability statements per week. This guide shows you what makes them stop on yours — specific numbers, proof of past performance, and a clear set-aside header.
Priya Nair
I've reviewed hundreds of capability statements as a VP of Proposals. Most of them say the same thing: experienced team, proven track record, commitment to mission. None of that means anything. The statements that land meetings say something specific — a dollar figure, a downtime number, a named agency. You have 30 seconds of attention. Here is how to use them.
Four sections, in this exact order
Core competencies first (what you do), differentiators second (why you specifically), past performance third (what you've delivered with numbers), company data last (the administrative facts needed to take action). This order is deliberate — it leads with value and closes with logistics, not the other way around.
- Core Competencies: 5–7 bullets on specific services or products, not general descriptions — 'cloud migration for AWS GovCloud' not 'cloud services'
- Differentiators: 3–5 reasons you specifically — certifications, clearances, proprietary methods, exclusive partnerships with named primes
- Past Performance: 3–5 contracts with agency name, contract value, and one sentence on what you achieved
- Company Data: UEI, CAGE code, primary NAICS, set-aside certifications, address, point of contact
Strip every adjective, replace it with a number
Go through your draft and cross out every adjective: 'large,' 'experienced,' 'proven,' 'innovative,' 'comprehensive.' Every single one. Then replace each with a number. 'Large IT programs' becomes '$8M IDIQ, 12 FTEs, 3-year PoP.' 'Experienced cybersecurity team' becomes '14 cleared professionals, 8 CISSP-certified.' If you cannot replace the adjective with a number, cut the claim entirely — it is doing nothing.
Past performance entries that actually work
Each entry needs four things: agency name, contract number (PIID) if public, total contract value (not annual), and one sentence about what you achieved — not what the contract required. 'Reduced system downtime from 4.2% to 0.8% across 14 mission-critical servers over 18 months' is a past performance entry. 'Provided IT support services to the Department of Defense' is a job description. There is a difference.
Design for 8 seconds, not 8 minutes
Contracting officers scan before they read. Use a two-column layout with section headers in a visually distinct color from body text. Your company name, logo, and set-aside certifications should be visible without scrolling — put them in the top quarter. If someone has to hunt for your NAICS code or CAGE number, the document has already failed.
Keep a version per agency type, not one generic doc
Your DoD capability statement should lead with clearances, CMMC compliance posture, and defense past performance. Your civilian version should lead with whatever past performance is most relevant to that agency's mission area. A single all-purpose capability statement is almost never the strongest document for any specific opportunity. It takes 20 minutes to customize. Spend them.
Frequently Asked Questions
How long should a capability statement be?
One page. Two pages maximum if you have extensive, highly relevant past performance that genuinely requires the space. Anything longer gets fewer than 10 seconds of attention at an industry day or networking event. Build the document for a decision-maker who is holding it at a conference table with ten other statements.
What file format should a capability statement be in?
PDF for email and digital distribution — it preserves formatting across devices and operating systems. Bring printed copies to in-person meetings; print quality signals professionalism. Keep the source file in an editable format (Word or InDesign) so you can quickly customize for specific opportunities.
Put this into practice
GovPillar helps you apply everything in this guide — AI-scored opportunities, RFP shredding, capture pipeline, and more. Free to start.