How to Write an RFP: 4 Phases From Define to Award
Writing an effective RFP is not about filling in a template. It is a 4-phase process that starts with defining what you actually need and ends with managing the vendor response cycle. Each phase has specific deliverables, stakeholders, and timelines.
Phase 1: Define Requirements (1 to 2 Weeks)
Before writing a single word of the RFP, you need clarity on what you are buying. This phase involves stakeholder interviews, requirements gathering, and market research. Skipping this phase is the single largest predictor of procurement failure. The Project Management Institute found that 37% of projects fail due to unclear requirements, and that failure starts at the RFP stage when organizations rush to market without sufficient definition.
Stakeholder Interviews (3 to 5 Sessions)
Interview each stakeholder group separately: executive sponsor (budget authority and strategic alignment), end users (functional requirements and pain points), IT team (technical requirements, integration constraints, and security standards), and procurement (contract terms, preferred vendors, and compliance requirements). Each interview should be 45 to 60 minutes with a structured question set. Document decisions, not just discussions. The output is a requirements matrix with each requirement traced to a stakeholder.
Requirements Prioritization
Use the MoSCoW method to categorize every requirement: Must-have (the solution is unusable without this), Should-have (important but the solution works without it), Could-have (desirable if budget allows), and Will-not-have (explicitly out of scope for this procurement). A typical enterprise project starts with 80 to 120 raw requirements from stakeholder interviews and prioritizes down to 30 to 50 for the RFP. The prioritization meeting takes 2 to 4 hours and requires the executive sponsor to make final calls on disputed items.
Market Research and Budget Estimation
Before setting your budget range, research market pricing. Methods include: requesting budgetary estimates from 2 to 3 vendors (clearly marked as non-binding and not part of the formal RFP process), reviewing industry benchmarks (Gartner, Forrester, or ISG publish annual pricing data for IT services), and consulting internal project records for similar past procurements. Your budget range should cover the 25th to 75th percentile of market pricing. Setting it below market will generate proposals padded with exclusions and assumptions.
Evaluation Committee Formation
Identify 3 to 5 evaluators before writing the RFP. Each evaluator should represent a different stakeholder group. Typical composition: technical lead, business owner, finance representative, and procurement lead. The committee agrees on evaluation criteria and weights before the RFP is written, not after proposals are received. This prevents criteria manipulation to favor a preferred vendor, which is both unethical and, in government procurement, illegal.
Phase 2: Draft the RFP (1 to 2 Weeks)
With requirements defined and prioritized, draft the 10-section RFP document. Assign one primary author for consistency of voice and style. The author should be the procurement lead or project manager, not a committee. Committee-written RFPs read like they were written by a committee: inconsistent tone, redundant sections, and contradictory requirements.
Writing the Project Overview
Start with the problem, not the solution. Describe the current state (what is broken or insufficient), the desired future state (what success looks like), and the business impact (revenue at risk, cost savings target, or compliance deadline). Use specific numbers: "Our current system processes 2,000 orders per day with a 4.7% error rate. We need to reduce errors to under 0.5% while scaling to 8,000 orders per day within 18 months." This level of specificity helps vendors propose the right solution rather than a generic one.
Structuring Requirements
Number each requirement with a unique ID (REQ-001 through REQ-n). Group them into categories: functional requirements (what the solution must do), technical requirements (infrastructure, integration, security), performance requirements (speed, capacity, availability), and compliance requirements (regulatory, audit, data residency). For each requirement, specify the acceptance criteria: how will you verify the vendor has met it? Requirements without acceptance criteria are unenforceable after contract signature.
Defining the Evaluation Section
Write the evaluation criteria and scoring rubric into the RFP document. For each criterion, describe what a score of 1 through 5 looks like. This is not extra work; it forces you to define what "good" means before you see any proposals. Without predefined scoring definitions, evaluators apply different standards and scores are not comparable. The World Commerce and Contracting Association recommends a minimum of 5 scoring levels with written descriptions for each level per criterion.
Setting the Budget Range
Express the budget as a range with a spread of plus or minus 25% to 30% around your target. For a $200,000 target, state $150,000 to $260,000. Include what the budget covers (all phases, travel, infrastructure, training) and what it does not cover (client-side resources, data cleanup, third-party licenses). According to the Hackett Group, organizations that include clear budget boundaries in their RFP receive proposals with 40% fewer assumptions and 25% fewer post-award change orders.
Phase 3: Review with Stakeholders (3 to 5 Days)
Never issue an RFP that has only been reviewed by the author. At minimum, get sign-off from the executive sponsor, legal team, and one subject matter expert from outside your project team who can spot assumptions and jargon. The review phase catches 60% to 80% of issues that would otherwise generate vendor questions or non-compliant proposals.
Legal Review (1 to 2 Days)
Legal reviews the terms and conditions section, intellectual property clauses, confidentiality requirements, liability limitations, and indemnification language. They also verify compliance with applicable procurement regulations (particularly important for public sector organizations subject to state procurement codes or federal FAR requirements). Flag any non-standard terms that might deter vendors, such as unlimited liability clauses or unreasonable IP ownership demands.
Technical Review (1 Day)
A technical subject matter expert reviews all requirements for feasibility, completeness, and internal consistency. Common issues caught during technical review: requirements that contradict each other, performance targets that are physically impossible with current technology, integration requirements that reference deprecated APIs or end-of-life systems, and security standards that do not align with the organization's actual security posture. This review typically takes 2 to 4 hours for a 10-page RFP.
Executive Sponsor Sign-Off
The executive sponsor reviews the budget range, timeline, and evaluation criteria to confirm alignment with organizational priorities. This is not a detailed line-by-line review. It is a strategic check: Does this RFP reflect what the organization actually needs? Is the budget approved? Are the evaluation weights appropriate? Getting this sign-off before issuance prevents the situation where the winning vendor is selected and then the sponsor rejects the recommendation because the criteria did not reflect their priorities.
Phase 4: Issue and Manage (3 to 6 Weeks)
Issuing the RFP is just the start of the active management phase. This phase requires daily attention during the Q&A period and structured evaluation after the submission deadline. Poor process management during this phase is the second most common cause of procurement protest, after biased evaluation.
Vendor Notification and Distribution
Send the RFP to all selected vendors simultaneously. Include a confirmation of receipt mechanism (email acknowledgment or portal timestamp). Provide a single point of contact for all communications. Any vendor who contacts other members of your organization about the RFP during the evaluation period should be warned, and repeated violations can be grounds for disqualification. This rule ensures all vendors have equal access to information.
Q&A Period Management (5 to 10 Days)
Monitor incoming questions daily. If a question reveals a material gap or error in the RFP, issue a formal addendum rather than just answering the question. Addenda become part of the RFP and are distributed to all vendors. When compiling Q&A responses, anonymize the questioner to prevent vendors from identifying competitors. Publish all Q&A responses at least 5 business days before the submission deadline to give vendors time to adjust their proposals.
Proposal Receipt and Evaluation
Log receipt time for every proposal. Late proposals are rejected without review. Distribute proposals to evaluators with a scoring template and a deadline for individual scores (typically 5 to 7 business days). Evaluators score independently before any group discussion. The evaluation committee then meets to calibrate scores, discuss outliers, and reach consensus. Document all scoring rationale in case of protest. The final output is a ranked list with scores and a recommendation to award, negotiate, or re-solicit.
Shortlisting and Final Selection
Invite the top 2 to 3 vendors for oral presentations, product demos, or best-and-final-offer (BAFO) rounds. Structure these sessions identically for all vendors: same time allocation (60 to 90 minutes), same question set, same evaluation panel. Score these sessions separately (typically weighted 70% written proposal, 30% presentation). Select the highest total scorer and begin contract negotiation. Notify unsuccessful vendors within 5 business days of the award decision with a brief, professional debrief offer.