Request for Proposal (RFP): How to Write One, With a Template and Examples

Quick answer: A request for proposal is a document you send to suppliers asking how they would solve your problem and what it would cost. Each supplier replies with a written proposal. You score the proposals against criteria you set in advance, then pick a winner. RFP stands for request for proposal.

Imagine you need a new roof. You could pick the first roofer who answers the phone. Or you could describe the job to five roofers and ask each one how they’d do it, how long it would take, and what they’d charge.

The second way takes longer. It also gets you a much better roof.

That’s an RFP. This guide shows you how to write one, gives you the actual wording to copy, and — the part most guides skip — explains how to score the replies when they arrive.

What Is a Request for Proposal?

A request for proposal is a document that describes a problem you need solved, and asks suppliers to explain how they would solve it and what they would charge.

If you want the short definition, request for proposal means: here’s our situation, tell us your plan and your price.

The key word is proposal. You are not asking for a price list. You are asking suppliers to think about your problem and propose an approach. Two suppliers can read the same RFP and come back with completely different solutions, and that’s the point — you get to compare approaches, not just numbers.

What is RFP in business?

In everyday business use, “RFP” means the whole process, not just the document:

1. You write the RFP and send it to a shortlist of suppliers
2. They send back written proposals
3. You score those proposals against set criteria
4. You shortlist two or three for presentations
5. You pick one and negotiate the contract

The RFP meaning in business is therefore closer to “a competitive buying process” than “a form.” When someone says “we’re running an RFP,” they mean all five steps.

Why bother with an RFP?

• You see different approaches. The best solution is often one you hadn’t thought of.
• Competition improves the offers. Suppliers sharpen their pricing and their thinking when they know others are bidding.
• It forces you to be clear. You can’t write a good RFP without deciding what you actually want.
• It creates a fair record. Useful for internal approval, and required in most public sector buying.
• It reduces regret. A documented comparison is easier to defend in a year’s time than “we liked them.”

RFP vs RFI vs RFQ vs RFT vs EOI vs RFQual

Six documents, all sent to suppliers, all constantly confused. Here’s the difference.

Document	Full name	What you’re asking	When
RFI	Request for information	“What do you offer?”	First, while you’re still learning the market
EOI	Expression of interest	“Are you interested and able?”	Very early, often for large public projects
RFQual	Request for qualifications	“Prove you’re qualified to bid”	Before inviting proposals, to filter the field
RFP	Request for proposal	“How would you solve this, and for how much?”	Once you know what you need
RFQ	Request for quotation	“What’s your price for exactly this?”	When the specification is fixed
RFT	Request for tender	“Submit a formal bid under these rules”	Formal, often public sector, legally structured

The simplest way to remember the usual order:

RFI = who’s out there → RFP = how would you do it → RFQ = what’s your price.

If you haven’t sent an RFI yet and you don’t know the market well, start there. Our guide to the request for information covers that step, and the two documents work as a pair.

When Should You Use an RFP?

An RFP is worth the effort when:

• The purchase is large or long-term enough to justify weeks of work
• More than one approach could work, and you want to compare them
• You need internal approval and a documented comparison
• The supplier’s method matters, not just their price
• You’re in the public sector, where competitive process is usually required

When to skip it

Situation	Use instead
You know exactly what you want, down to the specification	An RFQ
You don’t know the market yet	An RFI first
The purchase is small	Get two or three quotes informally
You need it urgently	A direct conversation with a trusted supplier
Only one supplier can realistically do it	A direct negotiation, documented

Running an RFP when you’ve already decided who you want is the worst option of all. It wastes weeks of other people’s unpaid work, and suppliers remember. The next time you genuinely need competition, the good ones won’t bid.

How to Structure a Professional Request for Proposal Document?

Twelve sections. Most RFPs that fail do so because one of these is missing.

#	Section	What it does
1	Introduction and summary	Who you are, what you need, in one paragraph
2	Background	Your organisation, your current situation, why you’re buying
3	Objectives	What success looks like, in measurable terms
4	Scope of work	What’s included, and explicitly what isn’t
5	Requirements	What the solution must do, split into must-have and nice-to-have
6	Deliverables	What you expect to receive, and when
7	Timeline	Project dates, and the dates of the RFP process itself
8	Budget	A range, or a statement that you’ll evaluate on value
9	Proposal format	Exactly what you want back, and how long it should be
10	Evaluation criteria	How you’ll score proposals, with weights
11	Terms and conditions	Contract type, payment terms, legal requirements
12	Contact and questions	One named person, a question deadline, and submission details

