The Dos and Don'ts of Request for Proposals (RFPs)

Introduction  

In fleet management, a request for proposal (RFP) enables organizations to invite bids from potential vendors, contractors, or service providers. Whether you're on the buying side seeking the best vendor or a vendor aiming to secure a contract, knowing the best practices and avoiding common pitfalls helps you land the right partnerships.  

In this detailed guide, you’ll find the "dos and don'ts" of the RFP process and four case studies that underscore the importance of crafting precise specifications. And we’ve included a helpful RFP template you can use as a baseline for your future RFPs.  

 GET THE FREE RFP TEMPLATE  

What Is an RFP?  

An RFP stands for Request for Proposal. In fleet management, it’s like a job listing for companies that sell fleet services or equipment. It lays out what a business needs, such as vehicles, upkeep, or tracking systems. Service providers can then offer bids showing how they can fulfill these needs and how much it will cost. This lets the business check out different options and pick the best one for their fleet. 

What Is an RFP Proposal?  

An RFP proposal is a response from a company to a request for proposal issued by another organization. When an organization needs specific services or products, it sends out an RFP to invite various vendors to submit proposals. The RFP proposal from each vendor details how they plan to meet the organization's needs, the costs involved, and other relevant information. This proposal helps the organization compare offerings from different vendors to choose the best fit for their project or requirement. 

What Happens if You Don’t Have a Good RFP?  

Study 1: Mismatched Solutions: How a Northwest Port Authority’s Choice of an Enterprise Asset Management System Over a Fleet Management Information System Led to Operational Challenges 

A major port authority in the Northwest United States opted for a well-known asset-based enterprise asset management (EAM) system over a specialized fleet management information system (FMIS) designed to manage a fleet's assets and operations.  

However, shortly after buying the EAM system, it became clear that it lacked a critical "Fleet Module," essential for fleet asset management and a key feature distinguishing an EAM from an FMIS.  

Additionally, post-implementation, the EAM vendor-imposed restrictions to prevent different fleet departments, such as maritime, fire, and aviation, from sharing asset information, transactions, costs, and best practices. The barrier led to significant challenges in data integration, resulting in over 300 duplications in the EAM data and complicating the project further.  

Ironically, the fire department already used a highly effective FMIS that could have been expanded to include the other departments. This oversight highlighted the port authority's lack of due diligence, including insufficient information gathering, stakeholder engagement, and detailed planning for the project scope and request for proposal (RFP) process, which could have otherwise helped avoid these issues.  

Study 2: Choosing Complexity Over Clarity: Lessons from a West Coast Sanitation District's Adoption of an Enterprise Asset Management System.  

A West Coast-based sanitation district enlisted a fleet management consultancy to evaluate its fleet system after choosing a robust enterprise asset management (EAM) system over a fleet management information system (FMIS) for managing fleet and warehouse assets.  

Post-implementation, the EAM system was industrially strong and offered some fleet functionalities. However, users found the system capable but overly complex compared to a more accessible, commercial-off-the-shelf (COTS) FMIS, particularly lacking straightforward fleet functions like fleet replacement modeling and synchronizing preventive maintenance schedules.  

The consultation revealed that a dedicated FMIS offers a broader range of relevant functionalities and supports best management practices more effectively than EAM or enterprise resource planning (ERP) systems. These purpose-built FMIS solutions are designed to handle complex fleet operations comprehensively and are continually updated to enhance user-friendliness and integrate innovative technologies like telematics and electronic manuals.  

In contrast, due to their complexity, EAM and ERP systems often require significant customization and supplemental tools like spreadsheets to meet basic operational needs.  

Moreover, FMIS developers actively update their products to follow new regulations from state and government agencies, a process that EAM and ERP providers typically leave to the user.  

Ultimately, the success of any fleet management system hinges not just on its features but on proper implementation, consistent use across the organization, and the ability to provide correct management information and uphold daily best practices.  

Study 3: Global Ambition, Local Frustration: The Challenges of a Beverage Company's ERP System for Fleet Management 

A major beverage company embarked on a project to consolidate its diverse fleet of over 50,000 fleet assets into a single management system to enhance control over its delivery and manufacturing assets.  

Initially, the company assessed the fleet management systems used across various locations. They found that one large facility effectively used an FMIS alongside existing ERP and enterprise asset management (EAM) systems.  

