Back
No items found.

How to Write a Statement of Qualifications That Wins Contracts

A statement of qualifications (SOQ) is a tailored document that demonstrates your firm's experience, skills, and qualifications against specific RFP requirements—serving as a critical screening tool in competitive bidding. Unlike a resume or cover letter, an SOQ responds directly to evaluation criteria with concrete evidence of your ability to perform the work.

This guide covers when you'll encounter SOQ requirements, what to include, how to structure your response step by step, and the common mistakes that get otherwise qualified firms eliminated from consideration.

What is a statement of qualifications

A statement of qualifications (SOQ) is a tailored document used in competitive bidding that acts as a screening tool to assess a firm's or individual's experience, skills, and qualifications against specific RFP requirements. It's not a cover letter. Instead, an SOQ is a fact-based, often bulleted narrative that provides evidence of your ability to perform the work—typically by answering specific questions or prompts from the solicitation.

You'll encounter SOQs in both government procurement and private-sector bids, though they're especially common in public contracts where strict evaluation criteria apply. The document responds to specific prompts, with each answer backed by concrete examples of relevant experience.

  • Purpose: Proves your firm's fitness for a specific project or contract
  • Format: Structured narrative responding to specific prompts, often with bullets
  • Audience: Evaluators scoring proposals against defined criteria

When contracts require an SOQ

Not every bid calls for an SOQ, but certain contexts almost always do. Knowing when to expect one helps you prepare well in advance rather than scrambling at the last minute.

Government and public-sector bids

Federal contractsapproximately $755 billion in FY 2024 according to the GAO—state bids, and municipal procurements frequently require SOQs as part of the selection process. If you've applied for State of California positions through CalCareers, you've likely seen SOQ requirements—they're standard for many government roles and contracts.

Architecture, engineering, and construction RFPs

With U.S. construction spending reaching $2.17 trillion in 2025, AEC firms submit SOQs to demonstrate relevant project experience and team qualifications before being shortlisted. Many infrastructure and public works projects use a qualifications-based selection process where the SOQ determines whether you even get to submit a full proposal.

Professional services procurement

Consulting firms, legal practices, and other project-based firms use SOQs when clients want to evaluate expertise before issuing a full RFP. This is common in advisory engagements where the client wants to understand your team's background before discussing scope or pricing.

SOQ vs. resume vs. cover letter

Confusing these three documents is a common mistake, and it can cost you the bid.

Document Purpose Tone Length
SOQ Demonstrates specific qualifications against RFP criteria Formal, fact-based Varies by RFP requirements
Resume Summarizes career history Professional One to two pages
Cover Letter Introduces interest and fit Conversational One page

SOQ vs. resume

An SOQ responds to specific prompts and evaluation criteria. A resume is a general summary not tailored to a single opportunity. You can't simply submit your resume in place of an SOQ—evaluators expect you to address their specific questions directly.

SOQ vs. cover letter

Cover letters are introductory and conversational. SOQs are structured, evidence-based documents that follow strict formatting requirements. The tone is more formal, and the content is far more detailed.

Letter of qualification vs. SOQ

You might see "letter of qualification" used interchangeably with SOQ, though it sometimes refers to a shorter introductory statement. When in doubt, check the RFP for specific requirements—an SOQ is typically more detailed and structured than a simple letter.

What to include in a statement of qualifications

Evaluators look for several key components, though the exact requirements vary by solicitation.

Firm or individual profile

Include a brief overview of the organization or individual, covering relevant background and core competencies. Keep this section concise—it sets context but isn't the main event.

Relevant project experience

Detail past projects that demonstrate your capability to perform the work described in the RFP. For each project, include the client, scope, your role, and measurable outcomes. This section often carries the most weight in evaluation.

Key personnel qualifications

List the credentials, certifications, and relevant experience of key personnel who will work on the contract. Evaluators want to know who's actually doing the work, not just that your firm has general expertise in the area.

Knowledge, skills, and abilities responses

Many SOQs require structured responses to specific KSA (Knowledge, Skills, and Abilities) prompts. Answer each one individually and explicitly—don't make evaluators hunt for the information they're looking for.

Certifications and compliance documentation

Provide licenses, insurance, bonding, and any required certifications such as DBE or small business status. Missing compliance documentation can disqualify an otherwise strong submission.

Statement of qualifications format and structure

Compliance with formatting requirements is often evaluated, so following instructions precisely matters as much as the content itself. Strict adherence to font size, page limits, and margins is mandatory—evaluators use this to assess your ability to follow directions.

Header and contact information

Place the firm name, address, contact person, and submission details at the top. Include the RFP reference number if one exists.

Opening paragraph

Write a strong opening that summarizes your firm's fit for the project and highlights key differentiators. This is your chance to make a first impression before evaluators dive into the details.

Qualifications and experience section

This is the body of the SOQ. Organize it by the evaluation criteria or prompts listed in the RFP, using clear headings and bulleted lists for readability. Mirror the structure of the RFP itself—if they list five criteria, you have five sections.

Closing statement

Reaffirm your interest and summarize why your firm is the best choice. If appropriate, include a call to action such as requesting a meeting or site visit.

How to write a statement of qualifications step by step

The real challenge in assembling an SOQ isn't writing skill—it's finding and trusting your data. Here's how to approach the process.