Two sections most buyers get wrong

Section 10, evaluation criteria. Publish your weights. Telling suppliers that experience is 20% and price is 25% produces far better proposals, because they know what to emphasise. Hiding them produces generic documents and gives you nothing useful to compare.

Section 8, budget. Many buyers refuse to share a budget, believing suppliers will just quote up to it. Some will. But hiding it wastes everyone’s time: you get proposals at £15,000 and £180,000, and both are useless. A range — “we expect this to fall between £40,000 and £60,000” — gets you comparable bids and lets suppliers who can’t work within it withdraw early.

Keep the whole document to 8–15 pages. A 60-page RFP signals a difficult customer, and the best suppliers quietly decline.

What Is the Request for Proposal RFP Process, Step by Step?

Nine steps, from blank page to signed contract.

Step 1: Define the problem internally

Before you write anything, agree inside your own organisation what you’re buying and why. Write the problem in one paragraph. If your team can’t agree on that paragraph, you’re not ready.

Step 2: Assemble the evaluation team

Decide who will score the proposals now, not later. Three to five people is usually right. Include someone who’ll use the solution daily, not just managers.

Step 3: Set your evaluation criteria and weights

Agree these before you write the RFP, and certainly before any proposals arrive. The criteria shape the questions you ask.

Step 4: Write the RFP

Use the twelve sections above. Have one person write it and one person review it for anything ambiguous.

Step 5: Build the supplier list

Four to eight suppliers is the sweet spot. Fewer and you don’t get real competition. More and your evaluation team drowns, and each supplier’s odds get so low the strong ones stop bothering.

Step 6: Issue it, and handle questions fairly

Send it to everyone at the same time. When one supplier asks a question, send the answer to all of them, without naming who asked. This is good practice everywhere and a legal requirement in most public procurement.

Step 7: Receive and score the proposals

Score independently first, then meet. The method is below.

Step 8: Shortlist, present, decide

Invite two or three to present. Ask each the same core questions so you can compare. Then decide, and write down why.

Step 9: Tell everyone, then negotiate

Tell the winner and the losers. Offer brief feedback to those who lost — it costs you twenty minutes and buys you a stronger field next time. Then negotiate the contract.

What Does Sample RFP Wording Look Like?

Most guides describe the sections and leave you with a blank page. Here’s the actual wording. The example is a mid-size insurance company buying help to implement a new CRM.

Section 1 — introduction

Brayford Insurance Services is seeking proposals from suppliers to implement a new customer relationship management (CRM) system across our sales and service teams.

We are a UK insurance broker with 240 employees across four offices. This RFP covers the implementation, data migration, training and first-year support of a CRM platform we have already selected.

Proposals are due by 5pm on 14 November 2026.

Section 3 — objectives

By the end of this project we expect to:

1. Have all 180 sales and service staff working in one CRM, with no parallel spreadsheets in daily use
2. Reduce the time to produce a renewal quote from an average of 22 minutes to under 10
3. Migrate 14 years of client records with no loss of regulatory audit trail
4. Be fully live before our renewal peak begins on 1 April 2027

Section 4 — scope

In scope: configuration of the selected platform, migration of client and policy data from our two existing systems, integration with our quoting engine, training for all 180 users, and 12 months of post-launch support.

Out of scope: the CRM licence itself (purchased separately), hardware, our website, and any change to our quoting engine’s internal logic.

Section 5 — requirements

Must have

• Experience implementing this platform for a UK regulated financial services firm
• A named project manager available for the full duration
• Data migration approach that preserves our FCA audit trail

Nice to have

• Experience with our specific quoting engine
• Offices within two hours of Leeds for on-site training

Section 9 — proposal format

Please submit a PDF of no more than 20 pages, excluding CVs and references, covering:

