Statement of Qualifications: How to Write One That Wins

A statement of qualifications (SOQ) is a document a firm submits to prove it is qualified for a contract, usually in response to a request for qualifications (RFQ). It presents the team, relevant past projects, capacity, and approach, so the buyer can shortlist the most qualified firms before discussing scope or price.

For architecture, engineering, and construction firms, the SOQ is often the most important document in a pursuit. In qualifications-based selection, the buyer ranks firms on competence first and negotiates fees later, so a weak SOQ ends the pursuit before price is ever discussed. The same pattern shows up with public agencies, universities, and other buyers that prequalify vendors before inviting full proposals.

Statement of qualifications vs. proposal vs. capability statement

The three documents overlap, and teams often reuse content across them. The difference is the question each one answers for the buyer.

One note on terms: RFQ can mean request for qualifications or request for quotation depending on the buyer, so read the solicitation title carefully. For the shorter, general-purpose document, see our guide to the capability statement.

What is a statement of qualifications used for?

SOQs are most common where the buyer is purchasing professional judgment rather than a commodity. In US federal contracting, architect-engineer services are acquired under the Brooks Act and FAR Subpart 36.6, which require agencies to publicly announce requirements, select firms based on demonstrated competence and qualifications, and then negotiate a fair and reasonable price.

Federal architect-engineer firms submit qualifications on Standard Form 330. Part I presents qualifications for a specific contract, and Part II presents the firm's general qualifications. FAR 36.603 requires firms to file Part II to be considered for these contracts, and it directs agencies to encourage firms to submit an updated Part II every year.

Many state and local agencies run comparable qualifications-based selection processes for design and engineering work, and private owners borrow the format for large capital programs. Whatever the setting, follow the page limits, section order, and forms that the specific request for qualifications calls for.

How evaluators score a statement of qualifications

FAR 36.602-1 lists the criteria federal evaluation boards apply to architect-engineer firms. Even outside federal work, these criteria are a reliable map of what reviewers look for:

• Professional qualifications necessary for satisfactory performance of the required services.
• Specialized experience and technical competence in the type of work required.
• Capacity to accomplish the work in the required time.
• Past performance on government and private contracts, in terms of cost control, quality of work, and schedule compliance.
• Location in the general geographic area of the project and knowledge of the locality, when that criterion still leaves enough qualified firms.

The evaluation board then holds discussions with at least three of the most highly qualified firms and recommends them in order of preference. Negotiation starts with the most preferred firm. In practice, the SOQ has to earn a place in the top tier on its own, because there is no price lever to pull later.

What to include in a statement of qualifications

Section names vary by solicitation, but most SOQs are built from the same components.

Cover letter and firm overview

Open with a one-page letter signed by a principal that confirms interest, names the point of contact, and states the two or three reasons your firm fits this project. Follow with a short overview covering history, disciplines, office locations, and relevant licenses.

Key personnel and resumes

Name the project manager and discipline leads, show an organization chart, and include resumes tailored to the project type. Evaluators score the people who will actually do the work, so avoid listing senior leaders who will not be involved.

Relevant project experience

Select projects that match the scope, size, delivery method, and client type. For each one, state the client, your role, the dates, the proposed team members who worked on it, and an outcome you can verify.

Capacity and approach

Show current workload and available staff time, then outline how you would manage the project, control quality, and hold the schedule. Keep this section specific to the owner's stated goals rather than generic process language.

Past performance and references

Provide references who can speak to cost, quality, and schedule, and confirm they are expecting a call. If the buyer uses a formal evaluation form, our guide to the past performance questionnaire explains how those evaluations work.

Required forms and certifications

Include every form the request for qualifications lists, such as the SF 330 for federal architect-engineer work, plus insurance, licensing, and small business certifications when requested. A missing form can make an otherwise strong submission nonresponsive.

How to write a statement of qualifications in six steps

1. Decide whether to pursue. Confirm you have relevant projects and available key staff before investing hours in the response.
2. Build a compliance checklist from the RFQ, covering page limits, section order, formatting rules, required forms, and the submission deadline.
3. Pick the team first, then the projects. Choose projects the proposed team actually delivered, so resumes and project sheets reinforce each other.
4. Pull approved content, then tailor it. Start from current resumes, project descriptions, and firm boilerplate, and rewrite the parts that speak to this owner's priorities.
5. Write to the evaluation criteria. Mirror the stated criteria in your headings so reviewers can find and score each item quickly.
6. Review for accuracy and compliance. Check every date, license, and project figure, confirm each named person is available, and run a final compliance pass before you submit.

Build every SOQ from a governed content library

Most of an SOQ is reused content: resumes, project profiles, firm history, licenses, and certifications. The problem is that this content goes stale quickly. A resume that omits the last two years of work, or a project sheet with an outdated contract value, undercuts the credibility the whole document is trying to build.

The Consortium for Service Innovation offers a useful model in its Knowledge-Centered Success methodology: capture knowledge in the flow of work, reuse it, and improve it each time it is used. The KCS resource library describes these practices in detail. Applied to SOQs, every submission becomes a chance to refresh the resumes and project profiles you drew from, so the next pursuit starts from better content.

A governed content library puts that into practice. Each resume and project profile has an owner, a review cycle, and an approval history, and approved content can be pulled into Word or Excel instead of hunted down across shared drives. The same library supports your RFP response work, so qualifications content and proposal content stay consistent.

If your team rebuilds resumes and project sheets for every request for qualifications, book a RocketDocs demo to see how a governed library turns that effort into a pull-and-tailor workflow.