Glossary

Statement of Qualifications vs Capability Statement

The difference in statement of qualifications vs capability statement comes down to depth and purpose: a capability statement is a one-page firm summary used to screen a firm quickly, while a statement of qualifications (SOQ) is a longer, tailored package submitted to a specific request for qualifications. The capability statement gets you noticed; the SOQ competes for a named opportunity.

Both documents present the same raw material - your projects, your key personnel, and your firm credentials - which is why they are so often confused. The distinction is the stage of the pursuit each one serves.

What is the difference between a statement of qualifications and a capability statement?

A capability statement is a single page written for fast screening across many buyers. It is not tied to any one opportunity: a contracting officer, prime contractor, or commercial buyer skims it in under a minute to decide whether your firm is worth a conversation. It leads with core competencies and past performance and carries registration codes (UEI, CAGE, NAICS for US federal work).

A statement of qualifications is a multi-page package written to one solicitation - a request for qualifications (RFQ). It expands the most relevant experience into detailed project descriptions, adds resumes of the key personnel proposed for the work, and follows the RFQ’s evaluation criteria and page limit. It exists to win a place on a shortlist for a specific job.

Capability statementStatement of qualifications (SOQ)
LengthOne pageMulti-page package (per RFQ limit)
Tied toNo specific opportunityOne specific RFQ
PurposeBroad screeningCompete for a named shortlist
Depth of projects3-5 compact past-performance linesDetailed descriptions with references
Key personnelRarely, or a brief mentionFull resumes of the proposed team
Reused as-is?Yes, across many buyersNo, tailored per RFQ

When should you use each?

Use a capability statement for first contact and screening - matchmaking events, sources-sought and RFI responses, vendor registrations, prime-contractor supplier portals, and email introductions. It is the document you hand out before a specific opportunity exists.

Use a statement of qualifications when a specific RFQ asks you to demonstrate your qualifications for a defined scope of work. In US federal architect-engineer selection, this qualifications response is often the mandated SF 330 form; in state, local, and private procurement it is a more flexible SOQ document - but both are qualifications-first responses to a named opportunity.

The practical takeaway: these are not competing formats to choose between, but two zoom levels on the same firm data. Store your projects, people, and credentials once and you can produce a one-page capability statement for screening and a full SOQ for an RFQ from the same source. The free project reference manager keeps that data in one place and assembles each document on demand - create a free SUNAGO account to build these from your projects automatically.

Frequently asked questions

Is a statement of qualifications the same as a capability statement?

No. A capability statement is a one-page firm summary used for broad screening across many buyers. A statement of qualifications is a longer, tailored package submitted to a specific request for qualifications (RFQ), with detailed project descriptions and key-personnel resumes. Both present firm credentials but serve different stages of the pursuit.

When should I use a capability statement instead of an SOQ?

Use a capability statement for first-touch screening: matchmaking events, sources-sought responses, vendor registrations, and email introductions, where a buyer skims many firms in seconds. Use a statement of qualifications when a specific RFQ asks you to demonstrate your qualifications for a named opportunity.

Do a statement of qualifications and a capability statement use the same information?

Largely yes. Both draw on your projects, key personnel, and firm credentials. The difference is depth and framing: the capability statement compresses this into one page for screening, while the SOQ expands the most relevant parts to answer one solicitation's evaluation criteria. Keeping the underlying data in one place lets you generate either document from the same source.