Sourcing

How to Run an RFP: A Step-by-Step Guide That Ends in a Good Decision

A good RFP is not complicated, but it is easy to run badly. Vague requirements, scattered vendor emails and a gut-feel final call turn a sourcing event into a slog and, worse, into a decision you cannot defend. Here is the process that avoids all three.

ATAavenir Team·July 2026·11 min read

Most RFPs do not fail because the team picked the wrong winner. They fail earlier and quieter: requirements that meant different things to different suppliers, a scoring rubric invented after the bids came in, and a final decision that no one could explain to finance six months later. The mechanics of an RFP are simple. Running one that ends in a decision you can defend takes a process.

Here is that process, six steps, in the order that actually works, with a realistic timeline and the traps that catch teams at each stage.

DefineWk 1 BuildWk 2 InviteWk 3 RespondWk 3-5 ScoreWk 6 AwardWk 7 ContractWk 7+ award flows to contract, no rekeying
A typical enterprise RFP runs about seven weeks. The last step, award to contract, is where teams lose the most time if sourcing and contracting live in different systems.
The short answer

Run an RFP in six steps: define the requirement and scoring criteria, build the RFP document, invite the right vendors, manage responses to clear milestones, evaluate and score against your pre-agreed criteria and pricing, then award the winner and move straight to contract. The biggest time sinks are vague requirements and the handoff to contracting, both of which disappear when you run the event in one platform.

Before you start: the shape of the whole thing

Seven weeks, six steps, one defensible decision.

A mid-complexity enterprise RFP typically runs about seven weeks from kickoff to signed contract. The single biggest predictor of whether it lands on time is not the vendors, it is how much work you do before the RFP goes out. Steps 1 and 2 feel slow and unglamorous. They are where the event is won or lost.

Step 1. Define the requirement (and how you will judge it)

Do this before you write a single question.

Get clear on what you actually need and how you will decide, and get your stakeholders to agree it in writing. Three things must be nailed down here:

  • Scope: what is in, what is out, and the must-haves versus the nice-to-haves.
  • Scoring criteria and weights: exactly how much price, capability, security, implementation and support each count, agreed now, before anyone sees a bid.
  • Stakeholders and their role: who scores, who advises, who signs off.

This step is the single biggest predictor of a smooth RFP. Skip it and every later stage inherits the ambiguity.

Step 2. Build the RFP document

Structure the questions so the answers are comparable.

Write the RFP as a set of clear questions mapped directly to your scoring criteria, plus a structured pricing request. If a question does not map to something you will score, cut it. Two practices separate good RFP documents from bad ones:

Author it collaboratively, not sequentially. Legal, procurement and the business should shape the document together, in one place. The old pattern, procurement drafts, emails legal, legal edits, emails back, wastes days and loses versions.

Ask for pricing in a fixed structure. Give vendors a pricing grid, not a blank box. When everyone submits the same structure, you can compare line by line instead of reverse-engineering four different pricing narratives.

Step 3. Invite the right vendors

A competitive field, without missing strong options.

Shortlist the suppliers worth inviting. Too few and you lose competitive tension; too many and you drown in evaluation. This is a place AI genuinely helps: it can recommend vendors based on category and past performance, surfacing credible options a team might not have thought of, so the field is competitive without being unwieldy.

Step 4. Manage responses to milestones

Keep every vendor on a level playing field.

Publish the RFP, set clear milestones (questions due, responses due), and manage all supplier questions in one place so every vendor sees the same clarifications. Milestone-based response requests keep vendors on track and keep the process auditable, which matters the moment a losing bidder asks why they lost.

Watch out

Answering one vendor's question privately. If a clarification changes the ask, every bidder needs it. Managing questions in a shared workflow instead of scattered emails is how you stay fair and defensible.

Step 5. Evaluate and score

Score against the rubric you agreed in step 1.

