Writing a Request for Proposal
One of the many ways in which contractors find out about what projects are available is the time-tested “Request for Proposal” or RFP. Generally speaking, an RFP requires the respondent to provide both a technical (process recommendations, samples of work products, etc.) and a cost proposal (sometimes embedded in the technical proposal as a budget or sometimes separated out and submitted in a sealed envelope to be opened after selection is made based on technical qualifications).
There are a number of options for those who are considering the solicitation of proposals from contractors – RFQ can stand for “Request for Qualification” for which the respondent provides only background information and perhaps work samples. It can also stand for “Request for Quotation” for which the respondent provides only a dollar amount for the work (usually used for low-bid awards and NOT recommended for interpretive planning projects).
Any of these options (and a variety of others, such as simple purchase orders) can be mixed and matched to a certain extent depending on the needs of the client for a particular project and the policies that govern contracting for the client’s organization or agency. Generally speaking, non-profit organizations have more latitude in how they approach a solicitation than government agencies, but even government agencies have some flexibility depending on the specific region, district, or individual contracting office’s interpretation of the rules. It never hurts to ask your powers that be what alternatives you have in preparing a solicitation, so that you are more likely to get the types of responses you’re looking for.
The best RFPs are simple, clear, and concise. They should include: a brief description of the project and the organization responsible for it; pertinent background information (has a plan already been started by staff? are there mitigating factors such as schedule or budget? how much assistance can be provided by client staff or other resources?); work products (deliverables) expected; instructions for how to put the proposal together (work samples, resumés of key personnel, references, process steps, cost, etc.); contact information for someone who can answer questions; selection process; evaluation criteria; and delivery instructions (date and time due, street address for delivery, etc.).
Resist the temptation to do the project in the RFP. If you have existing information, let the respondents know that, but allow some flexibility in process among respondents – no two planners or companies work exactly the same way and they may be able to save you time and money if they’re allowed to suggest a process rather than having to hold to a rigid construct that you provide. Having said that, if there are specific meetings that you know must be held, or deadlines that can’t be missed, or work products that you absolutely have to have (such as measurable objectives in a logic model construct), be sure to include those in the RFP.
Because NAI staff will not respond to RFPs in a competitive process, a service we can offer is to review your RFP before it hits the street to see if there are any red flags. There is no charge for this – just send your RFP to me (lbrochu@interpnet.com) and give me a day or two to comment on anything that might put off contractors from bidding or that needs clarification. If you send your distribution-ready RFP to us at NAI, we can immediately send it (or the link to it) to all commercial members so that you get better distribution of your solicitation.
Next week, I’ll address how to respond to an RFP for better success in landing projects. If you have specific questions that you’d like answered related to that, please feel free to comment below.







