Vendor RFP evaluation workflow
Request for proposal evaluation from criteria scoring to final selection.
Every company buys from vendors — cloud infrastructure, software licenses, consulting, managed services. An RFP (Request for Proposal) evaluation workflow is how large organizations do this systematically. You publish an RFP, vendors submit proposals, you score them against weighted criteria, invite the top few to demo, negotiate terms, and have legal review the contract. This diagram shows the complete flow with decision points and the loops where you cycle back — rejecting a candidate, re-opening negotiations, or gathering more vendors if your initial screening pool is too small.
The key insight is that each gate eliminates candidates cost-effectively. Initial screening happens on paper (does their price fit your budget?). Scoring lets you compare apples to apples. Demos let you validate that they can actually deliver. Negotiation happens only with finalist vendors, not the entire pool. This keeps costs down while ensuring you pick the best-qualified vendor.
When to use this template
- Procurement documentation — show new team members the standard vendor evaluation process so they understand when to move a vendor forward versus when to eliminate them.
- RFP planning — before publishing an RFP, review this workflow with stakeholders to agree on screening criteria, scoring weights, and decision gates. Misalignment here causes delays and disputed vendor selections later.
- Procurement audits — when you need to show auditors or finance that vendor selection was fair and well-documented, this diagram plus populated scoring spreadsheets prove the process was systematic, not ad-hoc.
How to adapt it
Customize the gates and scoring to your business:
- Add reference checks after demos — call existing customers before negotiating to validate the vendor's claims.
- Expand criteria scoring — add nodes for each weighted dimension (price, support, roadmap, implementation) with separate sub-gates for each one.
- Insert proof-of-concept — after negotiation, require a limited pilot before full contract to de-risk the relationship.
Visual edits regenerate clean Mermaid code, so you can document your actual process without learning syntax — just drag and rename nodes to match your procurement policy.
Mermaid code
Copy it anywhere Mermaid is supported — GitHub, Notion, or your docs.
flowchart TD
A[Publish RFP] --> B[Vendors submit proposals]
B --> C[Initial screening<br/>cost, tech fit?]
C -->|Fails| D[Reject]
D --> E[Send rejection notice]
C -->|Passes| F[Score criteria<br/>price, support, roadmap]
F --> G[Calculate weighted scores]
G --> H{Top 3 candidates?}
H -->|No| I[Expand search<br/>add RFP round]
I --> B
H -->|Yes| J[Request demos]
J --> K{Demo acceptable?}
K -->|No| L[Eliminate candidate]
L --> H
K -->|Yes| M[Negotiate terms]
M --> N{Agreement reached?}
N -->|No| O[Return to demo feedback]
O --> M
N -->|Yes| P[Legal review]
P --> Q{Contract approved?}
Q -->|No| R[Provide redlines]
R --> M
Q -->|Yes| S[Award contract]
S --> T[Vendor onboarding]
Frequently asked questions
- What is an RFP evaluation workflow?
- An RFP (Request for Proposal) evaluation workflow maps the entire process from publishing the request to signing the contract. It includes initial screening to eliminate unqualified vendors, scoring on weighted criteria (price, support, roadmap, implementation speed), demo calls, negotiation rounds, and legal review. The loops show where the process might cycle back if a top candidate fails a step.
- Why does the workflow loop back to publishing RFP if fewer than 3 candidates pass screening?
- If your initial vendor pool is too small or all candidates fail initial screening on cost or technical fit, publishing another RFP round with adjusted criteria or to a different market segment is faster than proceeding with unqualified vendors. This loop keeps the final three candidates competitive and well-qualified.
- What criteria should I use for scoring?
- Common categories are: Implementation cost (price per unit or total), Support SLA (response time, hours, escalation), Roadmap alignment (does the vendor build what you need?), Time to value (how fast can they go live?), and Risk (financial stability, customer references). Assign weights based on what matters most to your business — price might be 30%, support 25%, roadmap 45%.
- How do I adapt this for internal tool evaluation or SaaS procurement?
- The core loop is the same — screening, scoring, demos, negotiation, legal. For SaaS, add a free trial phase after scoring but before negotiation. For internal tools, the demo phase becomes a proof-of-concept build. Visual edits regenerate clean Mermaid code, so you can customize nodes and loops to match your procurement process.