A winning statement of qualifications (SOQ) answers the evaluation criteria in the RFQ, in the order the RFQ lists them, with specific evidence: relevant projects, the actual team, and an understanding of this scope. Evaluators score against a matrix, not a general impression, and most SOQs lose points on responsiveness, not qualifications.
That distinction is worth sitting with. Most firms treat the SOQ as an assembly problem: gather the best projects, the strongest resumes, the firm history, and package them well. The person on the other side has a stack of submittals, a scoring sheet, and an afternoon. The SOQ that wins is the one that makes their scoring easy.
What Is an SOQ?
An SOQ is a firm-prepared document that demonstrates qualifications for a specific contract or a standing roster: relevant experience, key personnel, capacity, and understanding of the work. It is not a priced proposal. Under qualifications-based selection, which governs most public A/E procurement, the SOQ is the entire first-phase competition, because price is excluded until the most qualified firm is chosen.
That is why the stakes are lopsided. In a price-based procurement, a middling document can be rescued by a sharp number. In an SOQ competition there is no number. The document is the bid. For how SOQs relate to SF330s, RFPs, and RFIs, see the full comparison.
Is an On-Call SOQ Different From a Project-Specific SOQ?
Yes, in emphasis. A project-specific SOQ is scored against one scope, so relevance to that scope and the understanding section carry the differentiation. An on-call or roster SOQ (for an IDIQ, master agreement, or standing list) is scored on coverage: the breadth of task-order types you can handle and the depth of bench behind each one. There, a capability matrix mapping staff and past projects to each service category often earns more than any single project narrative.
The discipline is the same in both: sections mapped to the published criteria, evidence over adjectives. But winning a roster seat is usually the start of the competition, not the end. Task orders get awarded through mini-competitions among the roster firms, which means the firms that win on-call work twice are the ones that can produce a tailored, task-order-sized response quickly, over and over, for years.
How Do Evaluators Score an SOQ?
Selection committees score SOQs against a matrix built from the evaluation criteria published in the RFQ. Every criterion carries points, every reviewer fills in the same sheet, and the shortlist comes from the totals. A typical A/E selection matrix looks something like this; the real one is in your RFQ, and it varies by agency.
| Criterion | Typical weight |
|---|---|
| Relevant project experience | 25–35% |
| Key personnel qualifications | 20–30% |
| Project understanding and approach | 15–25% |
| Capacity, schedule, and past performance | 10–20% |
| Certifications, DBE participation, forms | 5–15% |
Three things about that room change how you should write.
First, there is a compliance gate before any scoring happens. A late submittal, a missing form, a busted page limit, or a lapsed prequalification can make an SOQ non-responsive before a single criterion is scored. The strongest qualifications in the stack earn zero points if the document never reaches the scoring stage.
Second, the first pass is fast. Reviewers are working through a stack, often on top of their regular job. Scored sections get read; boilerplate gets skimmed. If the content that earns points is buried behind ten pages of firm history, it may as well not be there.
Third, scores cluster. Most shortlisted firms are genuinely qualified, so the spread between making the interview and missing it is often a handful of points. That is why sweating responsiveness and evidence is not perfectionism. It is where selections are actually decided, the same way a few points decide SF330 shortlists on the federal side.
What Do Evaluators Look For in an SOQ?
| What they score | What earns points | What loses them |
|---|---|---|
| Responsiveness | Sections mapped to the RFQ criteria, in the RFQ's order | A firm brochure organized the firm's way |
| Project experience | Recent projects of similar scope, size, and agency type, with outcomes | The firm's biggest projects regardless of fit |
| Key personnel | The team that will do the work, with role-matched resumes and availability | Bench-strength padding and borrowed star resumes |
| Understanding | Specifics about this site, this scope, this agency's standards | An approach section that fits any project |
| Evidence | Numbers, outcomes, named references | Adjectives: responsive, collaborative, committed |
| Compliance | Every form, limit, and format requirement met | Anything that makes the evaluator hunt or forgive |
The thread running through the left column is relevance to this pursuit. An evaluator scoring "relevant project experience" is not scoring impressiveness. A $4M water main replacement for a neighboring district outscores a $90M landmark project in another sector, every time, because the criterion says relevant and the evaluator has to defend the score. The same logic runs through people: the resume that wins is the one matching the advertised role, not the longest one. Differentiation is evidence, not adjectives, and in an SOQ the evidence has to be mapped to the criteria where the evaluator expects to find it.
How to Structure a Winning SOQ
-
Follow the RFQ's requested organization exactly. If the RFQ lists five criteria, your SOQ has five sections in that order, with matching headings. You are handing the evaluator a document that fills in their scoring sheet as they read. Never make them hunt for the content that earns your points.
-
Write a cover letter that scores. One page: the scope in your words, the proposed project manager by name, the one differentiator you want remembered, and any commitment the RFQ asks for. Committee members read it even when they do not score it, and it frames everything after.
-
Keep the firm overview short. A half page to a page of scope-relevant capability. This is where boilerplate bloat lives, and it is the least-scored real estate in the document.
-
Choose projects for relevance, then prove it. Four to six project sheets tailored to this pursuit: same scope, comparable size, same client type, recent. For each, state the relevance connection explicitly and give outcomes with numbers (schedule performance, budget performance, change-order rate, the client contact who will confirm it).
-
Match key personnel to the advertised roles. Resumes tailored to this pursuit, an org chart that agrees with the resumes, and an availability statement. Evaluators have seen the firm-wide bench slide before; what they score is whether this team's qualifications fit these roles.
-
Make the understanding section do the differentiating. When experience scores cluster, this is the section that separates. Name the site constraints, the permitting path, the agency's design standards, the phasing problem. That specificity usually comes from research done before the RFQ dropped, which is why the firms that win were often working on the pursuit before it was advertised.
-
Sweep compliance last, against a checklist. Forms signed, certs current, DBE commitments stated, page limits honored, file format and delivery method confirmed. Ten minutes of checking protects every point above.
Five SOQ Mistakes That Cost Shortlist Points
-
Recycling the last SOQ. Evaluators notice another agency's name in paragraph three, and they notice criteria mirrored from a different RFQ. Reuse your data, never your document.
-
Choosing projects by size instead of relevance. The greatest-hits reel reads impressive and scores poorly, because the criterion says relevant and the evaluator has to justify the number they write down.
-
Resumes that contradict the org chart. A project manager on the chart whose resume shows no comparable role, or key personnel obviously committed elsewhere, reads as assembled rather than planned.
-
Burying the scored content. Firm history up front, awards and philosophy in the middle, and the scope-specific material on page 14. The evaluator's first fast pass never finds it.
-
Treating format rules as suggestions. Page limits, font sizes, required forms, and delivery methods are pass/fail in the evaluator's hands. At best you irritate the person scoring you; at worst you are non-responsive and unscored.
Why Winning SOQs Come From Tailoring, Not Rebuilding
Every winning behavior above is a retrieval-and-tailor behavior. Relevant project sheets exist and are current, so choosing four for this scope takes an hour instead of a week. Resumes regenerate against the advertised roles instead of being reformatted from last year's versions. Certs and prequal status are known, not discovered on the final night. Firms that rebuild each SOQ from old PDFs spend the response window on archaeology, and the tailoring that earns points is what gets cut when time runs out, which is how a qualified firm ends up submitting the generic version of itself.
This is the problem a proposal workspace like RFPM.ai exists to remove: staff, projects, and past content live in one place as current, structured records, so each SOQ becomes selection and tailoring rather than reconstruction. The payoff is not just better documents. It is the capacity to answer more of the RFQs your firm is qualified for without adding headcount or burning the team.
Frequently Asked Questions
How long should an SOQ be?
Whatever the RFQ specifies, exactly. Absent a stated limit, most A/E SOQs land between 10 and 20 pages plus required forms. Length does not earn points; relevance density does. A tight 12-page SOQ mapped to the criteria beats a 30-page firm showcase in nearly every scoring room.
What is the difference between an SOQ and a proposal?
An SOQ demonstrates qualifications: experience, people, capacity, understanding. A proposal typically adds a priced scope of work and detailed approach. Under qualifications-based selection, the SOQ is the competition, because price is excluded until the most qualified firm is selected and negotiations begin.
How many projects should an SOQ include?
Follow the RFQ if it says. Otherwise, four to six highly relevant projects beat ten generic ones. Every project should share scope, scale, or client type with the pursuit, state that connection explicitly, and carry at least one outcome an evaluator can verify with the named reference.
Do evaluators really read every page?
Not on the first pass. Reviewers work through a stack against a scoring sheet, so scored sections get read carefully and everything else gets skimmed. Write for that reality: put point-earning content under headings that match the criteria, and treat unscored pages as space you are spending, not filling.
Can you reuse an SOQ between pursuits?
Reuse the source data, not the document. Projects, resumes, and firm facts should carry over; the selection, ordering, and framing should be rebuilt against each RFQ's criteria. Recycled SOQs are among the most common self-inflicted losses, because evaluators recognize a document written for someone else.