1. Your understanding of our situation (max 2 pages)
2. Your proposed approach and method (max 6 pages)
3. Timeline with key milestones (max 2 pages)
4. Team, with named roles (max 3 pages)
5. Two relevant case studies (max 3 pages)
6. Full costs, broken down by phase (max 2 pages)
7. Assumptions and anything you’d want to change about this brief (max 2 pages)

Please do not send general marketing material.

Section 10 — evaluation criteria

Proposals will be scored out of 5 against the following, by a panel of four:

Criterion	Weight
Understanding of our requirements	25%
Relevant experience	20%
Proposed approach	20%
Total cost	20%
Timeline and availability	15%

Notice section 9, item 7. Asking suppliers what they’d change about your brief is the most useful question in any RFP. The good ones will tell you something you got wrong, and that answer alone often justifies the whole exercise.

What Goes in the RFP Template?

Copy this and fill it in.

REQUEST FOR PROPOSAL

Organisation:
RFP reference:                  Date issued:
Questions due:                  Answers published:
Proposals due:                  Decision expected:
Contact name and email:

1. INTRODUCTION
   What we are buying, in one paragraph.

2. BACKGROUND
   About our organisation:
   Our current situation:
   Why we are buying now:

3. OBJECTIVES
   By the end of this project we expect to:
   1.
   2.
   3.

4. SCOPE OF WORK
   In scope:
   Out of scope:

5. REQUIREMENTS
   Must have:
   Nice to have:

6. DELIVERABLES
   | Deliverable | Expected by |

7. TIMELINE
   | Stage | Date |
   | RFP issued |  |
   | Questions due |  |
   | Proposals due |  |
   | Shortlist notified |  |
   | Presentations |  |
   | Decision |  |
   | Project start |  |

8. BUDGET
   Expected range:
   Or: how we will assess value for money.

9. PROPOSAL FORMAT
   Maximum length:              File format:
   Required sections:
   What we do NOT want:
   Submit to:

10. EVALUATION CRITERIA
    | Criterion | Weight |
    Scoring scale:
    Panel size:

11. TERMS AND CONDITIONS
    Contract type:               Payment terms:
    Insurance / certification required:
    Confidentiality:
    Costs of responding are the supplier's own.
    We reserve the right not to award.

12. CONTACT AND QUESTIONS
    Named contact:
    Question deadline:
    All questions and answers shared with all bidders.

How Many Vendors, and How Long Should You Give Them?

Decision	Typical range	Why
Suppliers invited	4 to 8	Real competition without drowning your panel
Response window	3 to 6 weeks	A proposal is days of work, not hours
Question deadline	1 to 2 weeks before the due date	Time to answer everyone fairly
Page limit	15 to 25 pages	Forces clarity, keeps scoring fair
Shortlist for presentations	2 to 3	More than that and the day becomes a blur

Scale it to the purchase. A £20,000 project doesn’t need six weeks and eight bidders.

One rule worth holding to: if you extend the deadline for one supplier, extend it for everyone. Quiet extensions are how fair processes quietly stop being fair.

How to Evaluate Vendors After Issuing a Request for Proposal

This is where most RFP processes fall apart. People read four proposals, form an impression, and argue. A scoring method prevents that.

Step 1: Lock the weights before the proposals arrive

Write them down and date them. Once you’ve read a persuasive proposal, it’s human nature to adjust the weights in its favour without noticing.

Step 2: Score independently

Each panel member scores every proposal alone, 1 to 5 per criterion, before anyone compares notes. Group scoring produces the loudest person’s opinion.

Step 3: Multiply by the weights

Here’s a worked example. Four proposals for the CRM implementation above, scored 1–5, weights out of 100, maximum score 500.

Supplier	Understanding (25)	Experience (20)	Approach (20)	Cost (20)	Timeline (15)	Total	%
Supplier A	5	4	4	3	4	405	81%
Supplier B	4	5	4	3	3	385	77%
Supplier C	3	3	3	5	4	355	71%
Supplier D	4	2	3	4	5	355	71%

Step 4: Meet and discuss the gaps

Don’t discuss the totals first. Discuss the places where panel members scored the same proposal very differently — one person gave Supplier B a 5 for experience, another gave a 2. That gap usually means someone spotted something, or someone misread something. Both are worth knowing.

Step 5: Handle ties properly