The fleet director suggested expanding the FMIS across more than two hundred locations at an estimated cost of two million dollars, given its success in managing fleet assets.  

However, after evaluating the options, management implemented a comprehensive ERP system to manage fleet asset transactions nationally and globally. In this case, this choice proved problematic as the ERP system required over 40 clicks to create a single work order, a task that a purpose-built FMIS could carry out in just a few clicks.  

The ERP system served primarily as a cost and asset tracker, lacking the necessary customization to function effectively as an FMIS. This experience mirrors that of many other companies, which have found that choosing an unsuitable asset-tracking solution for fleet management can be cumbersome and costly.  

Study 4: Costly Compromises: A State's Journey from an EAM System to an External Solution for Fleet Management 

A large state in the southeastern United States initially bought an enterprise asset management (EAM) system to manage its 20,000 fleet assets but soon found it inadequate.  

In response, they appointed a new fleet director to analyze the system and recommend improvements, given the absence of a purpose-built fleet management information system (FMIS).  

After several discussions with the EAM provider's executive team to address these shortcomings, it was revealed that the provider offered a transportation package designed to enhance fleet management as the state consolidated its assets into a single solution. However, the cost quoted by the provider for this added module was prohibitively high.  

Consequently, the fleet director decided to compile a detailed set of business requirements for a purpose-built FMIS. Once the specifications were ready, they were converted into an official request for proposal (RFP) and issued for bids. The bids received, however, were significantly higher than expected, leading to the project's cancellation.  

Ultimately, the state partnered with one of its external statewide maintenance providers to adopt their system for tracking assets and managing transactions. While this solution was not ideal, it provided the necessary data for making informed asset decisions. This case echoes many others, underscoring that such problems could often be avoided with proper due diligence, including a professionally prepared and executed RFP.  

These examples underscore the importance of thoroughly assessing the suitability of ERP systems for specific operational needs and ensuring that implementation plans are realistic and well-supported by all stakeholders involved. Moreover, these examples illustrate how choosing the wrong system to manage a fleet of assets can lead to numerous problems and high costs, underscoring the importance of carefully addressing critical issues through a well-prepared RFP.  

Understanding the Dos and Don’ts of a Well-Written RFP 

 DOWNLOAD THE RFP INFOGRAPHIC 

The Dos  

1. Define the Project Plan and Scope: Start by outlining the project's objectives, requirements, and scope thoroughly. Clearly state your goals, expectations, needs, and evaluation criteria. This clarity ensures that all parties—your organization and potential vendors—are aligned.  
   
   
2. Collaborate with Stakeholders: Engage key stakeholders from your organization and potential vendors early in the process. Their insights and earlier experiences can shed light on the project's nuances, possible challenges, and desired outcomes. Conduct market research to better understand potential vendors and craft an RFP that attracts suitable candidates and sets realistic expectations.  
   
   
3. Be Clear and Concise: Draft an RFP that is straightforward and easy for bidders to understand. Maintain transparency about your decision-making process, timelines, and criteria to enable vendors to tailor their proposals accurately. Avoid jargon and technical terms to ensure clarity and relevance in the proposals received.  
   
   
4. Encourage Questions: Allow and encourage vendors to ask questions and provide detailed responses. This interaction clarifies details and prevents misunderstandings, leading to more correct and fitting proposals. Provide an appropriate amount of time to receive questions after the RFP is issued, time for the organization to review and respond to questions, and time for vendors to acknowledge the Q&A and make relevant changes to their submittal.  
   
   
5. Include Evaluation Criteria: Clearly define how proposals will be evaluated. Consider factors such as cost, technical capability, vendor experience, length of time in business, and references. Use a fair and consistent evaluation process and develop a scoring system to objectively assess each proposal. This approach ensures proposals meet your organization's needs and expectations.  
   
   
6. Request Key References: Always ask potential vendors for references about their past projects. Follow up with these references to verify the vendors' reliability, performance, and capability to deliver as promised.  
   
   
7. Proofread the Proposal: Before completing, thoroughly review the RFP document for errors and ensure it is well organized. A well-presented proposal reflects professionalism and sets the tone for the responses you expect from vendors.  
   
   
8. Implementation Assistance: Include implementation support as a fundamental aspect of the RFP, or at least as a possibility. This support can range from setting up the system to training staff ensuring that the transition to the new system is smooth and effective right from the start.  
   
   
9. Invite Vendors for Demonstrations: Allow vendors to demonstrate their products. Consider developing a demo script to ensure consistency across all vendor presentations so you can evaluate their systems. 
   
   
10. Communicate with Who ISN’T Selected: It’s standard to send an RFP letter of rejection to vendors who submitted proposals but were not selected for the project. This letter informs them that their proposal has not been chosen and typically includes a brief explanation or thanks for their time and effort in responding to the RFP. It's important to maintain professionalism and courtesy in these letters to keep a good relationship with the vendors for potential future opportunities. 

