Guides · Updated June 10, 2026
How to write a capability statement that gets calls back
A capability statement is your shop's one-page federal resume — the document agencies expect with a sources-sought response and primes expect before adding you to a bid list. Most are bloated and interchangeable; a good one is scannable in thirty seconds.
The five blocks every capability statement needs
One page, five blocks, in this order:
- Core competencies — the specific scopes you self-perform, in the buyer's vocabulary (spec divisions, not marketing copy). Six bullets maximum.
- Differentiators — why you over the next shop: response radius, crew depth, certifications, niche capability, safety record (EMR if it's good).
- Past performance — three to five relevant jobs: agency or prime, location, contract value, scope, completion. Federal references first if you have them.
- Company data — legal name, UEI, CAGE, your NAICS codes, size status and certifications (8(a), HUBZone, SDVOSB, WOSB), bonding capacity (single and aggregate), licenses, insurance.
- Contact — one named human with direct phone and email, plus the website. Not info@.
What separates the ones that work
Specificity. "Electrical contractor for federal facilities" disappears into the pile; "Design-assist electrical sub self-performing distribution, lighting, and fire alarm on occupied federal medical campuses; C-10; bonded to $5M single / $10M aggregate" gets kept. Numbers beat adjectives everywhere they can appear — crew counts, bonding limits, response radius, completed contract values.
Tailor the top third when it matters: a sources-sought response should mirror the agency's own scope language, and a version aimed at primes can lead with the scopes you take off their plate. Keep the company-data block identical everywhere — that part is for verification, not persuasion.
Where it actually gets used
Sources-sought responses are the highest-leverage destination — they're how agencies decide set-aside strategy, and a tight capability statement is most of the response (see set-asides explained). Beyond that: agency small-business offices keep vendor files, primes collect them when building sub lists for upcoming bids (finding primes to sub for), and industry-day sign-in sheets get followed up with whatever you handed over.
Keep it living: update past performance as jobs close, and re-issue when your bonding, certifications, or size status change. JobsiteBids asks for your capability statement at signup for the same reason — it's the densest single description of what your shop does, and we parse it to seed your match profile.
Put this on autopilot.
JobsiteBids watches the federal feed, parses every packet, and emails your strong matches at 6 AM — ranked against your trade, service area, and bid size.