Supplier C and Supplier D tied on 355. Agree your tie-break rule in advance. The usual one: whoever scored higher on the heaviest criterion. Here that’s “understanding of our requirements,” where D scored 4 and C scored 3. So D ranks above C.

Step 6: Sanity-check the result

Supplier C was cheapest and still finished joint third. That’s the weights doing their job — cost was 20% of the decision, not 100%.

But do pause before you accept any result. Ask the panel one question: is there anything we know about these suppliers that the scoring didn’t capture? If someone says “their named project manager leaves in March,” that belongs in the decision, recorded as a reason.

Step 7: Write down why

One paragraph, naming the winner, the score, and the main reasons. In eight months, when someone asks why you chose them, this is the only thing that will answer it.

What Does the RFP Timeline Look Like?

Stage	Typical duration
Define the need internally	1 to 2 weeks
Write the RFP	1 to 2 weeks
Supplier response window	3 to 6 weeks
Scoring and shortlisting	1 to 2 weeks
Presentations	1 week
Decision and notification	1 week
Contract negotiation	2 to 6 weeks
Total	about 10 to 20 weeks

Plan backwards from the date you need the work to start. Most RFP processes run late because somebody assumed the whole thing would take a month.

Best Practices for Writing a Request for Proposal

Ten things that separate RFPs that work from RFPs that waste everyone’s time.

1. Describe the problem, not your preferred solution. If you specify the answer, you’ll never hear a better one.
2. Publish your evaluation weights. Suppliers write better proposals when they know what matters.
3. Give a budget range. It saves weeks and filters out the wrong bidders early.
4. Separate must-have from nice-to-have. A list of 90 equally-weighted requirements tells suppliers nothing.
5. Set a page limit. It forces clarity on them and fairness in your scoring.
6. Ask what they’d change about your brief. The most valuable question you can include.
7. Name one contact. Questions routed to a committee get slow, inconsistent answers.
8. Share every question and answer with everyone. Fairness is also practical — it stops you repeating yourself.
9. Give a realistic deadline. Three weeks minimum for anything substantial.
10. Tell everyone the outcome. Including the ones who lost, with a sentence of why.

Why Don’t Good Vendors Respond to Your RFP?

If you issue an RFP to eight suppliers and three reply, something in the document put the others off. Usually one of these:

What you did	What they concluded
Gave a two-week deadline	“They don’t understand how long this takes”
Listed 120 requirements, all mandatory	“Nobody can meet all of these. This is a tick-box exercise”
Refused to give any budget	“We could spend five days on this and be wildly out”
Wrote criteria that match one supplier exactly	“The incumbent has already won this”
Asked for free sample work	“They want consultancy without paying for it”
Gave no named contact	“We can’t ask anything, so we’d be guessing”
Didn’t say how many suppliers were invited	“This might be a field of twenty”

A proposal costs a supplier real money — often several days of senior time. They are making a bet. Make the bet look reasonable and good suppliers will take it.

Should You Respond to an RFP? The Bid/No-Bid Test

If you’re on the receiving end, the most valuable skill is deciding which RFPs to ignore. Chasing everything means thin, rushed proposals and a low win rate.

Score each RFP out of 10. Two points for each yes:

1. Can we genuinely meet the must-have requirements? Not “probably” — genuinely.
2. Do we know this buyer, or have we spoken to them before this RFP arrived?
3. Is the timeline realistic for us to do a good job?
4. Is the budget, or the likely budget, worth winning?
5. Is there any sign this isn’t pre-decided? Open questions, a real question period, criteria that aren’t suspiciously specific.

8–10: bid, and put real effort in. 6: bid only if you have capacity, and reuse heavily. 4 or below: decline politely, and say you’d welcome the next one.

Declining well is worth doing. A short, courteous “not this time, but please keep us on your list” keeps you in the running for the one you’d actually win.

How Do You Write a Proposal That Wins?

Six things that consistently separate winning proposals from the rest.

