Federal capability statement: what makes it different from a commercial one

Five fields are effectively required on a federal capability statement. Missing any of them is a credibility issue.

• UEI (Unique Entity Identifier). 12-character alphanumeric identifier assigned when you register in SAM. Replaces DUNS as of April 2022. Visible on your SAM entity profile. Required.
• CAGE code. 5-character code assigned by the Defense Logistics Agency (DLA) when SAM registration completes. If you are registered in SAM, you have a CAGE. Required for any federal work; especially important for DoD-facing capability statements.
• NAICS codes with size status. Your primary NAICS first, followed by 2-5 secondary codes. Each with a note on whether you are small under that NAICS. Example: "541512 (small, $34M size standard) / 541519 (small) / 541690 (other than small)." Match SAM exactly.
• Socioeconomic certifications. 8(a), HUBZone, SDVOSB, VOSB, WOSB, EDWOSB, if applicable. Name the verifying registry (certify.SBA.gov or VetCert) and the current verification date.
• Contract vehicles held. GSA MAS (with schedule number), CIO-SP4, SEWP VI, OASIS+ (category and pool if applicable), 8(a) STARS III, specific IDIQs. Specify prime vs subcontractor role. A CO looking to issue a task order cares which vehicles you are eligible for.

Beyond the required fields, four content patterns belong on a federal capability statement and rarely on a commercial one.

• Past performance tied to CPARS where available. If a federal customer has rated you in CPARS (Contractor Performance Assessment Reporting System), note it. "CPARS rating: Exceptional / Very Good / Satisfactory on the above contract" is a strong signal, because CPARS ratings are the primary input into source-selection past-performance evaluation.
• Clearance levels and cleared headcount. If your work requires facility clearance (FCL) or personnel clearances (PCL), note the FCL level and the number of cleared staff. Example: "FCL: Secret. Cleared staff: 14 at Secret, 3 at TS/SCI." Intelligence community buyers check this before engaging.
• Specific agency experience. Name the agencies you have worked for. A capability statement that lists DoD, DOL, HHS, and DHS by name is more useful than one that says "multiple federal customers." If you have sub-agency or component-level experience (CDER within FDA, CBP within DHS, NAVSEA within DoD), specify.
• Contract-vehicle standing. If you hold a contract vehicle, spell out what categories or SINs you are on. "GSA MAS, SIN 54151S (IT Professional Services)" is more useful than "GSA MAS holder."

Federal buyers have specific expectations; commercial content patterns hurt you.

• Generic value propositions. "We empower your mission through innovative solutions that drive operational excellence" is commercial brochure language. Federal buyers discount it on sight. Replace with specific capabilities.
• Customer logos as a "proof" row. Commercial pitches use logo rows to imply endorsement. On a federal capability statement, skip the logo row and list agency names in past performance with contract numbers. The contract number is the proof.
• Non-federal testimonials. Commercial testimonials ("XYZ transformed our business") do not translate. If you have glowing CPARS ratings, cite them; if not, leave testimonials out entirely.
• Sales-funnel CTAs. "Schedule a demo," "Book a discovery call," "Download our whitepaper" read as commercial prospecting. A federal capability statement ends with contact information, not a conversion CTA.
• Anything in the commercial brochure voice. First-person plural ("we partner with you"), adjectives ("innovative," "cutting-edge," "customer-centric"), and verb choices that lean marketing ("empower," "elevate," "transform") all dilute the document. Rewrite in declarative voice: "We perform FedRAMP Moderate authorization packages for civilian agencies."

Four audiences, each scanning for different signals.

• Contracting officers (COs). Check NAICS, size status, set-aside certifications, and past performance that matches the requirement they are working. Spend 30-60 seconds on the document.
• Agency small-business specialists (OSDBU staff). Maintain internal vendor databases. Look for NAICS codes that map to agency acquisition forecasts, set-aside certifications, and geographic alignment with agency field offices.
• Prime contractor BD teams. When chasing a large opportunity that requires small-business subcontracting, primes build teams from their capability-statement file. They look for NAICS match, certifications, past relevant performance, and capacity indicators (staff count, facility, bonding for construction).
• Agency matchmakers and industry-day hosts. Scan for NAICS match and certification match before choosing who to invite to one-on-one sessions. A mismatched NAICS code means you do not get the meeting.

Most cabinet agencies publish annual acquisition forecasts listing upcoming contract opportunities by NAICS code, expected award quarter, and estimated dollar range. A federal capability statement positioned well against an agency's forecast gets attention from that agency's OSDBU.

Workflow to use the forecast:

1. Pull the target agency's current-year acquisition forecast (published on the agency's OSDBU or acquisition page).
2. Filter for NAICS codes that match yours.
3. Note the forecasted awards, expected set-aside type, and incumbent if listed.
4. Send your capability statement to the agency OSDBU contact referencing the forecasted opportunities by line item.

"Acme Cybersecurity notes your FY2026 forecast item 47 (NAICS 541512, HUBZone set-aside, Q3) and has relevant past performance on CDM integration. Attached." is a stronger outreach email than a blind "here is our capability statement."