How to write a capability statement that gets calls back

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.

The thirty-second read

Assume your document gets thirty seconds from someone holding forty of them. In that window a reviewer is answering three questions: does this firm do the scope we need, are they the size and status that helps our numbers, and is there a human here I can call. Everything on the page either answers one of those or is taking up space.

That is why the top third matters disproportionately, and why the most common failure is not ugliness but vagueness. Specificity is what survives the scan — and specificity almost always means a number.

The mistakes that get statements discarded

Four failures account for most of the pile that gets set aside, and none of them are about design:

• Running long. Two or three pages signals you could not decide what mattered. One page, every time.
• Marketing voice instead of buyer vocabulary. Write in spec divisions and scope language the agency itself uses, not in adjectives.
• Stale past performance. A statement whose newest project is three years old reads as a firm that stopped winning work.
• Missing the verification block. No UEI, no CAGE, no NAICS codes, no size status — now the reviewer has to look you up, and often just doesn't.

Frequently asked questions

How long should a capability statement be?

One page. Federal buyers and prime estimators read these in stacks, and length reads as an inability to prioritize rather than as thoroughness. If you cannot fit it, cut past performance to your three or four most relevant projects rather than shrinking the type.

What goes in a construction capability statement?

Five blocks: core competencies (the scopes you self-perform, in spec-division language), differentiators, past performance with agency or prime plus value and scope, a company-data block with legal name, UEI, CAGE, NAICS codes, size status, certifications, bonding capacity, licenses and insurance, and one named human with a direct phone and email.

Do I need a different version for each agency?

Tailor the top third, keep the bottom fixed. Core competencies and differentiators should mirror the scope language of the agency or prime you are sending it to, and a sources sought response should echo that notice's own wording. The company-data block stays identical everywhere — that part exists for verification, not persuasion.