Capability statement: what a contracting officer checks, and how to fit it on one page

A capability statement is the document a small business hands a contracting officer, a prime contractor or a purchasing agent to answer one question: can you do this work, and can we buy from you? It is one page, it is read in about thirty seconds, and it is scanned for facts rather than read for prose. This guide covers what those facts are, how to write differentiators a buyer can check, and how to lay the page out so the things they verify sit where they look for them.

What a buyer verifies

The first thing a contracting officer does with a capability statement is check whether they can buy from you at all. That means the identifiers: your Unique Entity ID and CAGE code, an active registration in the System for Award Management, your business size and any socioeconomic certifications (small business, HUBZone, 8(a), service-disabled veteran-owned, woman-owned), and the NAICS codes that describe your work, with the primary marked. Put these in a sidebar down one side of the page, in the order a buyer checks them, and keep them current: an expired registration or a lapsed certification on a capability statement is the fastest way to lose the call you were trying to earn.

• Company data: UEI, CAGE code, SAM.gov status and expiry, business size, socioeconomic status, year and state established
• NAICS codes, primary first, each with its size standard
• Certifications and registrations: the quality system (ISO 9001), the trade listings (UL 508A), the socioeconomic certificates with their dates
• Contract vehicles you already hold: a GSA schedule, a BPA, an IDIQ, or “open market” if none
• One point of contact: a name, a direct line and an email that is answered

Core competencies

Core competencies are the list of what you do, in the buyer’s vocabulary: the work as a contract would describe it, not as your marketing does. Five or six short lines, such as “UL 508A control panel fabrication” or “instrument calibration and commissioning”, each of which maps to something a solicitation might ask for. A competency that no solicitation would name is a marketing point, and belongs elsewhere.

Differentiators that carry a number

Differentiators are where most capability statements fail, because they are written as adjectives: responsive, experienced, customer-focused. A contracting officer cannot verify an adjective. Write each differentiator as a claim with a number someone could check (a lead time, a count, a date, a contract) and let the past-performance table below be what the numbers point to. “Thirty-four authorized manufacturer lines on one purchase order” is a differentiator; “broad product range” is not. “First units on site within 72 hours of an emergency PO” is a differentiator when the contract it happened on is listed underneath.

Past performance

Past performance is a table, not a paragraph: the customer, the contract or purchase-order number and your role (prime or sub), the period, the value, and one line on the outcome. Three to five rows, the most relevant first. Choose contracts a buyer can call about, and describe the outcome in terms they care about (on schedule, no change orders, zero punch-list items) rather than in terms of what you delivered. If you have no federal past performance yet, commercial contracts with the same scope are better than an empty section, and say which they are.

The one-page layout

A capability statement has a conventional shape, and the convention exists because buyers have learned where to look. A masthead with the company name and a one-line description of what you do. A banded sidebar down one side carrying everything a buyer verifies: the identifiers, the NAICS codes, the certifications, the contract vehicles, the contact. The main column carrying the case: a two-sentence overview, core competencies, differentiators, past performance, and the bonding, insurance and payment terms a purchasing office will ask for next. Put the document number, revision and date in the footer, because the page will be filed and compared with the next version.

Keeping it to one page, and current

One page is the rule, and the sidebar is what makes it possible: facts in a compact band, prose in the column beside it, nothing that needs a heading of its own. If the page runs over, cut differentiators to four and past performance to three rows before shrinking the type; a buyer who needs more will ask. Then treat the statement as a controlled document: registration expiry dates, certification dates and contract values all change, and a statement carrying a stale one is worse than none. Reissue it with a new revision whenever the sidebar changes, and keep the old revisions, because the one a buyer has on file may be two versions behind.