To run an RFP, define the requirement and the scoring weights first, write questions that map to those weights, invite a competitive but manageable field, evaluate every bid against the criteria you agreed before bids arrived, then award and move the winner straight into a contract. Most of the outcome is settled before the RFP is sent.
RFPs that go wrong rarely fail at the award. They fail earlier: requirements that meant different things to different suppliers, a scoring rubric written after the bids came in, and a decision nobody can explain to finance six months later. This guide walks through the process that avoids all three.
What are the steps to run an RFP?
Five steps cover the whole event. The first two happen before any supplier hears about it, and they decide most of what follows.
- Step 1 Define the requirement Scope, must haves, criteria, weights and roles, agreed in writing
- Step 2 Build the RFP document Questions mapped to criteria, pricing in a fixed grid
- Step 3 Invite and manage suppliers A competitive field, clear milestones and one shared Q&A
- Step 4 Evaluate and score Independent scoring against the weights you locked
- Step 5 Award and contract Record the rationale, then draft the contract from the award
AI contract lifecycle management| Step | What you decide | The usual trap | What prevents it |
|---|---|---|---|
| 1. Define | Scope, criteria, weights, who scores | Weights agreed after bids arrive | Sign off on criteria before publishing |
| 2. Build | Questions and pricing format | Questions nobody scores, free text pricing | Map every question to a criterion and use a pricing grid |
| 3. Invite and manage | Who bids, dates, clarifications | Answering one supplier privately | Share every clarification that changes the ask |
| 4. Evaluate | Scores and the shortlist | The loudest voice anchors the room | Score independently, then reconcile |
| 5. Award | Winner, rationale, contract | Retyping the deal into a separate contract tool | Draft the contract from the award record |
Where each step usually goes wrong, and the habit that prevents it.
How do you define the requirement and scoring criteria?
Get clear on what you need and how you will decide, and get stakeholders to agree it in writing before you write a single question. Three things must be settled here:
- Scope: what is in, what is out, and which items are must haves rather than nice to haves.
- Criteria and weights: how much price, capability, security, implementation and support each count, fixed before anyone sees a bid.
- Roles: who scores which sections, who advises and who signs off.
Skip this step and every later stage inherits the ambiguity. If the weights are chosen after responses arrive, you have not run an evaluation. You have rationalized a preference, and a losing bidder can say so.
How do you write an RFP document suppliers can answer well?
Write the RFP as a set of clear questions mapped to your scoring criteria, plus a structured pricing request. If a question does not map to something you will score, cut it.
- Author together, not in sequence: legal, procurement and the business shape one document in one place, instead of procurement drafting, emailing legal and waiting for a marked up copy.
- Ask for pricing in a fixed structure: give suppliers a pricing sheet with your line items, not a blank box, so bids compare line by line.
- Reuse what already worked: start from a category template, or clone a past event with its questions and criteria.
Not sure an RFP is the right request at all? An RFQ is faster when the spec is fixed and price is the only variable. See RFI vs RFQ vs RFP for the decision.
Introducing RFPflow: event setup, supplier responses, AI scoring and award on one record.
How many vendors should you invite, and how do you keep it fair?
Too few suppliers and you lose competitive tension. Too many and evaluation drags on. Shortlist the suppliers who can meet the must haves, and check supplier risk before you invite, not after you award.
Then publish with clear milestones: questions due, responses due, presentations if you need them. Keep every supplier question in one shared place. When a clarification changes the ask, every bidder needs to see it, and a milestone change has to reach all of them at once. That record is what keeps the event defensible when a losing bidder asks why.
The answer goes back to one supplier. The others bid on a different reading of the scope.
Every supplier uses its own format. Someone rebuilds them in a spreadsheet before anyone can compare.
Scores arrive in separate files after a meeting where one view already won.
The award sits in a spreadsheet. Legal starts the contract from a blank template.
How should you evaluate and score RFP responses?
Score each proposal against the weighted criteria you locked in step 1, and compare pricing on the structured sheet. Two habits make this stage trustworthy:
- Score independently, then reconcile: evaluators submit scores before they discuss, so the first opinion voiced does not set the result.
- Benchmark the price: compare bids with what you paid before, not only with each other, so you know whether the lowest bid is actually a good price.
AI helps most with the reading. In RFPflow, Aavenir AI reads every response against your criteria, drafts a score and a summary for each section and recommends suppliers. Evaluators accept or change every score, and the decision stays with them.
Why does the award to contract step slow teams down?
Pick the winner on the total weighted score and document the rationale. That record is your audit trail. Then watch for the cost most teams accept without noticing: the award lives in the sourcing tool or a spreadsheet, and the contract is created from scratch in another system. Someone retypes the supplier, the terms and the pricing, and negotiated discounts or service levels go missing in the gap.
When sourcing and contracting share one record, the award is the start of the contract. In RFPflow you can split an award by line item, and Contractflow drafts a contract for each winner with the awarded lines and value carried over. The full flow is on the source to contract page.
We always had to manually create, edit, deliver, organize, and evaluate our RFx process. Aavenir has saved us countless hours of administrative work. The tool has also allowed us to focus on other tasks instead of organizing responses and dealing with email chains. Everything is organized in one place now, and we can respond to suppliers twice as fast.
Procurement Manager, a global premium petfood manufacturer
Source: global premium petfood manufacturer case study, RFPflow on ServiceNow.
When is a full RFP not worth running?
An RFP is a heavy instrument. It earns its cost when the decision depends on approach, capability and risk as much as on price. It is the wrong tool when:
- The spec is fixed and price is the only variable: run an RFQ and compare line items.
- There is only one credible supplier: a sole source justification and a negotiation are more honest than a contest with one real bidder.
- The spend is small or already covered: buy from the framework agreement or catalog you already negotiated.
- You do not yet know the market: send an RFI first, or the RFP will ask the wrong questions.
Software will not fix a requirement nobody agreed on. If stakeholders cannot settle the scope and the weights, delay the event rather than publish it.
What goes on an RFP checklist?
- Scope, must haves and nice to haves agreed in writing
- Scoring criteria and weights locked before any bid arrives
- Evaluators and their sections named
- Every question mapped to a criterion, nothing you will not score
- Pricing requested in a fixed, comparable grid
- Milestones published, supplier questions answered in one shared place
- Evaluators score independently, then reconcile
- Pricing benchmarked against history, not only against other bids
- Award rationale documented for audit
- Winner moves straight to contract, with nothing retyped
The bottom line
A good RFP is mostly won before it is sent. Define the requirement and the scoring first, keep the middle fair and recorded, and close the gap between award and contract at the end.
Run those steps in one system and the event stops leaking time and terms. It ends in a decision you can explain to finance, to legal and to the bidders who lost.