RFP vs RFQ vs ITB

Why the label changes your whole approach

These acronyms are not synonyms for "the document you have to fill in". Each one encodes a different answer to the same underlying question: how much does the buyer already know about what it wants?

When the buyer can describe the requirement completely — four hundred laptops of a defined configuration, a paving job to a published specification, a fixed quantity of a commodity — there is nothing left to compare except price and conformance. So the instrument is a sealed bid, the award is mechanical, and no amount of persuasive writing changes anything.

When the buyer knows the outcome it wants but not the best route to it — a customer service operation, a software implementation, a concession that has to work commercially for both sides — it needs to compare approaches, not just prices. So the instrument is a proposal request with published, weighted criteria, and the narrative is the product.

Everything downstream follows from that one difference: whether negotiation is permitted, whether price is opened publicly or sealed away from the evaluators, how long your response should be, and which failure modes are most likely to end you. Reading the label correctly is therefore the first real decision on any pursuit, and it is made before the bid/no-bid call rather than after it.

ITB and IFB — invitation to bid

An Invitation to Bid — or Invitation for Bids, the same instrument under a different local convention — is used when the buyer can specify the requirement completely and therefore has nothing to evaluate except conformance and price.

Bids are submitted sealed, opened at a stated public time, and often read aloud, which makes your price a public record the moment it is opened. Award goes to the lowest responsive and responsible bidder. There is normally no negotiation, no interview, no clarification round and no opportunity to explain yourself.

What that changes about your response

Nothing you write persuades anybody, because there is no scored narrative to persuade anybody with. Effort therefore goes to exactly two places: not being non-responsive, and sharpening the number. That makes the ITB the instrument where the mechanical failures do the most damage — there is no strong technical volume to offset a missing form, because there is no technical volume at all.

Two practical consequences follow. First, the pricing form is the deliverable, so it gets the same scrutiny a narrative would get on an RFP: every cell filled, arithmetic independently checked, no conditions, no annotations, the required validity period stated exactly. Second, because price is public, a losing bid is genuinely informative — you find out where you sat against the market, which is useful data you should actually go and collect.

RFQ — the acronym that means two things

This is the one that causes real confusion, because RFQ is used for two different instruments that behave almost oppositely. Read the document, never the acronym.

RFQ as Request for Quotation

A quotation request for a defined item or service, usually below a small-purchase threshold where the issuer's rules allow a simplified process — frequently "obtain three quotes". Turnarounds are short, sometimes days. The forms package is light. Award is usually to the lowest conforming quote.

The trap here is treating it casually because it is small. A quotation still has a due date, a submission channel, a signature requirement and a price form, and those four things are exactly what gets quotations set aside. A compliance matrix of eight rows takes fifteen minutes and eliminates the entire failure class — see the compliance matrix guide for the columns.

RFQ as Request for Qualifications

A completely different instrument, sometimes written RFQu and sometimes producing a Statement of Qualifications (SOQ). Here the buyer describes a problem, asks firms to demonstrate their qualifications to solve it, ranks them on those qualifications — and only then negotiates scope and fee with the top-ranked firm. If that negotiation fails, the buyer moves to the second-ranked firm.

Qualifications-based selection of this kind is the long-standing norm for architecture and engineering design services in US public procurement, and it is used elsewhere too. The defining characteristic is that price is not a selection criterion — in many cases it is not submitted at all in the first round.

What that changes: do not lead with price, do not offer a discount, and do not compete on being cheap. Compete on directly comparable project experience, on the specific individuals who will actually be assigned, and on demonstrated performance on projects of the same type and scale. Named people with relevant, verifiable history are the product.

RFP — request for proposals

An RFP is used when the buyer knows the outcome it wants but not the single best way to get there, or when there are several legitimate approaches worth comparing. Rather than specifying the solution, it publishes criteria and weights, and asks responders to propose.

Award is on best value: a committee scores each response against the published rubric, price is one factor among several, and the highest total — not the lowest price — wins. Because scoring is meant to be blind to price, the pricing volume is normally submitted as a separate sealed file or envelope and opened after technical scoring, or scored by a formula applied separately.

Negotiation is usually permitted in some form: written clarifications, a competitive range or shortlist, interviews or oral presentations, product demonstrations, and revised or best-and-final offers. That flexibility is the whole reason an issuer chooses this instrument rather than a sealed bid.

