Capability statement: one page, and it is not a brochure

A capability statement is the one-page document a contractor sends to a government buyer to introduce itself. It is the standard artefact of federal business development, requested by name, and it has a conventional structure that its readers expect — which makes it one of the few marketing documents where following the convention beats standing out.

The reason is how it is used. A contracting officer or small business specialist receives many of these, scans for whether the company can do the work and whether it is registered and eligible, and files it against a category. A statement that buries the identifiers under a designed layout does not fail because it is ugly; it fails because the reader could not extract the two facts they needed in fifteen seconds.

The five blocks of a capability statement

• Core competencies — what you do, in the buyer’s vocabulary rather than your own marketing language, in a few tight lines.
• Differentiators — why you rather than a comparable firm, stated concretely. Certifications, clearances, geography, capacity, a proprietary method.
• Past performance — named clients with contract type and scope, most relevant first. Government past performance outranks commercial; recent outranks old.
• Corporate data — unique entity identifier, commercial and government entity code, industry codes, socio-economic certifications, contract vehicles held, accepted payment methods.
• Contact — a named person, direct line and email, not a general inbox.

Write it for a specific office

A single generic statement is worth having and worth tailoring. Reordering competencies to lead with what a particular agency buys, and swapping in the past performance most similar to their work, takes ten minutes and materially changes how the document reads. The version sent to a defence logistics office and the one sent to a civilian IT directorate should not be identical, even though the corporate data block is.

Keep it to one page. Two pages is a brochure, and a brochure does not get filed in the category the sender wanted. If the content genuinely will not fit, the competencies section is too broad — narrow the claim rather than adding a page.

Past performance is the section that decides it

New contractors have the least of it and treat the section apologetically, which is the wrong instinct. List commercial work with the scope stated in terms the buyer recognises, name subcontract roles honestly, and describe the outcome rather than the activity. What must not appear is vagueness — unnamed clients, unquantified scope, or claims of experience that a reference check would not support, since the whole purpose of the section is to be checkable.

Keeping versions straight

Because it is tailored per agency and updated whenever certifications or performance change, the failure mode is an outdated version circulating with expired identifiers. Ettex Docs holds the statement with version history and the tailored variants, Ettex Records keeps the corporate data that feeds it — identifiers, certifications, vehicles — with their expiry dates, and the registration those identifiers come from is covered in sam registration.

Plainly: this is documents and records, not a proposal service. What wins federal work is past performance and pricing; the capability statement’s job is narrower — to get you into the right file when somebody is looking for a firm like yours.