An RFP (Request for Proposal) is a formal document a buyer publishes to describe a project or need and invite suppliers to bid. Vendors respond with their approach, timeline, team, references and pricing so the buyer can compare them on the same terms.
Why it matters
RFPs are common in government, enterprise and large IT purchases because they make selection structured and defensible. A clear RFP gets comparable answers and reveals which vendors truly understand the problem. A vague one produces proposals that cannot be compared, and it is a frequent source of scope disputes later.
Example
A typical outline:
- Background and goals
- Scope and technical requirements
- Submission format and deadline
- Evaluation criteria and weighting (for example price 30%, approach 40%, experience 30%)
- Contract and legal terms
The winning bid often becomes the basis for a statement of work and a master services agreement.
Common mistakes
- Describing a solution instead of the problem, which limits creative answers.
- Leaving out evaluation criteria and the budget range.
- Mixing up an RFP with an RFQ (price quote for a defined item) or RFI (request for information).
- Setting a deadline too short for serious vendors to respond.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.