---
title: "RFQ Process"
url: "https://www.arphie.ai/glossary/rfq-process"
collection: glossary
lastUpdated: 2026-08-12T18:39:19.054Z
---

# RFQ Process

The request for quotation (RFQ) process is the end-to-end workflow a buyer and prospective suppliers use to define a well-scoped purchase, request comparable quotes, resolve questions, evaluate responses, select a supplier, and convert the award into a purchase order or contract. It fits purchases with settled specifications, quantities, delivery needs, and decision rules.



Our role begins when the RFQ reaches a supplier. With [Arphie's AI agents](https://www.arphie.ai/features), we import the buyer's file, create source-backed first drafts from approved knowledge, show sources and confidence signals, coordinate review, and export the approved response. We do not run buyer-side sourcing or select suppliers.



## When to Use an RFQ, RFP, or RFI



Choose the document based on what is still unknown. The U.S. General Services Administration makes the practical distinction that an [RFQ seeks pricing](https://www.gsa.gov/small-business/training-and-events/rfis-rfqs-and-rfps) when the buyer already knows its need. A request for proposal (RFP) asks suppliers to explain a fuller solution, while a request for information (RFI) gathers market input before a formal solicitation.



| Document | What the buyer knows | What the supplier returns | Best fit |
| --- | --- | --- | --- |
| RFI, request for information | The business need is known, but the market or available approaches are unclear | Capabilities, market information, and possible approaches | Market discovery and requirement shaping |
| RFP, request for proposal | The outcome is known, but suppliers may solve it in different ways | A proposed solution, delivery plan, evidence, and pricing | Complex services, technology, and outcome-based work |
| RFQ, request for quotation | The specification, quantity, and commercial baseline are defined | A comparable quote with price, delivery, terms, and required qualifications | Standardized goods or tightly scoped services |



Use an RFQ when two capable suppliers should be able to read the requirement and price substantially the same scope. Use an RFP when supplier approach is part of the decision. For that broader workflow, see [Mastering RFP Management: Strategies for Success in Proposal Development](https://www.arphie.ai/articles/mastering-rfp-management-strategies-for-success-in-proposal-development). Use an RFI before either document when the buyer still needs to learn what the market can provide.



In architecture, engineering, and some public-sector contexts, RFQ can also mean **request for qualifications**. The workflow here uses the procurement meaning, **request for quotation** or **request for quote**.



## What an RFQ Package Should Include



The response format matters as much as the request. A narrative prompt such as “provide your best price” pushes suppliers to make different assumptions. A line-item schedule makes those assumptions visible.



| RFQ section | What to include | Why it matters |
| --- | --- | --- |
| Purchase context | Business objective, intended use, and procurement contact | Helps suppliers spot scope conflicts early |
| Scope and specifications | Item or service descriptions, standards, mandatory requirements, and permitted alternatives | Establishes the common baseline |
| Quantities and term | Units, volumes, contract length, option periods, and forecast assumptions | Prevents different volume bases |
| Delivery requirements | Locations, milestones, lead times, implementation dates, and acceptance conditions | Makes timing comparable |
| Pricing schedule | Unit price, extended price, one-time fees, recurring fees, currency, freight, tax treatment, discounts, and total | Exposes the full evaluated cost |
| Commercial terms | Payment terms, quote validity, warranties, service levels, and required contract terms | Surfaces exceptions before award |
| Response instructions | File format, portal, deadline with time zone, required attachments, and naming rules | Reduces avoidable disqualification and rework |
| Clarification process | Question deadline, approved channel, response date, and amendment method | Gives every supplier the same information |
| Award basis | Pass/fail requirements, scored factors, cost formula, and expected decision date | Tells suppliers how to build a responsive quote |



Every invited supplier should receive the same version. If the buyer changes a requirement, it should issue a numbered amendment and extend the deadline when the change materially affects the response effort.



## The RFQ Process in 8 Steps



The RFQ is one shared process with two owners. The buyer controls the requirement, competition, and award. Each supplier controls its decision to bid, evidence, price, exceptions, approvals, and submission.



![Eight-step RFQ process from requirement definition to order and learning](https://cdn.prod.website-files.com/672fc2345132970736914b73/6a7952e5204f7a9be2459f6c_56a00f5d-80cd-448b-8ddb-c110fac47ca0.png)



### 1. Define the Requirement and Award Basis



The buyer converts an internal purchase need into measurable requirements. That means naming the exact product or service, quantity, quality standard, delivery point, timeline, and acceptance condition. Stakeholders should separate mandatory requirements from preferences so a useful option does not become an accidental disqualifier.



The award basis belongs in this step, before any quote arrives. The U.S. Federal Acquisition Regulation captures a sound discipline for simplified federal purchases: [disclose whether award uses price alone or other factors](https://www.acquisition.gov/far/13.106-1), then [evaluate on the stated basis](https://www.acquisition.gov/far/13.106-2). Private and public buyers may follow different rules, but changing criteria after seeing prices undermines the comparison in either setting.



**Handoff:** An approved requirement, budget, sourcing owner, and evaluation model.



### 2. Build the Package and Invite Viable Suppliers



The buyer turns the requirement into an RFQ package with a structured pricing schedule and response template. Procurement then invites suppliers that can plausibly meet the mandatory scope, capacity, location, security, and timing requirements.



Supplier qualification and quote evaluation are different decisions. Qualification asks whether a supplier is capable and eligible. Quote evaluation asks which compliant offer provides the best result under the published award basis. Keeping those gates separate avoids spending review time on quotes that could never receive the award.



**Handoff:** A controlled RFQ version, invitation list, and distribution record.



### 3. Intake the RFQ and Make a Go/No-Go Decision



Each supplier records the [RFQ submission deadline](https://www.arphie.ai/glossary/rfq-submission-deadline) as an exact date, time, and time zone, along with the submission channel, question cutoff, required attachments, and named owner. The owner then assesses fit before assigning response work.



A useful decision considers mandatory compliance, delivery capacity, commercial fit, competitive position, relationship strength, approval availability, and the effort required before the deadline. A documented [go/no-go scorecard](https://www.arphie.ai/blog/rfp-go-no-go-scorecard) keeps enthusiasm for a logo or deal size from hiding a weak fit. A fast no-go protects time for opportunities the supplier can serve and win.



**Handoff:** A bid decision, accountable owner, response plan, and internal review schedule.



### 4. Run a Controlled Clarification Period



Suppliers should flag contradictions, missing units, ambiguous acceptance criteria, incomplete technical details, and terms that affect price. Questions should describe the decision needed without revealing unnecessary competitive strategy.



The buyer collects questions through one channel, answers them consistently, and shares material clarifications with every bidder. Any change to scope, quantity, or terms belongs in an amendment rather than an informal email. Suppliers should update their compliance map, pricing assumptions, and task plan against the latest version.



**Handoff:** A final question log and common, version-controlled requirement.



### 5. Draft the Response and Build the Price



The supplier creates the quote against the buyer's structure. Each answer should state compliance directly, provide the requested evidence, and identify any assumption or exception beside the affected requirement. Pricing should connect units, quantities, rate, extended amount, one-time fees, recurring fees, discounts, currency, tax treatment, validity, and total.



For document-heavy RFQs, we use Arphie to import the buyer's Word or Excel file and generate source-backed first drafts from connected company knowledge. Sources and confidence signals help the response owner send uncertain or high-risk answers to the right subject matter expert. Finance still owns the price. Legal, security, product, and delivery leaders remain accountable for commitments in their domains.



**Handoff:** A complete first draft, pricing schedule, exception log, and evidence set.



### 6. Review, Approve, and Submit



A dependable final review uses three passes:



- **Compliance review:** Confirm that every required field, attachment, signature, format, and instruction is satisfied.



- **Commercial review:** Recalculate extensions and totals, then confirm currency, fees, discounts, payment terms, validity, margin, and approval authority.



- **Evidence and risk review:** Confirm that claims match approved sources and that exceptions, dependencies, service levels, security statements, and delivery promises have accountable sign-off.



The response owner resolves comments, locks the final version, exports it in the required format, and submits through the approved channel. The supplier should retain the exact package sent, its timestamp, and the buyer's receipt confirmation.



**Handoff:** An approved, traceable submission.



### 7. Normalize Quotes, Evaluate Them, and Award



The buyer first applies disclosed pass/fail gates. It then normalizes compliant quotes to the same currency, quantity, delivery basis, and evaluation period. Evaluated cost may include unit prices, implementation, freight, support, maintenance, and other costs named in the RFQ. A clarification can resolve ambiguity, but it should not silently rewrite a supplier's offer.



An illustrative model for a standardized business-to-business service could look like this:



| Factor | Method | Example weight |
| --- | --- | --- |
| Mandatory specifications | Pass/fail gate | Required |
| Evaluated cost | Lowest cost divided by the supplier's cost, multiplied by 100 | 55% |
| Delivery or implementation | Score against the stated required date | 15% |
| Service and warranty | Score against disclosed service requirements | 10% |
| Commercial terms | Score payment, validity, and exceptions | 10% |
| Supplier performance and risk | Score using the evidence requested in the RFQ | 10% |



Multiply each factor score by its weight, then add the weighted scores. Pass/fail gates contribute no points. The weights are only an example and should reflect the purchase and applicable procurement rules. Scenario-test a relative price formula before publishing it, because one unusually low quote can distort the remaining scores. Current [UK public procurement guidance](https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-procure-phase/assessing-competitive-tenders-html) defines value for money through whole-life economy, efficiency, and effectiveness, and says tenders do not have to be awarded on the lowest price.



**Handoff:** A documented evaluation, approval, award notice, and any required supplier feedback.



### 8. Turn the Award Into an Order and Capture What Changed



The award starts a commercial handoff. The buyer and selected supplier reconcile the final scope, prices, terms, dates, and exceptions before the quote becomes a purchase order, purchase agreement, or contract. Delivery owners should receive the same assumptions used to price the work.



The buyer archives the RFQ, amendments, responses, evaluation, approvals, and award record. The supplier archives its final response, commitments, and outcome. Reusable, approved answers can return to the knowledge base, while customer-specific pricing and negotiated terms stay with the opportunity. A short debrief should identify requirement gaps, repeated clarifications, approval delays, and content that needs an owner.



**Handoff:** An executable commercial document and a cleaner starting point for the next RFQ.



## A Compact RFQ Response Example



Consider a fictional software buyer requesting 1,000 user licenses, implementation, single sign-on, and support. A response that exposes the pricing basis is easier to evaluate than a quote containing only a grand total.



| Buyer field | Supplier response | Internal review point |
| --- | --- | --- |
| Subscription | 1,000 users × $120 per user per year = $120,000 per year | Quantity, unit, term, and total agree |
| Implementation | Fixed fee of $18,000; six weeks from completed kickoff | Delivery lead approves scope and dependency |
| Security Assertion Markup Language (SAML) single sign-on | Included; configuration described in the technical appendix | Product and security evidence is current |
| Premium support | $12,000 per year; stated hours and response targets attached | Service owner approves the commitment |
| First-year total | $150,000 in USD, excluding applicable taxes | Finance recalculates every component |
| Quote validity | Valid through September 30 | Date supports the buyer's award schedule |
| Assumptions | Buyer provides an administrator and required data by kickoff | Assumptions are visible and acceptable |



The detail protects both sides. The buyer can normalize competing offers, and the supplier avoids committing to an unstated scope.



## Where RFQ Automation Helps, and Where Humans Stay Accountable



[RFQ automation](https://www.arphie.ai/glossary/rfq-automation) should remove retrieval, copying, routing, and status work. It should not make commercial promises or approve risk.



| RFQ task | Useful automation | Human accountability |
| --- | --- | --- |
| Intake | Extract questions, sections, instructions, and deadlines | Confirm scope, fit, owner, and plan |
| Knowledge retrieval | Find approved answers across connected sources | Decide whether the evidence fits this buyer |
| First draft | Draft responses in the buyer's structure | Tailor positioning and confirm accuracy |
| Collaboration | Assign reviewers, track status, and send reminders | Resolve conflicts and escalate decisions |
| Quality control | Flag blanks, weak support, and inconsistent answers | Approve price, legal terms, security claims, and delivery promises |
| Export and submission | Return answers to the original Word or Excel file | Conduct final compliance review and submit |



Buyer-side e-sourcing tools handle invitations, bid collection, and evaluation. A one-line commodity quote may need only the buyer's pricing sheet. Our platform addresses the supplier-side response work that appears when an RFQ contains technical, security, service, or implementation questions and several reviewers. We turn approved knowledge into a reviewable first draft, while accountable people retain control over the final quote.



## RFQ Metrics That Expose Bottlenecks



End-to-end cycle time reveals that an RFQ is slow. Stage metrics reveal why.



| Metric | Owner | What it diagnoses |
| --- | --- | --- |
| Requirement-to-issue time | Buyer | Specification and internal approval delays |
| Clarification rate | Buyer | Ambiguous requirements or response fields |
| Complete-quote rate | Buyer | Template and instruction quality |
| Issue-to-award time | Buyer | Evaluation and decision delays |
| Time to first draft | Supplier | Knowledge retrieval and drafting friction |
| Subject matter expert review hours | Supplier | Weak reuse, ownership, or source quality |
| Submission rework | Supplier | Compliance and approval failures |
| Win rate by fit tier | Supplier | Go/no-go quality and competitive fit |
| Award-to-order time | Both | Contracting and handoff friction |



Track the timestamp and owner at each gate. A single average across every RFQ can hide the difference between a simple price sheet and a strategic response with security, legal, and implementation review.