RFP in Project Management: Request for Proposal Guide

I still recall the first instance I had to engage an external vendor for a sophisticated software implementation. I had scores of prospective partners to contend with, each one boasting the best match for my requirements. How could I undertake a fair assessment of all the options to ensure I settled on the most suitable one? That was my first experience with the utility of a good Request for Proposal.

A Request for Proposal (RFP) is a formal business document that an organization uses to obtain descriptive vendor proposals. It captures the organization's project requirements, the expectations, and the criteria for evaluation. Thus, RFPs enable service providers to prepare competitive proposals for the organization's project. Whether you are preparing for your PMP certification training or are tasked with your first procurement initiative, learning to prepare and handle RFPs will greatly enhance your chances of success in vendor selection.

An RFP is a critical document for vendor selection when your project management plan involves outsourcing. You can think of it as an in-depth invitation to a vendor to describe how they plan to execute the project, what they are going to give you, and how much it is going to cost. The RFP outlines the expected deliverables, timeline, budget, and how you plan to grade the vendor's RFP.

An RFP provides an even playing field for all vendors, as the RFP process is much more inclusive compared to a process where a vendor is awarded the project based on relationship ties. You are able to receive detailed RFP responses and objectively grade them, making it easier to select the vendor that is able to suit your requirements the best. Overall, the RFP approach, as compared to an informal approach, mitigates procurement risks, and as a result, the project has a much higher chance of success.

Using the RFP approach is not a necessity for every project. I tend to use RFP documents when the situation requires a detailed vendor assessment, and there are complex requirements that are best suited to RFP documents. In most cases, governmental institutions and big corporations are bound by regulation to use RFP documents to promote fairness and transparency.

You may issue an RFP if your project has a budgetary limit that has been surpassed, if you are creating a long-term partnership with a vendor, or if you do not have internal staff available to do the work. However, do not do the RFP for straightforward projects that are quickly moving, when you have a good vendor relationship, or when the project is so small that it is not worth the effort.

These three procurement documents are commonly confused by project managers; however, each has a very distinct role in the project selection.

An RFI, or a Request for Information, is used for market evaluation. It is an exploratory document used to determine market options before project specifications are known in detail. An RFQ, or a Request for Quotation, is used when a project is defined and the only remaining detail is pricing. An RFP, or Request for Proposal, sits in the middle of the two described documents and asks the vendors to provide a full proposal, including methodology, timeline, and team, in addition to pricing.

The time it takes to create an RFP can take 8 to 12 weeks to complete. I begin by laying the foundation to avoid unnecessary revisions. This includes outlining what the project goals are, determining who the stakeholders will be, and setting the criteria I will use to evaluate the RFP.

Focusing on structure and organization is my writing priority. Vague requirements make it worse for everyone involved, as it makes writing the RFP and awarding the project nearly impossible. I prioritize detailed objectives, comprehensive scopes of work, realistic time lines, solid budgets, project guidance, and clear instructions on what I expect for submissions.

I typically reach out to 5 to 7 companies to get the RFP, and I set aside 3 to 4 weeks to allow for the preparation of the proposals. Throughout these weeks, I will hold several Q and A sessions where I will answer any clarifying questions about the RFP. Because I do not answer questions in private, everyone has access to the same information.

One of the most difficult but essential parts of the RFP evaluation process is maintaining an objective perspective. One of the best ways is to create a scoring matrix where each item is weighted based on how critical it is to achieving the goals of the project. For example, out of a possible 100 points, I would assign Technical Capability to 35 points, Cost to 25 points, Relevant Experience to 20 points, Proposed Timeline to 10 points, and Team Qualifications to 10 points. This decision matrix approach also helps to eliminate bias and create defensible decisions.

Any RFP document I have crafted includes these components. The executive summary and company overview give prospective vendors an outline of who you are and why you are requesting their services. The overview of your project gives a succinct outline of what you are trying to achieve, inclusive of specific business goals, and how you intend to measure success.

The scope of work section deserves your utmost attention. Here, you describe in detail what you expect vendors to deliver, the technical criteria they are to fulfill, and the quality control parameters you have. If certain systems, tools, or methodologies are non-negotiables to your project, say so.

When outlining your project timeline, you should indicate key milestones, in addition to your final deadline. This gives vendors an idea of how you expect the project to unfold and its interdependencies. I always include the deadline for submission of the proposal, the timeline for evaluation of proposals, the expected date of commencement of work on the project, and the expected completion date.

The desired budget and the pricing section can vary in terms of how transparent they are. Some organizations are upfront with what their budget runs, and this helps vendors self-screen, as well as submit proposals that are realistic with respect to the budget. On the contrary, some organizations prefer to see what the market will bear. I usually work with a budget range to avoid wasting everyone's time with unrealistic expectations.

The evaluation criteria section specifies which requirements a vendor must meet in order to receive a certain score for their proposals. With this knowledge, a vendor can direct their efforts to meet the primary expectations of a scoring rubric. Such clarity boosts the quality of proposals substantially.

The primary motivation for RFPs is the chance to foster direct competition among vendors. In my experience, the RFP process has yielded highly valuable, innovative solutions. For me, the value in the suggestions came without me openly soliciting the ideas. As vendors compete for the opportunity to provide value, they utilize novel means to provide resolution to the stated problems.

In a regulated industry setting, RFPs bring the necessary transparency. The recorded history of decisions shows the stakeholders that the case is merit-based and that the decision-making process is transparent. The documentation of a decision helps to lower the number of project risks for commitments to untested vendors.

Most valuable to project managers seeking to complete the PMP certification, RFPs enable and encourage forethought. Proper planning prevents the usual problems of scope creep and decreasing clarity that may lead to the failure of the project.

Drafting a detailed RFP takes a lot of time and resources. For complex projects, I spend approximately two to four weeks drafting the initial document. The review component takes about the same amount of time, three to four weeks. To try to relieve these time frames, I keep RPF templates. I find customizing these templates for the various jobs to use them as time-savers rather than starting from scratch each time.

Evaluators can easily feel overwhelmed with large volumes of proposals. I try to implement a two-stage evaluation process when I predict receiving more than ten proposals. The first stage reviews the proposals only against the minimum requirements, and all proposals that do not meet the minimum standards are eliminated. The result is a narrowed selection of only three to five proposals, which are subjected to full reviews.

Unbalanced submissions can be a result of the early deadlines when RPFs are issued. If I need to modify requirements, I submit official amendments to all bidders and delay the deadlines to ensure that all bidders can amend their submissions.

I suggest that you aim for deadlines that are realistic. Avoid rushing your bidders, as this will lead to a proposal that is low quality. On moderate complexity projects, I recommend 3 weeks as the minimum time-frame for bidders.

During this entire process, maintaining clarity and a consistent communication strategy is imperative. There should be only one liaison for vendor queries, and all answers should be sent to each vendor to ensure fairness. Every communication should be recorded to preserve a history of events.

After choosing a preferred vendor, be prepared to negotiate. The proposal is merely a starting point, and most final agreements are a result of lengthy negotiations. You should determine which proposal elements are firm and which elements allow for some negotiation before beginning negotiations.