What is an RFP in procurement, and when does procurement use one?

What does RFP mean in procurement?

In procurement, an RFP (request for proposal) is one of the formal ways to buy through competition. The procurement team uses it when suppliers must propose how they will meet a need, and the winner is chosen on several criteria, such as quality, risk and price, published before anyone answers.

Outside procurement, people often see the RFP as a document. Inside procurement, it is first a decision: of all the ways to buy this need, which one fits? A city that needs a new building permit system cannot write a specification precise enough to compare prices alone. Each software vendor will propose a different product, plan and team. The procurement team therefore chooses an RFP, publishes the evaluation criteria and their weights, and lets the vendors compete on the whole proposal.

The document itself, what it contains and how proposals are scored, is explained in the RFP guide. This page looks at the RFP from the procurement side: when it is the right method, where it fits in the procurement cycle, who owns it, and which rules apply in the public and private sectors.

When does procurement choose an RFP over other buying methods?

Procurement chooses an RFP when two things are true: the buyer cannot fully specify the solution in advance, and the award will weigh quality or risk as well as price. When the need is fully specified and price decides, a quotation or a sealed bid is faster and easier to defend. The table shows the usual methods and when each one fits.

US federal rules turn this choice into a test. Under FAR 6.401, contracting officers must use sealed bids when four conditions are met: there is time to run the bid, the award will be made on price and price-related factors, no discussions with bidders are needed, and more than one bid is expected. When these conditions are not met, they may ask for competitive proposals, which is the RFP route. Organisations that spend US federal grants follow the same logic under 2 CFR 200.320: sealed bids need a complete specification, at least two willing bidders and an award made mainly on price, and they are preferred for construction; proposals are used “when conditions are not appropriate for using sealed bids”.

The FAR also describes a best value continuum (FAR 15.101). When the requirement is clear and the risk of poor performance is low, price may play the main role. The less definite the requirement, the more development work it needs or the greater the performance risk, the more technical quality and past performance count. In practice, a procurement team asks four questions before it chooses:

1. Does an existing contract or framework cover the need? If yes, order from it or run a mini-competition among its suppliers.
2. Can the need be specified in full, down to quantities and standards? If yes, a quotation or a sealed bid is usually enough.
3. Will suppliers propose different solutions, teams or plans? If yes, price alone cannot decide, and an RFP is the method.
4. Is there enough time and market knowledge to run it? If the market is unknown, send a request for information first; if time is short, check whether the rules allow a faster route.

The request for quotation is explained in the RFQ guide, and the choice of route before an RFP, including frameworks, in the RFP process guide. A side-by-side comparison of the RFI, RFP and RFQ is in preparation.

Where does the RFP sit in the procurement cycle?

The RFP sits in the middle of the procurement cycle, between sourcing and the contract. Before it, procurement analyses the spend, decides the sourcing approach for the category and studies the market. After it, the award becomes a contract, and the contract feeds the orders and payments. A good RFP is written with both ends in mind.

Upstream, the RFP is the go-to-market step of strategic sourcing. The sourcing plan for the category, for example from category management, says whether to buy at all, how many suppliers to keep and for how long. The RFP then turns that plan into a competition. Many organisations run it in an e-sourcing tool, so that every supplier gets the same documents and answers.

Downstream, most of the RFP becomes the contract. In US federal practice this is literal: the RFP is drafted in the uniform contract format, and at award the contracting officer removes only Part IV, which holds the representations, the instructions to offerors and the evaluation factors. FAR 15.204-1(b) says these parts are not physically included in the contract but are kept in the contract file. The rest of the RFP, completed by the winning offer, is the contract. Private buyers work in the same spirit: what the RFP fixes is what the buyer will later order, receive and pay against.

For example, an RFP for facilities services asks for a monthly fixed fee per building plus hourly rates for extra work. If the contract keeps that structure, the order can carry one line per building, and an invoice for extra hours can be checked against the agreed rate. The next steps are covered in contract management, the purchase order guide and the three-way match guide.

Who owns an RFP: procurement or the business?

Procurement owns the RFP as a process: the method, the rules, the timetable, the contact with suppliers and the fairness of the competition. The business owns the need: why it buys, the budget and the requirements. Neither can run a good RFP alone. Procurement without the business writes requirements nobody needs; the business without procurement tends to favour the supplier it already knows.

The City of Portland’s guide for suppliers shows a typical public split. A city bureau decides what it needs and its budget, then writes the RFP together with the city’s Procurement Services. Procurement Services publishes the RFP and checks which proposals are responsive. An evaluation committee scores the proposals against the criteria listed in the RFP, and the city then issues a notice of intent to award to the top-scoring proposer. UK central government uses a similar split in its commercial standard, GovS 008: a senior business owner owns the justification for the contract, while the senior officer accountable for commercial activity owns the commercial strategy and signs contracts.

Inside a company, the same roles appear under other names: a category manager or buyer runs the RFP, the budget holder signs off the need, legal reviews the contract terms, and finance confirms the budget and the price structure. A full table of roles at each step is in the RFP process guide.

How do public and private procurement rules for RFPs differ?

Public buyers run RFPs under procurement law; private companies run them under their own procurement policy. The steps look alike, but the law fixes for public buyers several things a company may choose freely: who may answer, whether the buyer may negotiate, and how losing bidders can challenge the award.

Names differ too. US public buyers speak of RFPs and invitations for bids. In the UK the same document is usually an invitation to tender, run under the open or the competitive flexible procedure of the Procurement Act 2023. EU law speaks of procurement documents and tenders. Minimum response times by jurisdiction are listed in the RFP guide, and the value thresholds that trigger formal methods in the procurement policy guide.

When should procurement not run an RFP?

An RFP costs weeks of work for the buyer and for every supplier that answers. Procurement teams avoid it when another route gives a sound decision with less effort. Five cases come up often:

• The need is fully specified and only price will differ: a request for quotation or a sealed bid decides faster and on clearer grounds.
• An existing contract or framework agreement already covers the need: an order or a mini-competition among its suppliers avoids repeating the competition.
• The value is below the limit at which the policy or the law asks for formal competition: a few quotes, or one reasonable price, are enough.
• Only one supplier can meet the need, or an emergency allows no delay: a single-source award with a written reason and the right approval. US grant rules list these cases in 2 CFR 200.320(c).
• The buyer does not yet know what the market can offer: a request for information first, so that the later RFP asks for something suppliers can deliver.

The opposite mistake is also common. A team sends an RFQ for a complex service, receives prices for very different scopes, and cannot compare them. When suppliers will answer in different ways, the RFP’s structured proposal and published criteria are what make the answers comparable.