A request for qualifications (RFQ) is a solicitation that asks firms to submit their credentials, relevant experience, key personnel, and past performance so a buyer can shortlist or select the most qualified provider before price is negotiated. Public agencies use it most often for architecture, engineering, design-build, and other professional services.

That makes a request for qualifications different from almost every other solicitation a response team sees. You are not pitching a solution or a number. You are proving that your firm, your people, and your track record are the safest choice for the work. The table below shows how it compares with the documents it is most often confused with.
| DOCUMENT | WHAT THE BUYER WANTS | IS PRICE INCLUDED | TYPICAL NEXT STEP |
|---|---|---|---|
| Request for qualifications | Credentials, team, relevant experience, and past performance | Usually not at this stage | Shortlist, interviews, or negotiation with the top-ranked firm |
| Request for proposal | A solution, approach, and price for a defined need | Usually yes | Evaluation, negotiation, and award |
| Request for quotation | Prices for clearly specified goods or services | Yes, price is the focus | Award to the best price that meets the specification |
| Request for information | Market information to shape a future solicitation | No | The buyer drafts an RFP or RFQ |
One naming warning: "RFQ" also stands for request for quotation, which is a price-focused document. Always read the title and the evaluation criteria before you assume which one you are holding.
What is a request for qualifications?
A request for qualifications is the buyer's first filter. Instead of asking every interested firm to write a full technical and cost proposal, the buyer asks for a qualifications package, scores it against published criteria, and moves only the strongest firms forward. Depending on the procurement, the next step might be interviews, a shortlist invited to submit full proposals, or direct negotiation with the top-ranked firm.
Your answer to an RFQ is usually called a statement of qualifications (SOQ). If you need the detail on building that document section by section, our statement of qualifications guide covers it. This article focuses on the solicitation itself: why buyers issue it, what they score, and how to respond.
Why buyers use qualifications-based selection
The model is written into law for federal design work. According to the National Society of Professional Engineers, the federal Brooks Architect-Engineers Act, enacted in 1972, requires federal agencies to use qualifications-based selection (QBS) when procuring design services, and forty-six states have implemented some form of QBS law. Many of those state laws are known as "mini-Brooks" acts.
Federal architect-engineer selection
FAR Subpart 36.6 sets the federal rules. Agencies negotiate architect-engineer contracts based on the demonstrated competence and qualifications of prospective contractors, at fair and reasonable prices. Firms file Standard Form 330, Architect-Engineer Qualifications, which GSA publishes as the standard qualifications form. Evaluation boards score each firm on six criteria:
- 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 contracts with government agencies and private industry, in terms of cost control, quality of work, and compliance with performance schedules.
- Location in the general geographical area of the project and knowledge of the locality.
- Acceptability under other appropriate evaluation criteria.
The board then holds discussions with at least three of the most highly qualified firms and recommends at least three in order of preference. Price is not one of the scoring criteria; negotiation comes after the selection.
Two-phase design-build
Design-build procurements follow a similar pattern. Under FAR 36.303-1, phase one evaluates technical approach (but not detailed design), technical qualifications such as specialized experience and capability to perform, and the past performance of the offeror's team. Cost or price factors are not permitted in phase one. The solicitation must state the maximum number of offerors invited to phase two, and that number cannot exceed five unless the contracting officer determines that a greater number is in the government's interest.

What a request for qualifications usually asks for
State, local, and private RFQs vary, but most ask for some version of the same building blocks:
- A cover letter and firm overview, including legal name, locations, and the office that will do the work.
- An organization chart for the proposed team, with clear roles.
- Resumes for key personnel, tied to the roles in the org chart.
- Relevant project experience, often limited to a set number of projects within a recent time window.
- Past performance evidence and client references.
- A statement of capacity, showing the team can absorb the work on the required schedule.
- A high-level approach or understanding of the project, without detailed design or pricing.
- Required forms, certifications, licenses, and insurance documentation.
How to respond to a request for qualifications
Treat an RFQ as a scoring exercise, not a brochure. A practical sequence looks like this:
- Decide whether to pursue. Check the scope, the evaluation criteria, and your relevant projects honestly. A thin qualifications package rarely makes a shortlist.
- Build a compliance checklist from the solicitation. List every required section, form, page limit, and formatting rule, and assign an owner to each.
- Mirror the evaluation criteria. Organize your response in the same order the buyer will score it, and use the buyer's terminology in your headings.
- Choose projects for relevance, not prestige. Pick the projects closest to the buyer's scope, size, delivery method, and geography, and name the staff who actually worked on them.
- Tailor every resume to the proposed role. Lead each resume with the experience that matches the role on this pursuit, not a generic career summary.
- Prove capacity and past performance with specifics. Current workload, availability of key staff, and references who can speak to schedule and quality carry more weight than adjectives.
- Review, complete the forms, and submit early. A missing signature, form, or expired certificate can get an otherwise strong package set aside.
Keep qualifications content ready before the RFQ arrives
Most of an RFQ response is reused content: firm descriptions, resumes, project sheets, and references. The pressure comes from the fact that this content goes stale quickly. People change roles, projects finish, and references move on. Teams that rebuild these pieces from old files for every pursuit lose time to searching and checking.
The Consortium for Service Innovation offers a useful model here. Its Knowledge-Centered Success (KCS) methodology treats knowledge as something captured and improved as part of everyday work, so the best version is always the one people reuse. Applied to qualifications, that means updating a project description when the project closes and refreshing a resume when someone takes on a new role, not when the next RFQ lands.

A governed content library makes that practical. In RocketDocs, each content record has an owner, an SME, a review cycle, an expiration date, and a version history, and records can be tagged with custom attributes such as service line, region, or market. Approved resumes, project descriptions, and past performance narratives are ready to pull into a new response, so the team spends its time tailoring instead of hunting. The same records also feed full proposals for RFP response, so one library serves every solicitation type.
If your team answers requests for qualifications regularly and wants approved resumes, project sheets, and references ready on day one, book a RocketDocs demo to see how a governed content library shortens the path from solicitation to submission.
Looking for the platform behind this? See the RocketDocs platform or book a demo.