Two-step procurement: qualify vendors first, open prices second

Reference article · 5 min read

A two-step solicitation splits one competition into two gates. In step one, firms submit a technical response with no pricing in it at all: approach, staffing, relevant experience, and sometimes a hands-on exercise. The agency evaluates them against criteria published in the solicitation and decides which firms continue. Only then, in step two, are sealed price submissions opened, and only from the firms that advanced.

The point of the extra step is control over what influences judgment. When price sits in front of an evaluator during technical review, it colors the reading of the technical material and hands a protesting firm an easy argument that scoring followed the number rather than the work. Many state and local procurement codes recognize some version of this, often under names like multi-step sealed bidding. Authority, notice, and protest timing vary by jurisdiction, so confirm the specifics in your own code and with counsel before building a schedule around it.

How the two steps fit together

There are two common shapes, and the solicitation has to say which one it is.

Qualify, then lowest price. Step one is pass or fail. Every firm judged technically acceptable advances, and award goes to the lowest responsive price among them. Technical scores do not carry forward, which suits buys where "good enough" is definable.
Qualify or shortlist, then best value. Step one produces scores. Firms that pass, or the top set, advance, and technical score combines with price using a weighting published up front. Use it where a stronger approach is worth paying more for.

Step one may also include clarifications, which ask a firm to explain what it submitted, and in some codes discussions, which allow revisions. Most rules treat the two differently, so decide which you may use and say so.

When the extra step earns its calendar time

A two-step process adds weeks: a separate evaluation window, notice to firms that did not advance, and in some jurisdictions a protest window at that decision. The cost is worth paying when:

Technical approaches will vary widely, as in systems integration, custom development, or replacing a system with unusual interfaces.
A demonstration or scripted exercise will be decisive and running it for every submitter is impractical.
The field is likely to be large and evaluating every submission in full would exhaust the panel.
Implementation risk, not unit price, is what is most likely to sink the project.

Skip it for catalog purchases, hardware refreshes, orders under an existing cooperative contract, or anything with a deadline the extra window would break.

Writing a step-one rule that survives challenge

Most two-step disputes are about the advancement decision, not the award. Write the rule so it can be applied mechanically and explained later.

Publish the mechanism. State whether step one is pass/fail, a shortlist to a fixed number, or a shortlist by minimum score, and state that score if there is one.
Define pass/fail in observable terms. "Demonstrates a migration plan addressing data conversion, cutover, and rollback" is reviewable. "Shows a strong understanding" is not.
Handle the edge cases in writing. Say what happens if fewer firms pass than expected, if there is a tie at the cutoff, and whether you may advance more or fewer than stated.
Use no criterion you did not publish. Subfactors invented during consensus are a common source of sustained protests.
Document reasons, not just numbers. A consensus record citing the language it relied on is harder to attack than bare ratings.
Give the notice your code requires. Debrief and protest rights at the non-advancement stage differ by jurisdiction.

Keeping price sealed until technical scores are locked

The separation has to be real, not just stated in the instructions.

Separate submission channels. A separate sealed envelope, or a separate upload slot with its own access role. Verify before release that your eProcurement platform supports this.
A custodian outside the panel. The procurement officer holds the price files and evaluators never receive them.
A stated rule for price leakage. Say what happens if pricing appears in the technical volume, including labor rates in resumes, and screen the volumes before distributing them.
Lock the scores first. Signed consensus results go to the file before any price is opened. Do not reopen technical scoring once price is known unless something forces it, and if that happens, document why and apply it to every firm.

Scripted exercises and demonstrations

If step one includes a live exercise, treat it as a controlled test rather than a sales meeting.

Give every firm the same script, the same synthetic or de-identified sample data, and the same time box.
Write the rubric before the first session and score immediately after each one.
Bar price discussion in the room.
Keep the effort proportionate. A long unpaid exercise narrows the field to firms with bench capacity, not to the best fit.

What to require in the solicitation and the contract

Key personnel named in step one, with substitutions requiring agency approval.
A statement that the demonstrated configuration reflects the product as it will be delivered, with roadmap features labeled as such.
A fixed price structure, so step two prices are comparable line for line.
Retention of step one submissions for the full record retention period.
Acceptance criteria that trace back to the technical claims that earned advancement.

To start, confirm your authority with counsel, pick one of the two shapes, draft the advancement rule and test it against your hardest edge case, set up the two submission channels, then build the calendar backward from your needed start date.

HQT builds and supports software for United States state and local government agencies. This article is general information, not legal advice.

Frequently asked questions

What is the difference between a two-step procurement and a two-envelope RFP?

In practice the terms overlap. Two-envelope usually describes the submission mechanics, meaning the technical response and the price response arrive in separate sealed envelopes or separate upload slots. Two-step describes the evaluation sequence, meaning technical review and an advancement decision happen first and only qualified firms have their price opened. Many solicitations use both, and the solicitation should spell out the mechanics and the sequence rather than relying on the label.

Can we disqualify a vendor for putting price in the technical volume?

You can, but only if the solicitation said so before submissions were due. Write the rule in advance, name the common forms of leakage such as labor rates in resumes or a sample invoice in an appendix, and state whether the consequence is rejection or a cure. Then apply the rule the same way to every firm and document what you found.

How much extra time does a two-step process add to a technology solicitation?

It varies with the size of the field, the length of your evaluation window, and whether your code creates protest rights at the advancement decision. Plan for a distinct technical evaluation period, time to notify firms that did not advance, any required debrief window, and then the price opening and award steps. Build the schedule backward from the date the work must begin and confirm the notice periods in your own procurement rules.

Do vendors that are not advanced after step one have protest rights?

Often yes, and the timing can be earlier than people expect because the advancement decision is itself a procurement decision in many jurisdictions. Some codes require notice and start a protest clock at that point rather than at award. Confirm the rule in your state code or local ordinance and with counsel, and write the notice and debrief steps into your schedule so the clock runs when you intend it to.

Can evaluators change technical scores after prices are opened?

Avoid it. The defensibility of a two-step process rests on technical scores being finalized and documented before anyone sees price. If something genuinely requires reopening technical evaluation, such as a discovered error or a corrective action, document the reason in the file and apply the same treatment to every firm still in the competition.