SOQ vs Proposal: Understanding the Key Differences in 2026
An SOQ proves your firm can do the work. A proposal explains how you'll do a specific project. The distinction sounds simple, but getting it wrong—or blurring the two—can knock you out of contention before evaluators finish reading.
This guide breaks down what belongs in each document, when to submit which, and how the procurement process determines your approach.
What is an SOQ
A Statement of Qualifications (SOQ) focuses on a firm's experience, team, and capabilities to prove they can do the job. It doesn't include pricing or a detailed project approach. Think of it as your firm's resume for a specific type of work—it answers "can this firm handle this?" rather than "how will they deliver this exact project?"
SOQs typically cover company background, key personnel resumes, relevant project experience, and certifications. The goal is demonstrating credibility and track record. You're not outlining a work plan or quoting a fee here.
Clients use SOQs to narrow down a large pool of interested firms to a manageable shortlist. Only after that do qualified firms move forward to compete on project specifics.
SOQ meaning in construction and professional services
In AEC, engineering, and consulting, SOQs are foundational to how work gets awarded. Many public sector clients follow qualification-based selection (QBS), which means they evaluate firms on credentials first—before discussing scope or price.
Government agencies like state DOTs and municipal authorities frequently require SOQs as the first step in procurement, with 46 states having implemented QBS laws following the federal Brooks Act.
On-call contracts work similarly. Agencies pre-qualify firms for a category of work, then assign projects as needs arise. If you're not on the qualified list, you're not in the running.
What is a proposal
A proposal is your firm's response to a specific project opportunity. It outlines how you'll approach the work, who will be on the team, what the timeline looks like, and often what it will cost.
Where an SOQ proves capability, a proposal proves fit. It answers "why choose us for this project?" with concrete details about methodology, staffing, and deliverables.
Proposals are typically submitted in response to a Request for Proposal (RFP), often after a firm has already been shortlisted based on qualifications.
Key differences between an SOQ and a proposal
The distinction comes down to purpose and timing. An SOQ demonstrates that your firm can do a type of work. A proposal explains how you'll do a specific project.
Purpose and timing
SOQs appear early in the procurement process, often before a project scope is fully defined. Proposals come later, once the client knows which firms are capable and wants to evaluate specific approaches.
Content and structure
SOQs emphasize past projects, key personnel resumes, and certifications. Proposals include technical approach, project-specific staffing plans, and fee structures.
There's real overlap—both include resumes and project experience. However, proposals tailor that content to a specific opportunity, while SOQs present a broader picture of firm capability.
Evaluation criteria
Evaluators score SOQs on experience, qualifications, and relevant track record. Proposals are judged on methodology, value, and often price. A strong SOQ gets you to the table. A strong proposal wins the work.
Reusability across bids
SOQ content—resumes, project sheets, firm qualifications—can be reused and tailored across multiple opportunities. Proposals are more project-specific and less reusable, though the underlying talent data feeds both.
Here's where many teams run into trouble. When resumes and project credentials live in scattered folders and outdated spreadsheets, tailoring content for each submission becomes a time-consuming hunt. The content exists somewhere—finding the right version is the problem.
When to submit an SOQ vs a proposal
The procurement method determines which document you'll prepare—and when.
Qualification-based selection
Common in public sector and AEC work, QBS requires firms to submit SOQs first. The client evaluates qualifications, shortlists the top firms, and then negotiates scope and fee with the most qualified firm. In some cases, there's no proposal competition at all. The ACEC Research Institute found that QBS projects experience only 3% cost growth compared to the 6% national average, reinforcing why agencies favor this approach.
Competitive bidding and RFPs
Private sector clients and some public projects skip the SOQ stage entirely. They issue an RFP, and firms compete on approach, team, and price from the start.
Two-stage procurement
Many large infrastructure and government contracts use both. Firms submit SOQs to get shortlisted, then submit full proposals. This two-stage process is common for complex projects where the client wants to confirm capability before evaluating detailed approaches.
What to include in an SOQ
SOQ requirements vary by solicitation, but most share common elements.
Firm qualifications and overview
- Company background: Brief history, size, and core services
- Relevant capabilities: Specific expertise aligned to the RFQ scope
Key personnel resumes
- Role-specific CVs: Tailored to show relevant project experience for proposed team members
- Certifications and licenses: Professional credentials required by the solicitation
Relevant project experience
- Project sheets: Past projects similar in scope, size, or complexity to the opportunity
- Client references: Contact information for verification
Certifications and compliance documentation
- Required forms: DBE/MBE/WBE certifications, insurance, bonding capacity as requested
Tip: The challenge isn't knowing what to include—it's finding the right version of each resume and project sheet when you need it. Teams that maintain a centralized, up-to-date content library spend less time hunting and more time tailoring.
What to include in a proposal
Proposals build on SOQ content but add project-specific detail.
Technical approach and methodology
- Understanding of scope: Demonstrate comprehension of the client's stated needs
- Work plan: How the firm will execute the project, including key tasks and milestones
Project-specific team and resumes
- Staffing plan: Named individuals assigned to the project with defined roles
- Tailored CVs: Resumes reformatted to highlight experience relevant to this specific project
Pricing and fee structure
- Cost proposal: Labor rates, expenses, total fee (if required)
- Value justification: Why the proposed approach delivers results
Schedule and deliverables
- Timeline: Key milestones and delivery dates
- Deliverables list: What the client will receive
How SOQs and proposals fit into the procurement process
Understanding where each document appears helps you prepare the right content at the right time.
- RFQ issued: Client requests qualifications
- SOQ submitted: Firms demonstrate capability
- Shortlist announced: Qualified firms advance
- RFP issued: Client requests detailed proposals
- Proposal submitted: Shortlisted firms compete on approach and price
- Selection and negotiation: Winning firm is chosen
Not every procurement follows all six steps. Some skip the SOQ phase entirely. Others never issue a formal RFP. But the underlying logic holds: prove you can do the work, then prove you're the best choice for this project.
Common mistakes in SOQ and proposal submissions
Most submission problems trace back to the same root cause: scattered, inconsistent talent data.
Recycling generic content without tailoring
Submitting the same boilerplate language without aligning to specific evaluation criteria signals that you didn't read the RFQ carefully. Evaluators notice when firm descriptions and project summaries feel copy-pasted.
Inconsistent or outdated resume formatting
Resumes with conflicting dates, old project information, or formats that don't match client requirements undermine credibility. This happens when data lives in shared drives with no version control—and nobody knows which file is current.
Missing compliance requirements
Failing to include required certifications, forms, or page limits can disqualify an otherwise strong submission. Teams without a single source of truth for firm credentials often discover gaps too late.
Relying on scattered files and manual processes
Hunting through emails, spreadsheets, and folders for the latest version of a resume or project sheet wastes hours and introduces errors. QorusDocs' benchmark survey found 80% of AEC respondents rank delivery deadlines and content creation as their top proposal hurdles. The last-minute panic is real—and it's usually a data organization problem, not a writing problem.
How to build SOQs and proposals faster without sacrificing quality
The firms that win consistently aren't necessarily better writers. They're better organized.
Purpose-built platforms like Flowcase help teams maintain a single source of truth for resumes and project credentials. Instead of hunting through shared drives, bid teams pull from a centralized, always-current database. The platform integrates alongside existing systems like Salesforce, Workday, and PSA tools, so talent data stays accurate without duplicate entry.
When your content is reliable and accessible, you can respond to more opportunities without adding headcount. Proposal teams focus on strategy and tailoring rather than reformatting and version control.
Book a demo to see how Flowcase helps firms respond faster while maintaining quality and compliance.
FAQs about SOQs and proposals
What is the difference between a scope of work and a proposal?
A scope of work defines the specific tasks and deliverables for a project. A proposal is the firm's response explaining how they will complete that scope, including approach, team, and pricing. The scope comes from the client. The proposal comes from the firm.
Can SOQ content be reused in future proposals?
Yes. Resumes, project sheets, and firm qualifications from SOQs can be tailored and reused across multiple bids. Maintaining a centralized, up-to-date content library makes reuse practical rather than theoretical.
How long should an SOQ typically be?
SOQ length varies by solicitation. Most RFQs specify page limits, and common lengths range from a few pages to more extensive submissions depending on project complexity and client requirements. Always check the solicitation instructions first.
When would you issue an RFQ rather than an RFP?
An RFQ is issued when a client wants to evaluate firm capability before discussing project specifics or pricing. This approach is common in qualification-based selection processes used in public sector and AEC procurement, where the client shortlists qualified firms before negotiating scope and fee.
.png)
.png)