What that changes about your response

The narrative is the product, and the rubric is its specification. Write to the criteria in the issuer's own order and vocabulary, let page weight roughly track point weight, and assume your reader is scoring a stack of submissions against a sheet rather than reading for pleasure. Evaluators award points for what they can find; content placed somewhere other than where the rubric expects it scores lower than the identical content placed correctly.

The full sequence — from pulling the solicitation through to confirming the upload landed — is in how to respond to an RFP.

RFI — request for information

An RFI makes no award. The buyer is doing market research: does a solution to this problem exist, who provides it, roughly what does it cost, what would a realistic schedule look like, and what should the eventual solicitation actually ask for?

It is easy to dismiss as unpaid work, and that is usually a mistake. An RFI is the last moment at which the requirements are still soft. Once they harden into a solicitation, a specification written around somebody else's product, or a minimum qualification set slightly above what you can evidence, will screen you out mechanically and there will be nothing you can do about it except file a question and hope.

How to respond well

• Answer the questions asked, in order, concisely. An RFI response is not a capability brochure and buyers notice which is which.
• Be honest about ranges and constraints. The buyer is building a budget and a schedule from these answers, and an unrealistic number now becomes an unrealistic requirement later.
• Flag requirements that would unnecessarily narrow competition, and say why. Issuers are frequently grateful, because a sole-sourced specification is a problem for them too.
• Describe your capability the way you would want it specified — in functional terms rather than brand terms.
• Mark anything genuinely proprietary exactly the way the issuer instructs. RFI responses are often public records, and there is usually a prescribed method for designating confidential material.

One caution: helping to write the specification is different from providing information. Some procurements carry organizational-conflict-of-interest rules that bar a firm which drafted the requirements from competing on the resulting contract. Read that language before you offer to draft anything.

Sole source and emergency procurement

A sole-source procurement is an intent to buy from one supplier without competing the requirement, supported by a written justification — typically that only one supplier can meet the need, that compatibility with an existing installed system requires it, or that a genuine emergency leaves no time to compete.

Most public issuers are required to post the intent publicly for a short window, during which another supplier may object by demonstrating that it can in fact meet the requirement. That window is frequently measured in days.

If you are the objector, that notice is your only opening, and it closes fast. The objection has to be specific: not "we also do this", but a point-by-point demonstration against the stated justification, with evidence, filed through the channel the notice names, inside the window. Watch the notices in your category — by the time you hear about the contract any other way, it is awarded.

If you are the intended supplier, your job is to help the buyer write a justification that survives audit. That means factual, verifiable statements tied to the requirement — a patented process, a proprietary interface, a certification only you hold, documented compatibility constraints — rather than statements about preference, incumbency or relationship. A weak justification is a risk to you as much as to the buyer, because a sustained objection or an adverse audit finding can unwind the award.

When the title and the document disagree

Issuers use these words inconsistently, and templates get recycled across departments for years. You will meet documents titled "RFP" that award to the lowest conforming price with no scored criteria whatsoever — that is an invitation to bid wearing the wrong name. You will meet documents titled "ITB" that contain a weighted evaluation rubric and contemplate interviews. The title is a filename. The document is the contract for how you will be judged.

Three clauses tell you what you are actually holding. Find all three before you plan anything:

1. The award-basis clause. Does it say lowest responsive and responsible bidder, or best value to the issuer, or highest-ranked qualifications? That single sentence decides whether narrative quality can affect the outcome at all.
2. The evaluation criteria section. Is there a rubric with weights or points? If yes, you are being scored and the criteria are your document specification. If there is no rubric, there is nothing to score and your entire effort belongs on compliance and price.
3. The pricing and negotiation provisions. Is price sealed separately from the technical response? Are clarifications, a competitive range, interviews or best-and-final offers contemplated? Separation and negotiation both point to a scored, best-value process regardless of what the cover page says.

Where those three clauses contradict each other — and they sometimes do, because different sections were written by different people in different years — that is not a puzzle for you to solve privately. It is a question for the question window, filed in writing before the deadline, quoting both clauses. The answer arrives as an addendum that binds every responder equally, which is exactly the outcome you want.

Whichever instrument it turns out to be, the mechanical failure modes are largely shared — they are set out in why bids are rejected — and the way we run a public-sector pursuit is described on the government track page.