Statement of Qualifications (SOQ)
.png)
A Statement of Qualifications (SOQ) is a firm-initiated or client-requested document that presents a company's credentials, relevant project experience, and key personnel to establish eligibility or competitive positioning before a formal proposal is solicited.
Where the SOQ sits in the procurement sequence
Most public agency procurements that follow qualifications-based selection under the Brooks Act (1972) begin with an RFQ that triggers SOQ submissions; the agency shortlists three to five firms before issuing an RFP. On federal projects, the SF-330 effectively functions as a structured SOQ with prescribed sections for project experience (Section F), key personnel (Section E), and organizational chart (Section D). Private clients often request an SOQ informally, outside any published procurement process, which means firms have no standard format to follow and must make deliberate decisions about depth, order, and emphasis. An SOQ submitted too early in a client relationship can look generic; submitted at the right moment, it positions the firm before a project is even publicly announced.
What separates a strong SOQ from a compliant one
Compliance in an SOQ context means meeting page limits, including required sections, and matching the scope language in the RFQ. Competitive positioning means something different: selecting the four or five projects that most precisely mirror the client's project type, delivery method, regulatory environment, and risk profile, not the firm's largest or most award-winning work. Personnel bios need to show relevant role continuity, not just credential lists; a client evaluating a CMAR pursuit wants to see the same project manager and superintendent pairing across comparable jobs, not a roster of fifteen names. Shortlisting decisions often turn on how legible that match is to a reviewer spending eight minutes per submission.
The institutional knowledge problem inside every SOQ
Firms that chase volume across multiple market sectors struggle with SOQ consistency because the people who know which projects are actually comparable to a given pursuit are rarely the people assembling the document on a two-week clock. Project data lives in ERP systems in formats that do not translate directly into narrative; personnel expertise is stored in previous SF-330s and resumes that may be two years out of date; client relationships and past feedback sit in someone's memory or email inbox. The common workaround is to reuse last quarter's SOQ and edit for fit, which is how firms end up submitting work that references the wrong project type or omits a directly relevant credential. Kantiv addresses this by connecting current project data, verified personnel histories, and pursuit records so the team building the SOQ starts from a complete, accurate picture of what the firm has actually done and who did it.
Related terms