Key Takeaways
- An RFP (request for proposal) is a structured document that invites suppliers to propose how they'd meet a defined need — use it when the solution, not just the price, is up for evaluation.
- The hard work happens before you write: define the requirement, assemble the team, and decide your evaluation criteria and weightings first.
- A strong RFP states the problem clearly, asks specific and comparable questions, and tells suppliers exactly how they'll be scored and on what timeline.
- Define scoring weights before you issue the RFP, not after responses arrive — that's how you keep the evaluation objective and defensible.
What an RFP Is and When to Use One
A request for proposal (RFP) is a formal document that describes a need and invites qualified suppliers to submit detailed proposals explaining how they would meet it, on what terms, and at what cost. Unlike a price-only request, an RFP evaluates the whole solution — approach, capability, fit, risk, and price together — which makes it the right tool when how a supplier solves your problem matters as much as the number at the bottom.
It helps to place the RFP among its siblings. An RFI (request for information) gathers background to shortlist suppliers when the market is unfamiliar. An RFQ (request for quotation) asks for pricing on a tightly specified item where the only real variable is cost. An RFP sits in between and above: you know roughly what you need but want suppliers to propose the best solution. RFPs are a core instrument of strategic sourcing, and choosing the right instrument is itself part of sourcing strategy — a theme we cover in our comparison of strategic sourcing versus procurement. Picking an RFP when an RFQ would do wastes everyone’s time; picking an RFQ when you actually needed proposals leaves you comparing prices for solutions that aren’t equivalent.
Before You Write: The Prep That Determines Success
Most weak RFPs fail before a word is written, because the requirement wasn't clear or the evaluation wasn't agreed. Do three things first. Define the requirement precisely: the business problem, scope, must-haves versus nice-to-haves, constraints, and budget envelope. Vague requirements produce vague, incomparable proposals. A useful test is whether you could hand the requirement to two different colleagues and have them describe the same need back to you; if not, it needs sharpening before it goes anywhere near a supplier. Time spent here is repaid many times over in the quality and comparability of the responses you get back.
Assemble the evaluation team and stakeholders. Identify who will score responses and who must sign off, and involve them in defining requirements so you don't discover a missing criterion after responses arrive. Agree the evaluation criteria and weightings up front. Decide how much price, capability, approach, risk, and support each count — before suppliers respond. This single discipline is what keeps the process objective and defensible if a losing bidder challenges the outcome.
How to Write an RFP, Step by Step
- Write the introduction and background. Briefly describe your organisation, the problem you're solving, and the goal of the RFP. Give suppliers enough context to propose intelligently.
- State the scope and requirements. Detail exactly what you need, separating mandatory requirements from desirable ones. Be specific enough to compare responses, but leave room for suppliers to propose their approach.
- Pose structured questions. Ask specific, comparable questions about capability, methodology, implementation, support, security, and pricing. Number them so responses map cleanly to your scoring sheet.
- Specify the response format. Tell suppliers how to structure their proposal, page or word limits, and the format for pricing, so responses are easy to compare side by side.
- Explain the evaluation criteria. Publish the criteria and their weightings. Suppliers who know what you value write better, more relevant proposals — and transparency strengthens the process.
- Lay out the timeline and process. Include the issue date, a questions/clarification window, the submission deadline, evaluation period, and expected decision date.
- State terms and submission logistics. Cover confidentiality, contractual expectations, the submission channel, and a single point of contact for questions.
- Review and pressure-test. Have a colleague who knows nothing about the project read it. If they can't tell what you need and how they'd win, neither can a supplier.
RFP Structure: A Copy-and-Paste Outline
Use this outline as the skeleton of your document. It mirrors the order suppliers expect and maps directly to a scoring sheet. For a more complete starting point, our dedicated RFP template expands each section with prompts.
RFP Outline
1. Introduction & organisation background 2. Project overview & objectives 3. Scope of work 3.1 Mandatory requirements 3.2 Desirable requirements 3.3 Out of scope 4. Supplier questions 4.1 Company & references 4.2 Solution & approach 4.3 Implementation & timeline 4.4 Support & service levels 4.5 Security & compliance 5. Pricing (fixed format / pricing schedule) 6. Evaluation criteria & weightings 7. Timeline & key dates 8. Submission instructions & contact 9. Terms, confidentiality & assumptions
How to use it: fill each section, delete what doesn't apply, and keep the supplier-question numbering aligned with your scoring sheet so evaluation is mechanical rather than subjective.
Setting Evaluation Criteria and Weightings
The evaluation framework is the heart of a defensible RFP. Define the criteria, assign weights that reflect what actually matters for this purchase, and use a consistent scoring scale (for example 1–5) across all evaluators. The illustrative weighting below shows the shape of a typical balanced framework — adjust the percentages to your priorities, since a commodity buy will weight price far more heavily than a strategic platform decision.
| Criterion | Illustrative weight | What you're assessing |
|---|---|---|
| Solution fit & capability | 30% | How well the proposal meets your requirements |
| Approach & methodology | 20% | How they'll deliver and de-risk the work |
| Price & total cost | 25% | Total cost of ownership, not just headline price |
| Experience & references | 15% | Track record on comparable work |
| Support & service levels | 10% | Ongoing support, SLAs, and account model |
Score independently first, then calibrate as a group to surface and resolve big differences. Keeping a clear record of scores and rationale protects you if the decision is questioned, and it feeds directly into the contract negotiation that follows — you'll know exactly where the winning supplier was strong and where you need protective terms.
Common RFP Mistakes to Avoid
Vague requirements. If you can't articulate what you need, suppliers will guess, and you'll get proposals you can't compare. Specificity is kindness to both sides.
Hidden evaluation criteria. Withholding how you'll score doesn't protect you — it just produces worse proposals and a weaker audit trail. Publish the weightings.
Too many open-ended questions. Essays are hard to score consistently. Favour specific, structured questions that map to your criteria.
Unrealistic timelines. Give suppliers enough time to respond well; rushed responses help no one. Build in a proper clarification window.
Copy-pasting an old RFP. Recycling without tailoring leaves irrelevant requirements and confuses suppliers. Start from a clean outline like the one above and adapt deliberately.
Building a Realistic RFP Timeline
A timeline that's too tight produces rushed, low-quality responses and erodes goodwill with the suppliers you most want to win. Build in enough time at each stage, and publish the dates in the RFP so suppliers can plan. The schedule below is a reasonable shape for a mid-complexity RFP; scale it up for major platform decisions and down for simpler buys.
| Stage | Typical duration | What happens |
|---|---|---|
| Preparation | 1–3 weeks | Define requirements, assemble team, agree criteria |
| RFP issued to deadline | 2–4 weeks | Suppliers prepare and submit responses |
| Clarification window | Within the response period | Suppliers ask questions; you publish answers to all |
| Evaluation | 1–3 weeks | Independent scoring, then group calibration |
| Shortlist & demos | 1–2 weeks | Presentations or proofs of concept if needed |
| Decision & award | 1 week | Final selection, notification, and debriefs |
Two timeline disciplines matter most. First, run a genuine clarification window and share every answer with all bidders — it keeps the process fair and produces better-targeted proposals. Second, don't compress evaluation; the temptation to rush scoring after a long preparation phase is exactly where objective frameworks get abandoned.
After Submission: Evaluation, Award, and Handover
Writing the RFP is half the job; running a clean evaluation is the other half. Once responses arrive, screen first for mandatory requirements — any proposal that misses a stated must-have is set aside before scoring, which saves the panel from debating non-compliant bids. Then score the compliant responses against your published criteria, independently, before any group discussion.
Calibration is where value is protected or lost. Bring evaluators together, compare scores, and probe the largest disagreements: they usually reveal either a misread requirement or a genuinely contested judgement worth resolving. Document the rationale for the final ranking. A shortlist stage with demos or a proof of concept is worth the time for high-stakes decisions, because a polished written proposal doesn't always match delivery reality.
Finally, treat award as a handover, not an ending. The insights from evaluation — where the winner was strong, where they were weak, what they assumed — are the agenda for your contract negotiation and for setting service levels. Give losing bidders a fair debrief; the market is small, and the supplier you decline this year may be the one you need next. Channelling the resulting spend correctly also matters: a well-run RFP only delivers value if subsequent purchasing flows to the chosen supplier, which connects the event back to the disciplined procure-to-pay process that executes it.
Writing Questions That Get Comparable Answers
The questions section is where most RFPs quietly fail. The goal is responses you can lay side by side and score consistently, which means favouring specific, bounded questions over open invitations to write essays. “Describe your approach to implementation” produces five incomparable narratives; “Outline your implementation plan including phases, your team's roles, our team's required time commitment, and key milestones with target dates” produces answers you can actually evaluate.
A few principles keep the section sharp. Ask one thing per question, so a weak answer to part of a compound question doesn't drag down an otherwise strong response. Tie each question to a requirement or evaluation criterion — if a question maps to nothing you're scoring, cut it. Ask for evidence, not assertions: request references, examples, or metrics rather than adjectives. And constrain pricing into a fixed schedule so every supplier prices the same scope; free-form pricing is impossible to compare and invites suppliers to quietly exclude costs.
Security, data handling, and compliance deserve their own structured block for any technology or services RFP, because gaps there surface late and expensively. The discipline of mapping every question to a criterion is also what makes AI assistance reliable later — a well-structured questionnaire is far easier for a tool to summarise and compare than a loose set of prompts.
Where AI Helps Write and Run RFPs
AI has become genuinely useful across the RFP lifecycle. On the buy side, it can draft requirement sections and structured questions from a brief, suggest evaluation criteria, summarise long supplier responses, and flag inconsistencies or gaps across proposals — compressing the most tedious parts of running an event. Tools in the RFP and sourcing agents category and the broader strategic sourcing AI space increasingly automate response analysis, and platforms such as JAGGAER embed sourcing workflows end to end.
From our analysis, AI is strongest at the structured, repetitive work — drafting, summarising, comparing — and weakest at judgement calls about strategic fit, which still need experienced humans. Treat it as an accelerator for the mechanics, not a replacement for the evaluation. Our independent negotiation and sourcing AI market analysis separates the capabilities that are real today from the marketing, and if you want to size the time savings against your own event volume, the ROI calculator is a useful starting point.
Run sourcing events faster
Compare the AI tools that draft RFPs, analyse responses, and automate scoring — reviewed independently against real sourcing workflows.