An SOQ and a proposal answer two different questions. An SOQ answers 'is this firm qualified?' A proposal answers 'how will this firm do the work, and at what price?' Confusing them - or volunteering a full proposal when the owner only asked for qualifications - is a common and avoidable mistake.
| Statement of Qualifications (SOQ) | Proposal | |
|---|---|---|
| Answers | Is the firm qualified? | How will the firm deliver, and at what cost? |
| Contains | Firm experience, key staff, relevant projects | Technical approach, schedule, staffing plan, usually price |
| Price included? | Usually no | Usually yes |
| When in the process | First - used to shortlist or select | After shortlisting, or as a combined RFP response |
| Typical length | Shorter, often page-limited | Longer and more detailed |
What an SOQ is
An SOQ is a qualifications package: firm profile, key personnel, relevant past projects, and sometimes a brief project understanding. Under Qualifications-Based Selection, owners use SOQs to rank firms and shortlist the most qualified before any pricing conversation. It responds to a Request for Qualifications (RFQ).
What a proposal is
A proposal goes further: a detailed technical approach, project schedule, staffing plan, and - in most non-QBS procurements - a price. It responds to a Request for Proposal (RFP). Where an SOQ demonstrates capability, a proposal commits to a specific way of executing the work.
How QBS uses both
In a classic QBS process, the SOQ comes first: firms submit qualifications, the owner shortlists the most qualified (often at least three), and shortlisted firms interview or submit a scoped technical proposal. Price is negotiated only with the top-ranked firm after selection. So the same pursuit can involve an SOQ early and a proposal later.
How to tell which one a solicitation wants
- If it's an RFQ or asks for 'qualifications' and sets a tight page limit, it wants an SOQ
- If it asks for a technical approach, schedule, or price, it wants a proposal
- If it says SF330, that is a standardized federal qualifications submission - an SOQ in form
- When in doubt, follow the document name and evaluation criteria the solicitation prints - and never volunteer price the owner didn't request
A two-step process, in practice
On many public pursuits the SOQ and the proposal are two stages of the same selection, not competing choices. The agency issues an RFQ; firms respond with an SOQ; the agency scores those and shortlists the most qualified. Shortlisted firms are then invited to interview or to submit a scoped technical proposal, and only the top-ranked firm negotiates fee. So a single opportunity can ask you for a qualifications SOQ in week one and a fuller proposal a month later - two different documents, each written for its stage.
What actually goes in each document
An SOQ answers 'trust us with this' using evidence you already have: firm profile, relevant project sheets, key-personnel resumes, references, and sometimes a brief understanding of the project. A proposal answers 'here is how we will do it,' which means new, project-specific thinking: technical approach and methodology, a work plan and schedule, a staffing and management plan, risk mitigation, and - in most non-QBS procurements - a priced cost proposal. The SOQ is largely assembled from a library; the proposal is largely authored for the job.
Mistakes when the two get confused
- Sending a full, priced proposal when the owner only asked for qualifications - which can violate a qualifications-only solicitation
- Submitting a thin qualifications blurb when the RFP wanted a real technical approach and schedule
- Repeating your SOQ verbatim as the proposal instead of adding approach, schedule, and staffing detail
- Leading the proposal with firm history the owner already scored at the SOQ stage, instead of the approach they now want
- Volunteering fee in a QBS process before the agency has ranked firms
Where the SF330 fits
On federal A-E work, the qualifications stage uses the SF330 rather than a free-form SOQ - but the logic is identical: qualifications first, price only after selection. Whether the form is an SOQ, an SF330, or a later proposal, the deciding question is always the same: does this document match what the solicitation asked for at this stage?
Reading the solicitation's signals
The document name is the clearest signal, but not the only one. Page limits, whether price is requested, whether a technical approach or schedule is asked for, and the language of the evaluation section all tell you which document the owner actually wants. When an RFQ says 'qualifications' but also asks for a brief project approach, give a qualifications-led response with a short approach section - answer what the criteria reward, in the proportions they reward it.
Why sending the wrong one hurts
Submitting a full, priced proposal into a qualifications-only process can breach the solicitation's rules and, under QBS, improperly inject price before selection. Submitting a thin qualifications blurb where a real technical proposal was required reads as a non-response. Matching the document to the stage is not pedantry - it is a compliance issue that can end an otherwise strong pursuit before anyone evaluates your team.
Plan for both from the start
On a two-step pursuit, treat the SOQ and the proposal as one campaign. The SOQ gets you shortlisted; the interview or technical proposal wins the ranking; fee is negotiated last with the top-ranked firm. Teams that treat the SOQ as the finish line are often unprepared when the real competition arrives weeks later. Map out both deliverables, and the people who will carry them, before you submit the first one.
Keep the story consistent across both
The team, projects, and win theme in your SOQ should carry straight through to the proposal and interview. Evaluators lose confidence when the firm that looked qualified on paper shows up with different people and a different pitch. Consistency signals a real, committed team; divergence signals a marketing exercise assembled for the shortlist.
A quick decision rule
When you are unsure which you are being asked for, default to the solicitation's own language and give exactly that - no more. If it asks for qualifications, submit qualifications and hold price. If it asks for an approach and a fee, provide both. The cost of guessing wrong is asymmetric: a qualifications response that omits an unrequested price is always safe, while volunteering price into a qualifications-only process can breach the rules. When the document genuinely blends the two, lead with qualifications and add only the approach detail it explicitly requests.
Built for both
Flodoc reads the solicitation, extracts the evaluation criteria, and matches your staff and past projects to each one - whether you're assembling a qualifications SOQ or a fuller proposal - so the team reviews instead of rebuilds.