Now the pre-work pays off. Score each proposal against the weighted criteria you locked before the bids arrived, and compare pricing on your structured grid. Two habits make this stage trustworthy:

  • Score independently, then reconcile. Have evaluators score before they discuss, so the loudest voice does not anchor the room.
  • Benchmark the pricing. Compare bids not just to each other but to historical pricing, so you know whether the "best" bid is actually a good deal.
If you agreed the scoring after the bids arrived, you did not run an evaluation. You rationalized a preference.

Step 6. Award and move to contract

The step where teams lose a week for no reason.

Pick the winner based on the total weighted score, document the rationale (this is your audit trail), and move to contracting. Here is the hidden cost most teams accept without noticing: the award lives in the sourcing tool or a spreadsheet, and the contract gets created from scratch in a different system. Someone re-keys the vendor, the terms and the pricing, introducing delay and errors at the worst possible moment.

Running sourcing and contracting on one platform closes that gap. With Aavenir RFPflow, awarding an RFP hands the winning vendor straight into contracting on ServiceNow, no re-keying, no lost data, no dropped week.

See the whole flow, end to end

We will run an RFP from authoring to one-click award to contract on your own scenario.

Book a walkthrough →

The full RFP checklist

Everything above, on one screen.

  • Scope, must-haves and nice-to-haves agreed in writing
  • Scoring criteria and weights locked before any bid arrives
  • Stakeholders and their roles named
  • Questions mapped to scoring criteria; nothing you will not score
  • Pricing requested in a fixed, comparable grid
  • Document authored collaboratively, one version
  • Vendor shortlist competitive but manageable
  • Milestones set; supplier questions managed in one shared place
  • Evaluators score independently, then reconcile
  • Pricing benchmarked against history, not just other bids
  • Award rationale documented for audit
  • Winner flows straight to contract, no re-keying
The bottom line

A good RFP is mostly won before it is sent. Define the requirement and the scoring first, keep the process fair and auditable in the middle, and close the gap between award and contract at the end. Do that in one system and a seven-week event stops leaking time, and ends in a decision you can actually defend.

Frequently asked questions

What are the steps to run an RFP?

Run an RFP in six steps: (1) define the requirement and scoring criteria, (2) build the RFP document with questions mapped to those criteria, (3) invite the right vendors, (4) manage responses to clear milestones, (5) evaluate and score against your pre-agreed criteria and pricing, and (6) award the winner and move straight to contract. Most of the outcome is decided in steps 1 and 2, before the RFP goes out.

How long does an RFP take?

A mid-complexity enterprise RFP typically runs about seven weeks from kickoff to signed contract. The biggest time sinks are vague requirements at the start and the handoff to contracting at the end. Running the RFP in one platform with AI scoring and one-click award to contract can cut RFx-to-award cycle time by up to 40%.

What is the most important step in an RFP?

Defining the requirement and the scoring criteria before the RFP goes out. This step is the single biggest predictor of a smooth event, because every later stage inherits any ambiguity in the scope or the scoring. Agreeing the weights before any bid arrives also keeps the final decision objective and defensible.

How do you keep an RFP fair and defensible?

Agree scoring criteria and weights before bids arrive, manage all supplier questions in one shared place so every vendor sees the same clarifications, have evaluators score independently before discussing, benchmark pricing against history, and document the award rationale. Running the event in one auditable system makes all of this straightforward.

Why does the award-to-contract step slow teams down?

Because in many organizations the award lives in a sourcing tool or spreadsheet and the contract is created from scratch in a separate system, so someone re-keys the vendor, terms and pricing. Running sourcing and contracting on one platform, as Aavenir does on ServiceNow, hands the award straight into contracting with no re-keying and no lost time.

AT
Aavenir Team

Aavenir builds RFPflow, AI RFP and RFx management on ServiceNow. This walkthrough reflects how high-performing sourcing teams run competitive events end to end.

Run your next RFP in one system

See collaborative authoring, AI vendor scoring, pricing grids and one-click award to contract, on ServiceNow.

Book a demo