• Answer in their order, using their headings. Evaluators are scoring across documents. Anything they have to hunt for loses marks.
• Lead with their problem, not your company history. The first page should prove you understood the brief.
• Be specific about the team. Name people. “A senior consultant will be assigned” scores badly against “Priya M., who led the same migration at a comparable firm.”
• Show the method, not just the outcome. Buyers are choosing an approach, not a promise.
• Price it clearly and break it down. Hidden or lumped pricing reads as something to hide.
• Say what you’d change. If the brief has a flaw, naming it respectfully shows expertise. This is the single most under-used move in proposal writing.

Our project proposal guide goes deeper on the response side.

What’s Different About Public Sector RFPs?

Public buying is legally structured, and the usual advice bends:

• Opportunities are published, not emailed. If you’re not registered on the right portal, you never see them.
• The process is fixed. Deadlines, question periods and scoring methods are set in advance and can’t be adjusted informally.
• Fairness is a legal duty, not just good manners. Every bidder gets identical information.
• Scoring is usually disclosed in detail, and sometimes published afterwards.
• Losing bidders can challenge the award. That’s why the written record matters so much.
• Standstill periods may apply between the decision and the contract.

If you’re buying in the public sector, follow your organisation’s procurement rules over anything in this guide. If you’re selling into it, register on the portals your target buyers use and read each notice carefully — the formal requirements are where most bids get disqualified before anyone reads the content.

Where to Find Software That Automates Request for Proposal Processes

Different tools handle different parts. Nothing does all of it well.

Job	What to look for	Type of tool
Writing the RFP	Templates, shared editing, version history	Document tools and AI writing assistants
Distributing it and collecting bids	One portal, timestamped submissions, Q&A log	E-sourcing / procurement platforms
Scoring proposals	Weighted criteria, independent scoring, auto totals	E-sourcing platforms, or a locked spreadsheet
Responding to RFPs (vendor side)	A content library of reusable answers	RFP response software
Public sector opportunities	Alerts matched to your categories	Government procurement portals

Four features worth more than the brand:

• An audit trail nobody can edit. Essential if a decision is ever challenged.
• Separate scoring per panel member, so people can’t see each other’s marks before they submit.
• A proper Q&A log that distributes answers to all bidders at once.
• Export. You’ll need the scoring record outside the tool eventually.

A caution: if you run one or two RFPs a year, you don’t need a platform. A shared folder, a clear email thread and a scoring spreadsheet work fine. Buy software when the volume justifies it, not before.

What Are the 8 Most Common RFP Mistakes?

1. Running an RFP when you’ve already chosen. Suppliers can tell, and they remember.
2. Specifying the solution instead of the problem. You rule out the better approach before you hear it.
3. Hiding the budget. You get incomparable proposals and waste weeks.
4. Too many suppliers. Eight good proposals is more than most panels can score properly.
5. Changing the criteria after reading the bids. It’s the fastest way to a decision nobody can defend.
6. No named contact or question period. Suppliers guess, and guessing produces bad proposals.
7. Deciding on price alone. If cost were the only criterion, you should have sent an RFQ.
8. Never telling the losers. It costs nothing to do and a lot to skip.

How Does Writegenic AI Fit In?

An RFP is a long, structured document with twelve predictable sections. So is the proposal that answers it. That structure is exactly what AI drafting handles well.

The Writegenic AI RFP tool drafts the full document from a description of what you need, so you start from a filled outline instead of a blank page.

You can also use Writegenic AI to:

• Turn a rough list of needs into clear must-have and nice-to-have requirements
• Write the evaluation criteria and the scoring descriptions for each level
• Draft the supplier invitation email and the question-and-answer bulletins
• Write the “thanks, but not this time” notes to unsuccessful bidders
• Draft a proposal response if you’re the supplier, using the project proposal writer
• Summarise four long proposals into a comparison table for your panel

When you’re earlier in the process, the request for information guide covers the step before this one.

Draft with the tool, keep the judgement. AI can write a clean, complete RFP in minutes. It cannot decide your budget, choose which requirements are genuinely non-negotiable, or weigh a supplier’s reputation against their price. Those are the decisions the whole process exists to make, and they stay yours.

Try Writegenic AI free

Frequently Asked Questions

Related reading:

• Request for Information (RFI): Template + Examples
• Project Proposal Writer: Create Proposals That Win
• Stakeholder Engagement Plan: Steps, Template + Example
• Project Charter Templates With Real Examples
• Contingency Plan in Project Management: Template + Example