1. Analyze the RFP requirements

Read the RFP thoroughly and identify all evaluation criteria, required sections, and formatting rules. Create a checklist of mandatory elements—missing even one can result in disqualification.

2. Gather current credentials and project data

This is where most teams lose time. Hunting through shared drives, spreadsheets, and outdated files for accurate CVs, project sheets, and certifications is the biggest bottleneck in SOQ production. The challenge isn't writing—it's locating information you can actually trust.

Firms that centralize their credential data in a single source of truth can pull together SOQs in hours rather than days. Platforms like Flowcase integrate with existing systems like Salesforce, Workday, and PSA tools to keep personnel and project information current and accessible.

3. Write a strong opening statement

Summarize your firm's qualifications and why you're a strong fit for the opportunity in two to three sentences. Be specific—generic openings don't differentiate you from competitors.

4. Structure qualifications around evaluation criteria

Address each prompt or criterion individually. Use the CAR method (Context, Action, Result) to provide concrete examples that prove your capabilities. If the RFP asks three questions, provide three clearly labeled answers.

5. Use measurable achievements

Replace vague claims with specific outcomes. Instead of "experienced in cost management," write "delivered project 15% under budget." Spell out acronyms on first use—evaluators may not share your technical vocabulary.

6. Review for compliance and formatting

Double-check font size, margins, page limits, and required attachments. Non-compliance signals an inability to follow directions, which is itself an evaluation criterion in many solicitations.

7. Finalize and submit

Proofread the entire document. Save it in the required formats. Verify that all team members' information is current and consistent across all sections—inconsistencies undermine credibility quickly.

Statement of qualifications template

Use this structure as a starting point, then customize it to match each RFP's specific requirements.

  • Header: Firm name, contact information, RFP reference number
  • Opening paragraph: Summary of qualifications and fit
  • Section 1: Firm overview and relevant experience
  • Section 2: Key personnel and their qualifications
  • Section 3: KSA responses (if required)
  • Section 4: Past project examples with outcomes
  • Closing statement: Reaffirm interest, summarize strengths, invite follow-up

Every RFP has unique requirements, so this template is a starting point rather than a final product.

Common SOQ mistakes to avoid

Even experienced bid teams make these mistakes more often than you'd expect.

Generic content not tailored to the RFP

Reusing the same SOQ for multiple bids without customization is a top reason for rejection. Each submission needs to directly address the specific opportunity—evaluators can tell when you've copied and pasted from a previous bid.

Outdated credentials or project information

Relying on old CVs, project sheets, or certifications introduces errors and misrepresents current capabilities. The challenge is keeping talent data accurate and accessible across the firm, especially as people change roles or complete new projects.

Missing required sections or formatting errors

Ignoring page limits, font requirements, or mandatory sections signals an inability to follow directions. In many evaluations, this alone can disqualify your submission before anyone reads the content.

Inconsistent team member profiles

When CVs and project descriptions lack clear content ownership, inconsistencies in job titles, dates, and project details undermine your firm's credibility. Evaluators notice when the same person has different titles in different sections of the same document.

How firms assemble SOQs at scale

The primary challenge in creating SOQs isn't writing—it's the operational difficulty of finding, trusting, and reusing talent data. Firms with centralized credential databases respond faster and with greater consistency than those relying on shared drives and email chains.

Platforms like Flowcase serve as a single source of truth for CVs, project experience, and certifications. The platform integrates with existing systems like Salesforce, Workday, and PSA tools, so bid teams spend less time hunting for content and more time tailoring their response to win the contract.

Streamline your SOQ process for every bid

When your credential data lives in one place and stays current, assembling SOQs becomes a matter of selection and tailoring rather than searching and reformatting. That's time you can redirect toward strategy and story—the elements that actually differentiate winning proposals.

Book a demo to see how Flowcase works alongside your existing systems to improve your bidding process.

FAQs about statements of qualifications

How long should a statement of qualifications be?

SOQ length varies by RFP requirements—always follow the specified page limits, font size, and margin rules. Non-compliance with formatting requirements can disqualify your submission regardless of content quality.

Can the same SOQ be reused for multiple bids?

Reusing a generic SOQ without tailoring it to each RFP's specific prompts and evaluation criteria is a common mistake that reduces your chances of being shortlisted. Evaluators expect responses that directly address their requirements.

What is the difference between an SOQ and an SF 330?

An SF 330 is a standardized federal form for architect-engineer qualifications required on certain U.S. government contracts. An SOQ is a more flexible document format that varies by solicitation—check your RFP to determine which is required.

Do subcontractors need to submit separate SOQs?

Many RFPs require subcontractors to provide their own qualifications, project experience, and key personnel information as part of the prime contractor's submission. Review the RFP carefully to understand what's expected from your team.

What does CalCareers mean by statement of qualifications?

CalCareers uses SOQ to refer to a written narrative—separate from your resume—that demonstrates how your experience meets the specific requirements listed in a State of California job posting. Each prompt typically requires its own response.

Keep reading

Using the Flowcase MCP Server with Claude Desktop

Technical

Using the Flowcase MCP with Microsoft Copilot

Technical

7 Steps to Improving Resumes for Proposals That Win

No items found.