The Don’ts  

1. Don’t Rush the RFP: We get it, when you’re ready for a solution, you want to get it as soon as possible. However, hastily created RFPs can result in vague requirements, incomplete information, and confusion for bidders. Take time to customize templates directly from preferred vendors or peer organizations because they often do not meet specific needs. Allocate sufficient time for drafting a comprehensive document and for vendors to respond effectively.  
   
   
2. Don’t Forget Your Due Diligence: Before drafting the RFP, thoroughly research potential vendors. Evaluate their financial stability, business longevity, online reviews, security measures, and compliance history. A diligent vetting process reduces risks and lays the groundwork for a successful partnership once the RFP is awarded.  
   
   
3. Don’t Complicate the Process: To avoid deterring potential vendors with overly complex requirements, keep the RFP simple. Keep communication open with vendors, providing regular updates and constructive feedback on their submissions to foster trust and professionalism. Include only essential information in the RFP to prevent information overload. However, allow vendors to show their capabilities by requesting case studies or examples that relate directly to your needs.  
   
   
4. Don’t Show Favoritism: Strive for fairness in evaluating proposals without favoring vendors or solutions. Clearly specify all terms, expectations, and deliverables, avoiding vague language that could lead to misunderstandings and unsuitable proposals. Assess each submission objectively based on predefined criteria.  
   
   
5. Don’t Get Distracted: Keep the RFP focused on the necessary requirements without straying into irrelevant details. Ensure that the presentation of the RFP response is professional because a presentation can undermine the perceived quality of the proposal. Adhere strictly to established deadlines and do not accept late submissions, regardless of the quality of the RFP.  

RFP Proposal Template Overview 

 DOWNLOAD OUR FREE RFP TEMPLATE 

1. Introduction and Background
   1. Provide a brief introduction of your company and the purpose of the RFP. 
   2. State the goal of implementing a fleet management system. 
2. Scope of Work
   1. Describe the specific requirements of the fleet management system, including: 
      1. Vehicle tracking and monitoring 
      2. Maintenance scheduling and management 
      3. Fuel management 
      4. Driver management 
      5. Reporting and analytics capabilities 
      6. Integration with existing systems (if applicable) 
3. Vendor Qualifications
   1. List qualifications and experience required from the vendor, such as: 
      1. Previous experience with similar systems 
      2. References from past clients 
      3. Support and training services 
      4. Compliance with industry standards 
4. Proposal Submission Requirements
   1. Detail what should be included in the proposal, such as: 
      1. Company background and experience 
      2. Detailed technical specifications of the proposed solution 
      3. Implementation plan and timeline 
      4. Pricing structure 
      5. Warranty and support details
         
5. Evaluation Criteria
   1. Outline how proposals will be evaluated, considering factors like: 
      1. Compliance with the scope of work 
      2. Cost-effectiveness
      3. Vendor experience and reliability
      4. Quality of the proposed solution
      5. Support and maintenance offerings 
6. Timeline
   1. Provide the timeline for the RFP process, including: 
      1. RFP release date 
      2. Deadline for questions 
      3. Proposal submission deadline 
      4. Expected decision date 
7. Contact Information
   1. List contact details for where to send proposals and whom to contact with questions. 
8. Additional Requirements
   1. Specify any additional requirements, such as insurance, confidentiality agreements, or compliance with specific regulations. 

By following these guidelines and avoiding common pitfalls, organizations can attract top-quality vendors, streamline the selection process, and realize their project objectives. Both buyers and sellers play pivotal roles in the RFP process. Effective communication, meticulous preparation, and detailed attention are the cornerstones of a successful RFP process.  

Remember, an RFP is more than just a formality—it's a strategic tool essential for finding the ideal partner. Here's to successful RFP writing!  

Download a copy of our free RFP template to get started. If you need advice or suggestions for crafting your request for proposals, our team is happy to help.