The RFP has been king of procurement for too long. It’s time for a coup.
After helping many jurisdictions improve their processes for writing and evaluating Requests for Proposals, I began to have a sneaking suspicion — that even cutting months off RFPs was really putting lipstick on the pig of a fundamentally ineffective tool. I wrote down all those ideas into an article I called “Death to the RFP,” published last month by Contract Management magazine.
The following is an excerpt from that article. You can download the pdf of the full article here, or view the original on Contract Management’s website.
When my family moved into our house, we had a bizarre problem: The prior owners added a room on the back of the house, and every time there was a rainstorm, water would seep out from the doorframe. I don’t know anything about roofs, so we had to hire a professional.
Think for a moment: What would you do if you needed a roofer?
Our process was something like this:
Compile a list of roofers, partly by asking neighbors for recommendations and partly by looking online for well-reviewed local contractors.
Call the top four to five roofers. Describe the problem for five minutes, get their initial thoughts on what’s happening, confirm their interest and availability to do the work, and get a sense of whether they would be good to work with.
Invite two to three roofers to look at the roof, do a deeper diagnosis, and provide estimates. Pay attention to where they agree and where they disagree.
Pick the roofer that seems to provide the best value—some combination of competence and low price.
Finally, work with that chosen roofer to make a more specific plan and timeline. (For example, we had no choice but to fix some flashing around a skylight to resolve the leak. We also found some other shingles that are wearing out, but determined that we could reasonably wait a couple of years to replace them.)
That’s what we did. It was annoying, but we found a decent roofer, and within a couple weeks, the repair was made. This year’s rainstorms have not resulted in any weeping doorways. Most people follow a process similar to this when they need to buy professional services: find a list of qualified vendors, identify ways to narrow them down, obtain estimates from the top few, and then make a choice. However, this is not how the government—any government, at least in the United States—buys professional services. The government uses formal competition to procure goods and services above a specific dollar threshold. The most common such procurement method is a request for proposal—the RFP. If you have spent much of your career working in the public sector, you have perhaps become inured to how bizarre the typical RFP process is to everyone else. Using the RFP process, choosing a roofer might look like this:
First, you begin by describing the tasks you want the roofer to do. You don’t know anything about roofing, or even what’s wrong, but you do your best.
You decide how long it will take and how much you’re willing to pay. For example, you want this done in a weekend, and you will only pay $1,000.
You don’t call roofers. Instead, you create a 20-page document, post it on the web, and wait for roofers to contact you.
If roofers contact you, you refuse to speak to them. Instead, you will only accept questions from them in writing.
Some roofers ask questions about the current condition of your roof. The roofers aren’t allowed to inspect your roof—you just clamber up there, take a look, and answer the questions two weeks later, in writing, as best you can.
Prospective roofers must spend 10 unpaid hours detailing in writing the way that they will fix your roof (which, again, they have not yet inspected). They must also send you resumes for every member of their team, a budget in an Excel spreadsheet that you created, and provide three signed letters of reference from prior roofing clients.
You created a scoring rubric before all this, and you will only choose the roofer that scores best in your predetermined rubric. But you have a set of social concerns beyond your roof, so you also require each prospective roofer to document what city they are incorporated in; whether the company uses recycled materials; the race, gender, sexual orientation, and veteran status of the owner of the firm and the roofers who will come to your house; and what laws their local government has passed about abortion.
It takes two months to create your request, one month for roofers to respond, and another two months for you to evaluate the prospective roofers. (You should probably go buy a bucket in the meantime.) However, you can’t make the decision yourself; you must convene a panel of your neighbors to decide for you.
If all goes well, six months later, the selected roofer (who still hasn’t seen your roof) will then be expected to complete the required tasks within the timeframe and budget you originally agreed upon. You hope that the actual problem with your roof won’t take longer than a weekend to fix.

That’s how our government buys professional services. The result is not only a massive expenditure of time and effort, but also a lot of leaky roofs and water damage (mostly metaphorical, but sometimes literal). I’ve been exposed to every side of government solicitations: When I worked in the San Francisco Controller’s Office, I helped write and evaluate RFPs for services the city was buying. Now, as a seller to the government, I not only respond to dozens of RFPs every year; I also help public agencies streamline their procurement processes. Here’s the truth: Everyone hates RFPs. The RFP mechanism may work fine for well-defined and low-complexity purchasing, but they’re poorly suited to the massively complicated construction, engineering, information technology (IT), and professional services work they’re mostly used for. RFPs take massive amounts of staff and vendor time. They often do a poor job of identifying the best vendor—or just fail outright. In my experience, public servants hate issuing them and bend over backward to avoid them. Vendors hate responding to them. I think it’s time to end the reign of the RFP.

Read the rest: download the pdf of the full article here, or view the original on Contract Management’s website.



Comments