A contracting officer once described her process for reviewing capability statements, and the honesty stung: "I give each one about ninety seconds. I'm not reading — I'm looking for reasons to keep it or reasons to stop." Somewhere in a stack, your one-pager gets its ninety seconds. Most capability statements are written as if they'll be studied — dense mission statements, walls of services, a company history nobody asked for. The ones that win are written for how they're actually read: scanned, under time pressure, by someone hunting for four specific things.
With federal year-end approaching — the season when officers move fastest and read least — here's how to build the version that survives the scan. (For the broader pre-season checklist, see getting award-ready before fiscal year-end.)
What the Ninety-Second Scan Is Looking For
An officer or small-business specialist opening your document has four questions, in roughly this order: What do you actually do? Can I buy from you easily? Have you done this before, for someone like me? How do I reach you right now? Every section of a strong capability statement answers one of those questions fast, and everything that answers none of them is a candidate for deletion. That's the entire theory. Now the sections.
Core Competencies: Say What You Do, Specifically
The opening section fails most often, and always the same way: abstraction. "Innovative solutions provider leveraging synergies across the enterprise" tells the reader nothing and costs you fifteen of your ninety seconds. Write instead the way a satisfied customer would describe you: the specific services you deliver, for the specific kinds of agencies or missions you deliver them to.
A useful drafting test — could a stranger, reading only this section, correctly guess what a task order to your firm would look like? If not, it's still too abstract. Five to seven crisp bullet points of genuine capability beat any paragraph of positioning language, and specificity has a second virtue: it's how you show up in keyword searches when someone's hunting for exactly what you do.
Differentiators: Answer "Why You" Without Adjectives
The second section is where you separate from the other qualified firms — and where "excellence" and "commitment" go to die. Differentiators persuade only when they're concrete: certifications and set-aside statuses that change how you can be bought, specialized clearances or credentials, niche expertise the big firms subcontract for, response times or staffing models a large prime structurally can't match, and your location when it matters — a DC firm's proximity to the agencies it serves is a real logistical fact, not a slogan.
The bar for every line in this section: is this a checkable fact? Facts survive the scan. Adjectives evaporate.
Past Performance: Evidence, Not References-Available-Upon-Request
Nothing de-risks you like proof you've done it before. List a handful of relevant engagements — customer, scope in one line, and anything that signals scale or complexity — choosing relevance over prestige. Three projects that look like the work you're chasing outweigh ten impressive ones that don't. New to federal work? Strong commercial or subcontracted past performance is far better than a thin section trying to look thick — and honesty about where you are reads as maturity, not weakness.
Company Data: The Section That's Pure Logistics
The final block is everything an officer needs to act on interest without emailing you first: your legal name, your identifiers — CAGE code and UEI — your NAICS codes, your socioeconomic certifications, your acceptance of government purchase methods, and your contact information. Missing identifiers are the most self-inflicted wound in the genre; if the officer has to ask for your CAGE code, you've added a day to a process that runs on hours. (New to those identifiers? Here's what a CAGE code is and how you get one.)
One quiet line in this section does more image work than people realize: the address. A commercial business address in the District — rather than a residential street in the suburbs — reads as an established firm with a real footprint near the customer. It's a small signal; in a ninety-second scan built entirely of small signals, it counts.
Format Ruthlessly, Update Relentlessly
The presentation rules are simple and non-negotiable: one page. Clean layout, generous white space, your logo, no design heroics. A PDF that emails well and prints legibly in grayscale. And a review cycle — quarterly, or before any big push like September — because a capability statement with a stale certification or an old phone number doesn't just miss; it advertises inattention.
Then put it everywhere: attached to introductions, handed off at matchmaking events, ready the same hour anyone asks. Which is where the logistics loop back to reachability — the best one-pager in the stack is wasted if the phone number on it rings into a void. That pairing — established address on the page, live answering behind the phone number — is exactly what we provide contractors at OSI Offices: a K Street address that looks the part on the document, with reception coverage that makes the "how do I reach you right now" answer immediately. Ninety seconds is all you get. Make every line of the page — and the first ring of the phone — count.
Does the contact block on your capability statement hold up? See how OSI equips DC contractors — the address and the answered phone behind the one-pager.