Learning projects can fail even before they get started if your request for proposal (RFP) is not developed well, and the bigger the ticket price for the system, the greater the need for a clear RFP. Developing a sound RFP is not rocket science, but it does require a systematic understanding of your problem, a clear articulation of your needs and requirements, and a well-defined set of steps that result in a document that clearly reflects your needs, assumptions, constraints, and criteria. It also requires a good business writing style and some internal political savvy.

This session will cover what to include and what to leave out, what to do before the RFP is written and what to do once you send it out, and how to decide which vendors should receive the RFP and how to select the right vendor to win the work. Participants will learn to distinguish between a request for information (RFI), request for proposal (RFP), and statement of work (SOW).

Handouts