RFI vs RFQ vs RFP: Which One to Send and When

These three acronyms get used loosely, and the cost lands on suppliers, who respond to the wrong question, and on you, who then cannot compare the answers.

Request for information

An RFI is research. You are asking who serves this market, what they do, roughly what it costs, and what you should be asking for. Keep it short — under ten questions — because response quality drops sharply with length and you have no commitment to offer yet.

Request for quotation

An RFQ works only when you can specify exactly what you want, down to quantities, specifications, and delivery terms. Its value is comparability: every response should differ only in price and lead time. If you find yourself writing explanatory paragraphs, you probably need an RFP.

Request for proposal

An RFP asks suppliers how they would solve the problem. It suits services, complex implementations, and anything where approach and team matter. It is also expensive on both sides, so reserve it for decisions that justify the effort.

Common mistakes

• Running an RFP for a commodity where an RFQ would settle it in a week.
• Asking 300 questions and reading none of the answers carefully.
• Inviting eight suppliers when you can only seriously evaluate three.
• Changing requirements mid-process without resetting the timeline for everyone.

Match the document to the decision, tell suppliers how you will score, and give them enough time to answer well. Sourcing quality tends to follow from those three things more than from the template you use. Which document your policy requires at which value belongs in the threshold table of your procurement policy, and whoever wins still has to clear supplier onboarding before a purchase order can be issued.

Start with the operating case, not the feature list

Context matters in sourcing document choice because the visible transaction is only the final record of several earlier decisions. Consider this operating case: A team sends a forty-question RFP for a standard courier lane where price, delivery coverage, and claims handling are already known. Suppliers spend a week writing prose that makes comparison harder. The useful question is not whether a form was completed. It is whether the evidence available at that moment was sufficient for a named owner to make a reversible, explainable decision. That distinction keeps the process practical: control is attached to consequence, not paperwork.

Trace one ordinary case and one awkward case from the first request to the final accounting entry. Record who knew what, which system held it, and what happened when the expected path failed. This exposes handoffs that a workshop diagram misses: the spreadsheet used to repair supplier names, the inbox where an approver asks for context, or the monthly reconciliation that makes reports believable after the fact.

Evidence to assemble before changing the process

Do not begin configuration with a blank workflow canvas. Build a small evidence pack first. It should be compact enough for the working team to challenge line by line, and representative enough that a successful pilot means something. The minimum useful pack contains the following inputs.

• A clear statement of the decision and what remains unknown
• Market maturity and the number of credible suppliers
• Comparable specification, volumes, constraints, and evaluation criteria
• Decision timetable, stakeholders, and commercial authority

The decisions the workflow must make explicit

A dependable sourcing document choice process does not ask everyone to approve everything. It identifies a small set of decisions, assigns each to the person with the authority and information to make it, and records enough context to explain the result later. If two reviewers are checking the same fact, remove one. If nobody can state what would cause rejection, the step is probably ceremonial.

• Use an RFI to learn, an RFQ to price a defined requirement, or an RFP to compare approaches
• How much supplier effort the opportunity justifies
• Which criteria can be scored consistently
• Whether negotiation follows the written response

Write these decisions as testable statements. For example: approve when the budget is available and the need is valid; route to security only when company data enters the service; reject when the supplier identity cannot be verified. Testable rules make demos, implementation workshops, and post-launch audits materially more useful than labels such as finance review or procurement check.

A practical implementation sequence

Sequence matters because teams otherwise automate the cleanest diagram and discover the real exceptions after launch. Keep the first release narrow, but do not make it artificially easy. Include enough volume to observe behaviour and at least one category with meaningful exceptions. A sensible sequence is:

1. 1Write the decision before the questionnaire
2. 2Give suppliers the same data and clarification window
3. 3Score independently against published criteria
4. 4Document assumptions and test the preferred response before award

At each step, preserve a manual recovery path and name the person allowed to use it. Recovery is not failure; invisible recovery is. An exception handled in a private message teaches the system nothing. An exception recorded with a reason can inform the next policy or configuration change.

Failure modes worth testing before launch

Happy-path acceptance testing proves very little. Build tests from the cases that cause delay, uncontrolled commitment, duplicate work, or misleading reporting. The following failures are common enough to deserve an explicit owner and expected response before rollout.

• Using an RFP when requirements are already standard
• Asking questions that do not affect scoring
• Changing weights after seeing supplier names
• Treating polished writing as implementation evidence

Run these as tabletop exercises with the requester, approver, finance operator, and system administrator in the same room. If the answer depends on somebody remembering an unwritten convention, document it or redesign the path. If the answer requires administrator intervention for an ordinary exception, calculate that support load before declaring the workflow scalable.

Measure the control without gaming it

A metric needs a stable denominator, a reproducible source, and an owner who can change the result. Publish the definition beside the number. Show medians with a tail percentile where time is involved, and split rates by material populations rather than averaging unlike work together.

• Comparable and complete responses received
• Supplier clarification volume
• Evaluation time and scorer variance
• Award assumptions validated before contract

Review the underlying records monthly during rollout, then quarterly once behaviour stabilises. A rising exception rate can mean the process is deteriorating, but it can also mean the system has started recording exceptions that were previously invisible. Interpret the movement before rewarding or correcting anyone.

Limits and cases that need a different tool

No sourcing document choice design is universal. State exclusions before estimating benefits. That protects the business case from inflated addressable volume and tells operators where a different control, specialist system, or human judgement remains necessary.

• A document cannot replace discovery with users
• Low supplier participation may indicate excessive effort
• Price comparison fails when scope remains ambiguous
• Competitive process does not guarantee a competitive market

Keep a decision record that survives the project

For each material choice, record the date, owner, evidence considered, option selected, rejected alternatives, and the condition that would trigger review. This is not meeting minutes. It is a compact explanation of why the company accepted a particular cost or risk. Six months later, a new operator should be able to distinguish an intentional compromise from an accidental omission without locating the original project team.

Use the record during monthly operations reviews. Compare the assumptions made at approval with actual volume, cycle time, exceptions, and supplier behaviour. When an assumption fails, change the rule or reopen the decision; do not quietly build manual work around it. That feedback loop is what turns a configured workflow into an operating system rather than a frozen implementation project.

The final design should be easier to explain than the process it replaces. If a requester cannot predict what information will be required and who will decide, complexity has merely moved behind the screen. Keep the common path short, make consequential exceptions visible, and revisit the rules when transaction patterns or organisational ownership change.